1. Vision and business model
Main persona, problem solved, market alternatives, business model (monthly/yearly subscription, freemium, usage-based), pricing plans, 12-month revenue projection.
SaaS specification in 2026: Complete guide, template and budget
TL;DR (60 seconds)
- → A SaaS specification frames 5 critical workstreams: multi-tenant architecture, technical stack, recurring billing, user onboarding, GDPR compliance and security.
- → Typical MVP SaaS budget: 15-40 k€ (3-4 months), full platform: 60-150 k€ (6-9 months).
- → The 3 mistakes that kill a SaaS project: underestimating onboarding, forgetting recurring billing (webhooks, dunning, refunds), building a monolith that does not scale beyond 500 users.
- → An MVP ships in 6-10 weeks if the scope is limited to 1 persona + 3 core features + 1 simple pricing plan.
The specification for a SaaS is structurally different from one for a showcase site or an e-commerce site. It must anticipate not only the first version (MVP), but also the capacity to host 100, 1,000 then 10,000 paying users without rebuilding everything. Underinvesting in this phase costs 3 to 5 times the initial budget in late rework.
Average budget observed
15.000 €–80.000 €
MVP 15-40 k€, full platform 60-150 k€, enterprise scale 150-500 k€.
Average delivery time
10–30 weeks
MVP 8-12 weeks, complete v1 16-24 weeks, continuous scale afterwards.
Standard specification structure
2. Multi-tenant architecture
Choice: database per tenant (strong isolation, high costs), schema per tenant (trade-off), row-level security (scales but complex). Impact on GDPR export/deletion, performance, backup strategy.
3. Technical stack
Back-end (Rails 8, Django, Node.js), front-end (Hotwire, React, Vue), database (PostgreSQL with row-level security, Redis for cache/sessions), async queue (Sidekiq, Solid Queue), hosting (Kamal + Docker, AWS ECS, Heroku for MVP).
4. Authentication and authorization
SSO (Google, Microsoft for B2B), 2FA, team invitations, granular roles and permissions, API keys for integrations. Devise + OmniAuth on the Rails side, Auth0/WorkOS for enterprise.
5. Recurring billing and invoicing
Stripe/Mollie integration (subscriptions, webhooks, proration), handling upgrades/downgrades, payment failures (dunning), partial refunds, PDF invoices compliant with EU VAT, Factur-X e-invoicing for FR B2B client.
6. User onboarding
Frictionless signup funnel (email + password or OAuth), confirmation email, interactive product tour, first-action checklist, targeted aha moment in < 5 min. Direct impact on activation and 30-day retention.
7. Compliance and security
GDPR (processing register, processor DPAs, user data export/deletion, cookie consent), encryption at rest (KMS) and in transit (TLS 1.3), audit logs, rate limiting (Rack Attack), WAF, annual pentest.
8. Performance and scalability
Target Core Web Vitals (LCP < 2.5 s, INP < 200 ms), background jobs for heavy tasks, strategic caching (Redis, fragment cache), CDN for assets, monitoring (Sentry, Ahoy, Grafana).
9. Analytics and product metrics
Ahoy/Mixpanel/PostHog tracking for MRR, churn, DAU/MAU, time-to-value, NPS. Admin dashboards (activation funnel, cohort retention). Outbound webhooks for HubSpot/Salesforce on the enterprise client side.
Written manually, this specification often takes dozens of hours. Flowayz generates it in a few minutes from your brief.
Generate my specification →Pitfalls to avoid
- Choosing a multi-tenant 'database per tenant' architecture without a matching infrastructure budget: it breaks at 50 tenants.
- Building onboarding last: 60% of users leave within the first 7 days if the experience is confusing.
- Underestimating billing: poorly handled Stripe webhooks = missing invoices, double charges, angry clients.
- Ignoring GDPR compliance at the start: forced rework in year 2 = 3-6 months of frozen development.
- No limits on plans: a Free user consuming 100 GB breaks the product's economics.
Frequently asked questions
How much does a SaaS specification document cost?
Writing the spec alone: 2,000 to 8,000 EUR if assigned to a consultant (15-30 h of work), or 5 minutes and 0 EUR with an AI generator such as Flowayz. The real cost lies in what the spec prevents: under-specifying a SaaS costs on average 3 to 5 times the initial budget in rework.
How long does it take to build a SaaS MVP in 2026?
8 to 12 weeks if the scope is strictly limited (1 persona, 3 features, 1 simple pricing plan with Stripe Checkout). Beyond that, you leave the MVP to enter a full v1 (16-24 weeks). 90% of MVPs that fail were over-scoped from the start.
Should a mobile app be planned in the SaaS spec?
Not at the MVP stage. A responsive web SaaS (Hotwire, PWA) covers 95% of B2B cases in 2026. A mobile app only makes sense if the use case is mobile-first (GPS tracking, product scanning, critical notifications). Otherwise, postpone by 12-18 months.
Which tech stack for a B2B SaaS in 2026?
For a small/medium tech team: Rails 8 + Hotwire + PostgreSQL + Redis + Solid Queue + Kamal for deployment. JavaScript alternative: Next.js + tRPC + Prisma + Postgres. Avoid 'trendy' stacks without a team that masters them — technical debt explodes within 6 months.
How to handle multi-tenancy in a SaaS?
Three options: database per tenant (maximum isolation, infrastructure cost x number of tenants), schema per tenant (standard compromise), row-level security with a tenant_id column (scales but adds complexity). The choice depends on data sensitivity and target size. For < 500 B2B tenants, row-level security is enough in 80% of cases.
Generate your specification in 5 minutes
Flowayz turns your brief into a complete professional specification using 22 AI assistants. Free for life, no credit card.
Open my free account →