Claude Prompt Library

30 Claude Prompts That Write OKRs

30 copy-paste prompts

Describe a goal and Claude returns a complete, measurable OKR set: an inspiring objective plus 3-5 quantified key results with baselines and targets, delivered as a copy-paste table. Prompts for company, team, product, marketing, sales, and career OKRs. Not "give me some goal ideas".

In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 15 prompts are free instantly โ€” no signup needed. Hand-curated and tested by the AI Academy team.

By Louis Corneloup ยท Founder, Techpresso
Last updated ยทHand-curated & tested by the AI Academy team

Company OKRs

5 prompts

Annual Company OKRs

1/30

You are a seasoned Chief of Staff who has run OKR cycles at high-growth companies. <context> I need our annual company-level OKRs for the year, delivered as a self-contained, ready-to-use document I can drop straight into our planning doc. </context> <inputs> - Company and what we do: [ONE LINE] - Stage and size: [E.G. SERIES A, 40 PEOPLE] - The single most important theme this year: [E.G. PROFITABILITY, EXPANSION] - Current baselines that matter: [REVENUE, USERS, MARGIN, ETC] - Hard constraints: [BUDGET, HEADCOUNT, RUNWAY] - What "a great year" looks like: [DESCRIBE] </inputs> <task> Write 3 to 4 company objectives, each with 3 to 5 key results. For every key result give the metric, a baseline, a year-end target, whether it is a leading or lagging indicator, the data source, and a suggested owner. Add a short rationale under each objective explaining why it earns a top-level slot, and a one-line "anti-goal" naming what we will NOT chase this year. </task> <constraints> - Objectives are qualitative and inspiring; every key result is numeric with a baseline and a target (no vague verbs like "improve"). - No vanity metrics; each key result must be an outcome, not a task or a launch. - Fits on one page; balance growth, product, and financial health. </constraints> <format> Return the OKRs as a markdown document with one table per objective, then a short note on how to cascade these to teams and how often to check in. </format>

Produces a full set of annual company objectives and quantified key results with owners and data sources, ready to use.

๐Ÿ’ก

Pro tip: Feed Claude your real baselines; without them it invents targets, and OKRs without a starting number can't be scored.

Quarterly Company OKRs

2/30

You are an OKR coach who translates annual strategy into focused 90-day plans. <context> I need this quarter's company OKRs, tightly scoped to what we can actually move in 90 days, as a ready-to-use planning document. </context> <inputs> - Our annual objectives: [PASTE OR SUMMARIZE] - Last quarter's results and misses: [WHAT SCORED HIGH/LOW] - The one bet this quarter must prove: [DESCRIBE] - Current key metrics and baselines: [NUMBERS] - Known risks or dependencies: [DESCRIBE] </inputs> <task> Write 2 to 3 quarterly objectives that ladder up to the annual goals, each with 3 to 4 key results. For each key result include the metric, this quarter's baseline, the target, the cadence for measuring it, and the owner. Add a "confidence" score (1-10) per objective and list the top 3 initiatives that would drive the numbers. </task> <constraints> - Every key result must be achievable and measurable inside 90 days; no year-long metrics. - Explicitly connect each objective back to a specific annual objective. - Keep it to a maximum of 3 objectives so focus is real. </constraints> <format> Return a markdown document: one table per objective plus an initiatives list, then a note on how to run a weekly check-in against it. </format>

Generates focused 90-day company OKRs laddered to annual goals with confidence scores and initiatives, ready to use.

๐Ÿ’ก

Pro tip: Paste last quarter's scores so Claude carries forward misses instead of quietly dropping goals you never finished.

Startup Runway & Fundraising OKRs

3/30

You are a startup operator who has taken companies through fundraising rounds. <context> We are raising soon and need OKRs that make us fundable, delivered as a ready-to-use document for the leadership team. </context> <inputs> - Round we are raising: [PRE-SEED / SEED / SERIES A] - Current traction: [REVENUE OR USERS, GROWTH RATE] - Runway remaining: [MONTHS] - The metrics investors in our space care about: [DESCRIBE] - Target raise and timeline: [AMOUNT, MONTH] </inputs> <task> Write 3 objectives covering traction, capital efficiency, and the raise itself, each with 3 to 4 key results. For each key result give the metric, baseline, target, and the milestone date it must hit before we open the round. Include a key result tied to burn or runway, and one tied to the specific traction number investors will underwrite. </task> <constraints> - Every key result is a number an investor could verify in a data room; no soft goals. - Tie targets to the round's benchmark metrics for our stage. - Flag any target that is aggressive versus our current growth rate. </constraints> <format> Return a markdown document with one table per objective, then a short note on which key results to feature in the pitch deck. </format>

Builds fundraising-ready OKRs spanning traction, burn, and the raise timeline with verifiable targets, ready to use.

๐Ÿ’ก

Pro tip: Tell Claude the exact metric your target investors underwrite (ARR, retention, growth) so the KRs match what the room will grade.

Efficiency & Turnaround OKRs

4/30

You are a turnaround operator who resets companies onto sustainable, efficient growth. <context> We need to shift from growth-at-all-costs to disciplined efficiency. I want OKRs for that reset as a ready-to-use document. </context> <inputs> - Current state: [REVENUE, BURN, HEADCOUNT, MARGIN] - The problem we are fixing: [E.G. NEGATIVE UNIT ECONOMICS, BLOATED COSTS] - Non-negotiables we must protect: [E.G. KEY CUSTOMERS, CORE PRODUCT] - Timeframe for the reset: [QUARTER / YEAR] - Targets from the board: [IF ANY] </inputs> <task> Write 3 objectives covering cost discipline, revenue quality, and operational efficiency, each with 3 to 5 key results. For each key result give the metric, baseline, target, and data source. Include at least one key result on gross margin or burn multiple, one on retained revenue, and one on a productivity or cost-per-outcome ratio. Add a short "what we are cutting" note per objective. </task> <constraints> - Targets must be realistic for the timeframe and defensible to a board. - Balance cost cutting with a key result that protects growth or quality. - No vanity metrics; focus on ratios and retained value, not raw activity. </constraints> <format> Return a markdown document with one table per objective, then a note on the sequence to execute them without stalling the business. </format>

