Strategy & Planning

How to track okr progress weekly as Small Customer Success Teams

Strategy & PlanningFor Small Customer Success Teams3 apps10 steps~20 min to set up

Your team owns OKRs that live in a Notion doc nobody updates, a HubSpot pipeline that tells half the story, and a weekly standup where someone says 'I think we're on track' without anyone actually knowing. Every Monday you're manually pulling HubSpot deal stages, counting open Intercom tickets, and eyeballing a usage dashboard that refreshed last Thursday to figure out whether the team's Q2 objective — reduce churn by 15%, expand 20% of accounts — is alive or dead. There's no CS-ops person to build a Gainsight scorecard. There's just you, a spreadsheet, and a nagging feeling you're behind on three key results you haven't looked at in two weeks.

Build this on Starch → See the apps used

Strategy & PlanningFor Small Customer Success Teams3 apps10 steps~20 min to set up

Outcome

What you'll set up

A live OKR progress tracker that pulls HubSpot expansion pipeline, Intercom ticket volume, and usage signals into one surface — updated automatically, not when someone remembers to update it

A weekly digest that lands in Slack or your inbox every Monday morning: which key results are on track, which are slipping, and which accounts are driving the most risk or opportunity that week

A lightweight check-in ritual where your three-person team each logs progress notes against specific KRs in under five minutes — and those notes are searchable the next time someone asks 'what did we decide last month?'

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

CRM Knowledge Management Task Manager

Data sources & config

Starch syncs your HubSpot data on a schedule — contacts, companies, deals, and owners update automatically so your expansion pipeline is always current. Connect Intercom from Starch's integration catalog; the agent queries ticket and conversation data live when your OKR dashboard runs. Starch syncs your Gmail and Google Calendar data on a schedule to pull in meeting activity and email threads tied to accounts. Slack is reachable from Starch's integration catalog so the weekly digest posts directly to your team channel.

Prompts to copy

Build me an OKR tracker for our CS team's Q3 objectives: reduce logo churn below 5%, expand 20% of accounts over $10k ARR, and hit 90% QBR completion rate. Pull deal stage and expansion ARR from HubSpot, open ticket count from Intercom, and show a red/yellow/green status for each key result based on thresholds I can set.

Every Monday at 8am, generate a CS OKR weekly digest: show me where each key result stands vs target, which accounts moved in the HubSpot expansion pipeline this week, how many support tickets are open per customer segment in Intercom, and flag any account that's had more than 3 tickets in the last 7 days.

Create a knowledge base section called 'OKR Check-ins' where each team member can log a weekly progress note against their owned key result. Auto-tag entries by KR name and date, and surface any entry older than 7 days that hasn't been updated.

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

Walkthrough

Step-by-step

1 Connect HubSpot — Starch syncs your deals, companies, and contacts on a schedule. Map your expansion pipeline stage names (e.g., 'Expansion Qualified', 'Expansion Closed Won') to the key result you're tracking: 20% of accounts over $10k ARR expanded.

2 Connect Intercom from Starch's integration catalog. Tell Starch which conversation tags or ticket statuses signal churn risk vs healthy engagement — the agent will query this live each time your OKR surface refreshes.

3 Describe your OKR structure to Starch in plain language: your one top-level objective for the quarter, the 3–4 key results, who owns each one, and what 'on track' looks like numerically for each KR.

4 Starch builds your OKR tracker app: one row per key result, with current value pulled from the relevant data source, a progress bar against target, and a red/yellow/green status based on thresholds you set. No spreadsheet formulas to maintain.

5 Set up the Monday 8am weekly digest automation. Starch pulls the latest HubSpot pipeline movement, Intercom ticket counts, and any accounts that crossed a risk threshold in the past week, then formats a summary and posts it to your Slack channel or emails it to the team.

6 Use the Knowledge Management app to create an 'OKR Check-ins' section. Each of your three team members logs a brief progress note against their owned key result once a week — two or three sentences, what moved, what's blocked.

7 Tell Starch to flag any key result where the owner hasn't logged a check-in in more than 7 days. This replaces the Monday standup question 'wait, where are we on that?' with an actual answer.

