How to set quarterly okrs as Asset Management Founders

Strategy & PlanningFor Asset Management Founders3 apps12 steps~24 min to set up

You're running a sub-$100M fund with no analyst, no chief of staff, and no ops person. Setting quarterly OKRs means pulling together data scattered across a QuickBooks export, a Notion doc nobody's updated since last quarter, three LP call notes buried in your Gmail, and a Stripe dashboard you have open in a tab somewhere. You write OKRs in a Google Doc, share them with your advisory board, and six weeks later you can't remember what you committed to because the doc is version 11 and the action items from the Q2 kickoff call were never written down. Large funds use dedicated strategy ops people for this. You're doing it Sunday night before the Monday partners meeting.

Strategy & PlanningFor Asset Management Founders3 apps12 steps~24 min to set up
Outcome

What you'll set up

A quarterly OKR framework grounded in your actual fund data — LP commitments, portfolio performance, deployment pace — not gut feel and last quarter's spreadsheet
A searchable, living knowledge base where every OKR, key decision, and LP conversation is organized and findable when you need it six months later
A meeting workflow that automatically captures your quarterly planning sessions, extracts your OKR commitments as action items, and archives them so nothing falls through the cracks
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.

Data sources & config

Starch syncs your Notion pages on a schedule so the knowledge-management app can pull in existing strategy docs, fund memos, and LP notes as context. Gmail is connected as a scheduled-sync provider so meeting follow-ups and LP correspondence can be surfaced when you're reviewing OKR progress. Calendly and Google Calendar sync on a schedule to tie planning sessions to your OKR review cadence. Task Manager queries your OKR data live when generating your weekly priority list.

Prompts to copy
Build me a quarterly OKR tracker for an emerging fund. I need objectives organized by: LP relations, portfolio deployment, fund operations, and personal development. Each objective should have 2-3 key results with a numeric target, owner (just me for now), current status, and a notes field. Pull in any relevant context from my Notion pages about fund strategy.
I just finished my Q3 planning call with my advisory board. Transcribe and summarize it, extract every commitment I made as an action item with a due date, and flag any key results I mentioned that differ from what's in my OKR tracker.
Create a priority task list from my Q3 OKRs. Any key result that needs an action in the next 30 days should become a P1 or P2 task with a due date. Remind me every Monday morning what's overdue.
Run these in Starch → or paste them into your favorite agent
Walkthrough

Step-by-step

1 Connect your Notion workspace — Starch syncs your pages on a schedule — and point the Knowledge Management app at your existing fund strategy docs, investment theses, and prior quarterly reviews so it has context before you write a single OKR.
2 In the Knowledge Management app, type: 'Build me an OKR library for an emerging fund manager. Organize by four pillars: LP Relations, Portfolio Deployment, Fund Operations, and Founder Development. Pre-populate with common emerging fund objectives and let me edit each one.' Use this as your starting scaffold.
3 Replace the template objectives with your actual Q targets — deployment pace in dollars, number of LP touchpoints, AUM growth target, number of new portfolio introductions — pulled from what Starch already knows about your Stripe and QuickBooks data.
4 Schedule your quarterly planning meeting in Google Calendar. Starch syncs your calendar on a schedule, so Meeting Notes will automatically know when the session is happening and be ready to transcribe.
5 Run the planning session. Meeting Notes transcribes in real time. After the call ends, ask it: 'Summarize the decisions made, list every commitment I made as an action item with a due date, and flag any targets we discussed that aren't in my current OKR doc.'
6 Review the extracted action items. Any OKR-level commitment — 'schedule LP updates for all 12 LPs before October 1' — goes into the Task Manager as a P1 with the due date Meeting Notes pulled from the conversation.
7 For each key result that requires tracking a metric you don't manually control — portfolio company revenue, fund cash position — wire the relevant connection. QuickBooks syncs on a schedule for fund-level expenses; Stripe syncs on a schedule for any revenue-bearing entities you manage.
8 Set a weekly check-in automation: 'Every Monday at 8am, pull my open P1 and P2 tasks, check which key results are behind target based on my current data, and send me a Slack message with a status summary and what I need to do this week to stay on track.'
9 After each LP call, open Meeting Notes and ask it to extract any feedback, commitments, or follow-ups relevant to your LP Relations OKR pillar. Archive it in the Knowledge Management app tagged to that LP and that quarter.
10 At the 6-week mark, run a mid-quarter OKR review: 'Compare my Q3 key results targets against current actuals from my connected data. Which key results are on track, which are at risk, and what changed since the quarter started?' Starch surfaces this from your synced QuickBooks, Stripe, and Notion data.
11 Build your end-of-quarter board or LP update by telling Starch: 'Draft a 1-page OKR retrospective for Q3 showing each objective, whether we hit the key results, and a two-sentence explanation of what drove the result.' The Knowledge Management app has all your notes; Meeting Notes has the call transcripts; the task history shows what got done.
12 Archive the completed quarter in your knowledge base and fork the OKR template for Q4, carrying forward any key results that rolled over and clearing the ones you hit.

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 — $42M AUM Emerging Fund, Solo GP