Creates disciplined turnaround OKRs balancing cost cuts, margin, and retained revenue with defensible targets, ready to use.

๐Ÿ’ก

Pro tip: Give Claude your burn multiple and gross margin so it anchors cuts to the ratios a board actually scrutinizes.

Mission-to-OKR Cascade

5/30

You are a strategy facilitator who turns fuzzy mission statements into concrete, measurable goals. <context> Our mission and vision are inspiring but abstract. I need a cascade that translates them into OKRs, delivered as a ready-to-use document leadership can act on. </context> <inputs> - Our mission statement: [PASTE] - Our 3-year vision: [PASTE OR SUMMARIZE] - The strategic pillars we bet on: [2-4 PILLARS] - This year's most important shift: [DESCRIBE] - Baselines for our core metrics: [NUMBERS] </inputs> <task> Produce a cascade in three layers: (1) restate the mission and vision, (2) derive 3 to 4 annual objectives from the strategic pillars, and (3) give each objective 3 to 5 key results with metric, baseline, target, and owner. Show a clear line of sight from each key result up to the pillar and mission it serves. </task> <constraints> - Every objective must trace explicitly to a stated pillar; no orphan goals. - Key results are numeric with baselines; objectives stay qualitative and mission-flavored. - Keep the cascade legible on two pages max. </constraints> <format> Return a structured markdown document (mission block, then one table per objective with a "serves pillar" column), then a note on communicating the cascade company-wide. </format>

Translates mission and vision into a traceable cascade of annual objectives and measurable key results, ready to use.

๐Ÿ’ก

Pro tip: List your strategic pillars explicitly; Claude uses them as the spine so no objective floats free of the mission.

XML tags are just the start. Learn the full Claude workflow.

A growing library of 300+ hands-on AI tutorials covering Claude, ChatGPT, and 50+ tools. New tutorials added every week.

Start 7-Day Free Trial

Team & Department OKRs

5 prompts

Engineering Team OKRs

6/30

You are an engineering leader who writes outcome-focused OKRs, not feature checklists. <context> I need quarterly OKRs for my engineering team as a ready-to-use document, focused on outcomes like reliability, velocity, and quality rather than a list of shipped tickets. </context> <inputs> - Team size and scope: [E.G. 12 ENGINEERS ON PLATFORM] - The company goal we support: [DESCRIBE] - Current pain: [E.G. INCIDENTS, SLOW RELEASES, TECH DEBT] - Current baselines: [UPTIME, DEPLOY FREQUENCY, LEAD TIME, ETC] - Big initiative this quarter: [DESCRIBE] </inputs> <task> Write 2 to 3 objectives with 3 to 4 key results each covering reliability, delivery speed, and code quality. For each key result give the metric, baseline, target, data source, and owner. Use DORA-style metrics where relevant (deployment frequency, lead time, change-failure rate, MTTR) and tie at least one objective to the business outcome the team enables. </task> <constraints> - Key results measure outcomes and system health, never "ship feature X" (put features in initiatives). - Every metric has a real data source (monitoring, CI, incident tracker). - Targets are ambitious but grounded in the baselines given. </constraints> <format> Return a markdown document with one table per objective plus an initiatives list, then a note on separating OKRs from the roadmap. </format>

Generates outcome-focused engineering OKRs using reliability, velocity, and quality metrics with owners, ready to use.

๐Ÿ’ก

Pro tip: Ask Claude to keep features in an 'initiatives' list, not the KRs, so shipping something doesn't count as hitting a goal.

Customer Success Team OKRs

7/30

You are a VP of Customer Success who builds OKRs around retention and expansion. <context> I need quarterly OKRs for my customer success team, delivered as a ready-to-use document that ties CS activity to revenue outcomes. </context> <inputs> - Book of business: [NUMBER OF ACCOUNTS, TOTAL ARR] - Current baselines: [GROSS RETENTION, NET RETENTION, CHURN, NPS] - The biggest churn risk right now: [DESCRIBE] - Team size and structure: [DESCRIBE] - Company goal we support: [DESCRIBE] </inputs> <task> Write 3 objectives covering retention, expansion, and customer health, each with 3 to 4 key results. For each key result give the metric, baseline, target, cadence, and owner. Include gross and net revenue retention, a health-score or adoption metric, an expansion or upsell metric, and a proactive-engagement outcome metric. </task> <constraints> - Key results are outcomes (retained ARR, expansion, adoption), not activity counts like calls made. - Every metric has a clear data source (CRM, product analytics, CS platform). - Targets tie back to the company's revenue goal. </constraints> <format> Return a markdown document with one table per objective, then a note on how CSMs turn these into weekly account actions. </format>

Builds customer success OKRs centered on retention, expansion, and health outcomes with data sources, ready to use.

๐Ÿ’ก

Pro tip: Give Claude your net retention baseline; it's the metric that most honestly grades a CS team and anchors the whole set.

HR / People Team OKRs

8/30

