A software company.Nothing more,nothing less.
A software studio founded by engineers. Not an agency, not a “solution partner”. We ship production software. Narrow focus, high standards, long view.
Why we started.
Founded in Ankara in 2021. The team's shared observation: most large software projects end up as marketing copy, technical debt, or both. We gathered because there was another way.
Today we're a small team shipping software at enterprise scale. A deliberately narrow service range: web, mobile, AI, cloud, enterprise integration, custom consulting. All delivered under one team. Six vendors means friction; one means accountability.
Focus is a deliberate choice. Instead of wider, deeper; instead of trends, decisions that hold up three years from now. Close to 30 projects shipped this way in five years. A quiet difference our clients notice.
Five years,in the open.
A small team compounding one project at a time. No sudden pivots, no funded expansion.
- 2021
Founding
Neophran Software Technologies established in Ankara. Mandate from day one: ship software that auditors and operators can both live with.
- 2022
First enterprise engagement
Signed our first regulated-sector build. Architecture decision records and audit-first documentation become the house style.
- 2023
Cross-border delivery
Began shipping for clients across three time zones. Async-first operating model formalised in writing.
- 2024
AI alongside web, mobile, cloud
AI engagements grow past demo stage. Evals, observability and cost tracking join the standard delivery toolkit.
- 2026
Where we are now
Around 30 delivered projects. Same team, same discipline, same phone number.
Five principles.Not culture slogans. Working rules.
- 01
Start with the problem, not the technology.
We don't treat every item in the modern stack as a solution. The right tool is shaped by the problem.
- 02
Beyond the demo.
Working in a demo isn't success. Still working three years in is.
- 03
One team, one accountability.
If you need six vendors, you have a system broken into six pieces.
- 04
Be transparent.
Timeline, cost, risk, limits. All visible. No surprises.
- 05
Long-term.
“Deliver and leave” isn't in our vocabulary. We're here after launch, too.
Four shapes of partnership.
One engineering discipline, different commercial shapes. The right one depends on what you need to decide next.
- 01
Project-based
Fixed scope, fixed price
- Right fit when
- You know what to build and need it built cleanly.
- How it starts
- Discovery sprint (1-2 weeks) → scoped proposal → build.
- Typical shape
- Three to nine month builds.
- 02
Monthly retainer
Dedicated team, capacity commitment
- Right fit when
- You have a roadmap and want a partner who ships every sprint.
- How it starts
- Onboarding week, pick up the existing backlog, deliver in month one.
- Typical shape
- Six-month minimum, renewed quarterly.
- 03
Fractional engineering leadership
Senior engineer or CTO, 1-3 days per week
- Right fit when
- You have an in-house team but need leadership weight: architecture, hiring, due diligence.
- How it starts
- Intro call → scope letter → weekly cadence.
- Typical shape
- Three-month commitment, extended by choice.
- 04
Discovery sprint
Short, structured, outcome-only
- Right fit when
- You are unsure what to build, or need a second opinion on a plan.
- How it starts
- Single-week engagement, fixed price.
- Typical shape
- One week. Deliverable: architecture brief and decision memo.
Work we decline.
A senior team stays senior by saying no to the right jobs. Here is where we decline, so the yes carries weight.
- 01
Body-shop staff augmentation
We sell engineering outcomes, not a seat-rate. If the ask is 'drop three developers in our Slack for a quarter', we are not the right fit.
- 02
One-sprint emergencies without discovery
Two-week firefights produce regret-ware. We decline scope that skips a proper brief, unless it is a real incident, which we respond to under a separate protocol.
- 03
Black-box delivery
Weekly demos, shared board, readable commits. If the engagement requires an opaque binary handed over at the end, we pass.
- 04
Adopting a tool because it's trending
We will not reach for a framework or model because the investor deck demands it. If the right answer is boring, we say so.
- 05
Claiming compliance we don't hold
We will not put an ISO 27001 logo on a deck to win an RFP. If a regulated build needs a certificate, we say so upfront and scope the path with you.
Senior-first.You talk to the architect directly.
We're a small team of engineers. Instead of a gallery of headshots we prefer to share the collective profile. When your project starts, you meet the people you'll actually work with.
- Average experience
- 8+ years
- Working languages
- Turkish · English
- Working model
- Senior-first · Low hierarchy
- Location
- Ankara · Remote-friendly
Architect and tech lead are in direct contact with you. No project-coordinator middle layer.
The questions that come upin every intro call.
If yours isn't here, ask it. We prefer specific questions over a generic pitch.
Headquartered in Ankara; delivery is remote-first across CET/EET and compatible time zones. On-site visits for kickoff, workshops and launch weeks are routine.
What backs the discipline.
Instead of chasing certifications, we invest in practices that hold up under real customer audits. The items below are part of the team's daily routine.
KVKK
Compliant
GDPR
Compliant
OWASP Top 10
Built into delivery
Dependency scanning
Active in CI
Penetration testing
On request
Security incident response
Defined process
Let's talk aboutyour project.
First call: 30 minutes, free, under NDA. 48-hour response. Information never shared.