Strategy & Planning

How to run annual planning as Small RevOps Teams

Strategy & PlanningFor Small RevOps Teams5 apps11 steps~22 min to set up

Annual planning for a 2-person RevOps team means rebuilding the quota model in Google Sheets every time territory changes, pulling HubSpot pipeline snapshots by hand, reconciling Apollo sequence data with LinkedIn touches and inbound attribution that live in three different tabs, and presenting a headcount plan to the CRO based on numbers that aged out the moment you exported them. You spend two weeks in Q4 stitching together a document that's already stale by the kickoff meeting — and fielding Slack messages about why the numbers don't match what the CRO said in the board deck.

Build this on Starch → See the apps used

Strategy & PlanningFor Small RevOps Teams5 apps11 steps~22 min to set up

Outcome

What you'll set up

A connected planning workspace that pulls live pipeline, headcount cost, and actuals from HubSpot, Apollo, Plaid, and Stripe into one view — so your annual plan reflects what's actually happening, not a snapshot from last Tuesday

A scenario model you can hand to the CRO that shows quota attainment, territory coverage, and revenue outcome under 3-5 named assumptions — built from your real burn and bookings data, not a blank spreadsheet

A structured territory and capacity plan with documented decisions and action items, searchable after the fact so you're not re-litigating January's calls in March

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 Sales Agent CRM Knowledge Management Meeting Notes Budgeting

Data sources & config

Starch syncs your HubSpot data on a schedule (contacts, companies, deals, owners) and your Apollo.io data on a schedule (contacts, accounts, sequences). Starch syncs your Stripe data on a schedule (revenue, subscriptions, churn) and your Plaid data on a schedule (transactions, burn, balances). Salesforce and Pipedrive connect from Starch's integration catalog and are queried live when your apps run. LinkedIn enrichment is handled through browser automation — no LinkedIn API needed.

Prompts to copy

Build me a revenue scenario model for 2026 annual planning. Connect Stripe so the baseline uses our actual ARR and churn. Connect Plaid for burn. Let me define 4 scenarios: conservative (80% of plan), base, aggressive (120% of plan), and a headcount-freeze version. Show runway, break-even, and net new ARR required per rep under each.

Build me a territory and quota capacity model pulling our open pipeline from HubSpot. Segment by rep, region, and deal stage. Flag reps where open pipeline is less than 3x their quota. Show me which territories have coverage gaps based on current headcount.

Create a knowledge base for our 2026 annual plan. Store our quota methodology, territory logic, attribution rules, and the agreed-upon assumptions from planning. Auto-detect when a doc hasn't been updated in 30 days and flag it for review.

Set up meeting notes capture for all annual planning sessions. After each call, extract decisions made, open questions, and action items by owner. Archive everything searchable so we can find the conversation where we agreed to change the SMB quota.

Build me a 2026 headcount budget tracker. Pull actual payroll spend from Plaid. Set targets by department. Show variance between planned headcount cost and actual, updated as each month closes.

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

Walkthrough

Step-by-step

1 Connect HubSpot and Apollo in Starch — both sync on a schedule, so your pipeline and sequence data refresh automatically without manual exports. If your team runs on Salesforce instead, connect it from Starch's integration catalog; the agent queries it live when your planning apps need it.

2 Connect Stripe and Plaid so Scenario Analysis uses your real ARR, churn rate, and monthly burn as the baseline — not a number someone typed into a cell six months ago.

3 Open Scenario Analysis and describe the planning scenarios your CRO actually argues about: base plan, conservative, aggressive, and a headcount-freeze version. Starch builds the model from your live data; you adjust only the assumptions you want to test.

4 Use the Sales Agent CRM app as a starting point and tell Starch to extend it into a territory and quota capacity view — segmented by rep, region, and deal stage, with a flag for any rep whose pipeline is less than 3x their quota number.

5 Ask Starch to pull your current headcount from Paylocity or ADP (both sync on a schedule) and overlay it on the territory model so coverage gaps show up next to pipeline gaps in the same view.

6 Set up Meeting Notes for every planning session — kick-off, territory review, quota negotiation, headcount sign-off. After each call, Starch extracts decisions, open questions, and owner-assigned action items automatically.

7 Create a Knowledge Management workspace and tell Starch to store your quota methodology, attribution rules, territory logic, and planning assumptions as living docs. Set a staleness alert for anything untouched after 30 days.

8 Connect Plaid to the Budgeting app and describe a headcount cost tracker that maps actual payroll spend against planned headcount budget by department, with monthly variance analysis.

9 At mid-year check-in, pull the scenario model back up and re-run it against six months of actual Stripe and Plaid data — Starch updates the baseline automatically because the connections are still live.

10 When the CRO asks 'why did we set SMB quota at $480K?' — search the Knowledge Management base and find the meeting note from the January 14th planning session where that number was agreed on, with the rationale documented.