You are a Head of People who writes OKRs that make HR measurable without becoming a task list. <context> I need quarterly OKRs for the People team as a ready-to-use document covering hiring, retention, and employee experience. </context> <inputs> - Company size and growth plan: [HEADCOUNT NOW AND TARGET] - Roles we must fill this quarter: [DESCRIBE] - Current baselines: [TIME-TO-HIRE, OFFER-ACCEPT RATE, ATTRITION, eNPS] - The people problem to solve: [E.G. REGRETTED ATTRITION, SLOW HIRING] - Company goal we support: [DESCRIBE] </inputs> <task> Write 3 objectives covering talent acquisition, retention and engagement, and organizational health, each with 3 to 4 key results. For each key result give the metric, baseline, target, data source, and owner. Include time-to-hire, quality-of-hire or offer-accept rate, regretted attrition, and an engagement metric such as eNPS. </task> <constraints> - Key results measure outcomes (hires closed, attrition, engagement), not process steps. - Every metric has a source (ATS, HRIS, survey) and a defined measurement window. - Balance speed of hiring with a quality or retention guardrail. </constraints> <format> Return a markdown document with one table per objective, then a note on which metrics to review monthly versus quarterly. </format>

Produces People-team OKRs across hiring, retention, and engagement with measurable outcomes and sources, ready to use.

๐Ÿ’ก

Pro tip: Ask Claude to pair every hiring-speed KR with a quality guardrail so you don't win on time-to-hire and lose on fit.

Finance & Operations OKRs

9/30

You are a Head of Finance/Ops who sets OKRs that keep the business efficient and predictable. <context> I need quarterly OKRs for the Finance and Operations function, delivered as a ready-to-use document covering forecasting accuracy, cost control, and process efficiency. </context> <inputs> - Company stage and size: [DESCRIBE] - Current baselines: [FORECAST ACCURACY, DSO, CLOSE TIME, OPEX] - The biggest operational drag: [DESCRIBE] - Systems in place: [ERP, BILLING, ETC] - Company goal we support: [DESCRIBE] </inputs> <task> Write 3 objectives covering financial predictability, cost efficiency, and operational speed, each with 3 to 4 key results. For each key result give the metric, baseline, target, data source, and owner. Include forecast accuracy, a cost-efficiency ratio, days sales outstanding or cash-conversion, and a process-cycle-time metric such as month-end close. </task> <constraints> - Key results are measurable financial or operational outcomes, not "implement tool X". - Every metric ties to a system of record and a clear formula. - Targets are realistic for the team's size and current maturity. </constraints> <format> Return a markdown document with one table per objective, then a note on how these feed the board and leadership reporting. </format>

Creates Finance/Ops OKRs on forecast accuracy, cost efficiency, and cycle time with formulas and sources, ready to use.

๐Ÿ’ก

Pro tip: State your current month-end close time; cycle-time KRs are easy wins that free the team for higher-value analysis.

Cross-Functional Alignment OKRs

10/30

You are an OKR program lead who aligns multiple teams around one shared goal. <context> Several teams need to pull in the same direction for one company priority. I need a shared, cross-functional OKR set as a ready-to-use document showing each team's contribution. </context> <inputs> - The shared company priority: [DESCRIBE] - Teams involved: [E.G. PRODUCT, MARKETING, SALES, CS] - The one shared outcome metric: [E.G. NEW ARR, ACTIVATION RATE] - Current baseline of that metric: [NUMBER] - Known handoff friction between teams: [DESCRIBE] </inputs> <task> Write one shared objective anchored to the priority, then for each team give 2 to 3 key results describing their specific contribution to the shared outcome. For every key result include the metric, baseline, target, owning team, and the dependency on other teams. Add a "shared success metric" that all teams are jointly graded on. </task> <constraints> - All team key results must visibly roll up to the single shared outcome metric. - Make dependencies explicit so no team can hit its numbers while blocking another. - Key results are outcomes, and each names one accountable team. </constraints> <format> Return a markdown document: the shared objective, then one table per team, then the joint success metric, plus a note on running a cross-team check-in. </format>

Builds a shared cross-functional OKR set with per-team contributions and explicit dependencies, ready to use.

๐Ÿ’ก

Pro tip: Name the single shared metric first; it forces every team's KRs to roll up instead of optimizing in silos.

Product OKRs

5 prompts

Product Launch OKRs

11/30

You are a Head of Product who sets OKRs around the outcome of a launch, not the launch itself. <context> We are launching a new product or major feature and I need OKRs that measure whether it actually lands, delivered as a ready-to-use document. </context> <inputs> - What we are launching: [DESCRIBE] - The audience and their job-to-be-done: [DESCRIBE] - Success in one sentence: [WHAT MUST BE TRUE 90 DAYS AFTER LAUNCH] - Baselines if relevant: [EXISTING USAGE, WAITLIST SIZE] - The business goal it supports: [DESCRIBE] </inputs> <task> Write 2 to 3 objectives covering adoption, engagement, and business impact of the launch, each with 3 to 4 key results. For each key result give the metric, baseline (or zero if new), target, measurement window, and owner. Include an adoption metric, a depth-of-use or activation metric, a retention-after-launch metric, and a business-impact metric such as influenced revenue. </task> <constraints> - "Ship it" is an initiative, not a key result; grade the outcome, not the release. - Every metric is quantified with a window (e.g. within 30 days of GA). - Distinguish leading indicators (early adoption) from lagging ones (retention, revenue). </constraints> <format> Return a markdown document with one table per objective, then a note on which key result to watch in week one versus month three. </format>

Generates launch OKRs that grade adoption, engagement, and business impact rather than shipping, ready to use.

๐Ÿ’ก

Pro tip: Set a retention-after-launch KR; adoption spikes on launch day but retention is what proves the feature was worth building.

Activation & Onboarding OKRs

12/30

