CoreCMO

Strategic Foundation


Right-to-Win.

The empirical truth about where you win consistently — not aspirational, observable. The bridge between knowing your Ideal Customer Profile (ICP) and being able to charge a premium for it. Captured as the Brief field every downstream prompt in the playbook inherits from.

Strategic Foundation 5 prompts 1 agent — Right-to-Win Council 5 brief-builder cards

The framework — strategy first


Right-to-Win — the empirical answer to where you win.

Right-to-Win is not your ICP.

TWO DIFFERENT QUESTIONS, TWO DIFFERENT ANSWERS

ICP is the segment you have committed to win — the buyer set your strategy says you go after. Right-to-Win is the segment you already win, observably, today. They are not the same. Most teams confuse the two and end up funding aspirational ICP work that the data doesn’t support.

Right-to-Win is the segment where your win rate is highest, your sales cycle is shortest, your churn is lowest, and your customer language is sharpest. It is the segment where you have already earned the right to charge a premium — whether or not your pricing reflects it yet.

QUESTIONICP ANSWERSRIGHT-TO-WIN ANSWERS
Where should we hunt?The segment our strategy committed to.The segment we already close in consistently.
What evidence supports it?Market sizing, strategic intent, competitive whitespace.Closed-won data, retention rates, expansion velocity, customer language.
Who validates the answer?Leadership and the board, against the strategic plan.Sales, customer success, and 5 customers in their own words.
How often does it refresh?Annual planning cycle.Quarterly, off the closed-deals data.
What does it unlock?Where to allocate budget against the strategic bet.What to charge a premium for. The pillars of the brand. The proof points every prompt and agent inherits from.

The honest Chief Marketing Officer (CMO) move is to run both in parallel. The ICP is the bet you’re making for the next 18 months; Right-to-Win is the truth about where you are today. The Brief stores both. When the two converge, the function is operating well. When they diverge, the divergence itself is the conversation — either the strategy is ahead of the proof, or the proof says the strategy is wrong.

The three intersections — where Right-to-Win lives.

THE THREE-INTERSECTION FRAMEWORK

Right-to-Win sits at the intersection of three observable conditions. If any one of them is weak, the position is not defensible — the win rate will revert as soon as a competitor notices.

INTERSECTIONTHE QUESTION IT ANSWERSWHERE TO LOOK
1. A buyer pain you uniquely solve What problem do you solve in a way competitors structurally cannot? Not better — differently. Closed-won deal notes filtered to the “why us” field. Customer interviews. Sales tribal knowledge about the segment where the team never feels like the underdog.
2. A segment where you have credibility Which vertical, geography, or buyer profile has named references, public proof, and word-of-mouth working in your favor? Logos on the homepage. The vertical with 3+ named case studies. Review-site filters where your G2 footprint is densest. Conference attendance where your community shows up.
3. A competitive gap that favors you Where do the incumbents structurally underperform — technical limitations, business-model constraints, geographic gaps, regulatory exposure? Win/loss interview themes. Battlecards. Where competitors fail discovery questions consistently. Where their pricing model penalizes the buyer pattern you serve.

The Venn intersection of all three is the segment where you have an unambiguous right to win. Inside that intersection, your win rate is highest because all three forces are working in your favor at the same time. Outside it, the win rate degrades quickly — you might still close deals, but you’ll close them on the customer’s terms, not yours, and you’ll lose them to the next vendor more easily.

THE WIN-RATE TELL

Pull win rates by segment from the Customer Relationship Management (CRM) system. The Right-to-Win segment will show a win rate at least 1.5× the company average and a sales cycle 30%+ shorter. If no segment in the data hits that bar, the company doesn’t yet have a Right-to-Win — it has a strategy and a hope.

How to find it — the two signals method.

The fastest path to a draft Right-to-Win runs two signals in parallel and then validates the intersection with customer conversations. Both signals are pulled from data you already have; the customer work is the qualitative layer that makes the answer defensible.

Signal 1 — the Sales signal

Pull the last 12 months of closed-won deals from the CRM. For each deal, capture: industry, company size, employee count, Annual Recurring Revenue (ARR), sales cycle length, win source (inbound, outbound, partner), the named competitor in the deal, and the “why us” reason. Filter for deals where the sales cycle was shorter than the team average and the win rate against the named competitor was 60%+.

