Strategy & Planning

How to track okr progress weekly as Professional Services Founders

Strategy & PlanningFor Professional Services Founders3 apps10 steps~20 min to set up

You set OKRs in January in a Notion page nobody reads by March. Checking progress means pinging five people on Slack, cross-referencing a HubSpot pipeline, squinting at a Google Sheet someone updated two weeks ago, and triangulating billable hours from Harvest or a timesheet email thread. By the time you've assembled the picture, the week is half over and the numbers are already stale. There's no single view of whether your firm is on track against revenue targets, utilization goals, or client-delivery commitments. OKR reviews become gut-feel conversations instead of data-driven ones — and when a key result slips, you find out a month too late to do anything about it.

Build this on Starch → See the apps used

Strategy & PlanningFor Professional Services Founders3 apps10 steps~20 min to set up

Outcome

What you'll set up

A weekly OKR tracker that pulls live data from HubSpot deals, Stripe invoices, and Google Calendar utilization into one view — so you walk into every Monday review knowing exactly where each key result stands

A structured meeting cadence with auto-captured notes, decisions, and action items from each OKR check-in — so nothing discussed on the call evaporates before anyone acts on it

A centralized knowledge base that stores the OKR definitions, scoring criteria, and historical progress so any senior on your team can find context without asking you first

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

Task Manager Meeting Notes Knowledge Management

Data sources & config

Starch syncs your HubSpot deal and pipeline data on a schedule (HubSpot is a scheduled-sync provider), syncs your Stripe charges and invoices on a schedule, and syncs your Google Calendar events on a schedule so billable-meeting hours are calculated automatically. Slack is connected from Starch's integration catalog and queried live to post the Monday summary. Notion, if you store OKR context there, is also synced on a schedule and searchable inside Knowledge Management. Any time-tracking tool like Harvest or Float that doesn't have a direct sync is reachable through browser automation — no API required.

Prompts to copy

Build me a weekly OKR progress tracker for a 12-person professional services firm. Pull our open deals and pipeline value from HubSpot, our collected revenue from Stripe, and count billable-meeting hours from Google Calendar. Show me a dashboard with each OKR, its target, current progress as a percentage, and a red/yellow/green status. Refresh every Monday morning at 7am and Slack me a summary.

Every time we run our weekly OKR review meeting, transcribe the call, pull out decisions made on each key result, assign follow-up tasks to the relevant team member, and archive the notes in our Knowledge Management app tagged by OKR and week.

Set up a Knowledge Management space for our firm's OKR program. Organize it by quarter. Each OKR should have a page with the original definition, scoring rubric, owner, and a running log of weekly check-in summaries. Flag any OKR page that hasn't been updated in 14 days.

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

Walkthrough

Step-by-step

1 Connect HubSpot, Stripe, and Google Calendar as scheduled-sync providers. Starch will pull your pipeline stage values, collected revenue, and calendar event data automatically on a recurring schedule — no manual exports.

2 Connect Slack from Starch's integration catalog so the agent can post your Monday OKR summary to a channel your whole team sees, like #ops or #leadership.

3 Tell Starch: 'Build me a weekly OKR dashboard for our consultancy. Our five key results this quarter are: $1.2M in collected revenue, 72% billable utilization, 90% client NPS, 8 net-new RFPs won, and 100% of retainers renewed on time. Show status for each one, pulling revenue from Stripe, utilization from Google Calendar, and pipeline wins from HubSpot.'

4 Starch builds the dashboard and sets a Monday 7am refresh. Review it each Monday before your team standup — green, yellow, red at a glance for all five key results.

5 Start your weekly OKR review meeting with Meeting Notes running. It transcribes in real time, so you can focus on the conversation rather than typing. After the call, it generates a summary with decisions flagged by key result.

6 Meeting Notes extracts action items automatically — 'Sarah to follow up with three lapsed retainer clients by Wednesday,' 'James to update utilization methodology in Notion' — and assigns them with due dates so nothing lives only in someone's head.

7 Archive each week's meeting summary into Knowledge Management, tagged by quarter, week, and the OKR it relates to. Next time someone asks 'wait, why did we change how we score utilization?' the answer is searchable in under ten seconds.

8 Use the Task Manager to track your personal OKR-related actions: 'Review pipeline coverage before Friday board call,' 'Send retainer renewal notices to clients expiring in 45 days.' Capture them via chat — 'remind me to check Q2 OKR status every Friday at 4pm' — and Starch sets the recurring task.

9 At mid-quarter (week 6), tell Starch: 'Compare our current OKR progress against where we were at week 6 last quarter. Flag any key results that are more than 15% behind pace and suggest what's likely driving the gap based on our HubSpot and Stripe data.' Starch surfaces the comparison without you building a spreadsheet.

10 At quarter-end, tell Starch: 'Generate a one-page OKR close-out summary for our Q2 review. Include final scores for each key result, a two-sentence explanation of what drove results above or below target, and three recommended adjustments for Q3.' Use the output as the backbone of your quarterly leadership debrief.

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

Sample numbers from a real run

