The business plan that gets funded

What do lenders and investors actually read first?

Not the vision. Whether it is a bank manager, an NBFC credit officer, a family friend with ₹30 lakh, or an angel who already owns two cafés, every reader of a restaurant plan performs the same 30-second scan: flip to the numbers page, check whether the break-even math is honest, check whether you have priced the licences and the deposit, and check what the cash balance looks like in month six. Pass that scan and they go back and read the concept with interest. Fail it and the concept never gets read.

This has a liberating consequence: you do not need to write well, you need to count well. A plan whose cash-flow line dips in months two through five and recovers on realistic covers is more fundable than a hockey stick, because everyone who has money to lend has seen a restaurant before. The plan is not a pitch, it is proof that you have already run the restaurant on paper and survived.

The three reader types do weight the pages differently, and it helps to know which one you are writing for. A bank or NBFC reads for downside: collateral, the deposit, licence timelines, whether the EMI survives a bad quarter, well-run restaurants typically net 8–15% after everything, and a lender wants to see you solvent even at the bottom of that band. An equity investor reads for upside and repeatability: unit economics that improve with volume, and a second-outlet story. Family money reads for honesty above all, they will not audit the yields on your paneer, but they will remember every promise. The same 12 sections serve all three; what changes is which number you lead with.

What are the 12 sections of a fundable plan?

The downloadable template follows this exact structure. What each section must actually prove:

1. One-page summary, format, location, ask, break-even month, payback horizon. Written last, read first.
2. Concept and format, what you serve, to whom, at what average ticket, and why this format (café, QSR, casual dining, cloud kitchen) fits this demand.
3. Market and location, the catchment in walkable or deliverable terms: offices, residences, footfall rhythms, and who already feeds these customers today.
4. Menu and pricing strategy, a costed sample menu, not an aspirational one. Per-dish pricing logic belongs here; the menu engineering guide shows how to build it.
5. Unit economics, THE page. Average ticket, covers per day, food-cost %, gross margin per cover, monthly fixed costs, break-even covers. One page, no adjectives.
6. Startup cost and funding ask, itemised capex, deposit, licences, opening stock, and how much working capital you are holding back.
7. Licences and compliance plan, the applicable stack, fees and the filing timeline. Reality check: government fees run roughly ₹15,000–₹60,000 excluding liquor, on a 30–90 day critical path, the licence guide has all twelve with issuers and renewals.
8. Operations plan, kitchen layout logic, staffing plan with salaries, supplier strategy (two vendors per critical ingredient), and daily controls.
9. Technology stack, billing, KDS, inventory, GST reporting, and who reads which report daily. Lenders increasingly read this as a proxy for whether the owner will actually know their numbers.
10. Marketing and channel plan, launch plan, aggregator strategy and its costs, and the direct-channel plan that protects margin.
11. Financial projections, monthly P&L and cash flow for the first 18–24 months, built from the unit economics, with the assumptions stated where the reader can attack them.
12. Risks and mitigations, the honest list: slow ramp, key-staff exit, rent escalation, licence delay. Naming risks reads as competence, not weakness.

Which four numbers decide whether you get funded in 2026?

Everything in the plan hangs off four numbers. Each has a calculator, so none of them needs to be a guess.

1. Startup cost, by format. Indian restaurant capex runs ₹5 lakh to ₹1 crore and beyond depending entirely on format, format is destiny. Typical bands: a cloud kitchen at ₹5–15 lakh, a QSR counter at ₹8–25 lakh, a café at ₹20–60 lakh, casual dining at ₹40 lakh–1 crore, with bar-and-dining formats going well past that. Itemise yours honestly, deposit (often 6–10 months of rent in metros), fit-out, kitchen line, licences, opening stock, then pressure-test whether the resulting fixed-cost load is survivable with the break-even calculator. The full cost anatomy is in the guide to opening a restaurant.

