How to make an app · Founder's guide

How to build a SaaS product
from scratch

To build a SaaS product from scratch, pick a painful, frequent problem for a specific type of business, validate it with 10–20 conversations and pre-sales, build a narrow MVP that solves one workflow end to end, then add the SaaS essentials — accounts and teams, multi-tenant data, subscription billing, onboarding and analytics. Win your first 10 customers by hand before scaling marketing.

By , FounderUpdated 6 min read

Share

Quick answer: How do I build a SaaS product from scratch?

  1. Problem — painful, frequent, owned by a buyer with a budget.
  2. Validate — 10–20 interviews and at least a few pre-sales or pilot commitments.
  3. MVP — one workflow, end to end, for one customer type.
  4. SaaS essentials — auth and teams, multi-tenancy, billing, onboarding, analytics, security.
  5. Go-to-market — first 10 customers by hand; then a repeatable channel.

Key takeaways

  • The best SaaS ideas replace a spreadsheet, a WhatsApp group or a manual process that someone already pays for in time.
  • Charge from the first customer; free pilots rarely tell you whether people will pay.
  • Design multi-tenancy, roles and audit logs in from the start — retrofitting them is painful.
  • In India, plan billing early: Stripe is invite-only for Indian businesses, so many use Razorpay or similar for subscriptions.
  • Retention is the metric that decides a SaaS business. Watch activation and churn before growth.

SaaS has a seductive reputation: build once, sell forever, collect revenue every month. The reality is that a SaaS product is a promise renewed every month — and the customer can cancel any time. That changes how you should build it. Here is the path from blank page to paying customers, with the parts most first-time founders get wrong.

How do I build a SaaS product from scratch? At a glance: Problem; Validate; MVP; SaaS essentials; Go-to-market.
At a glance: How do I build a SaaS product from scratch?

Step 1: choose a problem worth paying for

Good SaaS problems are painful, frequent and owned by someone with a budget. The tell-tale sign: a business is already solving it badly — with a spreadsheet, a WhatsApp group, a part-time person or a pile of paper.

Checklist: Step 1: choose a problem worth paying for — Who exactly feels the pain? (Role, company size, industry); How often? (Daily or weekly beats yearly); What does it cost them today in time, money or errors?; Who signs off on paying for a fix?; What do they use now, and why do they hate it?.
Step 1: choose a problem worth paying for
  • Who exactly feels the pain? (Role, company size, industry)
  • How often? (Daily or weekly beats yearly)
  • What does it cost them today in time, money or errors?
  • Who signs off on paying for a fix?
  • What do they use now, and why do they hate it?

Step 2: validate before you build

Talk to 10–20 people who have the problem. Ask about what they did last time, not whether they like your idea — the approach popularised by Rob Fitzpatrick's The Mom Test3. Then ask for a commitment: a paid pilot, a pre-order or a letter of intent. Polite interest is not validation; money and time are.

See how to validate an app idea for scripts and cheap tests.

Step 3: build a narrow MVP

Solve one workflow end to end for one customer type. A clinic appointment SaaS does booking, reminders and a daily schedule — not billing, inventory and payroll on day one.

Step 4: add the SaaS essentials

The SaaS essentials and the mistakes to avoid
EssentialWhy it mattersCommon mistake
Accounts, organisations and team invitesB2B buyers share access across a teamBuilding single-user only and retrofitting teams later
Roles and permissionsAdmins, members and read-only usersHard-coding "admin" checks everywhere
Multi-tenant data modelEach customer's data stays separateMissing the organisation filter in one query — a data leak
Subscription billingPlans, trials, upgrades, invoices, failed-payment handlingBuilding billing logic from scratch
OnboardingGets new users to their first success fastA blank dashboard with no guidance
AnalyticsTracks activation, usage and churn signalsMeasuring sign-ups only
Security and audit logsTrust with business customersTreating security as a later problem

The OWASP Top 10 is a good security baseline for any web SaaS4, and India's DPDP Rules apply to personal data you process for customers5.

Step 5: billing in India

Plan payments early. Stripe currently accepts Indian businesses by invite only1, so many Indian SaaS companies use domestic gateways with subscription support, such as Razorpay, whose standard pricing is published on its site2. For international customers, check which processors can serve your business, and get advice from a chartered accountant on GST — export of services has its own rules.

Step 6: onboard by hand, then make it self-serve

For your first ten customers, set them up personally. Watch where they get stuck, what they ask, and what they never use. Then turn those lessons into onboarding: templates, sample data, checklists and in-app guidance that get the next hundred customers to their first success without you.

Step 7: measure what decides SaaS

Share of new accounts reaching first value
Activation
Share of customers still active after 3, 6, 12 months
Retention
Share of customers or revenue lost each month
Churn
Revenue kept and expanded from existing customers
Net revenue retention