Then ask the sales team three questions:

  1. Which leads do you get most excited about — where do you walk into the call already 70% sure you’ll win?
  2. Which companies or buyers have no tradeoffs in the conversation — where you don’t have to apologize for any part of the product?
  3. Who has the fastest buying cycles — where the deal closes in under 60 days, with under three meetings?

The pattern you’re looking for is the segment where the answers to all three questions cluster on the same buyer type. That cluster is the first half of the Right-to-Win hypothesis.

Signal 2 — the PLG signal

If you ship a Product-Led Growth (PLG) motion (free tier, trial, freemium, or self-serve sign-up), the activation data is the second signal. Pull the last 12 months of sign-ups by firmographic. Look for:

  • Who activates fastest after sign-up? Segment by time-to-first-value — the buyer cluster that hits the activation event within 7 days is the cluster where the product solves the problem immediately, with no implementation overhead.
  • Who expands naturally without a Customer Success Manager (CSM) nudge? Look at seat expansion and tier upgrades that happened without a customer-success motion. Those are the buyers where the product genuinely outgrows itself inside the account.
  • Who has the lowest churn? Segment by 12-month logo retention. The cluster with retention above 90% is the cluster where the product fits the underlying job-to-be-done at maturity.

Where the Sales signal and the PLG signal both point at the same buyer profile, you have a strong Right-to-Win candidate. If they point at different profiles, run both as separate Right-to-Win hypotheses and let the customer conversations break the tie.

Sales-led-only contingency

If you don’t run a PLG motion (enterprise-only, sales-led, no self-serve product), the PLG signal is replaced by the Customer Success signal:

  • Net Promoter Score (NPS) by segment — the cluster with NPS above 50 is the cluster where the product is meeting expectations consistently.
  • Expansion velocity by segment — the cluster where net dollar retention is above 130% is the cluster where the relationship is compounding.
  • Reference willingness by segment — the cluster where customers say yes to reference calls without hesitation is the cluster where the relationship is healthy enough to publicly advocate.

Validate with the five customer questions.

The data signals point at a hypothesis. The customer conversations validate it — and almost always sharpen it. Pick five customers from the candidate Right-to-Win segment. The ones to pick: a recent closed-won, a high-NPS expansion, a long-tenure logo, a recent reference call participant, and an early adopter who’s been around since before the product was good. The five span the lifecycle and surface different parts of the truth.

Run the same five questions on every call:

  1. Why did you choose us? Listen for the specific competitor they were comparing against and the moment in the evaluation when the decision tipped.
  2. What were you trying to solve? Listen for the words they use to describe the problem — not the words your marketing uses.
  3. Why us over the alternatives? This is the differentiator question. The answer is rarely the feature your team is proud of; it’s usually a positioning or trust factor.
  4. What changed after using us? The outcome question — specific, in their measurement system, in their timeframe.
  5. What business impact did you see? The quantified answer — cost saved, revenue gained, time recovered, risk reduced.

What you’re listening for across five calls: the recurring phrase. The exact words four or five of them use, unprompted, to describe what you do or who you serve. That phrase is almost always closer to your real Right-to-Win than anything in the existing brand deck. Capture it verbatim — it becomes the language for the statement, the pillars, the homepage hero, and every downstream prompt.

WHO RUNS THE CALLS

Not the sales rep who closed the deal — they’ll subconsciously fish for validation. Not the CSM — they’ll fish for renewal. The right interviewer is a marketing leader, a product leader, or a third party (advisor, agency, consultant) whose only job is to listen for what the customer actually says. Record the calls (with consent) so the recurring-phrase work isn’t left to memory.

Synthesize into the statement.

The Right-to-Win statement is one sentence. The discipline is in the constraint: if it takes two sentences, you don’t have it yet. The shape is consistent:

THE RIGHT-TO-WIN STATEMENT SHAPE

“We win in [specific segment] because we solve [specific buyer pain] in a way [named competitor or alternative] structurally cannot, and our customers describe us as [the recurring phrase].”

Three rules. The segment is specific — not “mid-market healthcare” but “US ambulatory care networks with 25–250 clinic locations running Epic.” The pain is in the customer’s language — not “clinical workflow optimization” but “every clinic runs the intake differently and I can’t standardize the patient experience.” The competitor is named — not “legacy electronic health record (EHR) extensions” but “athenaOne, eClinicalWorks, and NextGen.” Vague Right-to-Win statements drift the moment they meet a real prospect; specific ones survive the meeting.