You are a product-led growth lead who improves the path from signup to first value. <context> Too many signups never reach value. I need quarterly OKRs to fix activation and onboarding, delivered as a ready-to-use document. </context> <inputs> - Our product and its core value: [DESCRIBE] - The activation moment (aha): [WHAT ACTION = ACTIVATED] - Current funnel baselines: [SIGNUP -> ACTIVATED %, TIME-TO-VALUE] - Where users drop off: [DESCRIBE] - Business goal this supports: [DESCRIBE] </inputs> <task> Write 2 to 3 objectives covering activation rate, time-to-value, and early retention, each with 3 to 4 key results. For each key result give the metric, baseline, target, and data source. Include the signup-to-activation rate, median time-to-value, a step-completion rate for the onboarding flow, and day-7 or week-1 retention. </task> <constraints> - Define "activated" precisely as the action that predicts retention; measure against it. - Key results are funnel outcomes, not "redesign onboarding" (that is an initiative). - Targets are grounded in the current baselines and realistic lift. </constraints> <format> Return a markdown document with one table per objective plus an initiatives list, then a note on instrumenting the activation event. </format>

Builds activation and onboarding OKRs around a defined aha moment, time-to-value, and early retention, ready to use.

๐Ÿ’ก

Pro tip: Make Claude pin down one precise 'activated' event first; a fuzzy aha moment makes every downstream KR unmeasurable.

Retention & Churn OKRs

13/30

You are a product analytics leader who sets OKRs to keep users coming back. <context> Users sign up but don't stick. I need quarterly retention and churn OKRs as a ready-to-use document. </context> <inputs> - Product and natural usage frequency: [DAILY / WEEKLY / MONTHLY] - Current baselines: [30-DAY RETENTION, CHURN RATE, DAU/MAU] - The moment users churn: [DESCRIBE] - Key retention driver we suspect: [DESCRIBE] - Business goal this supports: [DESCRIBE] </inputs> <task> Write 2 to 3 objectives covering retention, engagement depth, and resurrection of lapsed users, each with 3 to 4 key results. For each key result give the metric, baseline, target, cohort definition, and data source. Include a cohort-retention curve target, a stickiness metric (DAU/MAU or WAU/MAU), a churn-rate target, and a reactivation metric. </task> <constraints> - Retention key results are cohort-based, not blended totals that hide churn. - Match the metric window to the product's natural usage frequency. - No vanity metrics; measure repeat value, not raw logins. </constraints> <format> Return a markdown document with one table per objective, then a note on reading cohort curves to know if you are winning. </format>

Produces cohort-based retention and churn OKRs with stickiness and reactivation metrics, ready to use.

๐Ÿ’ก

Pro tip: Tell Claude your product's natural cadence so retention windows fit reality instead of a generic 30-day default.

Platform Reliability OKRs

14/30

You are a platform/SRE leader who turns reliability into measurable OKRs. <context> We need reliability OKRs that protect the customer experience without freezing shipping, delivered as a ready-to-use document. </context> <inputs> - What the platform powers: [DESCRIBE] - Current baselines: [UPTIME, P95 LATENCY, ERROR RATE, MTTR] - Recent reliability pain: [DESCRIBE] - Any customer SLA commitments: [DESCRIBE] - Business goal this supports: [DESCRIBE] </inputs> <task> Write 2 to 3 objectives covering availability, performance, and incident response, each with 3 to 4 key results. For each key result give the metric, baseline, target, and data source. Include an SLO-based availability target, a latency target (p95 or p99), an error-budget or error-rate target, and an MTTR or incident-count target. </task> <constraints> - Frame availability as an SLO with an error budget, not "100% uptime". - Every metric maps to monitoring or incident tooling as its source. - Include a guardrail so reliability work does not fully block feature delivery. </constraints> <format> Return a markdown document with one table per objective, then a note on using the error budget to decide ship-versus-harden. </format>

Creates SLO-based reliability OKRs for availability, latency, and incident response with error budgets, ready to use.

๐Ÿ’ก

Pro tip: Have Claude frame uptime as an SLO with an error budget; '100% uptime' is unachievable and kills all shipping velocity.

Product-Led Growth OKRs

15/30

You are a growth product manager who drives self-serve, product-led expansion. <context> We want the product itself to drive acquisition, conversion, and expansion. I need PLG OKRs as a ready-to-use document. </context> <inputs> - Product and self-serve model: [FREEMIUM / FREE TRIAL / PLG + SALES] - Current baselines: [FREE-TO-PAID %, VIRAL/INVITE RATE, EXPANSION] - The growth loop we rely on: [DESCRIBE] - The biggest leak in the loop: [DESCRIBE] - Business goal this supports: [DESCRIBE] </inputs> <task> Write 3 objectives covering self-serve acquisition, free-to-paid conversion, and in-product expansion, each with 3 to 4 key results. For each key result give the metric, baseline, target, and data source. Include a product-qualified-lead or signup metric, a free-to-paid conversion rate, an in-product referral or invite metric, and a seat or usage expansion metric. </task> <constraints> - Key results measure the growth loop's output, not marketing spend. - Every conversion metric is tied to a defined qualifying action in-product. - Targets reflect realistic lift on the current baselines. </constraints> <format> Return a markdown document with one table per objective, then a note on where in the loop to focus first for compounding gains. </format>

Builds product-led growth OKRs across self-serve acquisition, conversion, and expansion loops, ready to use.

๐Ÿ’ก

Pro tip: Ask Claude to map each KR to a stage of your growth loop so you can see which leak, if fixed, compounds the most.

Marketing OKRs

5 prompts

Demand Gen & Pipeline OKRs

16/30