2. Monthly break-even covers. Fixed costs ÷ (average ticket × gross margin) = covers per day to break even. This is the single most-checked number in the document. Run it in the break-even calculator, then apply the acid test: if break-even exceeds 60% of realistic capacity, the plan has a lease problem, and no marketing section can fix a lease problem.

3. Food-cost % target. The healthy band for most Indian formats is 28–32% of revenue, and the plan must show you arriving there through costed recipes, not assumption. Build per-dish costs with the food-cost calculator, price dishes back from target with the menu price calculator, and read the food-cost guide for yields and sub-recipes. A plan that says "30% because industry standard" tells the reader you have not yet costed a single dish.

4. Month-6 cash position. The number that kills real restaurants. Model cash monthly, not revenue, cash, including deposit outflow, capex schedule, the slow ramp of months one to three, GST outgo (size it with the GST calculator), and salaries that are due whether or not covers show up. Hold 20% of the total budget as working capital for the first 90 days. If modelled month-6 cash goes negative, the ask is wrong, raise more or spend less, but do not open and hope.

How do the numbers change by format?

One row of model logic per format, the template carries a fuller version of this table to fill in:

Two format-specific notes. Cloud kitchens are the capital-efficient test of an unproven concept, the cloud kitchen guide covers the 30–45 day version of this plan, and cloud kitchen software is what makes the multi-brand math legible per brand. And for any dine-in format, the projections section should show weekday and weekend as different businesses, because they are.

City choice moves these bands too, deposits, fit-out rates and licence sequencing all differ between a Mumbai high street and a tier-2 market, so anchor the startup-cost section to quotes from your actual city, not a national average. Whatever the format, the reader should be able to trace every projection row back to a stated assumption: covers × ticket × days for revenue, costed recipes for food cost, the salary table for staff. A projection the reader can rebuild is a projection the reader can trust.

Which mistakes kill restaurant business plans?

The same handful, plan after plan:

• Fantasy footfall. Projecting 80–100% occupancy from month one. Lenders discount the whole document the moment they see it. Model a slow ramp and let month one look bad on paper, it will in life.
• The missing licence line. No budget and no timeline for licences, then shock when the trade licence takes its 30–90 days. Put ₹15,000–₹60,000 and the filing calendar from the licence guide into section 7 and the Gantt into section 11.
• No working capital. The deposit and fit-out consume the entire raise, and the restaurant opens broke. Hold 20% back; undercapitalisation kills more restaurants than bad food.
• Ignoring aggregator economics. Delivery revenue booked at menu price, with commissions nowhere in the P&L. If aggregators are in the channel plan, their take must be in the margin math.
• Round-number food cost. A single assumed percentage across the menu instead of costed recipes. This is checkable in one question, "walk me through the costing of your butter chicken", and plans die on it.
• No owner salary. A plan where the founder eats air for a year is not conservative, it is unstable, and experienced readers know it.

Where do you get the template?

Right here: download the CountStand restaurant business-plan template (2026, .docx), free, no email gate, no watermark nonsense. It carries the 12 sections above with India-specific prompts in each: the licence checklist references the actual issuing authorities, the unit-economics page is pre-structured around the four numbers, and every placeholder tells you which calculator produces the figure that belongs there. Fill the numbers first and the words last. A plan whose numbers are real writes its own prose.

What happens after the plan? From paper to opening day

A plan that gets funded starts a 90-day clock, leases, licences, fit-out, hiring, and the complete opening guide maps every week of it. One choice in section 9 deserves making before the doors open rather than after: the operating stack. Opening on spreadsheets and a bill book means rebuilding operations twice, and it means your investor updates are guesses. CountStand is an AI-native restaurant operating system for India, offline-first billing, KDS, inventory, GST & compliance, and an autonomous AI manager, in one platform, from ₹999/mo per outlet. Practically, that means the numbers your plan promised, covers, ticket, food cost, break-even, are measured from the first bill, and the month-6 review against plan takes minutes instead of a weekend of reconstruction. The full case is on the restaurant POS page, current plans are on the pricing page, and if you want the day-one stack demonstrated before you commit to anything, book a demo.