Sample numbers from a real run
LP Relations — Schedule 1:1 updates with all 18 LPs before Oct 118
Portfolio Deployment — Deploy $4.2M across 3 new investments by Sept 304,200,000
Fund Operations — Reduce monthly close time from 12 days to 7 days7
Founder Development — Complete 2 anchor LP intro meetings for Fund II pipeline2

It's July 7th. You just finished a 90-minute Q3 planning call with your two advisors. Meeting Notes transcribed the whole session and flagged four commitments you made out loud: schedule all 18 LP updates by October 1, deploy $4.2M in the quarter (you're at $1.1M deployed so far, per your Stripe and QuickBooks data), get your monthly close time from 12 days to 7 by fixing the Plaid-to-QuickBooks reconciliation lag, and set up two Fund II anchor LP intro meetings before the summer ends. Those four commitments become your Q3 OKRs in about 20 minutes. The Task Manager immediately surfaces three P1 tasks: draft the LP update email this week, schedule the two anchor LP meetings by July 15, and review the close process with your accountant by July 20. At the 6-week mark you ask Starch for a mid-quarter read: you've done 11 of 18 LP updates, deployed $2.8M of the $4.2M target, and the close time is at 9 days — better, not there yet. You've got six weeks to close the gap, and you have the data to show your advisory board exactly where you stand.

Measurement

How you'll know it's working

Quarterly deployment pace — dollars invested vs. target, tracked against fund commitment schedule
LP touchpoint coverage — number of LPs contacted vs. total LP count in the quarter
Monthly close time — days from month-end to finalized fund financials
Key result completion rate — percentage of quarterly key results hit at end of quarter
Fund II pipeline progress — number of anchor LP intro conversations completed vs. target
Comparison

What this replaces

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

Google Docs + Notion
Free and familiar, but OKRs live in a static doc disconnected from your fund data — you're manually updating numbers and losing action items in meeting notes that never get written down.
Lattice or Weekdone
Built for teams with managers and direct reports; the check-in workflows assume you have people to check in on, not a solo GP managing 18 LPs and a portfolio.
Juniper Square or Addepar
Purpose-built for fund operations but starts at $50k+/year, assumes a dedicated ops team, and doesn't touch your OKR or meeting workflows at all — you'd still need something else for planning.
Asana or ClickUp
Good task tracking but no connection to your fund financials, no meeting transcription, and no AI layer to generate OKRs from your actual data — you're still doing the synthesis manually.
On Starch RECOMMENDED

One platform — knowledge management, meeting notes, 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 connect to the fund accounting tools I already use, like QuickBooks or NetSuite?
Yes. Starch syncs your QuickBooks data on a schedule — invoices, bills, payments, vendors, journal entries — so when you're setting a key result like 'reduce operating expenses by 15%' you're working from real numbers, not a number you vaguely remember from last month's close. NetSuite syncs the same way. One honest note: QuickBooks report views like P&L summaries are temporarily unavailable while we fix an upstream issue, but entity-level data syncs normally.
I already take notes in Notion. Will Starch overwrite or duplicate what's there?
Starch syncs your Notion pages on a schedule and reads them as context — it doesn't write back to Notion or modify your existing docs. Your Notion stays as-is. The Knowledge Management app in Starch becomes the layer where your OKRs, meeting summaries, and action items live together and stay searchable, pulling context from Notion when it's relevant.
What if my LP relationship notes are in Gmail, not Notion?
Starch syncs your Gmail on a schedule too. When you're reviewing your LP Relations OKR pillar, you can ask Starch to surface relevant threads — 'show me all emails with LP X in the last 90 days' — and use that context when drafting your update or logging a touchpoint. You can also connect Outlook if that's what you use.
Is Starch SOC 2 certified? I need to think about what data I'm putting in here.
Starch is not SOC 2 Type II certified yet, and there's no on-prem or self-hosted option. That's worth knowing before you connect sensitive LP data or fund financials. We're building toward SOC 2 and will communicate clearly when it's done. For founders at the early emerging-fund stage, most find the tradeoff acceptable given the alternative is manual processes and worse security hygiene, but it's your call to make.
The Meeting Notes and Task Manager apps are listed as 'in development.' Can I use them now?
They're currently in development. You can request beta access and get notified when they launch. In the meantime, the Knowledge Management app is live and can handle your OKR documentation and search. For meeting capture, your current workflow (whatever you're doing now) bridges until Meeting Notes ships.
Can Starch build me a custom OKR tracker if the pre-built template doesn't fit how I run my fund?
Yes — that's the core idea. Describe what you want in plain language and Starch builds it. If you track OKRs differently — say, by LP cohort rather than by pillar, or you want to tie each key result to a specific portfolio company — just tell Starch that. You're not locked into any template structure. The Knowledge Management app is the starting point; a fully custom OKR surface is a description away.

Ready to run set quarterly okrs on Starch?

Request closed-beta access. Everything is free during beta.

You're on the list! We'll be in touch soon.