Choosing who builds your software is a bigger decision than choosing what they build. The code will outlive the project, and so will the relationship. Here is what to look for in a software development partner, what a good proposal contains, and the warning signs worth taking seriously.

Start with what you are buying

A price for a build is only part of the cost. You are also choosing who understands your business, who makes technology decisions on your behalf, and who answers the phone when something breaks in a year's time.

So compare partners on more than the quote. The questions below are the ones that separate a supplier from a partner.

Do they start by understanding your business?

A partner who quotes after one phone call is guessing. A sound one wants to understand your objectives, your users and your existing systems first, usually in a structured discovery phase.

Look at what that step produces. You should receive something written down, such as who the software is for, a prioritised list of features and a recommendation for what it should be built on. If you could not hand that document to another supplier and have them price the work, it is a sales tool, not a plan.

Who owns what you pay for?

Ask this before you sign, not after. You need a clear answer on:

A partner confident in the quality of their work has no reason to make leaving difficult.

How do they choose technology?

The honest answer is on evidence: a track record and long-term support, weighed against your needs for scalability, security, hosting and budget. The poor answer is whatever is fashionable, or whatever the team happens to prefer.

Ask why a technology was chosen for you, and what happens if the company behind it changes direction. You are not looking for a technical lecture, only for a reason you can follow.

Will they build in stages?

Large projects that arrive in one leap carry the most risk. If you are replacing existing tools, a better plan replaces the most painful one first, moves its data across, and runs old and new side by side where needed before anything is switched off. Your team gets value early and the business keeps running.

Ask how data from your existing systems will be migrated and checked with you. A vague answer here is a real risk.

What do they say about AI?

Many developers now use AI tooling to build faster. That is not a problem in itself. What matters is what happens to the output. Ask who reviews and tests the code, and whether AI features are proposed because they save real time or because they sound good in a pitch.

What happens after launch?

Software is never finished. It needs security updates, upgrades, monitoring and new features, and someone has to be responsible for them. We cover this in more detail in who looks after bespoke software once it has launched.

Ask what support is on offer, and how you will be kept informed. Some clients want regular calls; others prefer a shared task board, or Slack or Teams. A good partner fits how you already work.

Warning signs

A hypothetical comparison

Imagine you ask two companies to propose a replacement for a set of tools your business has outgrown.

The first sends a single figure after one call, with a feature list copied from your email and nothing about support. The second asks to run a workshop with the people who use the tools daily, proposes replacing one tool first, explains why it recommends a particular technology, and says in writing that you keep the planning documents.

The second may not be the cheaper quote. It is the one that shows how the project will actually be run, which is what you are paying for.

Questions to ask every candidate

The last question is the most telling. A partner who can tell you what to leave out is thinking about your business, not just their invoice.