Strategy & Planning

How to run a scenario analysis for a strategic decision as Small RevOps Teams

Strategy & PlanningFor Small RevOps Teams2 apps10 steps~20 min to set up

When the CRO wants to know what happens to quota attainment if the team adds 8 reps in Q3, you're rebuilding the territory model in a Google Sheet that's already three versions stale. When the board asks about pipeline coverage under a conservative ARR assumption, you're copy-pasting HubSpot snapshots into slides at 10pm. Your scenario modeling lives in a spreadsheet that one person understands, pulls from disconnected exports, and breaks the moment someone changes a formula. You're not a finance team — you're RevOps — but nobody else is going to run these numbers before the planning call.

Build this on Starch → See the apps used

Strategy & PlanningFor Small RevOps Teams2 apps10 steps~20 min to set up

Outcome

What you'll set up

A live Scenario Analysis dashboard connected to your actual Stripe revenue and Plaid bank data, so every scenario starts from real baseline numbers instead of last month's export

Side-by-side scenario comparisons — headcount expansion vs. price increase vs. slower growth — each showing runway, burn rate, and break-even, updated without manual rebuilds

A shareable planning view you can drop into the forecast call or send to the CRO without rebuilding it in slides first

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

Scenario Analysis Runway Analysis

Data sources & config

Starch syncs your Stripe data on a schedule for revenue and your Plaid bank feed on a schedule for expenses — both are scheduled-sync providers that keep the baseline current without manual exports. Salesforce or HubSpot pipeline data can be pulled live from Starch's integration catalog when you want to layer in pipeline coverage assumptions on top of the financial model.

Prompts to copy

Build me a scenario analysis that starts from our actual Stripe MRR and Plaid burn. I want to compare three scenarios side by side: (1) we hire 8 AEs in Q3 at $120k OTE each, (2) we raise average contract value by 15% and hold headcount flat, (3) we miss our Q3 revenue target by 20%. Show runway, net burn, and break-even for each.

Show me our current net burn and runway based on the last 6 months of Plaid transactions and Stripe revenue. Flag which expense categories are growing fastest and how each scenario changes the break-even month.

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

Walkthrough

Step-by-step

1 Connect Stripe and Plaid in Starch — both sync on a schedule, so your revenue and expense baseline is always current. This replaces the 'export last month's data' step you do before every planning session.

2 Open the Scenario Analysis starter app from the Starch App Store. It ships with a baseline model wired to your connected Stripe and Plaid data — no blank spreadsheet to build from.

3 Type your first scenario in plain language: describe the headcount change, pricing move, or revenue miss you want to model. Starch builds the scenario against your real baseline, not a static assumption.

4 Add your second and third scenarios the same way. Each one adjusts only the assumptions you specify — runway, burn, and break-even update automatically for each branch.

5 Pull in pipeline coverage context: connect HubSpot or Salesforce from Starch's integration catalog so the agent can query live pipeline data and let you stress-test revenue assumptions against what's actually in the funnel.

6 Annotate each scenario with the decision it maps to — for example, 'Scenario 2 = raise Series A at current pace' or 'Scenario 3 = delay hiring until Q4 covenant'. This makes the output immediately usable in a planning conversation, not just a finance artifact.

7 Open the Runway Analysis app alongside Scenario Analysis to validate your baseline. Runway Analysis shows 6-month historical burn trends and 24-month forward projections — use it to sanity-check whether the baseline Starch is modeling matches what you're actually seeing month over month.

8 Share the scenario view directly with the CRO or board prep owner. Because it's a live app, not a static export, the numbers reflect current data every time someone opens it — no re-export before the call.

9 When assumptions change mid-quarter — a rep leaves, a big deal slips — describe the update to Starch and it rebuilds the affected scenario. You're not hunting for which cell to edit in a shared Sheet.

10 Use the scenario outputs to prep the forecast call narrative. Instead of pasting screenshots into slides, point to the Starch app directly or describe the summary to Starch and ask it to draft talking points from the numbers.

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

Q3 2026 Headcount vs. Pricing Scenario — July Planning Cycle

Sample numbers from a real run

Current net burn (Plaid baseline, 6-month avg)	-187,000
Stripe MRR (current)	134,000
Scenario A: +8 AEs at $120k OTE — incremental monthly cost	-80,000
Scenario A: projected MRR uplift by month 9 (at 0.6 quota attainment)	43,200
Scenario B: +15% ACV on new bookings — incremental MRR by month 6	28,400
Scenario C: Q3 revenue miss 20% — MRR impact	-26,800

