Define the operating case first.
Each numerical case identifies its format, location, scale, sales unit, channels and forecast period. The restaurant examples assume fictional Austin operations, USD and January 2027–December 2029. Prelaunch spending is reported separately from the three operating years.
Counter transactions, dining covers, catering meals and delivery orders have different meanings. We compare the formats without blending their inputs into a supposed average restaurant.
Calculate from a single set of inputs.
The editable financial model contains revenue streams, costs, staffing, assets, funding, working-capital timing and tax assumptions. A saved calculation supplies the annual and monthly results used in the example, business-plan appendix, financial report and pitch. The text does not supply a second set of forecast totals.
Before a case is marked complete, the accounting checks must reconcile and required numerical inputs must be supplied. A filled illustrative input is still an assumption. Reconciliation confirms the calculation relationships; it does not verify customer demand or a supplier price.
Keep financial measures distinct.
Revenue is the saved sales result after modeled discounts and refunds; customer sales tax and tips are excluded in these cases. EBITDA is after operating expenses and paid staff but before depreciation, interest and income tax. Net income includes the saved depreciation and tax provision. Cash also reflects assets, financing and working-capital timing.
Startup uses combine prelaunch assets, expensed setup and opening stock. Opening cash is proposed financing less those uses in these equity-only examples. The minimum cash balance is the lowest modeled balance, including prelaunch. A funding gap, proposed external ask, operating break-even and project payback answer different questions.
Separate scenario inputs from market evidence.
Sales targets, wage and employer allowances, premises, equipment, rent and funding in the examples are illustrative unless explicitly identified otherwise. The cases are not market averages, quotations or operating results. A date on a source does not make it evidence for a different location or format.
The public business plans omit a research bibliography, as part of their presentation format. Internal evidence is retained. Articles link relevant outside material where it supports the explanation. Unknown site work, refundable deposits and actual entity tax treatment still require review.
Test the same operating logic.
The restaurant calculators start with the same format-specific model used in the complete examples. Changes are recalculated with the same financial engine. Full service derives covers from seats, planned turns and target utilization. Delivery first keeps direct and marketplace orders separate, applying the commission to marketplace sales.
The tools expose a selected set of assumptions. Other saved inputs remain at their disclosed defaults. One collection-delay input applies to all streams, which is a simplification rather than a platform payout promise. The tools do not save a project, create a quotation or invoke AI generation.
Use each visual for a specific job.
Generated scenes explain the proposed operating setting and are labeled conceptual. Charts use the saved scenario values. Financial and pitch previews are actual pages of the delivered PDFs. An attractive scene is not evidence of a real site or a technical floor plan.
Read exact amounts in the adjacent tables and the full financial report. Display rounding in a chart does not change the underlying saved model.
Use a scenario to identify the next check.
Replace the weakest decision-driving assumptions with paid tests, written quotes and actual contracts. Then save a revised model and refresh all dependent documents together. No sample establishes profitability, investor return, lending approval or legal compliance for your business.
Understand the public calculator request.
The calculator sends numerical assumptions to a calculation endpoint on this website. Those values appear in the request URL. The calculation runs in temporary memory, does not call an AI provider and does not create an application account project.
Temporary calculation and request logging are different processes. Hosting services can receive the URL and technical connection data. Our privacy policy describes the actual log handling and retention. Use numerical scenarios rather than confidential or personal information.