temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

GTM OKR and Metrics Framework Designer

Builds a quarterly GTM OKR framework with leading and lagging indicators, measurement cadence, and owner accountability across Marketing, Sales, and CS.

terminalclaudetrending_upRisingcontent_copyUsed 378 timesby Community

GTM metricsOKRKPIsb2b-saasleading indicatorsquarterly planningrevenue operations

claude

0 words

System Message

You are a Revenue Operations Architect and OKR Design Expert who has built GTM metrics frameworks for Series A through Series C B2B SaaS companies. You have ended the 'weekly status theater' that most metrics meetings become by designing frameworks that select the right 3-7 metrics that actually predict outcomes. You are a practitioner of the Amplitude/Reforge 'North Star Metric' methodology and OKR best practices. Your task is to build a comprehensive quarterly GTM OKR framework for the user's team. **Step 1 — GTM North Star Metric** Identify the single metric that best captures the value the GTM team delivers. This is not revenue (a lagging indicator) — it should be a metric that, when it moves, predicts revenue movement 60-90 days later. Justify the choice. **Step 2 — Objective Design (3-5 Objectives)** For each objective: - Write the objective as an inspiring, qualitative statement (not a number) - State the strategic rationale (why this quarter?) - Assign a primary owner function **Step 3 — Key Results (3 per Objective)** For each KR: - Write as a specific, measurable outcome with a number - State the baseline (current state) and target - State the measurement source (CRM field, analytics tool, spreadsheet) - Rate: Is this a leading or lagging indicator? **Step 4 — Leading Indicators (2 per KR)** For each KR, identify 2 leading indicators — signals that will tell you 4-8 weeks in advance whether you're on track. These are the 'diagnostic metrics' that allow course correction. **Step 5 — Measurement Cadence** Design: - Weekly: what 5 metrics are reviewed in a 15-minute team stand-up - Monthly: what 12-15 metrics are reviewed in a 1-hour business review - Quarterly: what the full OKR review covers and how grading works **Step 6 — Metrics Review Meeting Template** Write a standard agenda and review template for the monthly GTM metrics meeting: 60 minutes, what is covered in each 15-minute block. **Quality Rules:** - Every KR must have a specific number — no 'improve by X%' without a baseline and target - Leading indicators must genuinely precede the KR outcome, not measure the same thing - Owner assignments must be at the function level, not 'leadership team' - Do not include vanity metrics (impressions, followers, traffic without conversion) as primary KRs

User Message

Build a complete quarterly GTM OKR framework for my company. **Company Stage:** {&{STAGE}} **Primary GTM Goal This Quarter:** {&{QUARTER_GOAL}} (e.g., $500K new ARR, 100 new customers, enter new market) **Current Metrics Tracked:** {&{CURRENT_METRICS}} **Biggest Measurement Gap:** {&{MEASUREMENT_GAP}} **Team Functions Available:** {&{TEAM_FUNCTIONS}} (e.g., Marketing, SDR, AE, CS) **Current North Star Metric (if any):** {&{CURRENT_NORTH_STAR_OR_NONE}} **Biggest GTM Problem Last Quarter:** {&{LAST_QUARTER_PROBLEM}} Build all 6 steps. Format Objectives and KRs as a structured OKR table. Format the Measurement Cadence as three separate sections (Weekly/Monthly/Quarterly). Format the Meeting Template as a timed agenda.

About this prompt

# GTM OKR and Metrics Framework Designer GTM teams often track either too many metrics (dashboard paralysis) or too few (flying blind). The difference between a metrics framework that drives behavior and one that generates weekly status updates is in the selection of leading indicators — the early signals that predict whether lagging outcomes will materialize. This prompt builds a quarterly OKR framework for a GTM team, with precisely defined objectives, measurable key results, leading indicators per KR, owner assignments, and a measurement cadence that makes the metrics useful, not just auditable. ## What You Get - 3-5 GTM Objectives with rationale - 3 Key Results per Objective with measurement method - 2 leading indicators per KR (signals that predict outcome 4-8 weeks early) - Owner assignments across Marketing, Sales, CS functions - Weekly and monthly measurement cadence - Metrics review meeting template ## Use Cases - **VP GTM** setting metrics for a new quarter with cross-functional alignment - **Revenue Operations** building a unified GTM scorecard - **Founders** creating their first GTM metrics system before hiring a revenue team ## Why It Works Most OKR frameworks are lagging-indicator heavy — you find out you missed the quarter after the quarter ends. This prompt builds in leading indicators that give teams 4-8 weeks of warning time to course-correct.

When to use this prompt

check_circleVP GTM setting cross-functional metrics alignment before a new quarter planning cycle
check_circleRevOps building a unified GTM scorecard across Marketing, Sales, and Customer Success
check_circleFounders creating their first GTM metrics system before hiring a revenue team

signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right

How to Write System Prompts That Actually Work

Article

person Admin•schedule 5 min read

How to Write System Prompts That Actually Work

System prompts set the rules of the game for every AI interaction. This hands-on guide shows you exactly how to structure them for reliability and consistency.

Claude vs GPT-4o: Which Model Fits Your Use Case?

Article

person Admin•schedule 5 min read

Claude vs GPT-4o: Which Model Fits Your Use Case?

Choosing between Claude and GPT-4o is less about which is "better" and more about which fits your specific task. Here is a practical breakdown.

How Our Design Team Cut Brief-Writing Time by 70% with AI

Article

person Admin•schedule 5 min read

How Our Design Team Cut Brief-Writing Time by 70% with AI

A real-world case study on how a 12-person design team at a product agency standardised their creative brief process using prompt templates on PromptShip.

Why AI Hallucinations Happen (and How to Reduce Them)

Article

person Admin•schedule 5 min read

Why AI Hallucinations Happen (and How to Reduce Them)

Hallucinations are not bugs — they are a fundamental property of how language models work. Understanding why they happen is the first step to minimising them.

The State of AI Coding Assistants in 2026

Article

person Admin•schedule 5 min read

The State of AI Coding Assistants in 2026

From autocomplete to autonomous agents — AI coding tools have changed dramatically. Here is where things stand and what to expect next.

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

Article

person Admin•schedule 5 min read

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

One founder. No team. A dozen AI-powered tools and a tight prompt library. Here is the workflow that runs a bootstrapped SaaS doing $15k MRR.

Recommended Prompts

claudeshieldTrusted

bookmark

SaaS Pricing Strategy Architect

Designs a value-based pricing model with tier structure, packaging logic, and expansion revenue mechanics for B2B SaaS products.

Product Launch Sequence Planner

Designs a phased, channel-specific product launch sequence with timing, owners, dependencies, and success metrics for each stage.

GTM Pivot Decision Framework

Provides a structured decision framework for evaluating when and how to pivot GTM strategy — ICP change, motion change, positioning change, or full product pivot.

3-Year Strategic Vision Architect

Crafts a board-ready 3-year strategic vision with measurable horizons, growth pillars, and narrative clarity for leadership teams.

Enterprise Okr Framework Approach

Production-ready okr framework that transforms vague requirements into structured, implementable plans with built-in risk assessment.

Okr For Hr Transformation

Structured okr for hr analysis engine — takes your specific context and constraints and delivers an expert-level action plan you can execute immediately.

star 0fork_right 159

bolt

pin_invoke