Sales & CRM

How to forecast quarterly revenue as Small Investor Relations Teams

Sales & CRMFor Small Investor Relations Teams3 apps11 steps~22 min to set up

Your two-person IR team is responsible for quarterly revenue forecasts that have to reconcile Stripe subscription data, QuickBooks billing records, and whatever the CFO last touched in a spreadsheet — three sources that never quite agree. You're pulling this together manually every quarter, usually the week before the LP meeting, usually at 11pm. The institutional IR platforms your larger peers use cost more than your annual team budget and assume a dedicated analyst. You end up living in Excel pivot tables that break when someone renames a column, and the forecast you present is already 10 days stale by the time it leaves your inbox.

Build this on Starch → See the apps used

Sales & CRMFor Small Investor Relations Teams3 apps11 steps~22 min to set up

Outcome

What you'll set up

A live revenue forecast dashboard that pulls from Stripe and QuickBooks on a schedule, so your quarterly numbers are never more than 24 hours out of date before a board or LP meeting

A scenario analysis layer that lets you model 'what if Q3 renewals come in 15% light' or 'what if we close the two pipeline deals in the catalog' — side by side, without rebuilding a spreadsheet from scratch

An investor reporting workflow that drafts your quarterly update narrative from the same live data, consistent with the tone and structure LPs expect from you

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 CRM

Data sources & config

Starch syncs your Stripe data on a schedule (charges, subscriptions, invoices) and syncs your QuickBooks data on a schedule (invoices, payments, journal entries). The Scenario Analysis and Investor Reporting apps run directly on top of this synced data. The CRM connects to Gmail from Starch's integration catalog so email thread history with LPs surfaces in the contact record. LP portal systems like Juniper Square or DocSend are reachable through browser automation — no API needed — for data room access checks and document delivery confirmation.

Prompts to copy

Build me a quarterly revenue forecast that pulls from Stripe and QuickBooks, breaks MRR into new business, expansion, and churn, and lets me layer in three custom scenarios — base, upside, and downside — with adjustable renewal rate and new logo assumptions

Generate a Q2 2026 investor update that shows our revenue forecast vs. actuals from last quarter, highlights the two largest pipeline deals by name, and flags the renewal cohort we're watching — keep the tone consistent with the Q1 letter I'll paste in

Build me an investor CRM that tracks LP names, commitment amounts, last contact date, and any open questions from the most recent quarterly call — and let me query 'which LPs haven't received the Q1 letter confirmation yet'

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

Walkthrough

Step-by-step

1 Connect Stripe: Starch syncs your charges, subscriptions, and invoices on a schedule — this becomes the live revenue spine your forecast runs on.

2 Connect QuickBooks: Starch syncs invoices, payments, and journal entries on a schedule, giving you a second source to reconcile against Stripe for recognized vs. collected revenue.

3 Start with the Scenario Analysis app from the App Store and tell Starch how your revenue breaks down — subscription tiers, renewal cohorts, new logo targets — so the baseline reflects your actual model, not a generic SaaS template.

4 Add three scenario tracks: base (current pipeline closes at historical rate), upside (two named deals close in Q3), and downside (renewal rate drops 12 points) — each one shows projected ARR, net new, and churn contribution for the quarter.

5 Wire the Investor Reporting app to the same Stripe and QuickBooks sync so the quarterly narrative pulls from the same numbers your scenario model uses — no copy-paste between tools.

6 Paste in your last LP letter and tell Starch to match the structure and tone — it will draft the Q2 narrative with burn, runway, MRR growth, and pipeline commentary filled in from live data.

7 Build the investor CRM app on top of your Gmail connection from the integration catalog — Starch maps LP contacts, tracks last touch date, and surfaces any open questions flagged in email threads since the last quarterly call.

8 For LPs who use DocSend or a portal you maintain, set up a browser automation that checks document access logs weekly and flags any LP who hasn't opened the quarterly packet within 7 days of send.

9 Schedule the full forecast refresh to run every Monday morning — Starch re-pulls Stripe and QuickBooks, recalculates each scenario, and Slacks you a summary with any metric that moved more than 5% week-over-week.

10 Before each quarterly board meeting, run a manual refresh and ask the agent: 'What changed in the revenue forecast since last quarter's presentation, and which scenario are we tracking closest to?' — you get a one-paragraph briefing you can paste directly into your board prep doc.

11 After the meeting, trigger the Investor Reporting app to send the final quarterly update to the LP list in your CRM, using the same data the board just reviewed.

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

Q2 2026 Quarterly Revenue Forecast — Mid-June Close

Sample numbers from a real run

Stripe MRR (subscription invoices, synced)	412,000
QuickBooks recognized revenue (invoices paid)	398,000
Expansion MRR (seat upgrades, Q2 cohort)	31,000
Churn (3 non-renewals, Q2 cohort)	-18,500
Pipeline — Upside scenario (2 deals, 70% close probability)	55,000
Q2 forecast — Base scenario ARR run rate	4,968,000
Q2 forecast — Upside scenario ARR run rate	5,628,000

