You've talked to three agencies about building your SaaS MVP. All three want to start with a "discovery phase." That'll be $10,000-$25,000 and 4-6 weeks before they write a single line of code. They'll produce wireframes, user stories, technical specifications, and a project plan.
Then they'll give you a proposal for the actual build. Another $40,000-$80,000. Total: $50,000-$105,000 before you have a working product.
We skip the discovery. Here's why — and what we do instead.
The Discovery Phase Business Model
Let's be honest about what discovery phases are: they're paid learning. The agency is billing you to understand your domain, your users, and your requirements. That's fair — if they haven't built anything like your product before.
But here's the question: if they need 4-6 weeks and $15,000 to understand your industry before they can estimate the work, how efficient will they be during the actual build?
Discovery phases make sense for generalist agencies taking on novel projects. If an agency that builds e-commerce sites takes on a healthcare compliance platform, they genuinely need to learn HIPAA, audit trail requirements, and role-based access patterns. That learning has real cost.
For a specialized agency? That learning happened on project #1. By project #50, the patterns are muscle memory.
Pattern Matching: How We Scope in 30 Minutes
When a founder describes their product on a call, we're not hearing it for the first time. We're pattern-matching against 50+ previous projects.
"I need a case management system for my legal practice." — We built Bridgelaw. We know the entities (cases, parties, documents, tasks), the compliance requirements (encryption, access controls, audit logging), and the typical user roles (attorney, paralegal, admin). We can estimate this in the call.
"I need a compliance tracking platform for pharmaceutical operations." — We built GuardianRx. DEA compliance, video witnessing, biometric authentication, audit trails. Known patterns.
"I need to process large CSV files for my multi-location business." — We built FleetGrid. Streaming processing, batch validation, background queues, multi-location sync. We literally wrote the case study.
The 80/20 of scoping
80% of any SaaS MVP is commodity architecture: authentication, RBAC, CRUD operations, dashboards, notifications, deployment. We've built these 50+ times. The remaining 20% is your unique business logic — the thing that makes your product different. That 20% is what we focus on during the scoping call. Not the 80% we already know how to build.
Our Scoping Process: Zero Cost, One Week
Call 1: Pain Points Detection (30 minutes, free)
- What problem does your product solve? (not what features it has — what pain it addresses)
- Who are your users and what roles do they play?
- What compliance requirements exist? (HIPAA, SOC 2, GDPR, industry-specific)
- What integrations are needed? (payment, email, third-party APIs)
- What's your timeline and budget range?
By the end of this call, we know which of our previous projects is the closest match, what's different about yours, and whether we're the right fit.
Days 1-3: Internal shaping
We shape the project using our appetite-based process. This means defining: which features fit within the budget, which features should wait for v2, what the architecture looks like (matched to our proven patterns), and what the weekly delivery milestones are.
Call 2: Proposal Review (30 minutes, free)
We walk you through the shaped scope: what's in, what's out, why we made the tradeoffs, and what the timeline and budget look like. You see the architecture sketch, the feature list by week, and the compliance checkpoints.
Total scoping cost: $0. Total scoping time: 1 week. You have everything a $15k discovery would produce — minus the wireframes you'll change during development anyway.
When Discovery IS Worth Paying For
We're not saying discovery phases are always a scam. They're valuable when:
- The agency has never built anything like your product. If their portfolio is e-commerce and you need FDA-regulated software, they genuinely need to learn your domain. Pay for that learning — or find a specialized agency.
- Your product is genuinely novel. Not "another CRM with a twist" but truly new technology or workflow. If nobody has built it before, discovery is research, not overhead.
- Multiple stakeholders have conflicting visions. If your co-founder wants feature A and your investor wants feature B, a facilitated discovery process forces alignment before development starts.
- You're replacing a legacy system with undocumented business rules. Extracting hidden logic from a 15-year-old system is genuine discovery work that can't be pattern-matched.
If none of these apply — if you're building a SaaS product in a domain where established patterns exist — you don't need to pay someone to discover what's already known.
What About Requirements Changes?
The main argument for discovery: "We need detailed specs to prevent scope creep." In practice, detailed specs don't prevent scope creep. They just make you feel better about the plan before reality deviates from it.
Our approach to changing requirements: trade, don't add.
Every project has a fixed time budget (appetite). When a new requirement emerges mid-build, we don't extend the timeline. We ask: "What's less important than this new requirement?" Something comes out, something goes in. The budget stays fixed.
This works because our weekly delivery milestones give you working software to react to. You see real features, not wireframes. Your feedback comes from using the product, not imagining it. That's where the real "discovery" happens — during development, with working software, at no extra cost.
Frequently Asked Questions
What is a discovery phase in software development?
A paid pre-development engagement ($10k-$25k, 2-6 weeks) where an agency explores requirements, creates wireframes and specs before building. For experienced specialized teams, most of this work is unnecessary because the patterns are already known from previous projects.
How do you scope without discovery?
Pattern matching from 50+ previous projects. On a 30-minute call, we identify the closest match, assess compliance needs and integrations, then shape the scope to fit your budget. Total cost: $0. Total time: 1 week. You get everything a $15k discovery would produce.
When IS discovery valuable?
When the agency hasn't built anything like your product, your product is genuinely novel, stakeholders have conflicting requirements, or you're replacing a legacy system with undocumented business rules.
What if requirements change during development?
Trade, don't add. New requirement comes in? Tell us which planned feature is less important. Budget stays fixed, scope adjusts. Weekly demos of working software give you real feedback to react to, not wireframe speculation.
Next Steps
- Book a free Pain Points Detection call — 30 minutes, we'll scope your project live
- $35k MVP vs $200k MVP — what each budget tier actually gets you
- Why We Don't Use Scrum — our full development process
- SaaS MVP Development — our services, process, and pricing