Worked example

A B2B SaaS selling clinical-workflow software to outpatient health systems runs the two-signals method. The Sales signal points at multi-site ambulatory care networks (25–250 clinic locations) on Epic in the Southeast and Texas; the Customer Success signal points at the same cluster. Five customer conversations surface the recurring phrase: “you’re the first system that was built for how outpatient actually runs.” The synthesized statement:

“We win in US ambulatory care networks with 25–250 clinic locations on Epic because we solve the ‘every clinic runs intake differently’ problem in a way Epic-extension competitors like athenaOne, eClinicalWorks, and NextGen structurally cannot — their workflow models were designed for inpatient operations, not for the throughput rhythm of outpatient — and our customers describe us as the first system that was built for how outpatient actually runs.”

That statement does work. The sales team uses it to qualify in or out. The brand pillars derive from it (outpatient-first workflow design, Epic-native integration depth, clinic-network scale operations). The pricing tiers segment around it (single-clinic buyers pay one price; 25–250 location networks pay a premium because the workflow standardization compounds with footprint). The content calendar leads with outpatient operations for multi-site network leaders, not generic healthcare IT content. Every downstream area gets sharper.

The three intersections behind the statement: (1) clinic-network scale — multi-site networks have a coordination problem single clinics don’t; (2) Epic integration depth — not just integrated, integrated in a way that respects Epic’s workflow primitives; (3) outpatient-first design — built for the 14-minute encounter cycle, not the multi-day inpatient stay. Where all three intersect is the segment where the team is structurally hard to displace.

The 90-day implementation guarantee is the second-order proof that the Right-to-Win is real. Buyers care about implementation speed because every week of delay is revenue lost at each clinic on the rollout list. The statement holds because the team can defend it: under 90 days to live across a 50-clinic network is empirically verifiable; the integration with Epic and Athena handles the reconciliation problem the buyer used to staff a small team to manage; and the workflow design assumes outpatient cycle times from the first screen onward.

What the Right-to-Win unlocks downstream.

The Brief field is the dependency that every downstream prompt in the playbook reads. The flow:

DOWNSTREAM AREAWHAT IT CONSUMES FROM RIGHT-TO-WIN
Pricing & PackagingThe segment where you can charge a premium and the buyer pain that justifies it. Tier design and value-metric selection both anchor on the Right-to-Win segment’s willingness-to-pay.
Win/Loss AnalysisThe hypothesis the win/loss program tests. Every closed-won deal inside the Right-to-Win segment validates it; every closed-lost deal inside it is the signal to refine.
Brand & PositioningThe conviction sentence. The pillars derive from the buyer pain + competitive gap. The voice rules come from the recurring phrase customers used.
Best-in-Class AssessmentThe benchmark against which capability gaps are scored. A team strong in the Right-to-Win segment doesn’t need to score high in every capability; they need to score high in the capabilities that serve the Right-to-Win.
Content & SEOTopic cluster prioritization. The Right-to-Win segment’s buyer pain dictates the first 30 articles, the keyword strategy, and the customer-story selection.
Paid MediaTargeting parameters. The Right-to-Win firmographic profile is the Tier-1 audience; everything else is Tier 2 or Tier 3 with reduced bids.
Account-Based MarketingTier-1 account list construction. Every account on the named-account list either is in the Right-to-Win segment or has trigger events suggesting it’s moving into it.
Customer MarketingCase study and reference selection. The flagship customer stories come from the Right-to-Win segment because they convert other prospects in the same segment most efficiently.
PR & CommsReporter targeting and topic prioritization. The Right-to-Win segment’s watering-hole publications get the highest pitch volume.

Without a Brief-level Right-to-Win, each of these areas makes its own assumption about who you sell to and where you win. They drift apart. With a shared Right-to-Win, they compound on the same buyer.

The biannual refresh cadence.

Right-to-Win is not a one-time exercise. The data changes — competitors reposition, the product expands, the buyer matures, the macro environment shifts. The discipline is a structured refresh every six months, ideally at the start of H1 planning and again at mid-year.

