Sales & CRM

How to forecast quarterly revenue as DTC Brand Founders

Sales & CRMFor DTC Brand Founders2 apps12 steps~24 min to set up

Your quarterly revenue forecast lives in a Google Sheet that pulls from nothing automatically. You export Shopify orders on a Monday, paste in Meta Ads spend from a CSV someone downloaded, squint at Klaviyo email revenue attribution that never quite matches Shopify, and try to guess what Q3 looks like based on Q2 vibes and a seasonality adjustment you made up. CAC is creeping, AOV is shifting by channel, and your best-selling SKU has a 10-week lead time — so the forecast you hand your board is already wrong by the time you print it. You're not missing data, you're missing a system that connects the data you already have.

Build this on Starch → See the apps used

Sales & CRMFor DTC Brand Founders2 apps12 steps~24 min to set up

Outcome

What you'll set up

A live revenue forecast that pulls Shopify orders, Stripe payouts, and Plaid bank transactions into one model — updated automatically, not when you remember to export a CSV

Channel-level CAC and revenue attribution broken out by Meta, email, and organic so your quarterly projection actually reflects where growth is coming from

A scenario model that shows your board what Q3 looks like under three assumptions: flat CAC, 20% CAC increase, and a new SKU launch — without rebuilding the spreadsheet each time

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 Investor Reporting

Data sources & config

Starch syncs your Stripe data on a schedule (charges, payouts, subscriptions) and syncs your Plaid bank transactions on a schedule — these are the baseline for revenue and burn. Shopify is connected from Starch's integration catalog and queried live when your forecast app runs. Meta Ads and Klaviyo are also connected from Starch's integration catalog, queried live for spend and email revenue data. No scheduled sync for ad platforms — data is pulled fresh each time the model refreshes.

Prompts to copy

Build me a quarterly revenue forecast that pulls from Stripe and Plaid. Break revenue by month, show me trailing 90-day average order value, and let me toggle CAC assumptions by channel — Meta Ads, Klaviyo email, and organic. Flag any month where projected revenue drops below my burn rate.

Connect my Shopify store from the integration catalog and pull order volume, average order value, and refund rate by product category for the last two quarters. Show me which categories are growing and which are shrinking as a share of total revenue.

Build me three Q3 scenarios: (1) CAC holds flat, (2) Meta CAC rises 20% with no offset, (3) we launch the new candle SKU in July and it does 15% of the volume our top SKU did in month one. Show runway, projected quarterly revenue, and break-even under each.

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

Walkthrough

Step-by-step

1 Connect Stripe and Plaid — Starch syncs both on a schedule so your revenue and cash data are always current without any manual exports.

2 Connect Shopify from Starch's integration catalog. When your forecast runs, the agent queries Shopify live for order volume, AOV, refund rate, and SKU-level sales — broken out by whatever time window you need.

3 Connect Meta Ads and Klaviyo from Starch's integration catalog. The agent pulls channel spend and attributed email revenue live so your CAC calculation reflects actual numbers, not a spreadsheet you updated last month.

4 Start with the Scenario Analysis app. Tell Starch your current baseline — Stripe revenue and Plaid burn — and ask it to build a Q3 forecast with channel-level CAC as an adjustable assumption.

5 Add a second scenario where Meta CAC rises 20%. Starch reruns the model with that single assumption changed and shows you the revenue and runway delta — no formula editing required.

