Choosing a Software Development Partner: Questions That Reveal the Truth

Choosing a development partner is difficult because the things that matter most are hardest to assess before you commit. Everyone demonstrates well. Everyone has a portfolio. The differences appear in month eight.

These questions surface those differences early.

"Walk me through a project that went wrong."

The most revealing question you can ask. A partner worth having will describe a real one — what was misjudged, what it cost, and what they changed afterwards. A partner claiming everything has always gone smoothly is either inexperienced or not being straight with you.

"Who will actually work on this?"

Many firms send senior people to sales meetings and staff the work with juniors. Ask who will write the code, how long they have been with the company, and whether you can meet them. Ask what happens if that person leaves mid-project.

"What is not included in this quotation?"

A good partner has a clear answer: data migration beyond a stated volume, third-party licence costs, changes to agreed scope, training beyond a stated number of sessions. A vague answer here becomes an uncomfortable conversation in month four.

"Show me a system you built four years ago that is still running."

Anyone can build something that works on launch day. A system still in daily use years later, still being enhanced, tells you about code quality, documentation and the client relationship all at once.

"What happens if we want to work with someone else?"

The answer should be straightforward: you own the code, here is the repository, here is the documentation, here is the handover process. Any hesitation, or any suggestion that this would be complicated, is telling you something important.

"What would you talk us out of?"

Ask them to look at your requirement and identify what is not worth building. A partner who says everything you have asked for is a great idea is optimising for the size of the invoice, not for your outcome.

Warning signs

• A quotation produced before anyone has understood your process in detail.
• Reluctance to put scope in writing.
• No named support arrangement after go-live.
• Payment terms heavily weighted to the front.
• Claiming deep expertise in every industry.

Good signs

• They ask more questions than they answer in the first meeting.
• They want to visit your premises before quoting.
• They propose a staged rollout rather than a single go-live.
• They are specific about what they do not do.
• They introduce you to a client in a similar business without being asked.

Start small if you can

Where the requirement allows, commission a small, well-defined first piece before committing to the full programme. Two months of actually working together tells you more than any number of reference calls.