Every founder asks the same question on the first call: how much will this cost? Every honest answer starts the same way: it depends. Then somebody quotes a confident-sounding figure anyway, the founder believes them, and twelve months later there's a gap between the budget and reality wide enough to fall through.
We've shipped 120+ SaaS products. This is the version of that conversation we wish someone had given us when we started — the ranges, the levers, the hidden costs nobody quotes, and a way to budget the actual 18 months in front of you instead of just the build.
The three SaaS cost tiers in 2026
Forget "small / medium / large" — those map to nothing. The brackets below come from actual production engagements:
Tier 1 · MVP — USD 25,000 to 50,000
One core workflow, one user role, one happy path. Auth, billing (Stripe single plan), a dashboard, and the feature that's the actual reason the product exists. Built in 6–10 weeks by 2 senior engineers and a part-time designer.
At this tier you're testing whether the problem is real and whether people will pay. You will rebuild parts of this in tier 2. Plan for that. The MVPs that don't get rebuilt are the ones that didn't find traction — that's the cheapest possible failure mode.
Tier 2 · Production SaaS — USD 50,000 to 150,000
Multi-tenant from day one. Plans, seats, RBAC, audit log, customer admin console, observability, basic analytics, and the feature breadth a paying customer expects. 10–18 weeks with 2–3 senior engineers, a designer, and 0.5 of a product partner.
This is the tier most early-revenue SaaS products live in. It's roughly half the team-month cost of building it in-house in the US, UK, or DACH if you include benefits, equipment, and management overhead.
Tier 3 · Platform / Enterprise — USD 150,000 to 500,000+
SSO (SAML / OIDC), org management, granular permissions, SCIM provisioning, usage-based billing, custom contracts, a public API, SDKs, partner integrations, white-label, regional data residency, and SOC 2 readiness baked into the architecture. 4–9 months with a team of 4–6.
At this tier the costs that matter aren't the engineering hours — they're the design choices that decide whether the system stays maintainable at 100× scale or rots into a rewrite.
The seven things that actually drive cost
Most quotes are sensitive to the wrong variables. Here's what actually moves the number, in roughly the order it does:
1. Number of distinct user roles
Every role is its own product surface. One role is an MVP. Three roles is a real product. Six roles is an enterprise platform with real RBAC and probably an admin role on top of that. Each one adds screens, permissions, edge cases, and tests.
2. Whether you need multi-tenancy from day one
Single-tenant feels cheaper for the first 5 customers and bites you forever after. Multi-tenant from day one costs about 15–20% more upfront and saves you a six-figure migration in year two. Always multi-tenant.
3. Compliance scope
SOC 2 Type 1 readiness adds 10–15% to the build budget. HIPAA-ready adds 20–30% and a different posture. PCI is its own world and we usually engineer around it. GDPR data export and deletion is now baseline, not a feature.
4. Real-time vs request-response
WebSockets, presence, live cursors, collaborative editing — all of these are 2–4× more expensive than the equivalent request-response feature. Don't ship them in v1 unless they're the product.
5. AI features that aren't demos
A GPT wrapper is a weekend. A production AI feature with eval suites, observability, fallback logic, prompt versioning, and cost ceilings is a 4–8 week initiative on top of the rest of the product.
6. Mobile + web
Mobile from day one roughly doubles the team-month cost. If you can ship a great responsive web app first and add mobile in 6–9 months, do that. Most B2B SaaS doesn't need mobile in v1.
7. The integrations list
Each non-trivial integration (Salesforce, HubSpot, QuickBooks, Stripe Connect, an industry-specific API) is 1–3 weeks of engineering. The list of integrations on the website rarely matches the integrations actually live; the gap is exactly equal to the integration backlog.
The hidden costs nobody quotes you
These line items will surprise you if no one warned you about them upfront. They typically add 20–35% to the build budget.
- Design system + component library — without one, every screen costs 2× to build. Budget USD 8–15k.
- Production infrastructure — staging, preview environments, CI/CD, secrets management, backups. USD 5–10k of setup plus ongoing cloud spend.
- Observability tooling — Sentry, Datadog, PostHog or LogRocket. USD 200–600/month operating, often more at scale.
- Customer email infrastructure — transactional email (Postmark / Resend), domain auth (DKIM, DMARC), inbox deliverability. USD 1–3k upfront, USD 50–200/month.
- Legal — Terms of Service, Privacy Policy, DPA, an MSA template, optional Impressum for DACH. USD 2–8k for templates, more if drafted by a lawyer.
- Branding & marketing site — logo, brand guidelines, marketing site, social cards. USD 6–25k depending on fidelity.
- Onboarding & support tooling — Crisp, Intercom, help docs, in-app guides. USD 100–400/month and someone's time.
- Year-1 cloud spend — typically USD 6,000–18,000 even at modest traffic, more if you're storing files or running inference.
Build vs hire vs partner — the honest comparison
We're a senior agency, so take this with the appropriate grain of salt — but the math below is independently verifiable on Glassdoor and Levels.fyi.
- Hire in-house (US): 2 senior engineers + 1 designer for 6 months ≈ USD 280–360k fully loaded. Plus 2–4 months to recruit them.
- Hire in-house (UK / DACH): ≈ GBP 200–280k or EUR 230–320k. Same recruitment lag.
- Senior agency: USD 80–180k for the equivalent scope, no recruitment lag, hand-over when ready. Higher hourly rate, fewer hours required to ship the same outcome because the team is already calibrated.
- Offshore body shop (USD 25–45/hr): Quoted USD 40–80k. Real total after rework, churn, and rescue projects: usually 2–3× quoted. We get a lot of rescue work from this tier.
- Build it yourself: If you're a technical founder with 6 months and no employer, your time has an opportunity cost that's invisible but very real. Budget that into the comparison.
Budget for the 18-month total cost — not just the build
The number that matters isn't the build cost — it's the 18-month total cost of getting to product-market fit and your first 100 paying customers. A rough framework:
- Build (months 0–4): tier 1 cost from above.
- Iteration (months 4–9): 30–50% of build cost again — fixing what users actually complained about.
- Operations (months 0–18): 15–30% of build cost annually — observability, maintenance, security patching.
- Growth feature gap (months 9–18): 50–80% of build cost again — the features paying customers ask for that aren't in v1.
For a USD 75,000 build, plan for USD 145–195k total over the 18-month runway to first revenue traction. If that number scares you, halve the v1 scope before you halve the budget.
What we'd ask you before quoting
If a vendor quotes a number before they've asked these questions, the number is invented:
- How many distinct user roles, including admin?
- Multi-tenant from day one, or single-tenant?
- What does success at month 6 look like — feature list or revenue?
- Compliance posture — SOC 2, GDPR, HIPAA, none?
- Real-time features — collaboration, presence, notifications?
- AI features — and is the eval / observability scope included?
- What integrations are non-negotiable in v1?
- What's the in-house team size on your side, today and in 12 months?
The TL;DR
Most SaaS products that ship to revenue come in between USD 50k and USD 150k for the build and USD 100k to USD 250k all-in over the first 18 months. Anything quoted dramatically lower is either scope-stripped beyond viability or under-quoted on purpose.
Budget for what you'll actually need, not what's on the quote. Halve the v1 scope before you halve the budget. And get the comparison with hiring in-house honestly on the table — usually the agency math is better than founders assume.