12 questions to ask before hiring a software development agency

Before hiring a software development agency, ask who will actually write your code, how you'll see progress, who owns the work, and what happens after launch. The answers separate agencies that ship working products from agencies that bill hours — and you can get all twelve answered in a single discovery call.

We're an agency, so read this knowing where we stand: these are the questions we'd want our own clients to ask us and every competitor, because they reward the way good teams already work. If you're still deciding between an agency, a freelancer, or hiring in-house, start with that comparison first.

Team and process: questions 1–4

• 1. Who will actually write my code? Good answer: named engineers, with the person you're talking to close to the work. Red flag: a sales engineer closes the deal, then the project moves to a team you never met — quality and context both leak at that handoff.
• 2. Who is my point of contact, and how many layers sit between me and the engineers? Good answer: zero or one. Red flag: an account manager relaying messages to a project manager relaying to developers. Every layer adds delay and translation error.
• 3. How will I see progress? Good answer: a working build you can click, on a schedule — weekly demos are the healthy default. Red flag: status reports and slide decks instead of software. Documents can look on-track while the product isn't.
• 4. What does a typical week look like? Good answer: a concrete rhythm — planning, demo day, async updates you can read on your schedule. Vague answers here predict vague weeks later.

Technical: questions 5–8

• 5. What stack would you use for my product, and why? Good answer: a boring-in-a-good-way default (for us: Next.js, TypeScript, Node.js, PostgreSQL — see our stack and why) with reasons tied to your product, hiring market, and hosting costs. Red flag: whatever's trendy, or a proprietary framework only they can maintain.
• 6. How do you handle security and scaling? Good answer: specifics — auth patterns, least-privilege data access, what they'd do before your first traffic spike. They should mention things you didn't ask about, like row-level security or rate limiting.
• 7. How do you test, and what's your definition of done? Good answer: automated tests on critical paths, staging environments, and 'done' meaning deployed and verified — not merely code-complete.
• 8. Where does the code live from day one, and who owns it? Good answer: a repository under your account, with IP assignment on payment written into the contract. Red flag: code in their repo 'for convenience' with handover 'at the end' — that's leverage, not convenience.

Commercial: questions 9–11

• 9. How do you price, and what happens when scope changes? Good answer: fixed milestones or a transparent retainer, with a written process for changes — new estimate, your approval, then work. Red flag: open-ended hourly with no cap and no definition of the deliverable. Our engagement models page shows what transparent structuring looks like.
• 10. What is explicitly not included? Good answer: a clear list — app store submissions, third-party service fees, content, ongoing maintenance — before you sign. Surprises here are the most common source of budget conflict.
• 11. What happens after launch? Good answer: a maintenance option you can choose (not a lock-in you can't leave), documentation, and a clean handover path to your own team if you'd rather take it in-house.

Proof: question 12

12. Show me a comparable product you shipped — and let me talk to that client. A portfolio page is marketing; a reference call is evidence. Ask the past client three things: did it ship on schedule, what broke after launch and how fast was it fixed, and would they hire the team again. Verify what you can independently: Clutch reviews are attributable to real companies, and an Upwork agency profile shows a work history with ratings the agency can't edit.

Any agency doing real work can point to something like a production SaaS serving 10,000+ users or an MVP shipped in 11 weeks — and should be comfortable putting you in front of the people who paid for it.

How should you run the evaluation?

Talk to two or three agencies, ask all twelve questions, and compare answers side by side. The pattern to watch isn't polish — it's specificity. Teams that ship answer with numbers, names, and examples; teams that bill answer with adjectives. Then start small: a discovery engagement or a tightly-scoped first milestone tells you more in three weeks than a proposal document ever will.