Glossary
Zero-Based Budgeting
Building budgets from zero each period, justifying every expense without historical anchors.
By Amit Tyagi, Fitoor Capital · AletheiaAI Glossary
Definition
Zero-based budgeting (ZBB) requires teams to justify every rupee of spending from scratch each cycle, rather than incrementing last year's budget. Each expense must be tied to a business outcome. You start at zero, then allocate based on current priorities and runway.
Traditional budgeting anchors to prior spend—if you spent ₹10 lakh last quarter, you budget ₹12 lakh next quarter by default. ZBB rejects this. Instead, teams rebuild budgets quarterly or monthly, forcing hard choices: Which channels drive CAC below ₹500? Which hires are critical to hit ARR targets?
For early-stage startups with 6–18 months of runway, ZBB surfaces waste. A Series A company might discover that a 3-person operations team costs ₹18 lakh monthly but delivers what two engineers could automate in 4 weeks. ZBB makes that visible. It also prevents the "use it or lose it" culture common in larger orgs, where teams inflate requests to protect budgets.
The discipline is uncomfortable but valuable at scale too. Companies like Amazon and Hindustan Unilever use variants of ZBB to stay capital-efficient. For startups burning 20–30% monthly, ZBB often extends runway by 2–3 months without cutting core product investment.
India Context
Indian startup founders face unique pressure: most VC rounds here assume 18–24 month runways, tighter than US norms. Using ZBB monthly—not quarterly—is common practice. The GST compliance burden also makes ZBB useful: every expense gets categorized for tax purposes anyway, so budget justification aligns naturally with compliance records.
Regulatory context: SEBI doesn't mandate ZBB, but startups raising from institutional VCs (Sequoia, Accel, Tiger) are often required to produce monthly zero-based forecasts as part of financial covenants. This practice has grown since 2018. Additionally, startups claiming R&D tax credits under Section 35(2AB) of the Income Tax Act must document R&D spend clearly—ZBB forces this rigor upfront.
Indian benchmarks: A Series A SaaS startup in India should target 40–50% CAC payback period and 3–4x net dollar retention. ZBB helps enforce these by cutting spend that doesn't move these metrics. Overheads (rent, salaries) should not exceed 40% of revenue for Series B+ companies; ZBB catches drift early.
Example
Dunzo, the quick-commerce startup, publicly discussed cutting 50% of workforce in 2023. Retrospective analysis suggests ZBB discipline earlier—scrutinizing every city's profitability month-on-month rather than assuming venture-backed growth—would have flagged unsustainable unit economics. A ZBB approach would have asked: "Is Bangalore's delivery cost ₹45 per order, but revenue only ₹60? Does this improve in 6 months?" If not, reallocate budget.
Practical example: A ₹2-crore ARR B2B SaaS startup (e.g., HR tech) using ZBB might discover that its ₹30 lakh/month Bangalore office rent serves 8 employees, while its core unit (sales + product) could operate from a ₹8 lakh/month co-working space. That ₹22 lakh monthly savings extends runway by 2 months and funds two extra engineers—shifting the budget from fixed overhead to variable product spend.
Frequently Asked Questions
Related Terms
Apply what you've learned
See this term at work on real Indian companies.
AletheiaAI checks market narratives against the filings behind them — screener, company disclosures, and sector reports across India’s listed companies, free.