You are a Head of Demand Generation who is measured on pipeline, not leads. <context> I need quarterly demand-gen OKRs tied to sales pipeline and revenue, delivered as a ready-to-use document. </context> <inputs> - Our motion: [PLG / SALES-LED / HYBRID] - Current baselines: [MQLS, SQLS, PIPELINE $, CAC] - The company revenue goal: [NUMBER AND TIMEFRAME] - Our best-performing channel: [DESCRIBE] - The pipeline gap to close: [NUMBER] </inputs> <task> Write 3 objectives covering pipeline generation, funnel efficiency, and cost per outcome, each with 3 to 4 key results. For each key result give the metric, baseline, target, data source, and owner. Include a sourced-pipeline dollar target, an MQL-to-SQL conversion rate, a cost-per-opportunity or CAC target, and a channel-mix or velocity metric. </task> <constraints> - Anchor the top objective to pipeline dollars, not lead volume. - Every metric ties to CRM or attribution data as its source. - Include an efficiency guardrail (CAC or cost-per-opp) so growth stays healthy. </constraints> <format> Return a markdown document with one table per objective, then a note on the sales-marketing SLA these numbers imply. </format>

Generates demand-gen OKRs anchored to sourced pipeline dollars, conversion, and cost efficiency, ready to use.

๐Ÿ’ก

Pro tip: Make the headline KR pipeline dollars, not MQLs; lead volume looks great while sales quietly rejects every one.

Content & SEO OKRs

17/30

You are a content and SEO lead who sets OKRs around organic outcomes, not output volume. <context> I need quarterly content and SEO OKRs measured by traffic, rankings, and conversions rather than posts published, as a ready-to-use document. </context> <inputs> - Site and topic focus: [DESCRIBE] - Current baselines: [ORGANIC SESSIONS, RANKING KEYWORDS, CONVERSIONS] - Target keyword clusters: [DESCRIBE] - Current domain authority or backlink profile: [DESCRIBE] - Business goal this supports: [DESCRIBE] </inputs> <task> Write 2 to 3 objectives covering organic traffic growth, ranking authority, and content-driven conversions, each with 3 to 4 key results. For each key result give the metric, baseline, target, and data source. Include organic sessions, keywords ranking in the top 10, an authority or backlink metric, and an organic-conversion or signup metric. </task> <constraints> - Publishing count is an initiative, not a key result; grade the traffic and conversion outcome. - Every metric ties to analytics or a rank tracker as its source. - Targets reflect realistic SEO timelines, noting which lag by a quarter or two. </constraints> <format> Return a markdown document with one table per objective plus an initiatives list, then a note on how long each metric takes to move. </format>

Builds content and SEO OKRs measured by traffic, rankings, and conversions rather than volume, ready to use.

๐Ÿ’ก

Pro tip: Let Claude flag which KRs lag by a quarter; SEO targets set on a 90-day clock are the classic reason teams miss.

Brand Awareness OKRs

18/30

You are a brand marketing lead who makes awareness measurable. <context> We want to grow brand awareness and I need OKRs that quantify it instead of relying on gut feel, delivered as a ready-to-use document. </context> <inputs> - Brand and category: [DESCRIBE] - Current baselines: [BRANDED SEARCH VOLUME, SHARE OF VOICE, SOCIAL REACH] - Target audience: [DESCRIBE] - Channels we invest in: [DESCRIBE] - Business goal this supports: [DESCRIBE] </inputs> <task> Write 2 to 3 objectives covering unaided reach, engagement, and brand demand, each with 3 to 4 key results. For each key result give the metric, baseline, target, and data source. Include a branded-search-volume target, a share-of-voice metric, an engaged-reach or follower-growth metric, and a direct-traffic or brand-lift metric. </task> <constraints> - Replace vanity impressions with metrics that indicate real recall or demand (branded search, direct traffic, share of voice). - Every metric has a data source and measurement method. - Distinguish leading engagement metrics from lagging demand metrics. </constraints> <format> Return a markdown document with one table per objective, then a note on proxy metrics for brand when you can't run a survey. </format>

Produces brand awareness OKRs using branded search, share of voice, and brand demand proxies, ready to use.

๐Ÿ’ก

Pro tip: Push Claude toward branded search and direct traffic; they're the cheapest honest proxies for awareness without a survey budget.

Product Marketing & Launch OKRs

19/30

You are a product marketing lead who owns launch impact and positioning. <context> I need quarterly product marketing OKRs covering a launch, messaging, and sales enablement, delivered as a ready-to-use document. </context> <inputs> - The launch or release: [DESCRIBE] - Target segment and their pain: [DESCRIBE] - Current baselines: [FEATURE ADOPTION, WIN RATE, SALES USAGE OF ASSETS] - The positioning shift we want: [DESCRIBE] - Business goal this supports: [DESCRIBE] </inputs> <task> Write 3 objectives covering launch adoption, message resonance, and sales enablement, each with 3 to 4 key results. For each key result give the metric, baseline, target, and data source. Include a feature-adoption metric, a win-rate or competitive-displacement metric, a sales-asset usage or ramp metric, and a message-resonance metric such as landing-page conversion. </task> <constraints> - Grade launch outcomes (adoption, win rate), not asset counts produced. - Every metric maps to product analytics, CRM, or web analytics. - Tie at least one objective to revenue or win rate, not just awareness. </constraints> <format> Return a markdown document with one table per objective, then a note on measuring whether new messaging actually moved win rate. </format>

Creates product marketing OKRs spanning launch adoption, win rate, and enablement outcomes, ready to use.

๐Ÿ’ก

Pro tip: Include a win-rate KR; it's the truest test of whether new positioning worked, unlike asset downloads or page views.

Lifecycle & Email Marketing OKRs

20/30