The refresh is three steps: (1) re-pull the Sales and PLG signals against the last 12 months; (2) re-run the five-questions interview with five new customers; (3) ask whether the statement still reads as true. If it does, sign it again and keep it. If it doesn’t, draft a v2 and circulate it through leadership, sales, and CS for stress-testing before adopting.

CAPTURE IN YOUR OPERATOR BRIEF — SECTION 2

The brief-builder cards below collect each input: the Sales signal evidence, the PLG/CS signal evidence, the customer-language phrase, the three intersections, and the synthesized statement. Once Section 2 is populated, every prompt here — and every downstream prompt in the playbook — uses your real Right-to-Win.

Brief-builder: your Sales signal evidence

Sales signal — where the team wins fast

Three observations from the last 12 months of closed-won data. Save to Brief Section 4.1 — available as [SALES SIGNAL] in every downstream prompt.

Saved to Brief Section 4.1.

Brief-builder: your PLG or CS signal evidence

PLG or CS signal — where retention and expansion compound

Three observations from product analytics or CS data. Save to Brief Section 4.2 — available as [PLG SIGNAL] in every downstream prompt.

Saved to Brief Section 4.2.

Brief-builder: customer language patterns

The recurring phrase from five customer conversations

Capture the exact phrasing four or five customers used to describe what you do. Save to Brief Section 4.3 — available as [CUSTOMER LANGUAGE] in every prompt.

Saved to Brief Section 4.3.

Brief-builder: the three intersections

The three intersections that make your Right-to-Win defensible

One sentence per intersection. Save to Brief Section 4.4 — the three together are the structural argument behind the statement.

Saved to Brief Section 4.4.

Brief-builder: the Right-to-Win statement

The one-sentence synthesized Right-to-Win

Use the shape: “We win in [segment] because we solve [pain] in a way [competitor] structurally cannot, and our customers describe us as [recurring phrase].”

Saved to Brief Section 4.5. Available as [RIGHT TO WIN] in every prompt and agent across the playbook.

The prompt pack


Five prompts to run the work.

For teams not yet ready to put this work on an agent — or for the human-in-the-loop pass before the agent runs at scale. Every prompt below uses your Brief fields; the bracketed tokens substitute your real values as soon as the Brief is populated.

Prompt 1 — Sales signal extraction

Surface the Right-to-Win hypothesis from closed-won data.

Hand the prompt the last 12 months of closed-won CRM exports. It returns the top three segments by win-rate-over-company-average, with the sales cycle and ACV stats that support each.

You are a Right-to-Win analyst working for [COMPANY NAME]. The product is [POSITIONING]. I am attaching the last 12 months of closed-won CRM export (CSV). For each closed deal you have: industry, company size, employee count, ARR, sales cycle (days), win source, named competitor in the deal, and the “why us” reason field. Analyze the data and return the top three segments where win rate is highest and sales cycle is shortest. For each segment, give me: - Segment definition (industry + size + geography if available) - Win rate vs. the overall company average (multiple) - Average sales cycle vs. the overall company average - The top three named competitors most frequently in the deals - The three most common phrases from the “why us” field Return as a markdown table I can paste into the Brief.

Prompt 2 — PLG / CS signal extraction

Surface the Right-to-Win hypothesis from retention and expansion data.

Hand the prompt your product-analytics or CS-platform export. Returns the segment with strongest retention + expansion. Use as the second signal that triangulates with Prompt 1.

You are a Right-to-Win analyst working for [COMPANY NAME]. I am attaching the last 12 months of product-analytics or customer-success data (CSV). For each customer you have: industry, company size, sign-up date, time-to-first-value (days), 12-month logo retention status, net dollar retention, NPS score, reference willingness. Analyze the data and return the top three segments by combined retention + expansion + activation strength. For each segment, give me: - Segment definition (industry + size + geography) - Time-to-first-value vs. the company average - 12-month logo retention rate - Net dollar retention - Average NPS - Reference willingness rate Return as a markdown table I can paste into the Brief.

Prompt 3 — Customer conversation synthesis

Find the recurring phrase across five customer calls.

Hand the prompt the five customer-call transcripts (recorded with consent). It pulls the recurring language — the exact phrasing customers used unprompted — and surfaces the pattern that anchors the statement.

