Finance & FP&A

How to forecast runway and months of cash as Restaurant and Hospitality Founders

Finance & FP&AFor Restaurant and Hospitality Founders2 apps12 steps~24 min to set up

You run the numbers every Monday morning by hand: pull last week's sales from Toast or Square, match deposits against your bank account, text your bookkeeper for the QuickBooks balance, and then guess at how many months you can survive if the private dining room stays half-empty. Your payroll runs through 7shifts or Homebase but those labor costs don't show up anywhere near your P&L until your bookkeeper closes the month — sometimes three weeks after the period ends. By the time you know your real cash position, you've already made two scheduling decisions and signed a produce contract you maybe couldn't afford. You need a number that updates daily, not a spreadsheet that's always last month's problem.

Build this on Starch → See the apps used

Finance & FP&AFor Restaurant and Hospitality Founders2 apps12 steps~24 min to set up

Outcome

What you'll set up

A live runway dashboard that pulls your actual bank balances and transaction data on a schedule, so you know today's months-of-cash figure without calling anyone

Side-by-side scenario models — slow February, a private dining surge, a new hire, a rent escalation — so you can see which decision changes your runway before you commit

A weekly digest that lands in your inbox before service starts, summarizing cash balance, net burn for the trailing 30 days, and the scenario most likely to force a decision in the next 90 days

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Runway Analysis Scenario Analysis

Data sources & config

Starch syncs your Plaid bank feed data on a schedule — transactions, balances, and categorized spend update automatically so runway calculations always reflect real deposits and real outflows. If you process revenue through Stripe (gift cards, online ordering, reservation deposits), Starch syncs your Stripe charges and payouts on the same schedule. Square and Toast don't have scheduled-sync integrations in Starch, but Starch connects to Square from its integration catalog and the agent queries it live when your dashboard runs; for Toast, Starch automates your Toast portal through your browser — no Toast API needed. Slack is connected for the weekly digest.

Prompts to copy

Connect my Plaid bank feeds and show me net cash burn for the last 6 months, broken down between food and beverage purchasing, labor, rent, and everything else. Project forward 18 months at current burn.

Build me three scenarios side by side: one where covers stay flat, one where I add a second brunch seating in April and revenue goes up 15%, and one where I lose my best bartender and have to hire two people at once. Show runway and break-even for each.

Every Monday at 7am, send me a Slack message with my current cash balance, last week's net burn, and which of my three scenarios I'm tracking closest to.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect Plaid in Starch — this is a scheduled-sync connection, so your bank balances and categorized transactions update automatically every day, including your primary operating account and any reserve accounts you hold.

2 If you take online orders or sell gift cards through Stripe, connect Stripe as a scheduled-sync provider so revenue hitting your Stripe account flows into the same runway calculation as your bank data.

3 For Square POS data, connect Square from Starch's integration catalog — the agent queries your sales figures live each time your dashboard loads, pulling daily totals and deposit timing.

4 If you use Toast, tell Starch to pull your daily sales summary from your Toast dashboard through browser automation — Starch logs in and reads the numbers the same way you would, no Toast API required.

5 Open the Runway Analysis app from Starch's App Store — it's pre-built for exactly this calculation. You'll see months of cash, net burn trend, and a 24-month projection within a few minutes of connecting your accounts.

6 Customize the expense categories to match how your restaurant actually spends money: split 'cost of goods' into food cost and beverage cost, separate your salaried kitchen staff from hourly FOH, and tag your rent and insurance as fixed overhead so the burn breakdown is actually useful.

7 Once the baseline is running, open the Scenario Analysis app and describe your first scenario: tell Starch the assumption you want to test — a second brunch seating, a rent increase in Q3, dropping a slow weeknight — and the app builds the projection against your real Plaid and Stripe baseline.

8 Add at least two more scenarios that bracket the realistic outcomes: one where nothing changes (your planning floor) and one stress case (a bad winter, a key departure, a health inspection closure week). Keep all three open side by side.

9 Tell Starch: 'Every Monday at 7am, post a summary to my Starch inbox with current cash balance, trailing 30-day net burn, and which scenario I'm tracking closest to.' Starch builds the automation and runs it without you touching it again.

10 Review the scenario outputs before any major commitment — new hire, equipment lease, menu reprint, private dining room renovation — so you're deciding with a number in front of you, not a gut feeling.

11 After each monthly close, update your Plaid-connected figures and re-run scenarios with any assumption changes. Since the data syncs automatically, the only thing you're updating is the assumptions, not the raw numbers.

12 Share a read-only link to the runway dashboard with your accountant or any investor who asks for a cash position update — one link, always current, no PDF exports required.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

February 2026 close — 62-seat neighborhood Italian restaurant, Chicago

Sample numbers from a real run