11 For the board update, describe the slide you need: 'a 6-slide annual plan progress deck showing pipeline coverage by territory, attainment to date vs plan, and the 3 scenarios we modeled at kickoff.' Presentation Agent (currently in development — request beta access) will draft it; until then, use the dashboard you've already built as the source and export the view.

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

Q4 2025 → 2026 Annual Planning Cycle

Sample numbers from a real run

Base ARR (Stripe sync)	3,200,000
Net new ARR required (base plan)	960,000
Net new ARR per rep (12 AEs, base)	80,000
Pipeline required at 3x coverage	2,880,000
Current open pipeline (HubSpot sync)	1,940,000
Coverage gap flagged	940,000

Going into November, the team connects HubSpot and Stripe to Starch and runs the Scenario Analysis app against real numbers: $3.2M ARR, 8% monthly churn, $210K monthly burn from Plaid. The base scenario requires $960K in net new ARR — $80K per AE across 12 reps. The territory capacity model, built on top of the HubSpot sync, shows that current open pipeline is $1.94M against a $2.88M coverage requirement — a $940K gap concentrated in two territories where two reps joined in September and haven't ramped. The aggressive scenario (20% above plan) would require either two additional AEs by Q2 or a 35% increase in average deal size. That trade-off conversation happens in the planning session on November 19th; Meeting Notes captures the decision: stay with 12 AEs, raise SMB ACV target from $18K to $22K, revisit in March. That decision lives in the Knowledge Management base. In March, when a new sales manager asks why SMB quota looks the way it does, the answer is one search away — not in someone's inbox.

Measurement

How you'll know it's working

Pipeline coverage ratio by territory (open pipeline vs. 3x quota requirement)

Quota attainment to date vs. annual plan by rep and region

Headcount cost variance: planned payroll budget vs. actual Plaid spend by department

Scenario spread: ARR outcome delta between conservative and aggressive plan at current burn rate

Planning cycle time: weeks from kickoff to signed-off quota and territory model

Comparison

What this replaces

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

Google Sheets + manual HubSpot exports

Sheets gives you full control but requires manual data pulls every time you refresh — the model is always a few days stale and breaks when someone edits the wrong formula.

Clari or Gong Forecast

Strong for weekly forecast calls but priced for larger ops teams, doesn't connect your headcount costs or financial scenarios, and won't build the territory capacity model from scratch.

Anaplan

Purpose-built for enterprise planning with dedicated admins — overkill for a 2-person RevOps team, requires months of implementation, and costs more than most small teams' entire tool budget.

Notion + manual docs

Good for documentation but doesn't connect live to HubSpot or Stripe — you're still copy-pasting numbers, and the plan drifts from reality as soon as the quarter starts.

On Starch RECOMMENDED

One platform — scenario planning, sales agent crm, knowledge management 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. Does this still work?

Yes. Connect Salesforce from Starch's integration catalog; the agent queries it live when your planning apps need pipeline data. HubSpot gets a scheduled sync (data refreshes automatically on a schedule), while Salesforce is queried live — for annual planning, both approaches give you current data.

Can Starch pull headcount data from our HRIS for the capacity model?

If you use Paylocity or ADP, Starch syncs that data on a schedule — employees, pay statements, org units. If you use Rippling, Gusto, or BambooHR, connect them from Starch's integration catalog and the agent queries them live. You can also pull headcount costs directly from Plaid transactions if your payroll shows up as categorized transactions.

Will the scenario model update automatically when Stripe or Plaid data refreshes?

The connections stay live — Stripe and Plaid sync on a schedule — so when you open the model mid-year, it's pulling current ARR and burn, not the numbers from November. You re-run scenarios against the updated baseline without rebuilding anything.

Is Starch SOC 2 certified? We have to answer this question for our security team.

Not yet. Starch is not SOC 2 Type II certified today. If your org requires SOC 2 before connecting CRM and financial data, that's worth knowing upfront — it's a real limit, not something to work around.

We want to store the planning methodology somewhere the whole team can find it, not just RevOps. Can Knowledge Management handle that?

Yes — Knowledge Management is built for exactly this. You describe the structure you want (quota methodology, territory logic, attribution definitions, planning assumptions), Starch organizes it and makes it searchable with AI. When a doc goes stale — say, the attribution rules from January haven't been touched since Q1 — Starch flags it for review so you're not sending reps to outdated documentation.

Our CRO is going to want a presentation, not a dashboard. Can Starch build the deck?

Presentation Agent is currently in development — you can request beta access to get notified when it launches. In the meantime, the dashboards and scenario views you build in Starch are exportable and designed to be screen-shared directly in planning calls.

We track attribution across Apollo sequences, LinkedIn touches, and inbound form fills. Can all of that feed into the annual plan?

Apollo syncs on a schedule (sequences, contacts, accounts). LinkedIn enrichment runs through browser automation — no LinkedIn API needed. For form fill attribution, if it flows into HubSpot or Salesforce it's already in the pipeline data. If it lives in a separate tool like a marketing platform, connect it from Starch's integration catalog and the agent queries it live when your attribution view runs.