You are a Right-to-Win analyst working for [COMPANY NAME]. The product is [POSITIONING] for [ICP]. I am attaching five customer-call transcripts. Each was a 30-minute conversation where I asked five questions: (1) Why did you choose us? (2) What were you trying to solve? (3) Why us over the alternatives? (4) What changed after using us? (5) What business impact did you see? For each transcript, extract: - The verbatim phrase the customer used to describe what we do - The buyer pain in their own words (not in marketing language) - The named competitor they evaluated against - The specific outcome they reported Then synthesize across all five transcripts: - The recurring phrase used by four or five of them - The pain language that recurs - The competitor named most often - The outcome pattern Return as a markdown summary. Quote the recurring phrase verbatim.

Prompt 4 — Right-to-Win statement drafting

Synthesize the one-sentence statement from the three signals.

Combines the outputs of Prompts 1, 2, and 3. Returns three candidate statements following the canonical shape, with the structural argument behind each.

You are a Right-to-Win strategist working for [COMPANY NAME]. I am giving you three inputs: (1) Sales signal: [SALES SIGNAL] — the top segment by win rate and sales cycle (2) PLG signal: [PLG SIGNAL] — the top segment by retention and expansion (3) Customer language: [CUSTOMER LANGUAGE] — the recurring phrase across five customer conversations Named competitor most often in the data: [NAMED COMPETITOR] Buyer pain in customer words: [BUYER PAIN LANGUAGE] Draft three candidate Right-to-Win statements following this shape: “We win in [specific segment] because we solve [specific buyer pain] in a way [named competitor] structurally cannot, and our customers describe us as [the recurring phrase].” For each candidate: - The full one-sentence statement - The structural argument (why this segment + why this pain + why this competitive gap) - The risk — the failure mode if the segment shifts Return as three numbered candidates, ranked by strength. Recommend one to lock in as the company Right-to-Win.

Prompt 5 — Stress-test against the ICP Researcher Agent

Run the draft Right-to-Win past simulated buying-committee personas.

Uses the persona deep-dive work in ICP & Audience to surface objections, gaps, and missing proof points before the statement ships to the rest of the org.

You are running an ICP Researcher Agent stress-test for [COMPANY NAME]. The draft Right-to-Win statement: [RIGHT TO WIN] Simulate four members of the buying committee from our ICP & Audience work: 1. The Economic Buyer ([ECONOMIC BUYER]) — what they react to: ROI math, risk, board defensibility 2. The Champion ([CHAMPION]) — what they react to: career risk, internal political ease, team enablement 3. The Technical Evaluator ([TECHNICAL EVALUATOR]) — what they react to: integration depth, technical credibility, performance at their scale 4. The End User ([END USER]) — what they react to: daily workflow impact, learning curve, mobile experience For each persona, generate: - First reaction to the statement (one sentence, in their voice) - The objection they would raise - The proof point that would disarm the objection - The single word or phrase from the statement that resonates or rings false Then synthesize across all four: - Where the statement is strong - Where it is weakest - The one revision that would strengthen it most Return as a markdown table per persona, then the synthesis below.

The agent


One agent that runs the loop.

For teams operating in AI Operating Model territory, the work above runs on one agent instead of five sequential prompts. The agent inherits the Brief, watches the CRM and product-analytics signals on cadence, and surfaces drift before the statement goes stale.

Right-to-Win Council

Keeps the ‘why we win’ thesis honest. Pressure-tests the Right-to-Win statement quarterly against fresh Win/Loss + competitive intel. Surfaces drift before positioning becomes a story we tell ourselves and not the market.