Operating account balance (Plaid, Feb 28)	84,200
Stripe deposits in transit (gift cards + Tock online)	6,400
Total available cash	90,600
Food cost — trailing 30 days (Plaid)	-28,500
Beverage cost — trailing 30 days (Plaid)	-9,800
Hourly labor — trailing 30 days	-31,200
Rent + CAM	-14,000
Utilities + misc fixed	-4,100
Net burn — February	-87,600
Implied monthly runway at current burn	1.03

February tells the story that every independent restaurant operator dreads reading. The Runway Analysis app pulled all of this automatically: $84,200 sitting in the operating account, another $6,400 in Stripe deposits from online gift card sales still clearing, so $90,600 total. But net burn for February came in at $87,600 — food cost running hot at 31% of revenue after a truffle special that didn't sell through, hourly labor up because of Valentine's Day double-staffing, and the quarterly insurance lump hitting in the same period. Months of cash: just over one. The Scenario Analysis app immediately flagged that the 'flat covers, tighten food cost to 28%' scenario extended runway to 2.4 months, while the 'add Sunday brunch, hold labor flat' scenario pushed it to 3.8. The owner used that output — not a spreadsheet, not a call with the bookkeeper — to decide to launch Sunday brunch in March and pull the truffle program from the menu immediately. The Monday morning Slack digest showed the new trajectory within two weeks.

Measurement

How you'll know it's working

Months of cash remaining at current net burn (updated daily from Plaid)

Food cost percentage — trailing 30 days vs. target (typically 28–32% for a full-service restaurant)

Labor as a percentage of revenue — split between hourly FOH and kitchen

Net burn vs. prior month — the direction matters as much as the number

Break-even covers per week under each scenario model

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

QuickBooks + monthly bookkeeper close

Your bookkeeper gives you an accurate picture but it's 3–4 weeks behind; you're making scheduling and purchasing decisions in a data vacuum every single week.

MarginEdge or Restaurant365

Purpose-built for restaurant cost control and AP, but neither tool gives you a forward-looking cash runway or scenario modeling without exporting to a spreadsheet first.

A spreadsheet you maintain yourself

Free and fully flexible, but it's only as good as the last time you updated it, and under-resourced restaurant operators update it inconsistently — which is exactly when it matters most.

Toast or Square built-in reporting

Great for sales and item-level margin, but neither tool sees your bank balance, your rent payment, or your payroll run — so runway is invisible to them by design.

On Starch RECOMMENDED

One platform — runway analysis, scenario planning all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

My sales go through Toast, which doesn't have a formal Starch sync — can I still use this?

Yes. Starch automates your Toast portal through your browser — it logs in and reads your daily sales summary the same way you would, then pulls that data into your runway dashboard. No Toast API is needed. The same approach works for any web-based system you can currently log into manually.

I use Square, not Stripe, for card processing. Does the runway calculation still work?

Yes. Connect Square from Starch's integration catalog and the agent queries your Square sales and deposit data live each time your dashboard runs. If you also have a Stripe account for online orders or gift cards, connect both — Starch combines them in the same runway calculation.

Is Starch SOC 2 certified? I'm connecting my bank account.

Not yet — Starch is not SOC 2 Type II certified today. That's worth knowing before you connect bank feed data. Plaid, which handles the bank connection itself, is SOC 2 certified and is the same connector used by most consumer financial apps.

My bookkeeper uses QuickBooks — can Starch pull from that instead of or alongside Plaid?

Yes, Starch syncs QuickBooks data on a schedule, pulling invoices, bills, payments, vendors, and journal entries. One note: the QuickBooks report views like P&L summaries are temporarily unavailable while an upstream fix is in progress, but the underlying entity data syncs normally and the runway calculation is built from that.

How is this different from just watching my bank balance every morning?

Your bank balance tells you what you have right now. The Runway Analysis app tells you how long that lasts at your actual burn rate, broken down by food cost, labor, and fixed overhead — and the Scenario Analysis app shows you how that number changes if you open Sunday brunch, cut a slow shift, or absorb a rent increase. The balance is a snapshot; this is a projection you can act on.

My cash situation changes week to week with private dining deposits and seasonal swings. Will this handle that?

The runway calculation is built on your trailing 6-month burn history from Plaid, so seasonal swings are already baked into the baseline. For a big private dining deposit that distorts one month, you can describe the adjustment to Starch — 'treat the $18,000 deposit in January as deferred revenue, not operating cash' — and it rebuilds the projection with that assumption.

I don't have a finance background. Is this going to require me to understand accounting to set up?

No. You describe what you want in plain language — 'show me how many months of cash I have and break it down by food cost, labor, and rent' — and Starch builds the dashboard. The App Store's Runway Analysis template is already configured for the most common operator use case; you're mostly just connecting your accounts and adjusting category labels to match your actual cost structure.