How to Vet a Software Development Agency

The short answer: how to vet a software development agency

Vet a software development agency by checking three things: proof they've shipped similar products, a clear written scope with milestone-based payments, and independent oversight of code quality. Ask for references, insist on owning your code and IP, and never pay large sums upfront for work you can't personally evaluate.

If you're a non-technical founder, here's the uncomfortable truth most agencies won't say out loud: your biggest risk isn't a bad developer. It's that you can't tell good work from bad work. You approve invoices based on demos and vibes, not code. That gap is exactly where budgets get burned. Industry research has long found that roughly two-thirds of software projects run over budget, miss deadlines, or fail outright (Source). This guide gives you the questions, the flags, and the structure to stack the odds in your favour.

11 questions to ask a dev agency (and how to read the answers)

Ask these before signing anything. For each, know what a strong answer sounds like and the red flag that should make you pause.

1. "Can you show me 2–3 live products you built that are similar to mine?"
   Good answer: Working links, App Store listings, and a named contact you can call. Red flag: Only mockups, NDAs "cover everything," or portfolios of designs that never shipped.
2. "Who exactly will write my code, and will they change during the project?"
   Good answer: Named developers with seniority levels, and a warning that mid-project swaps are rare. Red flag: Senior people in the sales meeting, juniors on the actual build ("bait and switch").
3. "How do you ensure code quality, and who reviews it?"
   Good answer: Code reviews, automated tests, and an independent technical lead signing off deliveries. Red flag: "Our developers are very experienced" with no process behind it.
4. "How is payment tied to delivery?"
   Good answer: Milestones you approve before releasing funds. Red flag: 50%+ upfront, or monthly retainers with no defined output.
5. "Who owns the code, repositories, and IP?"
   Good answer: You do, in writing, with repo access from day one. Red flag: They "host it for you" and hand over code only at the end.
6. "What happens when we disagree on whether something is 'done'?"
   Good answer: A written definition of done and acceptance criteria per feature. Red flag: Vague reassurance and no acceptance process.
7. "How do you estimate and what happens if you go over?"
   Good answer: Ranged estimates, documented assumptions, and change-request rules. Red flag: A suspiciously low fixed price that quietly balloons with "out of scope" charges.
8. "How and how often will you communicate progress?"
   Good answer: Weekly demos, a shared tracker, and one accountable point of contact. Red flag: Updates only when you chase, or a wall of jargon that hides slippage.
9. "What does support and handover look like after launch?"
   Good answer: Documentation, a bug-fix window, and a clean handover so any team can continue. Red flag: Code only they can maintain, locking you in.
10. "Can I speak to a past client whose project went badly?"
    Good answer: Honesty about a project that struggled and what they learned. Red flag: "Every client loves us" — nobody has a perfect record.
11. "Will an independent senior engineer review deliveries before I pay?"
    Good answer: Yes, or openness to you bringing your own reviewer. Red flag: Resistance to any outside technical check.

Red flags: walk away when you see these

These signals correlate strongly with burned budgets and stalled projects (Source).

• Large upfront payment demanded before any work is shown.
• No named developers, or the sales team differs from the build team.
• Vague scope, no written statement of work, no acceptance criteria.
• They own the code, repos, or hosting instead of you.
• Quotes far below every other bid (someone always pays the difference — usually you, later).
• Communication is slow, defensive, or drowning in jargon.
• No independent quality checks — you're the only reviewer, and you can't read code.

Green flags: signs of an agency worth hiring

• Live, verifiable products and reachable references.
• Milestone-based payments you release only after approving work.
• You own the code and IP from day one, with repo access.
• A written scope, definition of done, and clear change-request process.
• Senior technical oversight and code review baked into the process.
• Straight talk about trade-offs, risks, and past mistakes.

Freelancer vs agency vs supervised build

The right model depends on how much you can personally judge the work. Here's how the common options compare on the dimensions that protect a non-technical founder.

The core idea: if you can't judge the work, buy the judgement. That's cheaper than buying it back after a failed build. Before you accept any quote, sanity-check the number with our app cost estimator so you know whether a price is fair or fantasy.

Why paying for work you can't evaluate is the real risk

The real risk for a non-technical founder isn't hiring a bad developer — it's paying for work you cannot judge. You see a demo that looks fine while the code underneath is fragile, undocumented, or half-finished. By the time it breaks, the money's gone and so is the team. That's why independent oversight matters more than any single hire.

Stratgik was built around this exact gap. A senior tech manager supervises developers by the hour and reviews every delivery before you pay — so you never fund work you can't assess. Oversight starts at $49/mo, versus traditional fractional CTO firms that charge $8,000–$25,000/mo (Source). If you want that senior layer without a full-time hire, our fractional CTO service covers it, and if you're starting fresh, see how we approach MVP development.

Frequently asked questions

How do I know if an agency is overcharging?

Get three quotes and benchmark them against an independent estimate. If one is far higher or far lower than the others, ask exactly what's included. Overcharging usually hides in vague scopes and padded hours, not headline prices — so insist on itemised estimates and milestone billing.

Should I pay upfront?

No — not large sums. A small deposit to book time is normal, but the bulk of payment should be tied to milestones you approve. If an agency needs most of the money before showing working software, that's a structural risk, not a cash-flow quirk.

How much should development cost?

It depends on scope, but rates vary enormously — from under $60 to over $300 an hour depending on region and seniority (Source). A simple MVP typically runs tens of thousands, not hundreds. Use a cost estimator to set a baseline before you talk to anyone.

How do I protect my idea and IP?

Put it in writing before work starts: a mutual NDA, and a contract stating you own all code, designs, and IP outright. Insist on access to your own repositories from day one. If the agency controls the code and only hands it over at the end, you don't really own your product.

What if I'm not technical enough to review the work?

Then don't review it alone. Bring in an independent senior engineer to check deliveries before you approve payment. This is the single highest-leverage protection a non-technical founder has, and it costs a fraction of a rebuild.

Fixed price or hourly — which is safer?

Fixed price feels safe but pushes agencies to cut corners or nickel-and-dime scope changes. Hourly is fairer if — and only if — someone independent verifies the hours produced real, quality work. Oversight is what makes hourly safe.

Get a free second opinion before you sign

Before you commit to any agency, get a free 30-minute session with a senior tech expert — not a salesperson. We'll review your quotes, your scope, and your risks, with no card required. Reach us at contact us, email contact@stratgik.com, or call +91-78400-58032. Spend 30 minutes now to avoid losing months later.