You are a lifecycle marketing lead who drives revenue through email and in-product messaging. <context> I need quarterly lifecycle and email OKRs focused on engagement and revenue per contact, delivered as a ready-to-use document. </context> <inputs> - Our lifecycle stages: [E.G. TRIAL, ONBOARDING, ACTIVE, WIN-BACK] - Current baselines: [OPEN RATE, CTR, LIST GROWTH, REVENUE PER EMAIL] - The stage with the biggest leak: [DESCRIBE] - List size and deliverability health: [DESCRIBE] - Business goal this supports: [DESCRIBE] </inputs> <task> Write 2 to 3 objectives covering engagement quality, lifecycle conversion, and revenue from owned channels, each with 3 to 4 key results. For each key result give the metric, baseline, target, and data source. Include an engagement metric (click-to-open or reply rate), a lifecycle-stage conversion rate, a deliverability or list-health metric, and a revenue-per-recipient or attributed-revenue metric. </task> <constraints> - Prefer click and conversion metrics over open rates, which are increasingly unreliable. - Every metric ties to the ESP or analytics as its source. - Include a deliverability guardrail so list growth doesn't hurt inbox placement. </constraints> <format> Return a markdown document with one table per objective, then a note on which lifecycle stage to optimize first for revenue. </format>

Builds lifecycle and email OKRs on engagement quality, stage conversion, and revenue per contact, ready to use.

๐Ÿ’ก

Pro tip: Ask Claude to demote open rate to a guardrail; post-privacy changes it's noisy, so grade on clicks and conversions.

Sales OKRs

5 prompts

Quarterly Revenue & New-Business OKRs

21/30

You are a VP of Sales who sets OKRs that go beyond a single bookings number. <context> I need quarterly sales OKRs covering new bookings, deal quality, and forecast accuracy, delivered as a ready-to-use document. </context> <inputs> - Segment and average deal size: [DESCRIBE] - Current baselines: [NEW ARR, WIN RATE, SALES CYCLE, ACV] - The quarterly bookings target: [NUMBER] - Team structure: [AEs, SEGMENTS] - Company goal this supports: [DESCRIBE] </inputs> <task> Write 3 objectives covering new-business bookings, sales efficiency, and pipeline health, each with 3 to 4 key results. For each key result give the metric, baseline, target, and owner. Include a new-ARR or bookings target, a win-rate target, a sales-cycle or velocity target, and a pipeline-coverage ratio. </task> <constraints> - Balance the bookings number with quality metrics (win rate, ACV) so reps don't chase junk deals. - Every metric maps to the CRM as its source. - Pipeline coverage must be realistic for the win rate given. </constraints> <format> Return a markdown document with one table per objective, then a note on the pipeline coverage needed to make the number safely. </format>

Generates quarterly sales OKRs balancing bookings, win rate, velocity, and pipeline coverage, ready to use.

๐Ÿ’ก

Pro tip: Add a pipeline-coverage KR; a bookings target with only 1.5x coverage is a miss waiting to happen, and Claude will flag it.

Pipeline & Conversion OKRs

22/30

You are a sales operations leader who fixes leaky funnels with measurable goals. <context> Our pipeline converts poorly and I need OKRs to fix each funnel stage, delivered as a ready-to-use document. </context> <inputs> - Our sales stages: [LIST THEM] - Current stage-to-stage conversion rates: [NUMBERS] - The weakest stage: [DESCRIBE] - Average sales cycle: [DAYS] - Company goal this supports: [DESCRIBE] </inputs> <task> Write 2 to 3 objectives covering funnel conversion, sales velocity, and pipeline hygiene, each with 3 to 4 key results. For each key result give the metric, baseline, target, and data source. Include stage-to-stage conversion targets, a sales-cycle-length target, a pipeline-hygiene metric (stale-deal rate or data completeness), and an overall lead-to-close rate. </task> <constraints> - Target the specific weak stage explicitly rather than a blanket "convert more". - Every metric maps to the CRM funnel report. - Include a data-hygiene key result so the funnel numbers are trustworthy. </constraints> <format> Return a markdown document with one table per objective, then a note on diagnosing whether a stage leaks from fit, timing, or process. </format>

Builds pipeline conversion OKRs targeting weak funnel stages, velocity, and hygiene, ready to use.

๐Ÿ’ก

Pro tip: Give Claude your stage-by-stage conversion rates; it will target the specific leak instead of a vague 'improve conversion' goal.

Expansion & Net Revenue Retention OKRs

23/30

You are a revenue leader who grows existing accounts through upsell and cross-sell. <context> We need to grow revenue from current customers. I need expansion and net-revenue-retention OKRs as a ready-to-use document. </context> <inputs> - Customer base and total ARR: [DESCRIBE] - Current baselines: [NET REVENUE RETENTION, EXPANSION ARR, UPSELL RATE] - Our expansion levers: [SEATS, TIERS, ADD-ONS, USAGE] - Churn or contraction risk: [DESCRIBE] - Company goal this supports: [DESCRIBE] </inputs> <task> Write 3 objectives covering net revenue retention, upsell and cross-sell, and contraction prevention, each with 3 to 4 key results. For each key result give the metric, baseline, target, and owner. Include a net-revenue-retention target, an expansion-ARR target, an upsell or cross-sell win-rate, and a downgrade or contraction-rate ceiling. </task> <constraints> - Net revenue retention is the headline metric; frame the set around it. - Every metric ties to billing or CRM data. - Include a contraction guardrail so expansion isn't wiped out by downgrades. </constraints> <format> Return a markdown document with one table per objective, then a note on which accounts to prioritize for the fastest expansion. </format>

Produces expansion OKRs headlined by net revenue retention with upsell and contraction guardrails, ready to use.

๐Ÿ’ก

Pro tip: Anchor everything to net revenue retention; over 100% means you'd grow even with zero new logos, and that's the real prize.

SDR & Outbound OKRs

24/30