Who is this agent
Identity card
NameRight-to-Win Council
RoleRight-to-Win thesis maintenance — the ‘why we win’ layer
OwnerVP Marketing (with CEO partnership)
Reports toVP Marketing + CEO
Versionv0.5 (supervised)
SurfaceClaude Project + Git (Right-to-Win, RtW, statement is versioned)
Output target/rtw/statement.md (versioned) + /rtw/pressure-test/Q<n>.md + drift alerts
Review cadenceQuarterly pressure-test; monthly drift watch; ad-hoc on category-shifting events
Mission
Keep the Right-to-Win thesis honest. The RtW statement is the answer to ‘why does this company win against the alternatives, in the segments it commits to, today?’. The Council pressure-tests this statement quarterly against fresh Win/Loss themes, competitive intel, customer references, and segment performance — and surfaces drift before the team is selling against a thesis the market no longer believes.
Goals & KPIs the agent moves
Leading indicators — the agent controls these
RtW pressure-test shipped quarterly within 21 days of quarter close, with named dimensions and source citations100% on-time
Drift signal turnaround — from triggering Win/Loss theme to surfaced drift proposal≤ 14 days
Lagging indicators — downstream outcomes with review triggers
RtW statement accuracy — pressure-test confirms current statement on each declared dimension. Trigger: confirmation rate drops below 70% in any single quarter pages the VP Marketing + CRO for a rewrite decision.≥ 80% of dimensions confirmed
Late-stage AE talk-tracks citing the current RtW statement (joint sales-marketing metric, sampled monthly). Trigger: 2 consecutive months below 60% pages the VP Marketing + CRO for a joint enablement review — the statement may be wrong, unclear, or unbought-in.≥ 75%
What it does
Task list
  1. Weekly Pull this week’s Win/Loss themes. Map each to a dimension of the current RtW statement (where-we-play, how-we-win, capabilities-we-have, capabilities-we-don’t).
  2. Weekly Pull the week’s competitive intel signals. Surface any that materially affect the ‘against the alternatives’ clause of the RtW.
  3. Monthly Drift watch: cumulative Win/Loss + competitive themes this month. Are any RtW dimensions tilting? Surface to VP Marketing.
  4. Monthly Segment audit: which ICP segments are winning at higher / lower rate than the RtW would predict? Flag mismatch.
  5. Quarterly Full RtW pressure-test — structured walkthrough of each dimension against the quarter’s Win/Loss + competitive + customer-reference evidence.
  6. Quarterly Sales talk-track audit: do AEs use the RtW statement language in late-stage conversations? Survey or sample.
  7. Quarterly Compose the ‘state of Right-to-Win’ memo. Three pages. What we’re still right about. What we’re drifting on. What we should change.
  8. Event When a competitor announces a category-shifting move (new product, acquisition, pricing change), pressure-test the ‘against alternatives’ clause within 7 days.
  9. Event When Win/Loss surfaces a theme that directly contradicts an RtW dimension, page VP Marketing same business day.
  10. Event When the ICP definition updates, audit RtW for consistency (RtW is per-segment; if ICP shifts, RtW may need to also).
Schedule grid
TaskFrequencyDurationOutput goes to
Weekly Win/Loss theme mappingWeekly Mon 14:00~30 minVP Marketing + PMM
Weekly competitive intel scanWeekly Mon 14:30~20 minVP Marketing + PMM
Monthly drift watchMonthly 1st~60 minVP Marketing + CEO
Monthly segment auditMonthly 15th~45 minVP Marketing + Sales Director
Quarterly pressure-testQuarterly Q+15 days~4 hours (compile) + 2 hours (review session)CEO + VP Marketing + CRO + Chief Product Officer (CPO)
Quarterly AE talk-track auditQuarterly Q+18 days~3 hours (sample + review)VP Marketing + Sales Director
Quarterly ‘state of RtW’ memoQuarterly Q+21 days~3 hoursCEO + Board (if material change)
Triggers

Scheduled (cron-style):

ScheduleWhat it runs
0 14 * * 1Weekly Win/Loss + competitive scan
0 9 1 * *Monthly drift watch
0 9 15 * *Monthly segment audit
0 9 15 1,4,7,10 *Quarterly pressure-test

Event-driven:

EventWhat it runs
Competitor announces category-shifting movePressure-test ‘against alternatives’ clause within 7 days
Win/Loss theme directly contradicts an RtW dimensionPage VP Marketing same business day
ICP Researcher updates ICP definitionAudit RtW for per-segment consistency within 14 days
Segment win-rate drops > 15 pts vs trailing 4Q averagePressure-test that segment’s RtW clauses immediately
CEO or Board flags a positioning concernRun an ad-hoc pressure-test within 5 business days
Who it works with
Inputs
SourceTypeCadenceRequired?
Operator Brief (Sections 1, 2, 4, 6)MarkdownRead every runRequired
Right-to-Win statement (current version)Markdown (Git-versioned)Read every runRequired — THE artifact
Win/Loss Agent themesMarkdownPer-interview + weekly rollupRequired — primary evidence stream
Market Intelligence Agent outputMarkdownDailyRequired for competitive evidence
Customer reference patterns (Customer Marketing Agent)MarkdownWeeklyRequired for ‘why we won’ evidence
Per-segment win-rate data (Revenue Attribution Engine)JSONWeeklyRequired for segment audit
AE talk-track samples (transcripts or summaries)TextQuarterlyRequired for adoption audit
Outputs
OutputFormatTarget pathAudience
RtW pressure-test report (quarterly)Markdown + Git PR/rtw/pressure-test/Q<n>.mdCEO + VP Marketing + CRO + CPO
‘State of Right-to-Win’ memo (quarterly)Markdown/rtw/state-of-rtw/Q<n>.mdCEO + Board if material
Monthly drift watch digestMarkdown + Slack message/rtw/drift/YYYY-MM.mdVP Marketing + CEO
Segment audit (monthly)Markdown/rtw/segment-audit/YYYY-MM.mdVP Marketing + Sales Director
Drift alerts (event-triggered)Slack DMSlack DM to VP MarketingVP Marketing
RtW statement proposed updatesGit PR against /rtw/statement.mdBrief Sync Agent + Section 4 ownerVP Marketing (final approval)
↑ Upstream — agents/sources that feed this one
  • Operator Brief (human-maintained). Section 4 RtW is the artifact under management.
  • Win/Loss Agent. Highest-signal source of RtW drift.
  • Market Intelligence Agent. Competitive moves that affect the ‘against alternatives’ clause.
  • Customer Marketing Agent. Customer reference patterns that prove or disprove the RtW capabilities clauses.
  • Revenue Attribution Engine. Per-segment win-rate ground-truth for the segment audit.
  • ICP Researcher Agent. ICP definition that bounds where RtW applies.
↓ Downstream — agents/humans that consume its output
  • CEO (human). Reviews quarterly memo; approves RtW statement updates.
  • VP Marketing (human). Owns the RtW maintenance program.
  • Every AE (human). Uses the RtW statement in late-stage talk tracks.
  • Brand Voice Agent. Uses RtW to score ‘positioning fidelity’ on drafted outputs.
  • Performance Marketing Agent. Uses RtW to write ad copy and landing-page messaging.
  • PR Comms Agent. Uses RtW for analyst briefings and press positioning.
  • Brief Sync Agent. Receives RtW updates to propose Brief Section 4 changes.
Human escalation paths
Trigger conditionEscalate toWithin
Win/Loss theme directly contradicts an RtW dimensionVP Marketing + CEOSame business day
Quarterly pressure-test missed Q+21-day deadlineVP Marketing + CEOImmediate
Segment win-rate drop > 15 pts with no clear causeVP Marketing + CEO + CRO< 7 days (immediate pressure-test)
AE talk-track audit shows < 70% adoptionVP Marketing + Sales DirectorSame quarter (enablement gap)
CEO disagrees with the ‘state of RtW’ memo’s conclusionVP Marketing + CEOSame week (alignment session)
How to build it
System prompt
You are the Right-to-Win Council for [COMPANY]. YOUR JOB Keep the Right-to-Win thesis honest. Pressure-test the RtW statement quarterly against fresh Win/Loss + competitive + customer evidence. Surface drift before positioning becomes a story we tell ourselves. INPUTS (always read in this order) 1. /operator-brief.md (Section 4 RtW) 2. /rtw/statement.md (the current canonical statement) 3. /win-loss/themes/ - latest themes by persona + segment 4. /competitive/snapshots/ - latest Market Watch output 5. /attribution/per-segment-winrate.json - win-rate ground truth OUTPUTS - /rtw/pressure-test/Q<n>.md (quarterly) - /rtw/state-of-rtw/Q<n>.md (quarterly memo) - /rtw/drift/YYYY-MM.md (monthly drift watch) - Git PR against /rtw/statement.md (when updates proposed) RULES 1. Pressure-test walks each RtW dimension: where-we-play, how-we-win, capabilities-we-have, capabilities-we-don't, against-alternatives. 2. Each dimension assessment cites at least 3 supporting evidence pieces from Win/Loss, competitive, customer references, or segment data. 3. Drift alerts cite specific contradictory evidence + dimension affected. 4. Never modify /rtw/statement.md directly. Propose via PR. 5. The "state of RtW" quarterly memo is 3 pages max: still right / drifting / change recommendation. No padding. 6. AE adoption audit samples real talk tracks - not survey self-report. ESCALATION - Theme contradicts a dimension: page VPM + CEO same day. - Pressure-test missed deadline: page VPM + CEO immediately. - Segment win-rate drops 15 pts: pressure-test that segment <7 days.
Tools & integrations
Platform / toolUsed forRequired?
Claude Project + GitRtW statement versioning + reasoning surfaceRequired
PostgresPressure-test history + drift signal corpusRequired
GitHub / GitLab APIFiling PRs against the RtW statementRequired
Slack APIWeekly digest + drift alerts + escalationRequired
Interview transcription (Otter / Fireflies / Granola)AE talk-track audit inputRequired
Salesforce / HubSpot APIPer-segment win-rate + opportunity dataRequired
Guardrails — what it must not do
  • Never modify the RtW statement directly. Propose via PR.
  • Never propose an RtW change without ≥ 3 supporting evidence pieces from at least 2 different sources.
  • Honor the per-segment scope of RtW — what wins in upper-mid-market may not win in enterprise.
  • Never compress competing evidence into a one-sided pressure-test. Surface tension; let humans resolve.
  • Never share the ‘state of RtW’ memo outside the executive scope without CEO approval — it’s competitive strategy.
  • Honor the AE talk-track audit methodology — sampling real calls, not self-report.
  • Never claim RtW alignment based on theory; require evidence from market reality.
