I've watched dozens of founders build SaaS products in the last five years — some at Excellence, many of our clients. The patterns that separate the products that ship and grow from the ones that die in beta are remarkably consistent. Here's the honest playbook.
Stage 0: Validate before you build
The single biggest mistake we see: founders building for 6 months without talking to 20 prospective customers. By the time the MVP is "ready", the market has either moved or never wanted it in the first place.
Spend the first 4 weeks doing customer interviews. Real ones. Not "would you use this?" but "what's the most painful workflow in your job right now?" Listen for the same problem mentioned 3+ times.
Stage 1: Pick the right MVP scope
Your MVP should solve one problem painfully well — not 5 problems mediocre-ly.
Ruthlessly cut: dashboards, settings pages, multi-user, SSO, exports, integrations beyond the one your customer absolutely needs. All of those can come later. Most of them shouldn't.
Stage 2: Tech stack that ships fast
For an Indian SaaS founder building a B2B tool in 2026, our recommended stack:
- Frontend: Next.js (React + server-side rendering).
- Backend: Node.js with Express, or just Next.js API routes for simpler apps.
- Database: PostgreSQL on Supabase or Neon. Don't roll your own DB hosting.
- Auth: Clerk or Auth0. Don't build auth from scratch.
- Payments: Razorpay for Indian customers, Stripe for global. Often both.
- Hosting: Vercel for the frontend, Render or Railway for any standalone backend.
- Email: Resend or Postmark. Transactional only at first.
- Monitoring: Sentry + Posthog from day one.
This stack lets a single full-stack engineer ship an MVP in 6–8 weeks.
Stage 3: Pricing from day one
Most early SaaS founders price too low because they're afraid to charge. Charge more than you think.
Our heuristic: if no one is complaining about your price, you're charging too little.
Pricing structure: start with one plan. Don't ship three tiers on day one — you don't have the customer data to know what features belong where.
Stage 4: Distribution > product
Most failed SaaS products had decent products and no distribution strategy.
Before you ship code, you should know:
- Where your first 100 customers will come from. Specifically. Not "via SEO" — "via the LinkedIn DMs I'm going to send to 500 founders of pre-Series-A startups in India".
- What you'll do for the next 100.
- What channel will scale to 10,000.
If you don't know the answers, the product is a bet with no exit plan.
Stage 5: Onboarding is the product
The first 5 minutes of a new user's experience determines whether they ever come back. Spend disproportionate effort on:
- Time-to-first-value (how quickly they see the product do something useful).
- Email/WhatsApp follow-up if they drop off.
- One-click sample data so they're not staring at an empty dashboard.
Stage 6: Pre-revenue traction signals
Watch these before optimising for MRR:
- Day-7 retention (do users come back a week later?).
- Activation rate (did they hit the "aha moment"?).
- NPS or simple "would you be disappointed if this product disappeared?" surveys.
If 40%+ say they'd be "very disappointed", you have product-market fit. Below that, you don't — keep iterating.
Stage 7: First ₹1L MRR
At Excellence, we've seen founders cross this milestone in two patterns:
- Slow-and-steady SEO/content: publish 2 posts/week for 6 months, organic compounds.
- Cold outreach: 100 emails/day to qualified prospects. Crude, effective.
Pick one and execute relentlessly. Don't run both half-heartedly.
Where Excellence fits
We've built the engineering side of several Indian SaaS products from MVP to ₹50L+ ARR. If you're at the "I have an idea and need someone to build it" stage, talk to our team. We're equally happy to be a thinking partner before any code is written.