You are a sales development leader who sets outbound OKRs on meetings and pipeline, not dials. <context> I need quarterly SDR/BDR OKRs focused on qualified meetings and sourced pipeline, delivered as a ready-to-use document. </context> <inputs> - Team size and territories: [DESCRIBE] - Current baselines: [MEETINGS BOOKED, SHOW RATE, SQL RATE, SOURCED PIPELINE] - Our ICP and outbound channels: [DESCRIBE] - The meeting-to-opportunity rate: [NUMBER] - Company goal this supports: [DESCRIBE] </inputs> <task> Write 2 to 3 objectives covering qualified meetings, sourced pipeline, and outbound efficiency, each with 3 to 4 key results. For each key result give the metric, baseline, target, and owner. Include a qualified-meetings-held target, a meeting-to-opportunity conversion rate, a sourced-pipeline dollar target, and an efficiency metric such as meetings per rep or reply-to-meeting rate. </task> <constraints> - Grade held-and-qualified meetings and pipeline, not raw activity like calls or emails sent. - Every metric maps to the CRM or sales-engagement tool. - Targets are realistic per rep given the baselines. </constraints> <format> Return a markdown document with one table per objective, then a note on the activity levels these outcomes likely require. </format>

Creates SDR outbound OKRs on qualified meetings and sourced pipeline rather than activity counts, ready to use.

๐Ÿ’ก

Pro tip: Grade on meetings-held-and-qualified, not booked; a booked-meeting target rewards no-shows and unqualified fluff.

Sales Enablement & Ramp OKRs

25/30

You are a sales enablement leader who shortens ramp time and lifts rep performance. <context> I need quarterly enablement OKRs measured by rep productivity and ramp speed, delivered as a ready-to-use document. </context> <inputs> - Team size and recent or planned hires: [DESCRIBE] - Current baselines: [RAMP TIME TO FULL QUOTA, % OF REPS AT QUOTA, WIN RATE] - The enablement gap: [E.G. PRODUCT KNOWLEDGE, DISCOVERY, OBJECTIONS] - Tools and playbooks in place: [DESCRIBE] - Company goal this supports: [DESCRIBE] </inputs> <task> Write 2 to 3 objectives covering ramp speed, quota attainment, and skill proficiency, each with 3 to 4 key results. For each key result give the metric, baseline, target, and data source. Include a time-to-full-ramp target, a percent-of-reps-hitting-quota target, a certification or skill-assessment pass rate, and a win-rate or deal-quality metric tied to the enablement gap. </task> <constraints> - Grade rep outcomes (ramp, attainment, win rate), not training sessions delivered. - Every metric maps to the CRM or LMS as its source. - Tie the skill metric directly to the named enablement gap. </constraints> <format> Return a markdown document with one table per objective, then a note on connecting certification scores to real deal outcomes. </format>

Builds sales enablement OKRs on ramp speed, quota attainment, and proficiency outcomes, ready to use.

๐Ÿ’ก

Pro tip: Tie the skill KR to your specific gap (discovery, objections) so certification actually predicts win rate, not trivia recall.

Most people use 10% of Claude. Tutorials unlock the rest.

AI Academy: 300+ hands-on tutorials on Claude, ChatGPT, Midjourney, and 50+ AI tools. New tutorials added every week.

Start Your Free Trial

Personal & Career OKRs

5 prompts

Career Growth OKRs

26/30

You are a career coach who turns vague ambition into measurable quarterly goals. <context> I want to grow toward my next role and need personal career OKRs for the quarter, delivered as a ready-to-use document I can review weekly. </context> <inputs> - My current role and level: [DESCRIBE] - The role or level I want next: [DESCRIBE] - The gap between them: [SKILLS, VISIBILITY, RESULTS] - Time I can invest weekly: [HOURS] - What my manager would need to see to promote me: [DESCRIBE] </inputs> <task> Write 2 to 3 personal objectives covering skill growth, visible impact, and relationships or visibility, each with 3 to 4 key results. For each key result give the metric, baseline, target, and a weekly checkpoint. Make impact key results tie to outcomes my manager can see, and include a stretch key result that signals readiness for the next level. </task> <constraints> - Every key result is measurable and self-trackable (numbers, artifacts shipped, milestones), not "learn more about X". - Targets fit within the weekly hours available. - Tie at least one objective to what triggers a promotion in my context. </constraints> <format> Return a markdown document with one table per objective plus a weekly tracker template, then a note on discussing these with my manager. </format>

Generates personal career OKRs across skills, visible impact, and visibility with a weekly tracker, ready to use.

๐Ÿ’ก

Pro tip: Tell Claude exactly what your manager must see to promote you; it turns that into KRs instead of generic self-improvement.

New-Manager Leadership OKRs

27/30

You are a leadership coach who helps new managers set measurable goals for their first quarter leading a team. <context> I just became a manager and need leadership OKRs for my first 90 days, delivered as a ready-to-use document. </context> <inputs> - Team size and function: [DESCRIBE] - The team's current state: [MORALE, PERFORMANCE, GAPS] - What success looks like for my boss: [DESCRIBE] - My biggest worry as a new manager: [DESCRIBE] - Time in role so far: [DESCRIBE] </inputs> <task> Write 3 objectives covering team performance, people development, and my own leadership habits, each with 3 to 4 key results. For each key result give the metric, baseline, target, and cadence. Include a team-output or delivery metric, an engagement or 1:1 consistency metric, a development metric (growth plans in place), and a feedback metric on my own leadership. </task> <constraints> - Balance driving results with building trust; do not make it all output. - Key results are measurable (completion rates, scores, cadence adherence), not "be a better leader". - Targets are realistic for a first 90 days. </constraints> <format> Return a markdown document with one table per objective, then a note on how to gather honest feedback on your leadership metric. </format>

Builds first-90-day leadership OKRs balancing team output, development, and leadership habits, ready to use.

๐Ÿ’ก

Pro tip: Ask Claude for a KR on gathering upward feedback; new managers over-index on output and miss how the team experiences them.