Coming into the June board meeting, the Stripe sync shows $412K MRR against $398K in QuickBooks recognized revenue — the $14K gap is two invoices that closed in late June but won't post in QuickBooks until July 1. The base scenario holds renewal rate at 91% (the trailing 4-quarter average) and gets to $4.97M ARR by September 30. The upside scenario closes the Hendricks Capital and Mercer Logistics deals currently sitting in the pipeline CRM at a combined $55K ARR, pushing the run rate to $5.63M. The downside scenario — modeled after the Q3 2024 macro softness period — drops renewal rate to 79% and shows ARR stalling at $4.41M with churn concentrated in the mid-market tier. The IR team used the Investor Reporting app to draft the LP quarterly letter directly from these three scenarios, flagging that 'we are currently tracking between base and upside, with Q3 renewal close rate as the primary variable to watch.' Total time to go from raw Stripe and QuickBooks data to a board-ready forecast with LP letter draft: under two hours, down from the two-day sprint last quarter.

Measurement

How you'll know it's working

Net new ARR vs. plan by quarter (new logo + expansion minus churn)

Renewal rate by cohort — trailing 4 quarters, flagged when any cohort drops below 85%

Scenario variance: distance between base and downside ARR forecast at quarter-end

LP letter open rate and time-to-open after quarterly send (tracked via DocSend browser automation)

Pipeline coverage ratio: total pipeline value divided by remaining quota for the quarter

Comparison

What this replaces

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

Juniper Square / Addepar / iLevel

Purpose-built for fund IR reporting but costs $50K+ per year, requires a dedicated IR-ops analyst to configure, and doesn't let you build the custom surfaces your specific reporting cadence needs — you adapt to the platform instead of the other way around.

Excel + manual Stripe/QuickBooks exports

Free and fully flexible, but your forecast is stale the moment you export it, reconciliation between sources is manual every quarter, and the model breaks when someone changes a column header — there is no live data layer.

Q4 Inc. (investor relations platform)

Strong for public company investor communications at scale, but overkill for a $100M-ARR company with a two-person team and no budget for an enterprise contract or implementation timeline.

HubSpot CRM for investor contacts

Handles contact and deal tracking well, but requires a paid admin to configure, doesn't natively connect to your financial data sources, and you'll still be building the revenue forecast separately — there's no composability between the CRM and the forecast model.

On Starch RECOMMENDED

One platform — scenario planning, investor reporting, crm 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 replace our fund admin or our ERP?

No — and it's not trying to. Starch connects to QuickBooks and NetSuite and syncs that data on a schedule; it connects to Stripe and Plaid the same way. Your fund admin and your ERP stay where they are. Starch is the surface layer your IR team actually works in on top of those systems — the forecast, the LP letter, the CRM — not a replacement for the record-keeping underneath.

Our Stripe MRR and QuickBooks recognized revenue never quite match. Can Starch reconcile them?

Starch syncs both sources independently and can surface the gap in a dashboard or flag it in your weekly summary. Identifying the discrepancy is straightforward. The reconciliation itself — deciding which journal entries to adjust — still requires a human with accounting judgment. Starch helps you find the problem faster; it doesn't make the posting decision for you.

We use DocSend for our data room. Can Starch pull access logs from it?

DocSend doesn't have a formal API connector in Starch's integration catalog today, but Starch automates DocSend through your browser — no API needed. You can set up a weekly automation that logs into DocSend, checks which LPs have opened the current quarterly packet, and Slacks you a list of anyone who hasn't opened it within 7 days of send.

Is Starch SOC 2 Type II certified?

Not yet. Starch is not SOC 2 Type II certified today. If that's a hard requirement for your fund's vendor approval process, you'll want to flag it. It's on the roadmap — but we'd rather tell you now than have you find out later.

Can Starch store historical revenue data going back multiple years for trend analysis?

Starch is built for live data surfaces, not a long-horizon data warehouse. Stripe and QuickBooks data sync on a schedule and are available for your forecast and reporting apps, but Starch isn't designed to replace a dedicated analytics warehouse for multi-year archival analysis. If you need a 5-year cohort study, you'd want a warehouse layer alongside Starch, not instead of it.

We already have a QuickBooks setup but some of the P&L report views aren't pulling in. Is that a Starch problem?

QuickBooks report views — P&L, Transaction List, Vendor Expenses — are temporarily disabled in Starch pending a fix on the connector side. Entity-level data (invoices, bills, payments, vendors, journal entries) syncs normally and is what the Investor Reporting and Scenario Analysis apps run on. The report views will come back; the underlying data is there in the meantime.

How long does it take to have a working quarterly revenue forecast after we connect our data sources?

Most teams have a working baseline forecast within a few hours of connecting Stripe and QuickBooks. The Scenario Analysis app gives you a starting point you can customize by describing your revenue model — tier structure, renewal assumptions, pipeline — in plain language. You're not configuring formulas; you're telling Starch how your business works and it builds the model.