Skip to main content
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.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 378 timesby Community
GTM metricsOKRKPIsb2b-saasleading indicatorsquarterly planningrevenue operations
claude-sonnet-4-20250514
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
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.