agentleFS
CodeAlive-AICodeAlive-AI/ceo-ai-os/skills/metrics-briefing/SKILL.md

metrics-briefing

Skill9 starsChanged 6 months agoMITView on GitHub

CEO-level metrics interpretation through 9-category framework (market learning, product value, usage, pipeline, retention, B2C->B2B, execution, economics, PMF). For raw PostHog data queries, use posthog-analytics instead.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do they share the same painful problem?

    line 17
  2. Distinctive:

    Do they get value quickly?

    line 18
  3. Distinctive:

    Do they come back?

    line 19
  4. Distinctive:

    Follow output preferences from USER.md (language, format, platform constraints).

    line 175

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Metrics Briefing

Metrics analysis through CEO Bible Section G — 9 categories. PostHog covers some; the rest come from conversations, CRM, and the founder's observations.

Principles (Bible G)

  1. All metrics by target wedge. Segment first, aggregate second.
  2. Behavior > opinions. Usage, money, time spent > compliments.
  3. Pre-PMF metrics answer 5 questions:
    • Are we talking to the right people?
    • Do they share the same painful problem?
    • Do they get value quickly?
    • Do they come back?
    • Can we win them again without heroics?
  4. MRR, CAC, LTV are guardrails, not the steering wheel. Until there is repeatability.

9 CEO Metrics Categories

1. Market Learning (MANUAL — ask the founder)

MetricDefinitionPostHog?
Qualified conversations/week20+ min conversations with target roles; explored problem, trigger, workaround, buyer, urgencyNo — track manually, target 8-12/week
Repeated pain rateSame problem + trigger + workaround recur / total qualified conversationsNo — from conversation notes
Objection concentrationLosses/stalls by top 3 reasons / all lossesNo — from CRM/notes

If conversations < 8/week -> flag hard. This is the main leading indicator.

2. Product Value (PostHog: partial)

MetricDefinitionPostHog
Median TTFVTime from signup to first meaningful successuser_journey_milestone WHERE milestone='First Value Moment', property timeSincePrevious
Activation rateTarget accounts hitting critical event sequence within X daysfunnel_next_stage_available WHERE currentStage='first_value_delivered' / total signups
Outcome attainmentActivated accounts achieving promised business resultfunnel_next_stage_available: first_value_delivered -> return_usage conversion rate

3. Usage / Engagement (PostHog: yes)

MetricDefinitionPostHog
Retained active target accounts (week 4/8)Accounts still performing core workflowuser_journey_milestone WHERE milestone='Weekly Active'
Workflow depthCore workflow at target frequency, multiple use casescore_query_performed frequency, deep_workflow_started, searchMode breakdown
Second-bite rateUsers repeating core action within X daysfunnel_next_stage_available: first_value_delivered -> return_usage

4. Sales / Pipeline (MANUAL — CRM/conversations)

MetricDefinitionPostHog?
ICP pipeline createdNew opportunities from target wedge per weekNo — CRM
Meeting -> opportunityNew opps / qualified first meetingsNo — CRM
Opportunity -> win rateClosed-won / closed in target wedgeNo — CRM
Median sales cycleDays from first meeting to signatureNo — CRM

5. Retention / Expansion (PostHog: partial)

MetricDefinitionPostHog
Healthy account ratePaid accounts with green usage + outcome + active championfunnel_next_stage_available: regular_usage+ stage, organizationId grouping
Expansion pull rateHealthy accounts requesting more seats/team rolloutfunnel_next_stage_available WHERE nextStage='team_invitation_sent'
Gross logo retentionPaying logos retained once cohorts matureNot fully — partially through return/regular/power stages

6. B2C -> B2B Conversion (PostHog: yes — key category)

MetricDefinitionPostHog
Target-signup rateSignups from target roles/domains / total signupsuser_journey_milestone milestone='Account Created', filter by email_verified + has_primary_integration_connected
Activated -> PQL rateActivated users hitting enterprise triggerspower_user stage + deep_workflow_started + organizationId
PQL -> sales conversationPQLs that book real sales callPartial — track manually
Same-company emergenceActive companies with >1 user or team invitefunnel_next_stage_available nextStage='team_invitation_sent', organizationId grouping

7. Team Execution (MANUAL)

