Choosing a development partner is a high-stakes decision made with limited information. Portfolios all look polished, every agency promises quality, and by the time you discover the truth you're months and lakhs in. The fix is to ask questions whose answers are hard to fake.
Here are the ten we believe every business should ask — including of us.
1. Who exactly will work on my project?
Agencies often sell you their senior people and staff your project with juniors. Ask for the actual names and experience of the team assigned to you, and whether the work is done in-house or subcontracted.
2. Can I talk to a past client?
Not a testimonial on a website — a phone call. A confident partner will connect you with a client whose project resembled yours. Ask that client what went wrong during the project and how the team handled it; every project has a moment like that.
3. How will I see progress?
The answer you want: working software on a regular cadence — weekly or fortnightly demos of real features, not slide decks and status reports. Long silences between kickoff and delivery are where projects die.
4. What happens when scope changes?
It will change. Ask how changes are priced, documented, and approved. Vague answers here become billing disputes later.
5. Who owns the code?
You should — fully, including the repositories, from day one. Walk away from any arrangement where the source code is held hostage to the relationship.
6. What does 'done' include?
Testing? Deployment? Documentation? Training? A support window? Get the definition of done in writing before comparing prices — a lower quote that excludes all of these is not a lower price.
7. How do you handle security and my data?
Listen for specifics: access controls, encrypted credentials, separated environments, and a willingness to sign an NDA without friction.
8. What happens after launch?
Software needs monitoring, updates, and fixes for as long as it runs. Ask what the support terms are, what response times look like, and what ongoing maintenance costs. "We'll figure it out later" is not a plan.
9. What would you cut first if the budget shrank?
This question reveals whether they think in business outcomes. A good partner will protect the features that earn money or save time, and defer the polish. A poor one will protect the parts that are easiest to bill.
10. Why shouldn't I build this at all?
The most valuable answer in this list. A trustworthy partner will sometimes tell you an off-the-shelf tool covers your need, or that your scope should be halved for a first version. If every idea you bring is met with an enthusiastic quote, be careful.
Ask all ten, and the difference between partners becomes obvious quickly. If you'd like to see how we answer them, we're happy to be interviewed.