Skill-Building & Learning OKRs

28/30

You are a learning strategist who designs measurable skill-acquisition plans. <context> I want to master a specific skill this quarter and need learning OKRs that prove real progress, delivered as a ready-to-use document. </context> <inputs> - The skill I want to build: [DESCRIBE] - Why it matters to me: [CAREER, PROJECT, ETC] - My current level: [BEGINNER / INTERMEDIATE / ADVANCED] - Weekly time available: [HOURS] - How I will use the skill: [CONCRETE OUTPUT] </inputs> <task> Write 2 objectives covering demonstrated competence and applied output, each with 3 to 4 key results. For each key result give the metric, baseline, target, and a checkpoint date. Prefer output-based key results (projects built, problems solved, assessments passed) over input-based ones (hours studied), though include one habit metric for consistency. </task> <constraints> - Grade demonstrated skill, not time spent; at least one key result is a real artifact or assessment. - Targets fit the weekly hours and current level. - Include a spaced-practice or consistency habit metric. </constraints> <format> Return a markdown document with one table per objective plus a simple weekly log template, then a note on choosing projects that prove the skill. </format>

Produces learning OKRs that grade demonstrated skill through projects and assessments, ready to use.

๐Ÿ’ก

Pro tip: Push Claude toward output KRs like a shipped project; 'hours studied' feels productive but never proves you learned it.

Job Search OKRs

29/30

You are a career strategist who runs a disciplined, metrics-driven job search. <context> I am searching for a new job and want to run it like a funnel. I need job-search OKRs as a ready-to-use document I can track weekly. </context> <inputs> - Target role and level: [DESCRIBE] - Target companies or industries: [DESCRIBE] - My timeline to land a role: [WEEKS/MONTHS] - Weekly hours available for the search: [HOURS] - My biggest current bottleneck: [E.G. NO REPLIES, FAILING INTERVIEWS] </inputs> <task> Write 2 to 3 objectives covering pipeline building, conversion through interview stages, and positioning, each with 3 to 4 key results. For each key result give the metric, baseline (if known), target, and weekly checkpoint. Include a quality-applications target, a networking-conversation target, an interview conversion rate, and a positioning improvement (resume, portfolio, or story). </task> <constraints> - Treat the search as a funnel with conversion rates, not just "apply to more jobs". - Key results are countable and self-trackable each week. - Target the stated bottleneck explicitly. </constraints> <format> Return a markdown document with one table per objective plus a weekly funnel tracker, then a note on diagnosing which funnel stage is failing. </format>

Creates job-search OKRs that run the search as a funnel with conversion rates and a weekly tracker, ready to use.

๐Ÿ’ก

Pro tip: Frame it as a funnel; if you get interviews but no offers the fix is different than if you get no replies, and Claude will target it.

Health & Work-Life Balance OKRs

30/30

You are a performance coach who sets sustainable, measurable personal wellbeing goals. <context> I want to improve my health and balance this quarter without vague resolutions. I need personal wellbeing OKRs as a ready-to-use document. </context> <inputs> - The areas I want to improve: [E.G. SLEEP, FITNESS, STRESS, BOUNDARIES] - My current baselines: [SLEEP HOURS, WORKOUTS/WEEK, WORK HOURS] - My biggest constraint: [TIME, ENERGY, SCHEDULE] - What "balanced" would feel like: [DESCRIBE] - How I will track it: [APP, JOURNAL, ETC] </inputs> <task> Write 2 to 3 objectives covering physical health, recovery, and work-life boundaries, each with 3 to 4 key results. For each key result give the metric, baseline, target, and a weekly checkpoint. Prefer process metrics I control (workouts completed, sleep window kept, hard stop time) over outcome-only metrics like weight, and include one metric that protects against overwork. </task> <constraints> - Key results are measurable and controllable; frame them as sustainable habits, not extremes. - Targets fit the stated constraint; no all-or-nothing goals that break in week two. - Include a boundary metric (work hours or a hard stop) to protect balance. </constraints> <format> Return a markdown document with one table per objective plus a weekly habit tracker, then a note on adjusting targets if a week goes sideways. </format>

Builds sustainable wellbeing OKRs across health, recovery, and boundaries using controllable habit metrics, ready to use.

๐Ÿ’ก

Pro tip: Have Claude use process metrics you control (workouts done, hard-stop time) over outcomes like weight that lag and demotivate.

Frequently Asked Questions

OKRs (Objectives and Key Results) pair one qualitative, inspiring objective with 3-5 measurable key results that prove you hit it. You give Claude your goal, current baselines, and constraints, and it returns a complete set with metrics, baselines, targets, owners, and data sources laid out in a copy-paste table.
A key result without a starting number can't be scored at the end of the quarter. When you paste real baselines (current revenue, retention, conversion rate), Claude sets targets as a defensible lift from where you are rather than inventing numbers. The prompts ask for baselines specifically so your OKRs are gradable.
Each prompt returns a full, structured artifact: objectives, quantified key results with baselines and targets, owners, data sources, and a scoring approach, ready to drop into your planning doc. They also enforce good OKR hygiene, such as keeping features and projects as initiatives rather than counting them as key results.
Yes. There are six categories covering company, team, product, marketing, sales, and personal or career OKRs. The personal prompts add weekly trackers and favor controllable process metrics, while the business prompts add owners, data sources, and cascade notes so team goals ladder up to company objectives.
Most of these prompts produce 3 to 4 key results per objective, which is the sweet spot: enough to define success from multiple angles without diluting focus. They mix leading indicators (early signals you can influence now) with lagging ones (revenue, retention) so you know both whether you are on track and whether you won.

Prompts are the starting line. Tutorials are the finish.

A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.

7-day free trial. Cancel anytime.