Choosing a software development company is one of the few decisions that is hard to undo. Six months in, switching means paying a second team to understand what the first one built. So it is worth spending real time on the choice, and spending it on the questions that predict how the project will go rather than on the ones that are easy to compare.
This guide covers what to settle before you start looking, what to check, the questions to ask on the first call, and the warning signs to take seriously.
Settle three things before you start looking
You will get far better answers from every company you talk to if you can tell them:
- The problem, in business terms. What costs you time or money today, and what changes when it is fixed. Not a feature list.
- What already exists. The systems the new software must connect to or replace, and the data that has to move.
- What “done” looks like for the first release. The smallest version that would be worth using.
You do not need a specification. A good company will help turn these three into a scope. A company that skips them and goes straight to a price has not understood the problem yet.
What to check
Relevant work, not just a portfolio
A portfolio shows that a company can make things look good. What you want to know is whether they have built something with the same hard parts as yours: the same kind of integration, the same scale of data, the same regulatory weight. Ask for a case study that describes the problem, the constraints and what changed afterwards, not just screenshots.
Who actually does the work
This is the most important question, and the one most often answered vaguely. Ask who will lead the project, who will write the code, who reviews it, and whether the people you meet during the sale are the people who build. A team that changes after the contract is signed is one of the most common causes of a troubled project.
How they handle scope and cost
Ask what you get in writing before any work starts. You should see a scope, a quote and the assumptions behind it. Ask how changes are handled once the project is running, because there will be changes.
How they test
Ask what runs before a change reaches users. Automated tests that run against every change are what keep a product working as it grows. If testing is described as a phase at the end, expect the end to slip.
What happens after launch
Ask who supports the software once it is live, how fast they respond, and how a handover works if you later bring the work in-house. The answer tells you whether they plan to stay or plan to leave.
The question that predicts the most is “who will actually write and review the code?” Ask it on the first call, and ask it again before you sign.
Questions to ask on the first call
Use these, and compare the answers rather than the prices:
- Who will lead the project, and who will do the work day to day?
- What will we have in writing before work starts?
- How do you test changes before they reach our users?
- Who owns the source code, and are there any license fees after launch?
- How do we see progress against budget and schedule?
- What happens when we want to change the scope?
- What does support look like after launch, and what does a handover include?
- Can you show us work with problems like ours, and what changed for that client?
A good answer is specific. “It depends” is fine if it is followed by what it depends on.
Choosing an engagement model
How you work with a company matters as much as which company you choose. Most fall into three shapes:
- A fixed-scope project. A defined result for a fixed quote. Best when the work can be scoped clearly.
- A dedicated team. A team that works on your product over time, with priorities that change as you learn.
- Engineers who join your team. People who work inside your existing process and tools. This is staff augmentation, and it suits companies that already have engineering leadership.
None is better in general. The right one depends on how clear the scope is and how much engineering leadership you already have.
Warning signs
Take these seriously, even when the price is attractive:
- No written scope before work starts.
- Vague answers about who does the work, or a different team after signing.
- Testing described as a phase rather than something that runs on every change.
- Unclear code ownership, or license fees that continue after launch.
- A quote that arrives before they understand the problem.
- No plan for after launch.
How we answer these questions
We think every buyer should hold their shortlist to the questions above, including us. Our answers are on our how we work page: a written scope and a fixed quote before work starts, a dedicated project manager reporting on budget and schedule, automated tests on every change, source code that belongs to the client with no per-user license fees, and the same team staying on after launch. If you want to put the questions to us directly, our custom software development team is happy to answer them on a first call.
