Strategy & Planning

How to set quarterly okrs as Small RevOps Teams

Strategy & PlanningFor Small RevOps Teams3 apps12 steps~24 min to set up

OKR season hits and you're the one holding the bag. The CRO wants quota attainment broken down by territory. The VP of Sales wants pipeline coverage ratios. The CEO wants a single-number win-rate trend. None of these live in the same place. You're exporting HubSpot deal stages to Sheets, cross-referencing Apollo sequence data, pulling Gmail thread counts as a proxy for rep activity, and then writing the actual objectives in a Notion doc that nobody updates after week two. By the time you've stitched it all together, the quarter is two weeks in and the OKRs are already stale. The 'strategy' part of RevOps gets squeezed out by the data assembly part.

Build this on Starch → See the apps used

Strategy & PlanningFor Small RevOps Teams3 apps12 steps~24 min to set up

Outcome

What you'll set up

A connected OKR dashboard that pulls live pipeline, attainment, and activity data from HubSpot, Apollo, and Gmail into a single view — so your objectives are anchored to real numbers, not last Tuesday's export

An automated quarterly kickoff workflow that drafts OKR language from your historical data and surfaces the three or four metrics that actually moved revenue last quarter

A standing check-in automation that scores OKR progress weekly and posts a digest to Slack before the Monday forecast call — so you're not building the slide by hand

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

Sales Agent CRM Knowledge Management CRM

Data sources & config

Starch syncs your HubSpot data on a schedule — contacts, companies, deals, and owners — providing the core pipeline and attainment numbers. Apollo.io is synced on the same schedule, giving you sequence activity and contact-level engagement to use as leading indicators. Gmail is synced on a schedule so rep email volume is trackable as an activity proxy. Salesforce and Pipedrive are connectable from Starch's integration catalog; the agent queries them live when your dashboard runs. Slack is available from Starch's integration catalog for posting weekly OKR digests. Notion is synced on a schedule if you keep strategy docs there.

Prompts to copy

Build me a quarterly OKR tracker for a 30-rep sales org. Pull win rate, pipeline coverage, average deal cycle, and quota attainment by territory from HubSpot. Show current quarter vs. prior quarter side by side. Flag any territory where coverage has dropped below 3x.

Create a knowledge base section called 'OKR History' that archives each quarter's objectives, the metrics we set them against, and whether we hit them. Auto-tag each entry by fiscal quarter and pull in the final attainment number from HubSpot when the quarter closes.

Every Monday at 7am, pull this week's open pipeline by stage from HubSpot, calculate coverage ratio against each rep's quota, compare to last week, and post a summary to the #revops Slack channel with a red/yellow/green flag per territory.

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

Walkthrough

Step-by-step

1 Connect HubSpot — Starch syncs your deals, stages, owners, and close dates on a schedule. This becomes the foundation for every attainment and coverage calculation in your OKR dashboard.

2 Connect Apollo.io — Starch syncs sequence activity and contact-level engagement on a schedule. Use this to set leading-indicator objectives (e.g., 'sequences started per rep per week') alongside lagging ones like win rate.

3 Connect Gmail — Starch syncs message data on a schedule so you can track rep email volume as a proxy for outbound activity, which you'll use to pressure-test whether reps are on pace before pipeline materializes.

4 If your org runs Salesforce instead of HubSpot, connect it from Starch's integration catalog. The agent queries it live when your dashboard runs — deal stage, ARR, territory, and owner all come through.

5 Open the Sales Agent CRM starter app and fork it into your OKR foundation. Describe the custom view you need: 'Add a quarterly attainment column per rep, a pipeline coverage ratio per territory, and a rolling win-rate trend for the past three quarters.'

6 Tell Starch to build your OKR draft surface: 'Look at last quarter's closed-won deals, average deal cycle, and win rate by territory. Suggest three to five revenue objectives for Q3 with specific numeric targets based on this data.' Review the output, adjust targets with the CRO, and lock the objectives.

7 Set up the Knowledge Management app to archive OKRs by quarter. Describe it as: 'Create a searchable OKR history section. Each quarter gets a page with the objectives we set, the metrics we used to set them, and final attainment. Auto-tag by fiscal quarter.' This is the institutional memory that prevents you from reinventing the quota model every 90 days.

8 Build the weekly check-in automation: 'Every Monday at 7am, calculate pipeline coverage by territory using this week's HubSpot open deals versus each rep's quota. Flag territories below 3x. Post a summary to #revops on Slack.' This replaces the Friday-afternoon slide-building session.

9 Add a mid-quarter alert: 'If any territory's win rate drops more than 5 percentage points below the Q3 target, send me a Slack message with the affected reps and their current pipeline.' Catch slippage before the QBR, not at it.

10 For the board or CRO OKR review, describe the presentation you need: 'Summarize Q3 OKR progress — show each objective, the metric we set, current performance, and delta to target. Format it as a five-slide update with one slide per strategic pillar.' Export to PDF or share the link directly.

11 At quarter close, run the attainment pull: 'Pull final closed-won ARR by rep and territory for Q3, calculate attainment against quota, and write it back to the OKR History section in the knowledge base.' The record stays current without a manual update.

12 Before Q4 kickoff, ask Starch to resurface patterns: 'Which territories consistently over- or under-performed against OKR targets in the last three quarters? What leading indicators — coverage ratio, sequences started, email volume — correlated most with hitting the number?' Use that to set smarter targets the next time.

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 OKR Set — 30-Rep Mid-Market Team