Collected revenue vs $1.2M target	610,000
Billable utilization vs 72% target	67
Net-new RFPs won vs 8 target	4
Retainer renewals on time vs 100% target	88
Client NPS vs 90 target	91

It's Monday, April 14. Starch's weekly OKR dashboard lands in #leadership at 7:03am. Collected revenue is at $610K against a $1.2M full-quarter target — right on pace at 51% with 7 of 13 weeks done. Billable utilization sits at 67%, five points short of the 72% target; the dashboard flags it yellow. Starch cross-references the Google Calendar sync and notes that four senior consultants had two or more internal-only weeks since March, pulling the number down. You open the weekly OKR review at 9am with Meeting Notes running. The team discusses resourcing. Starch captures the decision: 'Marcus to move off the internal methodology project back to client delivery starting April 21.' That action item is assigned to Marcus with a due date and lands in his Task Manager before the call ends. The retainer renewal score — 88%, one client not yet confirmed — triggers a follow-up task to you: 'Call Meridian Partners re: Q3 renewal, deadline May 1.' RFPs at 4 of 8 wins prompt a Slack message to the BD lead. NPS at 91 is green, the one bright spot. The whole review runs 28 minutes. The summary, decisions, and tasks are in Knowledge Management before noon, tagged Q2 / Week 7 / each relevant OKR. By Wednesday you know Marcus is back on client work, the retainer call is booked, and the utilization trend is reversing. None of this required a spreadsheet or a Friday-afternoon data-gathering session.

Measurement

How you'll know it's working

Billable utilization rate by week (target vs. actual, per senior)

Collected revenue against quarterly target (from Stripe, week-over-week)

Pipeline coverage ratio — open HubSpot deal value vs. revenue needed to hit target

Retainer renewal rate and days-to-renewal for at-risk accounts

OKR completion rate at quarter-end (number of key results scored green)

Comparison

What this replaces

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

Notion OKR tracker + manual HubSpot export

Free and flexible, but the data is always a week stale and someone has to own the update — usually you.

Lattice or Leapsome

Purpose-built OKR tools with good structure, but they don't pull financial or pipeline data automatically, so utilization and revenue progress still require manual input from your stack.

Kantata / Projector / Deltek (PSA platforms)

Comprehensive for 50+ person firms, but implementation takes a quarter, pricing assumes headcount you don't have, and they still won't connect your Stripe invoices to your OKR view without custom work.

Google Sheets OKR template + Zapier automations

Cheap and customizable, but you'll spend more time maintaining the zaps and formulas than reviewing the actual numbers — and it breaks every time a source schema changes.

On Starch RECOMMENDED

One platform — task manager, meeting notes, 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 track billable hours in Harvest. Can Starch pull that in?

Harvest doesn't have a dedicated scheduled-sync in Starch today, but Starch can reach Harvest through its integration catalog — the agent queries it live when your dashboard runs. Alternatively, if your utilization is already reflected in Google Calendar (which Starch syncs on a schedule), Starch can calculate billable hours directly from calendar event data without touching Harvest at all. Many professional services founders find the Calendar sync is sufficient for weekly tracking.

We use Notion for our OKRs today. Will Starch replace that?

It doesn't have to. Starch syncs your Notion data on a schedule, so your existing Notion OKR pages stay where they are and Starch reads from them. The Knowledge Management app in Starch can complement Notion — handling meeting note archives and action-item history — without you having to migrate everything. If you eventually want to consolidate, you can, but it's not required to get value on day one.

What if we don't use HubSpot — our pipeline lives in a Google Sheet?

Google Sheets is reachable from Starch's integration catalog and queried live when your OKR dashboard runs. Tell Starch: 'Pull our pipeline data from this Google Sheet — column C is deal name, column E is deal value, column G is stage' — and it maps accordingly. It's not as structured as a native CRM sync, but it works for a firm that hasn't moved to HubSpot yet.

Is the Meeting Notes app capturing calls from Google Meet or Zoom?

Meeting Notes is built to capture your OKR review meetings. Google Meet and Zoom are reachable from Starch's integration catalog. For the best results, run the OKR review with Meeting Notes active at the start of the call. The transcription, summary, and action-item extraction happen automatically after the call ends.

Does Starch store our financial data? We're cautious about data security.

Starch stores the data it syncs from scheduled-sync providers — Stripe revenue, HubSpot pipeline, Google Calendar events — in Starch's database so your dashboard can query it quickly. Starch is not currently SOC 2 Type II certified, so if your firm has compliance requirements that mandate certified vendors for financial data processing, that's worth knowing upfront. For most 12-person consultancies, this isn't a blocker, but we'd rather you ask now than discover it later.

Can I set this up myself or do I need someone technical on my team?

The whole point is that you don't. You connect your tools through Starch's integration browser — HubSpot, Stripe, Google Calendar take a few minutes each — and then describe what you want in plain language. 'Build me a weekly OKR dashboard that tracks these five key results against these targets and Slacks me every Monday morning' is a complete instruction. No code, no drag-and-drop configuration, no implementation consultant.