Hiring a SaaS development agency is one of the higher-stakes vendor decisions a business ever makes. A typical engagement is $50K–$500K, runs 4–12 months, produces software you will depend on for years, and has an ugly unwind if it goes wrong. Most buyers have never done it before. Most agencies — including good ones — are not great at making the evaluation easy.
This post is the checklist we would use if we were the buyer, not the agency. We have been on both sides of this hundreds of times. Some of these questions are ones we love to be asked because they separate us from the pack. Others are ones we will answer honestly even when the honest answer is "not us." All 15 are questions that would save most buyers from the mistakes we see most often.
Use this as a scorecard. Give each question a yes, partial, or no. Eleven-plus clean yeses from a single agency means you have a real candidate. Under eight means keep looking.
Before you even start the search
Two questions to ask yourself first:
- Do I know what I am actually building? If your answer is "a SaaS for [industry]" with nothing more specific, you are not ready to hire an agency yet. You are ready for a discovery phase with a consultant. Those are different engagements with different price points.
- What is the smallest version of this that proves the business case? If you cannot describe the MVP in two paragraphs, do not sign a $300K build contract. Scope will explode.
With those settled, here is the 15-point checklist.
Discovery and fit (questions 1–4)
1. Did they ask about your business model before asking about your tech stack?
A good agency leads with "tell me about your customers, your revenue model, and your 18-month roadmap." A mediocre one leads with "so you want a React/Node app?" Technical questions are the easy part. Business context drives every architectural decision that matters.
Red flag: The agency quoted you before a 30+ minute discovery call.
2. Do they push back on your scope?
The best agency engagements we have seen (both as the agency and as a customer) started with the agency saying "you do not need all of that in V1." A team that agrees with everything you say is a team that will build everything you ask for — including the parts you will later regret paying for.
Green flag: They offered to cut features to protect the launch date.
3. Have they shipped products in a domain adjacent to yours?
You do not need them to have built your exact product before. You do want them to have shipped something where the technical pattern overlaps — real-time collaboration, multi-tenancy, billing, marketplace dynamics, compliance-regulated data, whatever your core concern is.
Ask to see a project where the domain was new to them but the pattern was familiar. That is the honest test.
4. Can you describe your project back to them and have them correct the misunderstandings?
During the discovery call, try this: paraphrase your own project in 90 seconds. See if they nod along or actively correct you. A good agency will interrupt with "wait — it sounds like you actually want X, not Y, because of Z." That is them doing the job before the contract is signed.
Technical fit (questions 5–8)
5. What is their default stack, and why?
Every serious agency has a default stack. Ours is roughly Next.js / React / TypeScript on the frontend, Node or Python on the backend (Python for AI-heavy work), Postgres as the default database, Vercel or AWS for hosting. We pick defaults deliberately because consistency across clients compounds quality.
Ask their reasoning. If it is "that is what our engineers know," fine — but they should be able to articulate tradeoffs. Bonus points if they tell you when they would deviate from the default.
6. How do they handle code ownership and IP?
You should own 100% of the code, designs, and IP at project completion. Period. This is standard in reputable US agency contracts. Watch for:
- "Licensed" code. Some agencies retain a license to reuse "components." That is usually fine for generic infrastructure, but not for business logic. Read carefully.
- Proprietary CMS or frameworks. If their "platform" is a closed system you cannot take elsewhere, that is a long-term lock-in.
- Third-party dependencies. Are all SaaS tools (CMS, auth, etc.) on your accounts, not theirs? Critical.
7. How do they use AI tools in their workflow, and how do they guard against AI-generated bugs?
It is 2025. Any agency not using AI tooling is leaving 20–40% productivity on the table, and will quietly charge you for it. But unguarded AI use ships subtle bugs. Ask:
- Which AI tools does the team use?
- How do they review AI-generated code differently than human-written code?
- How have their testing practices changed in the AI era?
If the answer is "we don't use AI," you are paying a premium for nothing. If the answer is "AI writes everything," run.
8. What is their testing and deployment pipeline?
Specifics matter:
- Automated tests (unit, integration, end-to-end) running in CI on every PR?
- Deploys on every merge to main, or some gated staging flow?
- Rollback plan for production issues?
- Feature flags for risky launches?
A team without real CI/CD will cost you in bugs, in downtime, and in weekend-fire-drill invoices.
Team and process (questions 9–11)
9. Who, specifically, will be on your project?
Get names. Get LinkedIn profiles. Get hours-per-week commitments. "You will have a senior engineer and a designer" is not specific. "Maria (senior engineer, 20 hrs/week), Jordan (designer, 10 hrs/week), Sam (tech lead, 4 hrs/week)" is.
Ask whether the people pitching you will actually be on the project. At smaller agencies (including us), yes — the principal is in the weekly standup. At larger agencies, probably not. Both models work, but know what you are getting.
10. What does a typical week look like — meetings, updates, demos?
A healthy cadence on a 3–6 month SaaS build looks roughly like:
- Weekly 30–60 min sync with the full team.
- Bi-weekly demo to stakeholders.
- Async Slack or equivalent for day-to-day questions (same-day response during business hours).
- Monthly written status report with budget burndown.
Less than this, and you will feel out of the loop. More than this, and you are paying for meetings. The agency should have opinions about this — if they ask "how often do you want to meet?" without offering their own recommendation, that is a sign they do not have an opinion on process.
11. How do they handle scope changes?
Scope always changes. The question is how.
- Change orders: Specific, priced, approved in writing before work begins? Good.
- "We'll just work it in": Beware. This is how projects either quietly go over budget or quietly drop the feature you thought was included.
- Frozen scope with buffer: A fixed-bid contract with a small buffer (say 10%) for in-flight changes is cleanest. But only if the original scope was shaped carefully.
Our SaaS development approach leans toward fixed-scope phases with explicit change-order discipline. It is not the only model but it keeps both sides honest.
Commercial and risk (questions 12–14)
12. What are their payment terms, and do they take deposits?
Reasonable terms for a 6-month $200K engagement:
- 25–30% deposit to start.
- Milestone-based payments over the project.
- Final 10–15% on delivery and acceptance.
Red flags:
- 100% upfront. Nobody should ask for this.
- Time-and-materials with no cap. Known for budget explosions.
- Pure hourly with no sprint-level budget commitment. Works for ongoing work, not for defined projects.
13. What does support after launch look like, and what does it cost?
This is where many agencies get ugly after the fact. Before you sign:
- Is there a warranty period for bugs in shipped work? (We provide 30 days by default.)
- What is the hourly or retainer rate for post-launch work?
- Who is on call if something breaks on a Saturday night?
- How long are they committed to being available for your project? 6 months post-launch? A year?
Get the post-launch terms in writing before you sign the build contract. Far better to negotiate when you have leverage (pre-signature) than when you do not (post-launch, your site down).
14. Can you talk to 2–3 past clients, ideally ones with projects 12+ months old?
Any reputable agency can provide references. The key is project age. References from a site that shipped last month tell you nothing about long-term quality. References from a site that has been in production 18+ months tell you whether the agency:
- Built something maintainable.
- Responded well to post-launch bugs.
- Left the client in good shape after the engagement ended.
Actually call the references. Ask specifically: "If you had to hire a SaaS agency again, would you pick them? If not, what would you change?" The answer is almost always more candid than you would expect.
The final check (question 15)
15. Gut check — do you like them, and would you work with them for 6 months?
This sounds soft but it is the most predictive question on the list. You will spend hundreds of hours on calls, Slack, and docs with this team over the build. If you left the first two calls feeling drained or uneasy, trust that. If you left energized, that is also signal.
We have turned down engagements that looked great on paper because the vibe in discovery calls suggested we were going to fight constantly. And we have taken engagements that looked underpriced because the founder was sharp, decisive, and a joy to think alongside. Both of those calls have aged well.
Scoring the checklist
Tally yes / partial / no across the 15 questions.
- 13+ yeses: Strong fit. Contract candidate.
- 10–12 yeses: Reasonable fit. Negotiate hard on the partial answers.
- Under 10 yeses: Keep looking. This is too much money to commit on a weak match.
The biggest mistakes we see buyers make
Three patterns that cost people the most:
-
Hiring on price alone. The cheapest quote is almost never the best value. The cheapest quotes usually come from agencies that either lowball to win the deal (then change-order you to death) or that genuinely cannot do the work at a real quality bar.
-
Skipping the checks on post-launch. Buyers focus on getting the product built and forget that they will need someone available for fixes, new features, and the inevitable "actually, let's change this" request. Negotiate post-launch terms before signing.
-
Not writing down the scope. A scope doc signed by both sides is the most valuable artifact in the entire relationship. If there is ambiguity in what is being built, there will be conflict when it comes time to ship. Push hard for a written scope even if it delays kickoff by a week.
When none of the candidates pass the checklist
Sometimes you run this process and nobody clears. Usually that means one of three things:
- You are looking at agencies outside your budget tier. A $50K budget looking at $200K agencies will find all of them unresponsive or sloppy in discovery. Adjust the search.
- Your project is not yet well-defined enough to evaluate against. Go back and sharpen the scope first.
- Your market has a shortage of serious agencies in your domain. Consider expanding geographically, or consider a smaller vetted firm.
The bottom line
Hiring a SaaS development agency is not magic and it is not luck. There is a checklist, and the checklist works. The 15 questions above would prevent 80% of the bad agency engagements we hear about in post-mortems.
If you are running this checklist against us right now, we invite it. We will happily answer all 15 on a discovery call, show you projects 24+ months old that are still thriving, and introduce you to clients who have been with us across multiple phases. If we are not the right fit for your project, we will tell you and point you toward someone who is.
Book a discovery call and we will walk through this exact checklist together — whether or not we end up the team you pick.