Sample numbers from a real run

Win rate target (East territory)	28
Win rate baseline Q2 (East territory)	21
Pipeline coverage target (all territories)	4
Pipeline coverage actual at OKR set date	2.7
Sequences-started-per-rep-per-week target	12
Sequences-started-per-rep-per-week Q2 average	7

It's the first week of July. Your two-person team has 90 minutes to walk the CRO through proposed Q3 OKRs before she leaves for a board offsite. In the past this meant exporting HubSpot deals to Sheets, pulling Apollo sequence counts manually, and writing objectives based on gut feel because the data was already three days old by the time you'd assembled it. This time you asked Starch: 'Using HubSpot deal data from Q2, calculate win rate by territory and identify which territories improved most.' East territory came back at 21% win rate — up from 17% in Q1 — driven by a cohort of reps who averaged 12 sequences per week versus the team's 7. Starch surfaced that correlation automatically. The OKR it suggested: 'Raise East territory win rate from 21% to 28% by increasing sequences started per rep per week from 7 to 12 across all territories.' That's a data-backed objective with a leading indicator attached, not a number pulled from a spreadsheet. Pipeline coverage across all territories sat at 2.7x at OKR set — below the 4x target you and the CRO agreed on last quarter. Starch flagged the three territories furthest below 3x and drafted the coverage objective: 'Achieve 4x pipeline coverage in all territories by week 8 of Q3.' The Monday automation posts a red/yellow/green territory scorecard to Slack every week. By week 6 you knew East was at 3.8x and on track; Central was at 2.4x and needed intervention. You had that conversation at the forecast call with data in hand, not a hunch.

Measurement

How you'll know it's working

Pipeline coverage ratio by territory (open pipeline / quota, tracked weekly)

Win rate trend by territory, quarter over quarter

Sequences started per rep per week (leading indicator for top-of-funnel OKRs)

OKR attainment rate at quarter close (percentage of objectives hit vs. set)

Time from OKR kickoff to final approved objectives (measures how much of the process is still manual assembly)

Comparison

What this replaces

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

Google Sheets + HubSpot exports

Gets the numbers eventually but the data is stale the moment you export it, and every quarter you're rebuilding the same model from scratch because there's no persistent OKR history.

Lattice or Betterworks

Good for company-wide OKR tracking and HR-side goal setting, but they don't connect to your pipeline data — so revenue objectives still get set in a vacuum and checked manually.

Notion + manual data pulls

Works fine as a home for OKR documentation, but the numbers inside are only as current as the last time someone updated them, which in a two-person RevOps team is never often enough.

Salesforce Reports + CRM-native dashboards

Pipeline data is live, but OKR logic (coverage ratios, attainment targets, leading indicators) has to be custom-built by an admin, and the output doesn't write itself to a strategy doc or post to Slack.

On Starch RECOMMENDED

One platform — sales agent crm, knowledge management, 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

We run Salesforce, not HubSpot. Does Starch work for us?

Yes. Connect Salesforce from Starch's integration catalog; the agent queries your deals, territories, and owner data live when your OKR dashboard or automation runs. The HubSpot scheduled sync gives slightly deeper out-of-the-box support — deal sync, owner mapping, schema discovery — but Salesforce is fully reachable for the pipeline and attainment calculations your OKRs depend on.

We also use Apollo for sequences and LinkedIn for prospecting. Can Starch pull activity data from both?

Apollo syncs on a schedule — sequences, contacts, accounts, and opportunities all come through. LinkedIn data comes in via browser automation, which means Starch navigates LinkedIn the way you would and pulls the data without requiring a formal API connection. You can use both as inputs to leading-indicator OKRs like 'sequences started per rep' or 'LinkedIn touches per account.'

Is Starch SOC 2 certified? We'd be connecting our CRM and email data.

Not yet. Starch is not SOC 2 Type II certified today. That's worth knowing before you connect HubSpot, Gmail, or Apollo. If your company has strict data compliance requirements, check with your IT or legal team before connecting production CRM data. The roadmap includes SOC 2 — but we won't tell you it exists before it does.

Will Starch actually set the OKRs for us, or does it just surface data?

Both, depending on what you ask. Starch can analyze last quarter's pipeline and attainment data and suggest objective language with specific numeric targets — it'll tell you 'East territory win rate improved 4 points when reps ran 12+ sequences per week; consider setting 28% win rate as the Q3 target.' But you and the CRO set the final numbers. Starch assembles the evidence and drafts the language; the strategy call is still yours.

We use Notion to document OKRs. Can Starch write back to Notion?

Starch syncs Notion on a schedule — pages and databases come in. For writing back to Notion, that depends on your specific workflow; describe what you want (e.g., 'at quarter close, create a new Notion page summarizing attainment') and Starch will tell you what's possible. The Knowledge Management app inside Starch is also a solid alternative if you want a purpose-built OKR archive that doesn't require a Notion export step.

The CRO keeps changing territory boundaries mid-quarter. How does Starch handle that?

When territory definitions change in HubSpot or Salesforce, Starch picks up the updated owner and territory assignments on the next sync. You'd describe the change to Starch ('the Southeast territory now includes Florida accounts that were in the East bucket — recalculate coverage ratios using the new mapping') and it rebuilds the view. It's not instant, but it's faster than rebuilding your Sheets model by hand every time the org chart shifts.