Going into the July planning call, the CRO wants to know whether to greenlight the Q3 headcount plan or wait until Q4. You open Starch's Scenario Analysis app — Stripe MRR is synced at $134k and Plaid shows a 6-month average net burn of $187k, giving you 14 months of runway at current pace. You type: 'Add Scenario A — hire 8 AEs in August at $120k OTE, assume 0.6 quota attainment ramping over 6 months. Show how runway and break-even shift.' Starch builds it: Scenario A burns an additional $80k/month in comp, eroding runway to 9 months before the revenue ramp covers the gap. You add Scenario B — raise ACV 15% on new bookings, hold headcount flat — which adds $28.4k in incremental MRR by month 6 and extends runway to 17 months. Scenario C models a 20% Q3 revenue miss and shows break-even moves from month 11 to month 15. Instead of defending a spreadsheet nobody else can read, you walk the CRO through three live views in the same app, each clearly labeled with the decision it represents. The planning call takes 20 minutes instead of an hour of screen-sharing a Sheet.

Measurement

How you'll know it's working

Months of runway under each scenario (baseline, aggressive hire, conservative growth)

Net burn delta between scenarios — how much each decision costs per month

Break-even month by scenario — when does each path hit cash-flow neutral

Pipeline coverage ratio at each revenue assumption — how much open pipe do we need to hit Scenario B vs. absorb Scenario C

Quota attainment assumption sensitivity — how much does the headcount scenario change if attainment drops from 0.7 to 0.5

Comparison

What this replaces

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

Google Sheets / Excel scenario model

Faster to start from scratch if you already have a template, but the baseline goes stale the moment you close the export tab — every planning cycle means re-pulling data, and one formula change by someone else breaks the whole model.

Mosaic or Drivetrain (FP&A platforms)

Purpose-built for this workflow and more powerful for multi-entity financial consolidation, but they're priced and scoped for a finance team — a two-person RevOps team will spend more time configuring the platform than running the analysis.

HubSpot + manual pipeline export + Slides

Already in your stack and fine for pipeline snapshots, but it doesn't touch burn or runway — you're stitching CRM data and financial data together manually every time, which is the exact problem Starch's cross-connection model solves.

ChatGPT or Claude with a pasted spreadsheet

Works for one-off math if you paste the right numbers in, but the model has no live connection to Stripe or Plaid — you're still doing the data-pull manually, and there's no persistent app to share or revisit next quarter.

On Starch RECOMMENDED

One platform — scenario planning, runway analysis 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

We use Salesforce, not HubSpot. Can Starch still pull pipeline data into the scenario?

Yes — connect Salesforce from Starch's integration catalog and the agent queries it live when your scenario app needs pipeline coverage data. The financial baseline (Stripe revenue, Plaid burn) comes from scheduled syncs; Salesforce pipeline data is queried live on top of that.

Is the Scenario Analysis app available today or still in development?

Scenario Analysis is a live app in the Starch App Store today. The Budgeting and Presentation Agent apps listed in some Starch materials are currently in development — those require beta access. Scenario Analysis and Runway Analysis are both live and ready to connect.

Our Plaid connection shows bank transactions but we also pay vendors via wire — will the burn number be accurate?

Plaid captures transactions at the bank account level, so wire transfers that clear through your connected accounts will be included. If you have expense flows that don't touch those accounts — like a separate corporate card account not yet connected — you'd want to connect that account too. Starch is honest that it's working from your actual bank feed, not a manually reconciled P&L.

Can I model a scenario where we raise prices only for new customers, not existing ones?

Yes — describe the assumption in plain language. Tell Starch 'apply a 15% ACV increase to new bookings only; existing contracts renew flat.' The agent builds the scenario against your Stripe revenue baseline, separating new bookings from renewal MRR based on what's in your connected data.

Starch isn't SOC 2 certified — is it safe to connect our bank feed and Stripe account?

Starch is not currently SOC 2 Type II certified — that's worth knowing. Plaid is a bank-read connection (read-only, no transaction initiation), and Stripe data syncs read-only as well. Whether that's acceptable depends on your company's data policy. If your security team requires SOC 2 Type II certification before connecting financial data, Starch can't meet that bar today.

How do I share the scenario view with the CRO without giving them a Starch login?

You can share a link to the live app or export a snapshot. Because the app stays current with your connected data, sharing the link means the CRO always sees the latest numbers — not a stale PDF from last week's export.

We already use QuickBooks for actuals. Can the scenario baseline pull from there instead of Plaid?

Yes — Starch syncs your QuickBooks data on a schedule, covering invoices, bills, payments, and journal entries. Note that QuickBooks report views (like the P&L summary) are temporarily unavailable due to an upstream connector issue, but entity-level data syncs normally. You can use that data as your expense baseline in the scenario model.