How to Choose a Software Development Partner

Fixed price, team churn, code ownership, exit costs: the trade-offs that decide your project after the contract is signed.

Maysan Engineering Team · · 4 min read

Xin

Choosing a software partner usually turns into a procurement exercise: three proposals, a portfolio check, a call about timelines, a decision on price. The costs that actually decide whether the project works — what a change request costs, whether the seniors in the pitch are the ones writing the code, what it takes to leave — are not in any of those documents. Founders, ops leads and CTOs at 20-200 person companies typically find this out in month four, when the first invoice has been paid and the scope has already moved.

How to choose a software development partner: the four trade-offs that surface later

You are not buying code; you are choosing which risks your company will carry for the next twelve months. Almost every later argument traces back to four things that were never compared during selection:

  • Scope risk — who pays when a requirement changes mid-build.
  • Attention risk — whether the senior people you met are actually staffed on your project.
  • Ownership risk — whose cloud account, repository and data the system lives in.
  • Exit risk — what it costs in time and money to move to another team.

A proposal that names all four, in writing, is worth more than one that is 15% cheaper and silent on them. The silence is not dishonest; nobody puts the failure modes in a sales document unless the buyer asks.

Fixed price vs time and materials: who carries the scope risk

Fixed price transfers scope risk to the vendor, but only for scope that was written down precisely — which, for a first version of most B2B portals, it rarely is. A fixed bid is genuinely appropriate for a defined integration, a migration, or a tightly specified dashboard; web platform builds with unclear workflows are the wrong fit. Watch the change-request rate instead of the headline number. In our experience, a fixed-price engagement quoted at ₹18 lakh can land near ₹22-24 lakh once six mid-project change requests are billed at ₹2,500-4,000 an hour, which is more than the time-and-materials estimate would have cost. Ask each vendor how changes are priced, and whether discovery is included or billed separately.

The team in the pitch is not always the team that writes the code

Ask for the named tech lead and the percentage of their week your project gets — and get it in the contract, not over a call. Senior-heavy pitches with junior-heavy delivery is the most common disappointment we hear about, and it is easy to test: request CVs of the two engineers who will do most of the work, then ask what else those two are staffed on. Check time-zone overlap too. Three to four overlapping hours with your team is workable; zero overlap means every clarifying question costs a day, and a two-week sprint loses a quarter of its clock to waiting.

Code ownership, infrastructure and the cost of leaving

Insist that the repository, cloud account, CI pipeline and DNS sit in your company's name from day one, with the vendor given access rather than ownership. This matters legally as well as practically: under the DPDP Act, if you handle personal data of Indian users, your company is the data fiduciary and the vendor is a processor — so the contract needs a processing clause, a deletion commitment and a working handover. Price the exit before you sign: two to three weeks of paid transition, a runbook, and an architecture document you own. If hosting lives in a vendor's account, moving it is a project in itself; keeping it in your own is one of the cheapest forms of insurance available to a small team.

What to check before you sign

Two reference calls with clients whose projects finished — not the ones still in progress — will tell you more than any portfolio. Ask those references three things: how change requests were priced, what happened when a deadline slipped, and whether they got the team that was pitched. Then run a paid two-week discovery with the final two vendors and compare the outputs, not the sales decks. A second opinion on the design before code is written is cheap; the same review at month five is not, which is why we usually suggest an architecture review at this stage. Finally, read the termination clause out loud. If you cannot exit in under a month, you have not hired a partner.

Where to start

Pick the vendor on how they handle the second change request, not the first proposal. A practical route: pay two firms for a two-week discovery, compare the scope documents line by line, and keep the infrastructure in your own name either way. Maysan Labs runs these engagements for Indian SMBs and mid-market B2B teams alongside its own products, and is as comfortable being the second opinion as the builder.

Buying software or a website?

Twelve questions to ask any vendor before you sign: price, your data, fit for an Indian business and support.

Get the free checklist

Written by Maysan Engineering Team at Maysan Labs, a software studio in Gurgaon, India. Follow us on LinkedIn