How to Choose a Software Development Agency: 10 Questions That Reveal the Truth

Every agency website says the same things: experienced team, agile process, client-focused. None of that helps you choose. What does help is asking questions whose answers can't be faked. Here are the ten we'd want a client to ask us — and what a good answer sounds like.

1. "Can I open three of your live projects right now?"

Not screenshots, not case-study PDFs — URLs and app store links. Open them on your phone. Run them through PageSpeed Insights. If a web agency's showcase sites score 40 on mobile, that's your future.

2. "Who exactly will work on my project?"

You want names, roles and seniority. Some agencies sell with senior people and deliver with juniors or subcontractors. Ask whether the people who write your code are employees, and ask to meet the lead developer before signing.

3. "How will I see progress?"

The right answer includes a repository you can access, a staging environment you can click through, and a fixed demo cadence (weekly is standard). "We'll send updates" is not an answer.

4. "Who owns the code and the accounts?"

You should own the source code (assigned on payment), the domain, hosting, app store and analytics accounts. Agencies that register everything under their own name are creating lock-in, whether they intend to or not.

5. "Fixed price, time & materials, or retainer — and why?"

Fixed price suits well-defined scope; time & materials suits evolving products; retainers suit ongoing work. A good agency explains the trade-off instead of pushing whichever is best for them. Be suspicious of a fixed price quoted without a discovery phase — one side is going to lose.

6. "What happens after launch?"

Ask about warranty period, maintenance options, response times and what a change costs. Software isn't finished at launch; the agency's post-launch model tells you whether they plan to be around.

7. "How do you handle performance, security and SEO?"

These are not add-ons. Listen for specifics: Core Web Vitals targets, dependency updates, HTTPS and headers, structured data, sitemap and hreflang. If the answer is "we can install a plugin for that", you've learned something.

8. "Can we start with a small paid discovery?"

A one- to two-week discovery sprint — requirements, architecture, clickable prototype, estimate — is the cheapest way to test an agency. Anyone who refuses to work in small steps first is asking for trust they haven't earned.

9. "What would you push back on?"

Describe your project and ask what they'd do differently. Yes-agencies are dangerous: they'll build whatever you say, including the mistakes. You want a team that argues with you occasionally.

10. "Can I talk to a client from last year?"

Not their favorite client — one from a year ago, so you learn what maintenance and support actually looked like after the launch glow faded.

Red flags worth walking away from

• A quote before anyone has asked you a hard question.
• No public work, or work that can't be opened.
• Ownership of your domain, hosting or store accounts under the agency's name.
• Guaranteed rankings, guaranteed timelines with no scope, guaranteed anything.
• An agency website that is slow, broken on mobile or years out of date.

You are not buying code. You are choosing who to be in a room with when something breaks.

We're happy to be asked all ten. If you're comparing agencies for a web, mobile or custom software project, send us the brief and we'll answer them in writing.