Choosing a software agency is one of the most consequential decisions a business leader can make. Get it right and you have a system that grows with your business. Get it wrong and you have a half-finished product, a drained budget, and months of lost time.
Most problems do not start with the code. They start with the conversation before the project kicks off. The right questions, asked early, tell you almost everything you need to know.
1. Do you ask about my process before talking about technology?
An agency that leads with technology - "we'll build this in React, we use microservices, our stack is..." - is not listening to your problem. They are fitting your business into their existing template.
A good agency will spend the first meeting understanding how your business actually works: the steps, the people involved, the pain points, the exceptions. The technology conversation comes second. If it comes first, that is a warning sign.
2. Who will actually build my project?
Many agencies win business with senior people and deliver it with junior ones. The person presenting in the sales meeting may never touch your project.
Ask specifically: who will be the lead developer? Can I meet them? Will the same team be on the project from start to finish? The answer matters more than the agency's name.
3. What does the handover look like?
The project does not end at launch. You will need to update the software, fix bugs, train new staff, and eventually extend it. What happens after delivery?
Ask about documentation. Ask whether your internal team will be trained. Ask whether the agency expects to remain involved or whether they are handing over a finished product. If the answer is vague, the handover will be too.
4. Will I own the code?
This seems obvious, but it is frequently misunderstood. Some agencies retain ownership of the codebase and license it back to you. Others use proprietary platforms that create permanent dependency.
You should own the source code outright. Ask for it in writing. If there is any hesitation or qualifications, treat it as a red flag.
5. How do you handle scope changes?
Every project encounters scope changes. What matters is how the agency manages them. Is there a formal change order process? How are additional costs calculated? How long does it take to get a response on a scope question?
An agency that cannot describe a clear process for this is likely to create billing surprises later. An agency that says "we are flexible, we'll figure it out" is not giving you a reassuring answer - they are deferring a problem.
6. What happens if the project runs over time or budget?
It is an uncomfortable question to ask, but a professional agency will have a direct answer. Do they charge for overruns? Do they absorb them? What are the circumstances under which the original estimate changes?
How an agency answers this question tells you more about their working relationship style than almost anything else. Vague answers mean vague accountability.
7. Can I speak to a client you have worked with on a similar project?
A portfolio is a curated highlight reel. A reference call is a real conversation. Ask to speak with a previous client in a similar industry or at a similar stage - not the showcase client they put on their website.
Pay attention to how easily the agency provides references. An agency confident in their work will not hesitate. One that redirects you to testimonials or case studies is a different signal.
A good agency will not be put off by any of these questions. In fact, the right ones will welcome them - because they know exactly how they would answer.
If you are currently evaluating options for a software project, get in touch. We are happy to walk through any of these questions with you directly.