Choosing a software agency is one of those decisions that feels straightforward until it isn't. You write a brief, get some quotes, compare prices, pick the one that feels right. Twelve months later, you're either glad you asked the hard questions upfront or wishing you had.

We've been on both sides of this. We've been the agency responding to briefs, and we've inherited projects from agencies that didn't work out. The pattern is always the same: the problems that surface later were almost always avoidable if someone had asked the right questions at the start.

1. Who Actually Does the Work?

This is the most underrated question in the entire process. During the pitch, you'll meet the founders, the senior engineers, the people who say all the right things. But who writes the code?

At some agencies, the people you meet in the pitch are not the people who build your system. Your project gets handed to junior developers, offshore contractors, or a rotating cast of whoever's available that sprint.

Ask directly: will the people in this room be working on my project? If not, who will? Can I meet them?

2. Who Owns the Code?

Some agencies retain ownership of the intellectual property they produce. Some use shared frameworks or proprietary platforms that create lock-in. Some will transfer ownership, but only at the end of the project, or for an additional fee.

The answer you want: you own the code, unconditionally, from day one. It lives in a repository you control, and you can take it to another team tomorrow if you need to.

3. What Happens After Launch?

Launch is the beginning, not the end. Software needs ongoing attention: security patches, dependency updates, bug fixes, performance monitoring, and feature evolution.

Ask your agency what their support model looks like. Is it included? Is it a separate retainer? What's the response time for critical issues? Who's on call?

4. How Do You Handle Scope Changes?

Every project changes scope. Requirements evolve, priorities shift, someone realises halfway through that the original spec missed something important. This is normal.

What matters is how the agency handles it. Do they have a process for evaluating change requests? Are the cost implications transparent? Do they push back when a change would introduce technical debt or risk?

An agency that says yes to everything is not doing you a favour. Good engineers will tell you when a request is going to cause problems, and they'll offer alternatives.

5. Can I See How the Work Is Progressing?

You should be able to see what's being worked on, what's been completed, what's blocked, and what's coming next.

If the answer is "we'll show you when it's done," that's a three-month window where anything could go wrong and you won't know about it until it's too late. Regular demos, a shared project board, and a staging environment you can access should be standard.

The Quote Is the Least Important Part

It's tempting to compare agencies purely on price. But the cheapest quote often comes from the agency that underscoped the project, plans to use junior developers, and won't be around for support.

The most expensive quote might be padding. But it might also reflect senior engineers, proper testing, documentation, and a team that takes ongoing support seriously.

Price matters, but the answers to these five questions will tell you far more about whether an engagement will succeed.