How to hire a software development agency: a founder's checklist

Hiring a software development agency comes down to a few questions that predict whether a project ships well: who writes the code, how scope and price are set, who owns the result, and what happens after launch. Use the checklist below before you sign anything.

The founder's checklist

1. Who actually writes the code? Ask whether the people on your calls are the people building the product, or whether work is handed off to an offshore team you never speak to. Direct access to the engineers is the single biggest quality signal.
2. How is scope and price set? A defined deliverable, a fixed price, and a written timeline protect you from scope creep. Open-ended hourly arrangements with no cap are where budgets quietly double.
3. Who owns the code? You should own the repository from day one — no per-seat licence, no recurring platform fee, no lock-in. Confirm the handover terms in writing.
4. What does the stack look like? Modern, well-supported tools (for example Next.js, TypeScript, Postgres) mean you can hire for it later. A bespoke or obscure stack makes you dependent on the agency forever.
5. How do they handle changes mid-project? Requirements shift. A good agency re-quotes the delta and you approve it — rather than silently absorbing changes into a slipping timeline.
6. What happens after launch? Ask about post-launch support, documentation, and whether you can take the project in-house. A documented codebase and a support window are the difference between an asset and a liability.

Red flags

• No fixed scope or written quote before work starts.
• You never talk to the people writing the code.
• The agency keeps the repository or charges to release it.
• Vague answers on timeline, ownership, or what is excluded.
• A proprietary platform you cannot leave without a rebuild.

Green flags

• A short scoping call that ends in a written, fixed quote.
• Direct, ongoing contact with the engineers and designer.
• A daily or weekly preview URL so you see progress, not promises.
• Full code ownership and a documented handover.
• A clear post-launch support window and an optional retainer.

Fixed-scope, retainer, or hourly?

Pick fixed-scope when the deliverable is clear — a storefront, a bot, a landing page. Pick a retainer when you need an embedded team shipping against a rolling backlog. Use hourly for audits, performance work, or unsticking your in-house team. The right agency will recommend the shape that fits your problem rather than the one that bills the most.

The short version

Favour agencies where you talk directly to the builders, scope and price are written down, and you own the code at the end. Those three things predict most good outcomes.