6 Add a third scenario for a new SKU launch. Give Starch the launch month and a volume assumption (e.g., 15% of your top SKU's month-one volume), and it builds the revenue ramp into the forecast.

7 Review the scenario side-by-side view. Each one shows projected quarterly revenue, monthly burn vs. revenue, and the month where you'd hit break-even or run out of runway.

8 Ask Starch to flag the assumptions that move the needle most — which variable (CAC, AOV, refund rate, new SKU volume) has the biggest impact on Q3 outcome. This tells you where to focus operational attention.

9 Connect the Investor Reporting app to the same Stripe and Plaid connections. Ask it to pull Q2 actuals — MRR, AOV trend, top SKU revenue, refund rate — and draft the financial section of your board update.

10 Tell Starch which scenario you're presenting as the operating plan. It incorporates that scenario's assumptions into the narrative, so your board letter and your financial model are saying the same thing.

11 Set a refresh cadence — weekly or monthly. Starch re-pulls Shopify, Meta Ads, and Klaviyo live each time so your forecast reflects what actually happened, not what you projected.

12 When Q3 starts, compare actuals to the scenario you committed to. Ask Starch: 'How does our July Shopify revenue compare to the flat-CAC scenario I built in June?' and get a real answer, not a pivot table exercise.

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 forecast — candle brand, $2.1M trailing annual revenue

Sample numbers from a real run

Shopify revenue (Q2 actuals, trailing 90 days)	487,000
Stripe payouts matched to Shopify orders	481,200
Meta Ads spend (Q2, live query)	94,000
Klaviyo email revenue attribution (Q2)	61,000
Refunds and returns (Shopify, Q2)	28,400
Projected Q3 revenue — flat CAC scenario	512,000
Projected Q3 revenue — Meta CAC +20% scenario	468,000
Projected Q3 revenue — new SKU launch scenario	539,000

This brand did $487K in Shopify revenue in Q2 with a blended CAC of about $38 across Meta and email. Refunds ran at 5.8% — elevated on one SKU that had a sizing issue, now resolved. The flat-CAC Q3 scenario gets to $512K assuming the same channel mix and AOV of $64. But Meta CPMs historically spike in Q3 as holiday advertisers enter the auction, so the +20% CAC scenario drops Q3 to $468K and pushes break-even two weeks later than the operating plan assumed. The new SKU scenario — a fall-scented candle launching July 14 — adds roughly $27K in incremental revenue if it follows the month-one curve of the existing top SKU. Starch built all three projections from the same Stripe and Plaid baseline; the founder adjusted only the CAC multiplier and SKU volume assumption. The Investor Reporting app pulled Q2 actuals from the same connections and drafted the board letter's financial section, citing the flat-CAC scenario as the plan and the +20% scenario as the downside case — without the founder rebuilding anything in a separate doc.

Measurement

How you'll know it's working

Blended CAC by channel (Meta vs. Klaviyo email vs. organic) — updated with each forecast refresh

Average order value by product category, trailing 90 days

Refund rate by SKU — tracked against the revenue forecast to catch demand signal issues early

Projected quarterly revenue under each scenario vs. operating plan commitment

Months of runway at current burn, recalculated from Plaid transactions weekly

Comparison

What this replaces

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

Google Sheets + manual CSV exports

Free and flexible, but every number is only as current as the last time someone ran a Shopify export — which means your forecast is usually 1–2 weeks stale when you need it most.

Shopify Analytics + Meta Ads Manager side-by-side

Each platform shows you its own numbers accurately, but there's no shared model — you're doing the CAC math in your head across two browser tabs.

Triple Whale or Northbeam

Purpose-built for DTC attribution and solid at it, but the output is a dashboard you read, not a model you can run scenarios against or pipe into a board update automatically.

Looker Studio / Google Data Studio

Good for visualization once someone builds the connections, but building and maintaining those connections requires ongoing technical work and the scenario modeling capability isn't there.

Runway (financial modeling tool)

Strong at financial scenario modeling, but it's a finance tool disconnected from your Shopify order data and ad spend — you're still manually inputting the revenue numbers it models.

On Starch RECOMMENDED

One platform — scenario planning, investor reporting 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

Does Starch connect to Shopify?

Yes — connect Shopify from Starch's integration catalog and the agent queries it live when your forecast or reporting app runs. You get order volume, AOV, refund rate, and SKU-level revenue. This isn't a scheduled sync, so data is pulled fresh each time the app runs rather than stored in Starch — which is the right call for an operational metric you want current, not a historical archive.

What about Meta Ads and Klaviyo — can Starch pull those too?

Both are available from Starch's integration catalog and queried live. Your Meta spend and Klaviyo email revenue flow into the same forecast model as your Shopify and Stripe data. The agent doesn't store a running archive of your ad spend history — it pulls what it needs when the app runs. If you need deep historical ad attribution going back years, that's a case where a dedicated attribution tool may complement Starch rather than replace it.

Can I actually build scenario models in Starch, or is it just dashboards?

The Scenario Analysis app is specifically built for this. You connect Stripe and Plaid as the financial baseline, then describe the assumptions you want to test — 'what if Meta CAC goes up 20%' or 'what if we launch a new SKU in July at half the volume of our current top seller' — and Starch builds the model. Each scenario shows projected revenue, burn, runway, and break-even under its own assumptions. You're not editing formulas; you're describing outcomes and Starch does the modeling.

Is Starch SOC 2 certified? I'm connecting bank accounts and Stripe.

Not yet — Starch is not SOC 2 Type II certified as of now. That's a real consideration when you're connecting financial accounts. It's on the roadmap. In the meantime, Plaid and Stripe connections use OAuth — Starch never sees raw credentials — and Plaid connections are read-only.

How is this different from just using Shopify's built-in analytics?

Shopify analytics tells you what happened in Shopify. It doesn't know about your Meta spend, your Klaviyo email revenue, your Stripe payouts, or your bank balance. Starch pulls from all of them into one model so your forecast reflects your whole business — CAC across channels, revenue net of refunds, and cash position — not just one platform's view of it.

Can Starch pull my QuickBooks data too, for the P&L side?

Yes — Starch connects directly to QuickBooks and syncs entities like invoices, bills, payments, and vendors on a schedule. One current limitation: QuickBooks report views (P&L summary, Transaction List, Vendor Expenses) are temporarily unavailable pending a connector fix, but the underlying entity data syncs normally. For most DTC revenue forecasting purposes — where you care about order revenue and ad spend more than accounting reports — this isn't a blocker.