North Star Framework
One metric that captures the value you deliver.
## 1. Define the value event — ## 2. Make the metric measurable in the stack — ## 3. Connect leading and lagging signals — ## 4. Set one owner and one operating cadence — ## 5. Use the metric to kill bad work —
Why it works▾
A 2026 North Star metric is a control system, not a slogan, and it only works when Clay, PostHog, and 11x are wired to one decision loop.
When to use▾
Use a North Star Framework when the team needs 1 metric that aligns product, marketing, sales, and retention in 2026. It works best for AI-native companies with fast feedback loops, clear user actions, and enough event data in PostHog or Common Room to prove causality. If your funnel is still vague, fix tracking first with Attio, PostHog, and n8n before picking the metric.
Steps in detail▾
1. Define the value event
For example, a B2B AI tool in 2026 might use Clay + LLM scoring to identify accounts that hit the value event within 7 days, then compare those accounts to zero-value accounts in PostHog. If the event does not correlate with retention or expansion, it is not the North Star. Decision rule: if the metric cannot be tied to revenue in Attio or Northbeam within 30 days, cut it.
2. Make the metric measurable in the stack
Example: a B2B SaaS team sends account-level events from Next.js on Vercel into PostHog, then uses Clay to enrich firmographics and Keyplay to flag ICP fit. n8n pushes a daily North Star dashboard into Attio for CSMs and into Slack for operators. Decision rule: if the metric needs manual reconciliation more than 1 time a week, the instrumentation is broken.
3. Connect leading and lagging signals
If your team runs AI SDR with 11x, the leading signals might be reply quality, meeting acceptance rate, and ICP match score from Clay. For a product-led motion, it might be ‘first workflow completed’ and ‘second team member invited’. Decision rule: keep 3 leading metrics max, because 6 leading metrics means nobody owns the number.
4. Set one owner and one operating cadence
Example: an AI-native startup has an ops owner review North Star movement every Monday at 09:00, then uses 11x for outbound, Framer for landing-page changes, and PostHog for conversion analysis. The owner only asks 3 questions: what changed, which segment moved, and what action ships this week. Decision rule: if a meeting has more than 1 slide on the metric, the meeting is already wrong.
5. Use the metric to kill bad work
Example: a growth team uses Clay + Claude scoring to prioritise accounts, then sees that one webinar series increases sign-ups but not the North Star. They replace it with a Relume-built Framer page and a tighter activation flow in Next.js on Vercel, tracked in PostHog. Decision rule: any initiative that does not move the North Star within 2 cycles gets terminated.
Pitfalls▾
- 01Choosing a vanity metric like sign-ups or site visits when PostHog shows no retention lift.
- 02Using 5 metrics and calling them a North Star, which just creates 5 owners and 0 accountability.
- 03Tracking manually in Sheets when Attio, Clay, and n8n can automate the daily number.
- 04Picking a metric that marketing can influence but product cannot, or vice versa, which guarantees blame.
- 05Letting the metric drift for 1 quarter without revalidating it against revenue, retention, and expansion.
Get one interactive framework in your inbox each week
Every Monday. No fluff.