Evals + hallucination defense

Evals — output quality checks:

  1. Pressure-test rigor. Quarterly: each dimension assessment cites ≥ 3 evidence pieces. Target 100%.
  2. Drift catch lead time. When RtW changes are eventually made, audit: how many quarters before the change did drift get surfaced? Target ≥ 1 quarter advance warning.
  3. AE adoption. Quarterly: % of late-stage AE talk-tracks using RtW language. Target ≥ 90%.
  4. CEO defensibility. Quarterly: CEO rates the ‘state of RtW’ memo 1–5 on “could you defend this to the Board?”. Target ≥ 4.5.

Hallucination defense — specific checkpoints:

  • RtW dimension assessments must cite specific Win/Loss interview IDs, competitive snapshots, customer references, or segment win-rate data.
  • Drift signals must cite specific contradictory evidence — never “the market feels different.”
  • AE adoption claims must trace to specific sampled talk-tracks with sample size declared.
  • When evidence is mixed, surface both sides explicitly in the pressure-test rather than file a one-sided assessment.
  • Segment win-rate claims must cite the data window + segment definition.
Maturity curve + first-run checklist
v0.1 — Manual-assistCouncil compiles pressure-tests on VP Marketing’s request. No autonomous drift watching. Useful from day 1 to formalize RtW discipline.
v0.5 — SupervisedWeekly theme mapping + monthly drift watch + quarterly pressure-test + quarterly memo. VP Marketing + CEO review every quarterly. Default ship state.
v1.0 — Semi-autonomousAfter 4 quarters of clean evals + CEO confidence ratings ≥ 4.5, agent auto-publishes monthly drift digests. RtW statement changes always remain CEO-approved.

First-run checklist — 5 steps from spec to running agent:

  1. Confirm the current RtW statement is in Git as /rtw/statement.md.
  2. Wire the evidence inputs — Win/Loss, competitive, customer references, segment data. Verify the agent can read each.
  3. Run the first quarterly pressure-test in shadow mode with VP Marketing + CEO. Tune the dimension framework.
  4. Schedule the quarterly pressure-test + monthly drift digest cadence. Subscribe VP Marketing + CEO.
  5. Train AEs to read the ‘state of RtW’ memo at quarter-start. Log every run in /rtw/agent-log.md.

What this unlocks


The Brief Section 4 hand-off.

Once Right-to-Win is captured in the Brief, every downstream prompt in the playbook imports it. Pricing & Packaging uses the segment to set premium-tier pricing. Win/Loss Analysis tests it on every closed deal. Brand & Positioning derives the pillars and voice from the recurring phrase. Every channel area targets the segment with sharper inputs than generic ICP work alone produces. The full handoff map sits in Operator Brief.