MetricDefinitionPostHog?
Experiment cycle timeDays from hypothesis to readoutNo — from hypothesis tracker
Hypothesis-linked roadmap %Work tied to hypothesis / total workNo — from backlog
Belief-change rateExperiments ending in keep/kill/reframe / totalNo — from weekly reviews

8. Unit Economics (MANUAL)

MetricDefinitionPostHog?
Net burn / runwayMonthly cash burn; cash / burnNo — finance
Core workflow contribution margin(Revenue - variable delivery costs) / revenueNo — finance
Revenue concentrationTop 3 customers / total ARRNo — finance

9. PMF Detection (MIX)

MetricDefinitionPostHog
Wedge repeatability scoreLast 10 wins matching same ICP/problem/buyer/onboarding / 10No — manual assessment
Durable revenue ratioRevenue from accounts past trial + healthy >90 days / totalPartial — through regular_usage/power_user stages
Organic pull indexTarget-cohort referrals, unsolicited inbound, expansion requestsPartial — public_output_viewed, output_sharing_enabled as signals

PostHog Implementation Layer

Core Funnel (funnel_next_stage_available events)

signup_started -> account_created -> email_confirmed
  -> workspace_created -> first_value_moment
  -> first_primary_resource_added -> primary_resource_processed
  -> first_key_action_executed -> first_value_delivered
  -> return_usage -> regular_usage -> power_user
  -> team_invitation_sent

4 Analytics Layers

  1. Anonymous visitor: $initial_utm_source, $initial_referring_domain, $initial_current_url
  2. User identity: $identify, email_verified, has_primary_integration_connected
  3. Product value: workspace_create_started, primary_resource_action, core_query_performed, core_action
  4. Account/company: organizationId (on all events) — B2B grouping

Attribution Model

  • First-touch (person.$initial_*): "What created initial interest?" -> content, SEO, founder content
  • Last-touch: "What triggered conversion?" -> pricing page, CTA performance
  • Right question: "Which source produces the most retained companies?" — apply to activation, PQL, paid, retained

PostHog Query Recipes

CEO Morning Briefing:

# Signups yesterday
posthog__query-generate-hogql-from-question question="How many user_journey_milestone events with milestone Account Created happened yesterday?"

# Funnel transitions yesterday
posthog__query-generate-hogql-from-question question="Show all funnel_next_stage_available events from yesterday, count by currentStage to nextStage"

# Active companies this week
posthog__query-generate-hogql-from-question question="How many distinct organizationId values had any events in the last 7 days?"

Weekly Dashboard:

# Funnel health (all stages)
posthog__query-generate-hogql-from-question question="Show funnel_next_stage_available events in the last 7 days, count unique users for each currentStage to nextStage pair"

# TTFV
posthog__query-generate-hogql-from-question question="What is the average timeSincePrevious for user_journey_milestone where milestone is First Value Moment, last 30 days?"

# Attribution: source -> activation
posthog__query-generate-hogql-from-question question="For users who reached first_value_delivered in funnel_next_stage_available last 30 days, what are the top initial UTM sources?"

# Account-level: companies with multiple users
posthog__query-generate-hogql-from-question question="Which organizationId values have more than 1 unique user performing events in the last 30 days?"

Vanity Metrics (DO NOT report as progress)

  • Total traffic, total signups, total "active users" mixed
  • Feature count shipped
  • Total pipeline across all segments
  • PR hits, likes, followers
  • Total MRR without durability/health filters
  • B2C DAU that never clusters into accounts
  • "AI usage" with no evidence of business outcome

Metrics That Matter LATER (after PMF)

CAC payback, LTV/CAC, quota attainment, forecast accuracy, mature NRR, Rule of 40, hiring efficiency.

Telegram Format (max 15 lines)

Metrics for [period]:

Learning: X conversations (target 8-12), pain rate Y%
Product: TTFV Xh, activation Z%
Usage: retained W4 X%, second-bite Y%
B2C->B2B: X signups -> Y activated -> Z PQL, same-co X
Pipeline: X opps, win rate Y%
PMF: repeatability [low/growing], organic pull [none/emerging]
Burn: $X/mo, runway Y months

Conclusion: [what this means for the current stage]
Action: [concrete action]

Follow output preferences from USER.md (language, format, platform constraints).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.