How to choose a software development company: 15 questions
How do you choose a software development company?
Send the same brief to a short list of companies, ask each of them the same 15 questions, and compare the answers before you compare the prices. The questions cover six things: who will actually do the work, how they scope and price it, how you will see progress, who owns the code, what happens after launch, and what they can show you. Good answers are specific and can be put in writing; vague ones are the warning.
We are a software development company ourselves, so where our own way of working is a fair example of a good answer, we say so. The questions work just as well on us as on anyone else.
Start by sending everyone the same brief
Answers are only comparable when everyone is answering the same question. Write a one- or two-page brief covering the problem, the users, the three to five things the first version must do, a budget range and a timeline, and send it to each company on your list. Our guide to writing a software project brief has a template. Then ask the questions below on a call, and ask for the important answers in writing.
Who will actually do the work?
The company you meet is not always the team that builds. These three questions find out who does.
- 1. Who exactly will build our software, and can we meet them before we sign? A good answer names people and their roles, and puts the lead developer on a call with you. Red flag: 'we will assign the team after signing'.
- 2. Will the people we talk to now be the people building it? Ask whether any of the work is subcontracted, and to whom. A good answer is a plain yes, or a plain list of who else is involved. At VA Org the two founders write the code, so the people you talk to are the people building it. Red flag: a senior person who sells the project and is never seen again.
- 3. How many of our working hours overlap with yours, and how quickly do you reply? A good answer is a number. We keep at least four hours of overlap with a client's working day, run everything else in writing so nobody waits overnight, and reply to a new inquiry within one working day. Red flag: 'we are flexible', with nothing specific behind it.
How do they scope and price the work?
A price only means something next to a written description of what it buys.
- 4. Will we get a written scope with a price and a date before we sign? A good answer is yes: a plan in plain language that says what will be built first, what it costs and when it ships. We write one before anyone signs anything, and if we don't believe it can be done for that price and date, we say so. Red flag: a firm price after one call, with no document behind it.
- 5. How will you price it, and what happens when the scope changes? Fixed price, time and materials and a dedicated team suit different projects, and a good company explains which fits yours and why; our comparison of the three pricing models covers the trade-offs. A good answer on change describes a process: small changes absorbed early, bigger ones re-scoped in writing before work on them starts. Red flag: 'no problem, we are agile', with no word on what changes cost.
- 6. What is not included in the price? Ask about design, testing, deployment, app store submission, hosting, third-party services and fixes after launch. A good answer is a clear list. Red flag: a quote that looks cheap because half the work is missing from it. To see whether a quote is in a sensible range, try our app development cost calculator.
How will you see progress?
The cheapest time to find a misunderstanding is the week it happens. These questions tell you how soon you will see one.
- 7. When will we first see working software? A good answer is a date in the first week or two, on a real address you can open. We put the first slice on a live URL in week one. Red flag: weeks of 'setup' before anything you can click, or one big reveal at the end.
- 8. How often will we see progress, and in what form? A good answer is a regular demo of working software, not a status report. Our work moves in two-week slices with a clickable demo every Friday, so changing your mind early stays cheap. Red flag: progress reported as a percentage complete.
- 9. Will we have access to the task board, the code and a test version while the work happens? A good answer is yes, from the first week. Red flag: a vendor who shows you only what they choose, when they choose.
Who owns the code, and what does a handover include?
Ask these early, while everyone is on good terms. They matter most on the day the relationship ends.
- 10. Where will the code live, and who will own it? A good answer is that it lives in your repository and your cloud account from the first commit, and the contract says it is yours. That is how we work: we are contributors, not landlords. Red flag: code kept in the vendor's account 'until the final payment'. Our article on who owns the code explains ownership, licences and handover in more detail.
- 11. If we part ways, what will the handover include? A good answer is a list: the repository, access to the infrastructure, the credentials, documentation and a walkthrough for your own team. Red flag: surprise at the question, or a handover fee nobody mentioned before.
What happens after launch?
Real users find problems that no test did. Agree how they will be handled before you need it.
- 12. What happens in the weeks after launch? A good answer is a defined period of fixes at no extra cost. Our fixed-scope builds include 30 days of fixes once real users are in the product. Red flag: every fix after launch is a new invoice from the first day.
- 13. What does ongoing support cover, and what does it cost? A good answer names what is included, such as monitoring, backups, security patches and who you call, and gives a monthly price. Ours is a care plan from $900 a month with a named engineer on call, or a clean handover to your team if you would rather run it yourselves. Red flag: a support contract you must sign before you can get your code.
What proof can they show?
A portfolio shows what a company can design. Running software and people you can call show what it can deliver.
- 14. Can we see software you have built that is running today? A good answer is a live product you can open and use, ideally close to what you need. We build our own products too: MobiSIM, a travel eSIM store in 12 languages, is one we designed and built. Red flag: screenshots and mock-ups, with nothing you can click.
- 15. Can we speak to someone you have built for? A good answer is an introduction to a client whose project looks like yours. When you talk to them, ask what went wrong and how it was handled; every project has something. Red flag: nobody you can call.
Red flags that should end the conversation
One weak answer can be an honest gap. Several of these together are a pattern:
- A firm price before anyone has written down what it buys.
- No working software until the end of the project.
- Code, servers or app store accounts kept in the vendor's name.
- The people who sell the project are not the people who build it, and you cannot meet those who will.
- No clear answer to what is not included.
- Pressure to sign before you have seen a written scope.
- Every question answered with 'it depends', and nothing after it.
Compare the answers before the prices
Put the answers side by side, one column per company, and read them before you look at the totals. A slightly higher quote with a written scope, working software in the first weeks and code in your own account is often the cheaper project in the end, because the risks it removes are the expensive ones. If you would like to put us through the same questions, here is how we run custom software development.
How many software development companies should I talk to?
Enough to compare and few enough to take each one seriously; three to five is usually about right. Send them all the same brief and ask the same questions, so the differences you see are real. With more than that, the comparison tends to collapse into price alone.
Should I choose the cheapest quote?
Only if it describes the same work as the others. Quotes differ most in what they leave out, such as testing, deployment, fixes after launch and ownership of the code, so compare written scopes, not totals. A cheap quote with no scope behind it can turn into the most expensive project.
Is it risky to hire a software company in another country?
Distance matters less than how the work is run. Ask about overlapping hours, how decisions are written down, how often you see working software and whether the code lives in your accounts. We work remotely from Kosovo, keep at least four hours of overlap with each client's working day and run everything else in writing.
What should I send a software development company first?
A short brief: what the software should do, who uses it and what happens today instead, with a budget range and a timeline. That is enough for a serious company to ask good questions and come back with a written scope. If you would like our answers to these 15 questions for your project, send us your brief: we reply within one working day.