How to Vet a SaaS Development Agency in 2026

Every founder who has been burned by an agency tells a version of the same story. The pitch deck was polished, the logos on the clients slide were recognizable, the discovery call felt warm — and four months later they had a half-working product, a developer they never once spoke to directly, and no clean way to take their own code with them. Learning how to vet a SaaS development agency is the highest-return hour you will spend before signing anything, because the cost of getting it wrong is not the agency fee. It is the six months of runway you never get back.

This is a practical framework: twelve questions you can ask on a single discovery call, grouped into five categories, plus three red flags that mean you walk away regardless of how low the price is. I have been on both sides of this — building SaaS MVPs for founders as an AI-augmented full-stack engineer, and being vetted by them. The agencies worth hiring answer these questions without flinching. The sales-front shops get visibly uncomfortable.

Before you even get to vetting, make sure an agency is the right shape for your build at all. For an early MVP, a single experienced contractor is often the better call — the agency vs freelancer comparison lays out when each makes sense. And if you are still deciding whether to build the team internally, the in-house vs outsource breakdown covers the tradeoffs. This guide assumes you have already decided an agency is the route.

How to Vet a SaaS Development Agency: The Live Work Questions

Category one is the easiest to fake and the easiest to verify, so start here.

Question 1 — Can you show me three live products I can use right now? Not screenshots, not a PDF case study, not a Figma prototype. Live URLs you can open in your own browser and click through. An agency that builds SaaS has shipped SaaS, and shipped software has a URL. If the answer is that everything is under NDA, that is one project's worth of excuse, not a whole portfolio's worth.

Question 2 — Which of these did your team build versus design or maintain? Plenty of shops list a product on their site because they did a landing-page redesign or a three-week maintenance contract. Ask specifically what their team wrote, from what starting point, and over what period.

Question 3 — Walk me through one technical problem you got wrong on a past build. The answer tells you whether you are talking to people who have actually shipped under pressure or people who have only sold the idea of it. Real builders have war stories. Sales fronts have only success theatre.

The Team Questions

The gap between the people who pitch and the people who code is where most agency relationships quietly fail.

Question 4 — Who specifically will write my code, and can I talk to them before signing? You want named engineers, not a faceless team. If the people on the sales call cannot connect you with the person who will actually be in your repository, you are buying through a staffing layer that adds cost and removes accountability.

Question 5 — Is the work done in-house or subcontracted? Neither is automatically disqualifying, but you need to know. Subcontracted work spread across three time zones with no shared standards is how a codebase becomes unmaintainable. If they subcontract, ask who owns code review.

Question 6 — What happens to my project if the lead developer leaves mid-build? A serious agency has an answer involving documentation, shared repository access, and overlapping knowledge across the team. A fragile one goes quiet on this question.

The Commercial Questions

This is where founders lose the most and ask the least.

Question 7 — Is IP assignment clean and written into the contract? You must own 100% of the code, the design assets, and the infrastructure accounts on final payment. Get it in writing. Some shops retain ownership and license the product back to you, which quietly traps you. If the contract is vague on intellectual property, treat it as a red flag, not a detail to sort out later.

Question 8 — What is the payment schedule tied to? Milestones tied to deliverables you can verify, not calendar dates. A schedule of 30% to start and then monthly rewards slow work. A schedule of 30% to start, 30% at working auth and billing, 30% at feature-complete, and 10% at handover ties their money to your outcomes.

Question 9 — Who owns and pays for the infrastructure accounts during the build? The Stripe account, the database, the domain, the email service — these should be in your name from day one, with the agency given access. Founders who let the agency own the accounts discover at handover that migration is a billable extra. For a realistic read on what the whole engagement should cost, run the numbers through the cost to outsource SaaS development guide and the app cost estimator before you negotiate.

The Technical Questions

You do not need to be technical to ask these. You need to listen for whether the answer is concrete or hand-waved.

Question 10 — How do you handle multi-tenancy and data isolation? For any B2B SaaS, this is the question that separates people who have built real multi-tenant systems from people who have only built single-user apps. A concrete answer names an approach — row-level security, schema-per-tenant, or separate databases — and explains the tradeoff. A vague answer along the lines of "our architecture handles that" means they have not done it. This is the exact boundary that shaped how I built the Callidus clinic platform (callidusos.co.uk) on React and Firebase with strict tenant isolation rather than a shared backend.

Question 11 — What does your observability stack look like? When my product breaks at 2am, how do you know before I do? A real answer names error tracking such as Sentry, structured logging, and uptime monitoring. An agency that ships software it never has to operate often skips this entirely, which means you inherit a product that goes dark silently.

Question 12 — Have you been through a customer security questionnaire? The moment your SaaS sells to a mid-market company, you get a 200-line security questionnaire. An agency that has been through SOC 2 readiness or a real security review with a past client can build with that in mind from the start. One that has never seen one will architect you into a corner you pay to escape later.

Three Red Flags That Mean Walk Away

Some signals are bad enough that price stops mattering.

Red flag 1 — They will not give you a reference from a founder, only a logo wall. Curated logos are marketing. A founder who will take a fifteen-minute call and tell you what it was actually like to work with the agency is proof. If every reference request is deflected, assume the references are not good.

Red flag 2 — The estimate arrives before the questions do. An agency that quotes a fixed price for a SaaS platform before understanding your data model, your tenancy needs, and your integrations is either guessing or planning to change-order you later. Real scoping produces questions first and numbers second.

Red flag 3 — They are vague or evasive on code ownership. If you cannot get a straight, written answer to whether you own 100% of the code on final payment, everything else is irrelevant. This is the one red flag that overrides a strong portfolio, a warm team, and a low price.

Why This Matters More in 2026

The reason vetting deserves real effort now is that the market is noisier than it was even two years ago. AI-assisted development has lowered the barrier to producing a convincing demo, which means more shops can show something that looks shippable without being able to operate it in production. A polished prototype is no longer evidence of competence — operating real software for paying customers is. That shift is exactly why the twelve questions lean so heavily on live work, multi-tenancy, observability, and security: those are the parts of building SaaS that AI tooling does not fake for you, and they are where the gap between a real engineering team and a sales front is widest. The cost side of the same shift is covered in the cost to outsource SaaS development guide, which is worth reading alongside this one before you commit a budget.

How to Run This in Practice

You do not need to fire all twelve questions like an interrogation. Pick the four that matter most for your situation — usually live work, code ownership, multi-tenancy, and a founder reference — and let the conversation breathe. The goal is not to catch the agency out. It is to find the one that answers naturally because they have nothing to hide.

If you want a starting shortlist rather than a cold search, the best SaaS development outsourcing companies for 2026 roundup is a vetted place to begin, and the outsourcing SaaS development resources guide covers the same ground in more depth on sourcing and managing the relationship.

I have shipped products like BookBed (bookbed.io), the Callidus clinic platform (callidusos.co.uk), and Pizzeria Bestek (pizzeriabestek.com) as an AI-augmented full-stack engineer, and the founders I work best with are the ones who ask hard questions early. If you are vetting agencies right now and want a second opinion on a proposal in front of you, email me — I will tell you honestly whether the numbers and the answers add up.