8 For QBR completion rate tracking (if that's one of your KRs), connect Google Calendar from Starch's scheduled sync. Starch can count completed QBR events per account over the quarter and compare against your book of business count from HubSpot.

9 Once a month, ask Starch to generate a mid-quarter OKR summary: which KRs are on track, which are behind, what the team logged as blockers in their check-in notes, and which accounts are showing the clearest expansion or churn signals. Use this as your team's 30-minute mid-quarter reset instead of a slide deck nobody made.

10 At quarter close, use the Task Manager to capture any KR-related action items that surfaced during the final review — things like 'schedule expansion conversation with Acme Corp' or 'update churn threshold for next quarter' — with P1/P2 priorities and due dates so nothing falls into the void between quarters.

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 Mid-Quarter OKR Check — Week 7

Sample numbers from a real run

KR1: Logo churn below 5%	3
KR2: 20% of $10k+ ARR accounts expanded	8
KR3: 90% QBR completion rate	11

It's Monday morning of week 7. The OKR digest hits Slack at 8am. KR1 shows 3 logos churned so far — you're tracking at 2.4% churn against a 5% target, green. KR2 shows 8 expansions closed or in 'Expansion Closed Won' in HubSpot out of a target of 14 accounts — yellow, 57% of the way there with 6 weeks left. The digest flags two accounts — Thornfield Health ($18k ARR) and Kellner Group ($12k ARR) — as having 5+ Intercom tickets in the past 14 days with no expansion deal in HubSpot, meaning they're high-touch but not yet in any expansion conversation. KR3 shows 11 QBRs completed out of a target of 24 for the quarter — also yellow. Your team's check-in notes from last week (logged in Knowledge Management) show one team member flagged that three QBRs slipped because of scheduling conflicts, not account health. That's a fixable problem. In 12 minutes of Monday morning, all three of you know exactly where you stand, which two accounts need attention this week, and that the QBR lag is a calendar problem, not a churn signal.

Measurement

How you'll know it's working

Logo churn rate (%) against quarterly target — tracked at the account level, not just as a lagging headline number

Expansion pipeline coverage: number of accounts in an active expansion deal stage in HubSpot vs target expansion count

QBR completion rate: QBRs held as a percentage of accounts due for a quarterly review

High-ticket accounts: number of accounts with 3+ open Intercom tickets in the last 14 days, used as a leading churn indicator

KR check-in cadence: percentage of key results with a team member update logged in the past 7 days — a proxy for whether the OKR process is actually running

Comparison

What this replaces

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

Gainsight or ChurnZero

Purpose-built for CS OKR and health scoring but starts at $30k–$60k/year, requires a CS-ops person to configure, and takes months to stand up — not built for a 3-person team with 250 accounts.

Notion + manual updates

Free and flexible, but someone has to remember to update it — and on a 3-person team, that person is you, every week, pulling numbers from three different tools by hand.

HubSpot Goals (native)

Tracks deal-based metrics natively but can't pull in Intercom support signals, calendar-based QBR completion, or usage data — so you still have a partial picture.

Lattice or Ally.io (OKR software)

Designed for HR and company-wide OKR programs, not CS-specific workflows — doesn't connect to HubSpot pipeline or Intercom ticket volume without custom integration work.

On Starch RECOMMENDED

One platform — crm, knowledge management, task manager 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 actually stay in sync with HubSpot, or do I have to trigger a refresh manually?

Starch syncs your HubSpot contacts, companies, and deals on a schedule automatically. You don't push a button — the data in your OKR tracker reflects what's in HubSpot as of the last sync. For most CS teams tracking weekly OKR progress, this is exactly the right cadence.

We track churn risk partly through Intercom ticket patterns. Can Starch read that?

Yes. Connect Intercom from Starch's integration catalog and the agent queries your ticket and conversation data live when your OKR dashboard runs. You can tell Starch what signal to look for — more than 3 open tickets in 14 days, specific tags, response time thresholds — and it will surface those accounts.

What if one of our key results involves something that isn't in HubSpot or Intercom — like QBR completion rate tracked through calendar events?

Starch syncs your Google Calendar data on a schedule — events going back 12 months and 3 months ahead. You can tell Starch to count events that match a naming pattern (like 'QBR' or 'Quarterly Review') per account and compare against your account list from HubSpot. It's not a formal QBR tracking system, but for a team of three it works.

Is Starch SOC 2 certified? We'd be pulling in HubSpot deal data and customer account information.

Starch is not currently SOC 2 Type II certified. If your company has strict data security requirements for third-party tools touching customer data, that's worth knowing before you connect production CRM data. It's on the roadmap.

Can Starch replace our weekly OKR standup entirely?

It can replace the part where everyone shows up unprepared and someone says 'I think we're on track.' The Monday digest gives your team the numbers before the meeting starts. What it doesn't replace is the judgment call about what to do when KR2 is yellow — that's still a conversation. Starch surfaces the facts; your team makes the call.

We use Zendesk, not Intercom. Does that matter?

No. Zendesk is reachable from Starch's integration catalog — the agent queries your ticket data live the same way it would with Intercom. Same setup, different tool.