Insights

How to choose a software development company in Turkey

Most vendor comparisons stop at a day rate and a logo wall. The questions below are the ones that decide whether the software reaches production and whether you can run it afterwards.

What should you ask before a proposal?

Ask who writes the scope and what it is based on. A proposal written before anyone has named the workflow, the users, and the systems it touches is a guess with a number on it. At Reorigin an inquiry is reviewed, a discovery conversation is held, and only then is a written proposal and delivery roadmap sent. The sequence is on how we work.

Ask what the first release contains. The useful answer is a production slice: one path a real user can complete, with authentication, the data model, a deploy, and monitoring. A demo that cannot replace the manual process is not a first release.

Questions to ask a software vendor, and what a usable answer looks like
QuestionA usable answerA warning sign
Who writes the scope?A written scope after a discovery conversationA fixed price before the workflow is named
Who does the work?Named owners of architecture and qualityA rotating pool of unnamed developers
Who owns the code?IP terms written into the agreementIP discussed only verbally
Where is it hosted?A region chosen to match your contractsRegion decided after launch
What is the first release?A production slice a real user completesA demo with no deploy or monitoring
What is handed over?Deploy, monitoring, and operating notesNo documentation in the scope
How was the price reached?A band first, a proposal after discoveryOne number with no assumptions listed

Who actually does the work?

Staff augmentation and scoped product work are different purchases. In the first you rent hours and manage them yourself. In the second the vendor owns architecture and delivery quality and you buy an outcome. Neither is wrong, but a proposal should say which one it is.

Reorigin sells scoped engagements, not unnamed hours. The studio is founder-led, in Şişli, Istanbul, and the people who own architecture are the people you speak with. See leadership.

Who owns the code, and where does it run?

Intellectual property belongs in the signed agreement, not in a sales call. The default Reorigin discusses is that you own the product code delivered for your engagement and Reorigin keeps its pre-existing tools and libraries. The signed agreement is the source of truth.

Hosting is a deployment fact with legal weight. If your contract says EU personal data stays in the EU, the region has to be chosen before the first deploy, and the same applies to backups and logs. We deploy to Cloudflare, AWS, and GCP. The engineering side of that is in KVKK and GDPR for SaaS built in Turkey.

How should the price be reached?

A planning band tells you the order of magnitude. A quote tells you what you will pay. They are not the same document. Reorigin publishes planning bands: a discovery-led custom software MVP at $2,000–$40,000 in 1 week and a production SaaS MVP at $1,000–$30,000 in 1–3 weeks. The figure you can sign is the proposal after discovery. What sits inside each band is in what a custom software MVP costs in Turkey.

What happens after launch?

Ask what you receive on the last day. Handover should include the production deploy, monitoring, and documentation your own team can operate. Ongoing product engineering is a separate scope. If a vendor cannot describe the handover, the product will depend on that vendor indefinitely.

How do you check what a vendor says?

Ask for something you can open. A live product with a public address tells you more than a slide of logos, because you can use it. Ours is RecycleOrigin, at recycleorigin.com. We name one product because it is the one we can describe in full, and we do not publish client logos, a headcount, or a savings percentage.

Then ask who you will speak with after signing. If the people in the sales call are not the people who own the architecture, ask to meet the ones who are. Ask how a change in scope is handled, and ask to see the handover notes from an earlier engagement with the client’s details removed.

What does Turkish law add to the contract?

One rule surprises foreign buyers. Under Article 52 of Turkey’s Law No. 5846, a transfer of economic rights in a work must be in writing and must list each right individually. A single sentence assigning all rights may not hold. The clauses to settle, including this one, are in the software development contract checklist.

The proposal should also say whether you are buying people or an outcome. The difference, and how to spot it in a document, is in staff augmentation vs scoped project delivery.

Read custom software development for the workflow band and contact to start a discovery conversation.

Sources and further reading

FAQ

What should I ask a software development company in Turkey?

Ask who writes the scope, who does the work, who owns the code, where it is hosted, what the first release contains, what handover includes, and how the price was reached. Ask for each answer in writing.

Is a lower day rate the right way to compare vendors?

No. A day rate says nothing about scope, ownership, or handover. Compare what the first production release contains and what you can operate yourself afterwards.

Does Reorigin sell staff augmentation?

No. Reorigin sells scoped product engagements from discovery to production. It does not rent unnamed developers by the hour.

Who owns the code when Reorigin builds it?

IP terms are written into the proposal. The default discussed is that you own the product code delivered for your engagement and Reorigin keeps its pre-existing tools. The signed agreement is the source of truth.