If activation is low, fix onboarding. If retention is low, fix the product. Only then spend heavily on acquisition — pouring users into a leaky product is the most expensive way to learn.

Common mistakes

Common mistakes: Building for everyone; Too many features; No pricing until launch; Ignoring churn.
Common mistakes

Building for everyone

"Small businesses" is not a customer. "Physiotherapy clinics with 2–10 therapists" is.

Too many features

Every feature is something to support, document and secure forever.

No pricing until launch

Pricing is a product decision. Test it with real buyers early.

Ignoring churn

New sales hide churn for a while. Then they don't.

A SaaS product that stalls during trials usually has an onboarding or activation problem rather than a feature gap — exactly what a SaaS UX audit looks for.

Key terms, defined

SaaS — software as a service, sold by subscription and accessed online. Multi-tenancy — one app serving many customers with separated data. Activation — a new user reaching first meaningful value. Churn — customers or revenue lost over a period. MRR — monthly recurring revenue. Net revenue retention — revenue retained and expanded from existing customers.

Frequently asked questions

How much does it cost to build a SaaS product?

A focused SaaS MVP — one workflow, accounts and teams, billing, onboarding and an admin panel — typically costs ₹8–30 lakh with an Indian agency, or much less with a technical founder. Running costs include hosting, email, monitoring and payment fees, and grow with customers.

How long does it take to build a SaaS MVP?

Usually 8–16 weeks for a focused first version, including design and testing. Founders with strong technical skills and AI coding tools can ship a narrow MVP faster; enterprise-grade security and integrations take longer.

What are the essential features of a SaaS product?

Sign-up and login, organisations and team invitations with roles, a multi-tenant data model, subscription billing and invoices, onboarding that gets users to value quickly, in-app help, analytics on activation and usage, an admin panel, and security basics such as audit logs and backups.

How do Indian SaaS companies collect subscription payments?

Many use Indian payment gateways with subscription support, such as Razorpay, for domestic customers, and international processors for global customers where available. Stripe accepts Indian businesses by invite only, so plan alternatives. Consult a chartered accountant on GST, especially for export of services.

How do I get my first SaaS customers?

From the people you interviewed during validation, your network, communities where your buyers gather, and direct outreach. Sell by hand, onboard each customer personally, and learn why they buy and stay before investing in ads or content at scale.

What is multi-tenancy in SaaS?

Multi-tenancy means one application serves many customer organisations while keeping each organisation's data separate and secure. It is usually done by tagging every record with the organisation it belongs to and enforcing that boundary in every query.

Sources

  1. Stripe Support — Stripe accounts are invite-only in India
  2. Razorpay — Pricing
  3. Rob Fitzpatrick — The Mom Test
  4. OWASP — Top 10 web application security risks
  5. Press Information Bureau — Government notifies DPDP Rules (2025)
  6. Checked October 23, 2026. Figures that change — fees, salaries, prices — are reviewed every six months; if something is out of date, tell us.
Pass it on

Know someone who'd enjoy this?

Send it to them — one tap, no sign-up. Good ideas travel best between friends.

Keep exploring

Where to go from here

Join free

Get the ideas, not the noise.

Sign up with Google and we’ll send you short UX psychology tips by email — why people tap, stall and leave, and what to do about it. Unsubscribe anytime. Prefer something to keep? Get the free Laws of UX guide as a PDF.

Get the free Laws of UX PDFFree · no spam · unsubscribe anytime
Before you launch

Make sure the first screen makes sense.

A behavioral UX audit of your app or SaaS product: why users hesitate, stall and leave, and a prioritized fix list. Fixed price, 2–4 weeks.

Free certification

Turn what you know into a credential.

Free, test-based UX, UI and product certifications. Answer real product scenarios, graded on our server, and earn a founder-signed certificate anyone can verify and you can add to LinkedIn.

  • Credential ID
  • QR verification
  • LinkedIn-ready
Free PDF · 74 pages · 2 editions

The Laws of UX, in one field guide

60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.

Pick your edition
Free. No card, no paywall — just your email.
Free PDF · 74 pages

Get Laws of UX by email

Choose your edition

You’ll also get occasional UX psychology tips. Unsubscribe anytime. Privacy policy

Free PDF · 90 pages · 2 editions

100+ Subscription Paywalls, decoded

110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.

  • 110 paywalls rated
  • 34 Laws of UX
  • 12 frameworks

Which paywall scored 4.8 out of 5, and which scored 2.6? It’s all inside.

Pick your edition
Free. No card, no paywall — just your email.
Free PDF · 90 pages

Get 100+ Paywalls, Decoded by email

Choose your edition

You’ll also get occasional UX psychology tips. Unsubscribe anytime. Privacy policy