From ₹0 to ₹8.4 Lakh MRR: Bootstrapping a Micro-SaaS With No Funding

How a two-person Indian SaaS reaches ₹8.4 lakh of monthly recurring revenue in 26 months on ₹4 lakh of founder savings, and the runway discipline that made it survivable.

Micro-SaaS Bootstrap Model

Modelled teardown — no funding, two founders

Sector
B2B workflow SaaS
Location
Pune, Maharashtra
Monthly recurring revenue

₹8,40,000

Month 26. 280 accounts at an average of ₹3,000 MRR.

Customers
280
ARPA
₹3,000
New MRR added / month
₹1,12,000
Monthly churn
2.8%
Net revenue retention
104%
Fixed monthly costs

₹3,45,000

41% of MRR. Cloud is the largest line and the only one that scales with usage rather than headcount.

Founder draws (2)
₹1,40,000
Contract engineer
₹80,000
Cloud and infrastructure
₹62,000
Tools and SaaS
₹28,000
Compliance and CA
₹35,000
Net margin

59.0%

₹4,95,000 of monthly contribution after every cost. Zero investor capital means this is entirely the founders'.

Gross margin
86%
Contribution / month
₹4,95,000
Operating margin
59.0%
Annual free cash flow
₹59,40,000
CAC payback

4.1 months

Blended ₹10,600 to acquire an account at ₹3,000 MRR and 86% gross margin.

Blended CAC
₹10,600
Gross profit / account / month
₹2,580
LTV (churn-adjusted)
₹92,143
LTV : CAC
8.7×
Payback
4.1 months

This is a modelled teardown, not an interview. It reconstructs a bootstrap path from the platform's own benchmark bands: two founders, no external capital, ₹4,00,000 of personal savings, and a B2B workflow product at ₹3,000 average revenue per account. The endpoint is ₹8,40,000 of monthly recurring revenue at month 26, a 59% net margin, and a CAC payback of 4.1 months.

The reason this path works is not product genius. It is that the company never once let runway fall below nine months before it was contribution-positive, which meant no decision in the first two years was made under duress. ₹4,00,000 of savings divided by an initial net burn of ₹42,000 a month is 9.5 months — barely enough, and the founders knew it on day one.

The constraint that shaped every decision

With ₹4 lakh and a 9.5-month runway, there is no room for a paid acquisition experiment, a conference booth, or a third hire. The only available growth engine is founder-led outbound to a narrow niche, and the only available pricing strategy is to charge from the first customer — no generous free tier, no “we will monetise later”. That constraint is usually described as a disadvantage. In practice it removed the three most common ways bootstrapped SaaS companies die: building for an imagined customer, hiring ahead of revenue, and pricing below cost to chase growth.

Every figure in this teardown is reproducible with the Runway & Zero-Cash Forecaster and the CAC payback tool. The point of publishing the model is that you can substitute your own numbers and see where the path breaks.

Month 0–6: sell before you build

The first eleven customers came from 340 cold conversations in a single vertical — Indian accounting firms with 5–20 staff — and were sold a workflow that was half manual on the founders' side. Pricing was ₹2,500 a month from day one, on an annual contract with monthly billing. By month 6, MRR was ₹27,500 across 11 accounts, fixed costs were ₹42,000, and net burn was ₹14,500. Runway had extended from 9.5 months to 27.

MonthMRRFixed costsNet burnRunway
1₹2,500₹42,000₹39,50010.1 mo
3₹12,500₹42,000₹29,50013.6 mo
6₹27,500₹42,000₹14,50027.6 mo
9₹62,500₹78,000₹15,50025.8 mo
The first six months in aggregate. The critical number is the revenue line crossing fixed costs — not the customer count.

Month 7–14: the first hiring decision

The first hire was not an engineer. It was a contract support person at ₹22,000 a month, because founder time spent on support tickets was the binding constraint on sales conversations. Only after support was offloaded did the founders add an engineer, and only as a contract engagement at ₹80,000 a month — deliberately variable, deliberately cancellable, and deliberately not a headcount commitment. Total fixed costs at month 14 were ₹2,05,000 against ₹3,60,000 of MRR.

The pricing change at month 11 mattered more than any hire. A move from a flat ₹2,500 to three tiers anchored at ₹3,000 raised average revenue per account by 34% with a churn increase of just 0.4 percentage points. Existing customers were grandfathered for six months, which is what kept that churn number small.

Month 15–26: compounding without a funding round

From month 15 the company was contribution-positive every month, so runway stopped being a constraint and growth rate became the only metric. New MRR added per month climbed from ₹38,000 to ₹1,12,000, almost entirely through referral and content rather than paid acquisition. At month 26 the blended CAC of ₹10,600 against ₹92,143 of churn-adjusted lifetime value gives an 8.7:1 ratio and a 4.1-month payback — comfortably inside the 12-month threshold below which paid acquisition is safe to scale.

LineMonthly% of MRR
MRR₹8,40,000100%
Cloud and infrastructure₹62,0007.4%
People (2 founders + 1 contract)₹2,20,00026.2%
Tools and compliance₹63,0007.5%
Contribution₹4,95,00059.0%
The end state. Notice that cloud cost is 7.4% of revenue — a managed micro-SaaS should not be spending 30% on infrastructure.

What would have broken this

  • A third co-founder. A 33% split on ₹4 lakh of savings is unworkable and the equity conversation would have consumed the runway.
  • A free tier. At 280 accounts and 2.8% monthly churn, a 10:1 free-to-paid ratio would have tripled infrastructure cost for no revenue.
  • One rupee of paid ads before month 12, when the product still needed founder-led explanation to close.
  • Filing the company as a private limited from day one. At ₹2,500 MRR the ₹12,000 incorporation plus ₹25,000 statutory audit is a meaningful fraction of the bank balance; a proprietorship or LLP was correct until month 18.
  • Treating the ₹4 lakh as capital rather than a deadline. It was the calendar, and treating it as anything else would have changed every decision.
This is an illustrative model, not advice or an interview. Your tax, compliance and cost structure will differ, and a single wrong assumption about churn will invalidate the whole path. Model your own numbers before following any playbook.

What founders ask about this teardown

Can you really reach ₹8 lakh MRR without funding?

Yes, but not quickly. This model takes 26 months, is contribution-positive from month 15, and depends on a high-gross-margin product with low churn. Lower margins or higher churn push breakeven beyond the point where personal savings run out.

What is the right first hire for a bootstrapped SaaS?

Whatever is consuming the founder's selling time. In this teardown that was support, not engineering — and it was a contract engagement rather than a headcount, so it could be cancelled without severance if growth stalled.

How much should a micro-SaaS spend on cloud?

Below 10% of revenue is the benchmark for a managed micro-SaaS at this scale; this model runs at 7.4%. Above 20% usually means unoptimised queries, over-provisioned instances, or a product whose unit economics will not survive scale.

When should you raise prices?

When a pricing change can be grandfathered. Raising prices on new customers while protecting existing ones caps the churn impact at new signups, which in this model was 0.4 percentage points for a 34% ARPA increase.

Should a bootstrapped company register as a private limited?

Only when the compliance cost is a small fraction of revenue. At ₹2,500 MRR, ₹12,000 of incorporation plus a mandatory ₹25,000 statutory audit is disproportionate. An LLP or proprietorship is usually correct until revenue is stable.

Every figure in this teardown is reproducible. Substitute your numbers and see where the path breaks.