Hiring a software agency is a decision most business owners make once or twice, with real money and very little to compare. The proposals arrive looking alike. Everyone is experienced, everyone is fast, everyone cares about quality. By the third call it is hard to remember who said what.
You do not need to be technical to choose well. You need to know what to look at, what to ask, and which answers should make you pause. This guide covers all three, from the point of view of the person paying for the work.
Write down the problem before you talk to anyone
Most poor agency choices start before the first call. Without a clear brief, every proposal answers a slightly different question, and you end up comparing prices for different projects. Half an hour spent on a short note saves weeks of confusion later.
What your brief should cover
- The problem you want solved, in one or two sentences.
- Who will use the software, and roughly how many people.
- What success looks like three months after launch.
- The budget range you are comfortable with.
- Any date that cannot move, such as a launch or a busy season.
You do not need technical detail. A good agency will turn your note into a technical plan. How they respond to it is your first piece of evidence: the best ones ask questions about it before they talk about price.
Five things worth weighing
Proof
Ask to see software that is live and in use, not only designs or screenshots. A named client, a working link and a case study that explains what changed for the business tell you far more than a page of logos. If you can, ask to speak to one of those clients for ten minutes.
Process
Ask what happens between signing and launch. You want to hear about a short discovery stage where the requirements are tested, a written scope, regular demos you can click through yourself, and a clear point where you approve the work. An agency that cannot describe its process will improvise one on your project.
Price
There are two common ways to charge. Hourly billing is flexible but leaves the final cost open. A fixed price for an agreed scope gives you a number you can plan around, as long as the scope is written down properly. Whichever you choose, ask how changes are priced, because changes are where most budgets grow.
Ownership
At the end of the project you should own the source code, the design files, the hosting account, the domain and the database. Ask for this in the contract, and ask for access to the code repository from the first week. Software you cannot take elsewhere keeps you tied to one supplier for as long as it runs.
People
Find out who will actually build your product and whether you can talk to them directly. Some agencies sell with a senior team and deliver with a different one. Short lines of communication mean fewer misunderstandings and faster answers when something needs a decision.
Questions to ask on the first call
These questions are simple, and the answers are revealing. Write down what each agency says so you can compare them side by side afterwards.
- What would you need to know before giving us a price?
- Can you show us something similar you built that is live today?
- Who will work on our project, and will we speak to them directly?
- What does the first month look like, week by week?
- How do you handle a change to the scope halfway through?
- Who owns the code, the hosting and the accounts when you finish?
- What happens after launch if something breaks?
- What would you advise us not to build?
The last question is the most useful. An agency that can tell you what to leave out is thinking about your budget and your users.
Good signs and warning signs
One warning sign is not a reason to walk away. A small agency may not have many named clients yet, and a new one may still be refining how it works. What matters is the pattern. If several of the signs on the right appear together, take that seriously.
Comparing quotes that look nothing alike
Quotes are hard to compare because each agency includes different things. One price covers design, testing and the first month of support. Another covers development only and adds the rest later. Before comparing numbers, check every quote against the same list.
- Is design included, or only development?
- Is testing on real phones and browsers included?
- Who sets up the hosting, and who pays for it?
- How many rounds of changes are included?
- What support is included after launch, and for how long?
- When are payments due, and what is each one tied to?
Once the quotes cover the same work, the real differences become clear. The cheapest quote is often the one that left the most out.
What a good first month looks like
The first few weeks show you whether you chose well. By the end of the first month with a capable agency you should have a written scope you have approved, a working link where you can see progress, a short demo every week or two, and access to the code from day one. If any of those are missing, raise it early, while changing direction is still cheap.
This is how we run projects at CoreFinity Tech. Every engagement starts with a written scope and a fixed price, the client owns the code and the accounts from the start, and progress is shown on a live link you can open at any time. Our IELTS Counsel case study shows what that looks like on a real project.