How to choose a software development company, as one client did after fifteen interviews
One client interviewed fifteen vendors and chose on things no portfolio shows. That is how to choose a software development company: test how each vendor works on your problem, what its quote assumes, and who will do the work.

One client interviewed fifteen vendors before choosing
In 2021 a platform for media producers needed a new prototype designed for its launch. The platform is built around discovering stories and adapting them. It had already tried WordPress and other vendors, and had not got the quality it wanted.
So it shortlisted fifteen companies on Upwork and other portals, and interviewed them. We were one of the fifteen, and the one it hired.
The client told Clutch what decided it: price, communication, design skill and focused deliverables. It found those out in the interviews, and the portfolios had not shown them. Once the work started, our designer worked inside their team, with daily and weekly stand-ups in Asana.
Afterwards the client praised the transparent pricing and the honest feedback. It did not praise the portfolio that had got us onto the list.
We sell software development. So this is advice on how to choose a software development company, written by one of the companies you might choose. Apply the tests below to us before anyone else. Our custom software development services page sets out how we scope the work, who does it and what you own at the end. The evidence for the tests is independent research, and the project is told from the client’s own review on Clutch, with the client left unnamed.
It was a design project, and it is one client. We start from it because a larger purchase poses the same problem. You have a long list of companies that all look qualified, and you have to choose on things a portfolio does not show.
Why fifteen companies can all look qualified
Fifteen companies can all look qualified because the usual checklist asks for things every serious vendor has. Its columns are portfolio, reviews, technology, communication and price. Every company you would seriously consider has shipped something impressive and has four or five stars somewhere. They all use the stack you asked about, and their sales teams all reply within a day.
Most advice on how to choose a software development company is that checklist. A test that every company passes does not decide anything.
We checked what the ranking advice adds to it. On October 10, 2026 we took the nine pages Google ranked for “how to choose a software development company” and counted what each one tells a buyer to do. Six would open: five guides and one forum thread. The three that would not are two Reddit threads and a Quora question.
Of the five guides, three tell you to look at case studies or past projects. None tells you to check reviews or references. Two suggest a trial project or a pilot before a larger commitment, and neither says it should be paid.
None tells you to find out, by name, who will build your system. One does warn against a company that will not let you speak to the team assigned to your project. All five are written by companies that sell software development, as this one is.
Research on how clients choose software providers is blunter. Magne Jørgensen at the Simula Research Laboratory showed that providers differ widely in productivity and quality. He also showed that the traditional ways of evaluating them, such as CVs and evaluations by reference clients, fail to separate the competent from the incompetent.
That matches what our client did. Fifteen portfolios did not decide anything. The interviews did, because an interview is where a vendor’s communication shows, and whether it will tell you what it thinks.
Decide what you are buying before the first call
Decide whether you are buying a project, a team or extra engineers, because the right vendor for one is often the wrong vendor for the other two. Software companies sell all three under the same name, and a vendor of any of the three may call itself a development partner. If you compare a vendor of one with a vendor of another, each answer looks reasonable on its own terms and the shortlist still goes wrong. Our client’s need was specific: one prototype design, for a launch.
(opens full size in a new tab)A project with a fixed scope fits when the system can be described before it is built and you want certainty on the price and the date. It asks for someone on your side who can decide the scope. It also asks for the discipline to price changes rather than absorb them.
A dedicated team fits when the work is continuous and you want a unit that owns a workstream and reports on outcomes. It asks for someone close enough to steer it, and outcomes clear enough to report against.
Engineers who join your own team fit when your leads already have the direction and need more hands. It asks for leads with the time to direct the work day to day.
Say too whether the work starts from existing software: a system to extend, replace or connect to. A company that builds new products well may not want to work inside someone else’s code. If it does, its first stage should include reading that code before it quotes, and application modernization is a different purchase from a new build.
Each one fails in its own way when its conditions are missing. Staff augmentation vs dedicated teams sets out how each fails, and how to hire a dedicated software development team covers that model in detail.
This is also the moment to check that you need a vendor at all. You do not need one if a product already does the job. Configuring software you buy is usually faster and cheaper than building it, and our client had tried WordPress before it drew up a shortlist. If that is your real question, start with build vs buy.
Two other cases call for waiting. If nobody on your side can own the scope, no vendor can succeed, because someone has to be authorized to decide. If the process you want to automate is still changing, building it now fixes the wrong shape in code.
Three tests for choosing a software development company
Judge every vendor on three things: how it works on your problem, what its quote assumes, and who will do the work. None of them can be read off a website, which is why they separate vendors the checklist cannot. Each one appears in our client’s decision in a smaller form.
(opens full size in a new tab)How they work on your problem
The strongest evidence of how a vendor will work on your system is how it works on your system. Jørgensen’s 2016 paper argues for this: ask several providers to produce a sample piece of work, and judge the work. He calls it trialsourcing.
A later field experiment by Jørgensen and Jon Grov tested the idea and found a limit. Fifty-seven freelance developers with good ratings were invited to a two-hour trial task, and 36 passed it. The trial may have kept out developers without the skills. Among those who passed, performance on the trial largely did not predict performance on the project. The experiment involved freelancers and small projects, not companies and large systems, so read it as a direction and not as a rule.
The lesson is to make the trial look like the real work. A two-hour coding exercise tests a skill. A short paid stage on your own problem tests more, for example a discovery that maps your integrations and your data and ends in a scoped plan. It shows how the vendor thinks, what it asks, how it writes things down and how it handles what it does not know. You will be living with those habits for the next year.
Our client’s version of this test was the interview, which suits a design project. On a larger system the interview becomes a paid first stage. The feedback the client praised becomes the vendor telling you, in writing, what in your plan it would change.
Be wary of a vendor that agrees with every requirement. It usually means the scope has not been challenged yet, so the arguments come later. Ask it what it would change or leave out, and why.
What the quote assumes
A quote tells you how a vendor understood your system, and how it intends to behave when that understanding proves wrong. Jørgensen’s review of estimation research found underestimation concentrated in price-competitive bidding. He names the result the winner’s curse. When a buyer chooses mainly on price, the winner is disproportionately the bidder who was most optimistic about the work.
So read a quote for what it assumes as well as for its total. Look for what is excluded, which integrations were priced and how, and how much contingency there is. Look for what happens to the price when the scope changes. The questions that explain the gap between two quotes are written for this.
Two kinds of quote need a direct question. The first is a firm price from a vendor that asked nothing about your data or integrations. It has priced a picture of your system that may not match it, so ask what it assumed about your data and about each integration.
The second is the lowest quote by a wide margin. That often means optimism, a narrower scope, or a plan to recover the gap in change requests. Ask what is excluded, and how changes are priced.
The pricing model tells you something too. A fixed price only makes sense once the scope is written down properly. Time and materials suits a brief that is still moving, and needs a visible backlog and regular demos to stop it drifting. Many good engagements use both: a fixed price for discovery, then time and materials for the build once the scope is clear.
Our client’s phrase for this test was “focused deliverables”. A quote that says exactly what you will get is easier to trust than one that promises everything. Transparent pricing is one of the two things the client praised afterwards.
Who does the work
The people in the sales meeting are rarely the people who build the system. Ask who will, by name and seniority, and how long they stay on it.
This matters more than it sounds. A Microsoft study of Windows Vista looked at measures of who owned the work, such as how many separate groups edited a component and whether one group owned most of it. Those measures predicted post-release failures better than any measure of the code itself.
A proposal with no named team usually means the people will be whoever is free when you sign. A vendor that cannot tell you who will work on your system, or that rotates people between clients, is offering you fragmented ownership. Meet the lead engineer before you sign, and ask what happens if that person leaves.
In our client’s project the designer worked inside the client’s own team, with daily and weekly stand-ups. The client knew who was doing the work.
What references and reviews are good for
References and reviews are good for one thing the three tests do not cover: what went wrong on past projects, and how the vendor dealt with it. Given the research above, they are weak evidence of competence. A reference call tells you whether a client was satisfied, and reference clients are chosen by the vendor.
So ask the reference what went wrong and how the vendor handled it. That answer separates vendors better than the satisfaction does. A track record is worth what you can check of it, and case studies with no one you can call are proof that cannot be checked. Ask to speak to a client whose project resembles yours.
Read reviews the same way. On a platform such as Clutch, skip the star rating and read what each reviewer would have liked done differently. That part tells you what working with the vendor is like.
We read our own this way. Clients have left us 15 reviews on Clutch, and on October 9, 2026 we counted the criticisms in them. Six reviews include a criticism and nine give none. None of the six is about the code or the technology.
Three are about process. One asks for a more structured content check at key milestones. One asks for more frequent progress updates with more explanation of design decisions. One asks for more rounds of early sketches. Two more are about attention to small details, and one says we lacked a bit of creativity.
Fifteen reviews is a small sample, and they are ours. They are still why we would read any vendor’s criticism for what it says about process. Process is the part of a vendor you deal with every week.
Is there a best software development company?
There is no single best software development company. There is the best one for your system, and the three tests are how you find it. People ask which company is best for software development, and plenty of pages answer with a list of ten logos. A ranking someone else made measured someone else’s project.
What does exist is the best company for one particular system, budget and team on your side. It does good work on your own problem in a paid first stage. Its quote says what it assumed. You have met its named people and expect them to stay. Only you can build that list.
Directories and review platforms are still useful for building the long list. Our client built its list of fifteen on Upwork and other portals. Filter by projects like yours, read the criticism, and then let the three tests do the choosing.
Where the company is based, and what that changes
Location changes two things: the working hours you share with the team, and the hourly rate. It matters less than it used to and more than some vendors admit.
The first change is the working day. It sets how many hours overlap with yours, how quickly a question gets an answer, and whether people can meet when it matters. Ask how many hours each day the team is available in your time zone, and how decisions get made while you are asleep. Our nearshore and offshore comparison works out the overlap by region.
Location also moves the rate, and here there is published data. Clutch’s software development pricing guide, updated in September 2026, puts the average rate to hire a software development company at 25 to 49 US dollars an hour, and its table by country runs from that band up to 100 to 149. The custom software cost guide sets out the countries.
Those figures are averages across projects reviewed on Clutch, which skew toward smaller work. They are not our prices. A lower rate buys cheaper hours and says nothing about the outcome, so the three tests still decide. A cheap vendor that fails the third test costs more than an expensive one that passes it.
We are based in Ahmedabad, India, so we have an obvious view. The useful test is the same for any location. Check that the people doing the work can be reached when you need them, and that you can meet them before you sign.
Eight questions to put to every vendor in writing
These eight questions cover the people, the scope, the price and the exit. Ask them in writing, put the same ones to every company on the shortlist and read the answers side by side. Count a vague answer as an answer.
The sixth question is about the exit. When the code, the accounts or the hosting are held by the vendor, leaving later is slow and expensive.
- Who will work on our system, and for how long? Names, seniority and time on the project, and what happens when someone leaves.
- What would you need to know before you could quote? A vendor that asks about data, integrations and users has understood the work. One that asks only about features has not.
- What have you assumed is out of scope? In writing, as a list. It is the fastest way to compare two quotes fairly.
- How are changes priced? The answer tells you whether change requests are an exception or the business model.
- Can we start with a paid first stage on our problem? A discovery or a first release that produces something you keep, whoever builds the rest.
- Whose accounts is it built on, and what do we receive at the end? The code repository, the cloud hosting, the app stores and the domains should be yours from the first day.
- Can we speak to a client with a similar project? Then ask that client what went wrong and how it was handled.
- What happens after launch? Support, warranty, the handover of code and documentation, and who keeps the system running.
Most vendors answer the first two easily. They start to differ on scope, changes and accounts, so compare those answers before you compare any totals.
If you have a shortlist and are sending these questions out, send them to us too, with the brief. The call is 30 minutes with the people who would build your system. They will answer the eight questions and tell you whether we are the right fit, including when the answer is that we are not.
Questions people ask about how to choose a software development company
How do I choose a software development company?
Decide first whether you need a project, a dedicated team or engineers who join yours. Then judge each vendor on how it works on your actual problem, on how it prices and what its quote assumes, and on who will actually do the work. Put the same written questions to every vendor and compare the answers side by side.
Which company is best for software development?
There is no single best company, only the best one for your system, your budget and your team. It is the vendor that does good work on your real problem in a paid first stage, prices openly with its assumptions written down, and names the people who will build it. Use directories and reviews for the long list, and those three tests for the choice.
What questions should I ask a software development company?
Who will work on the system and for how long, what they need to know before quoting, what is out of scope, how changes are priced, whether you can start with a paid first stage, whose accounts it is built on, which client you can speak to, and what happens after launch. The full list explains what each answer tells you.
Should I choose the cheapest software development company?
Not on price alone. Research on software estimation found underestimation concentrated in price-competitive bidding, so the lowest quote is the one most likely to have underestimated the work. Find out why it is lowest before you trust it.
Should I ask vendors for a trial project?
A paid first stage on your real problem is the strongest evidence you can get. Keep it close to the real work: a field experiment found that a short, generic test kept out weak developers but did not predict how well the rest performed.
Who should own the code when a vendor builds my software?
You should, along with the repository, the hosting and any store accounts, from the first day. Check that the contract says so and that the accounts are created in your organization’s name.



