Strategic Foundation
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.
The framework — strategy first
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.
| QUESTION | ICP ANSWERS | RIGHT-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-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.
| INTERSECTION | THE QUESTION IT ANSWERS | WHERE 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.
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.
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:
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.
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:
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.
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:
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:
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.
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.
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.
The Brief field is the dependency that every downstream prompt in the playbook reads. The flow:
| DOWNSTREAM AREA | WHAT IT CONSUMES FROM RIGHT-TO-WIN |
|---|---|
| Pricing & Packaging | The 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 Analysis | The 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 & Positioning | The conviction sentence. The pillars derive from the buyer pain + competitive gap. The voice rules come from the recurring phrase customers used. |
| Best-in-Class Assessment | The 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 & SEO | Topic cluster prioritization. The Right-to-Win segment’s buyer pain dictates the first 30 articles, the keyword strategy, and the customer-story selection. |
| Paid Media | Targeting 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 Marketing | Tier-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 Marketing | Case 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 & Comms | Reporter 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.
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.
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.
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.
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.
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.
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
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
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.
Prompt 2 — PLG / CS signal extraction
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.
Prompt 3 — Customer conversation synthesis
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.
Prompt 4 — Right-to-Win statement drafting
Combines the outputs of Prompts 1, 2, and 3. Returns three candidate statements following the canonical shape, with the structural argument behind each.
Prompt 5 — Stress-test against the ICP Researcher Agent
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.
The agent
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.
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.
| Task | Frequency | Duration | Output goes to |
|---|---|---|---|
| Weekly Win/Loss theme mapping | Weekly Mon 14:00 | ~30 min | VP Marketing + PMM |
| Weekly competitive intel scan | Weekly Mon 14:30 | ~20 min | VP Marketing + PMM |
| Monthly drift watch | Monthly 1st | ~60 min | VP Marketing + CEO |
| Monthly segment audit | Monthly 15th | ~45 min | VP Marketing + Sales Director |
| Quarterly pressure-test | Quarterly Q+15 days | ~4 hours (compile) + 2 hours (review session) | CEO + VP Marketing + CRO + Chief Product Officer (CPO) |
| Quarterly AE talk-track audit | Quarterly Q+18 days | ~3 hours (sample + review) | VP Marketing + Sales Director |
| Quarterly ‘state of RtW’ memo | Quarterly Q+21 days | ~3 hours | CEO + Board (if material change) |
Scheduled (cron-style):
| Schedule | What it runs |
|---|---|
0 14 * * 1 | Weekly 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:
| Event | What it runs |
|---|---|
| Competitor announces category-shifting move | Pressure-test ‘against alternatives’ clause within 7 days |
| Win/Loss theme directly contradicts an RtW dimension | Page VP Marketing same business day |
| ICP Researcher updates ICP definition | Audit RtW for per-segment consistency within 14 days |
| Segment win-rate drops > 15 pts vs trailing 4Q average | Pressure-test that segment’s RtW clauses immediately |
| CEO or Board flags a positioning concern | Run an ad-hoc pressure-test within 5 business days |
| Source | Type | Cadence | Required? |
|---|---|---|---|
| Operator Brief (Sections 1, 2, 4, 6) | Markdown | Read every run | Required |
| Right-to-Win statement (current version) | Markdown (Git-versioned) | Read every run | Required — THE artifact |
| Win/Loss Agent themes | Markdown | Per-interview + weekly rollup | Required — primary evidence stream |
| Market Intelligence Agent output | Markdown | Daily | Required for competitive evidence |
| Customer reference patterns (Customer Marketing Agent) | Markdown | Weekly | Required for ‘why we won’ evidence |
| Per-segment win-rate data (Revenue Attribution Engine) | JSON | Weekly | Required for segment audit |
| AE talk-track samples (transcripts or summaries) | Text | Quarterly | Required for adoption audit |
| Output | Format | Target path | Audience |
|---|---|---|---|
| RtW pressure-test report (quarterly) | Markdown + Git PR | /rtw/pressure-test/Q<n>.md | CEO + VP Marketing + CRO + CPO |
| ‘State of Right-to-Win’ memo (quarterly) | Markdown | /rtw/state-of-rtw/Q<n>.md | CEO + Board if material |
| Monthly drift watch digest | Markdown + Slack message | /rtw/drift/YYYY-MM.md | VP Marketing + CEO |
| Segment audit (monthly) | Markdown | /rtw/segment-audit/YYYY-MM.md | VP Marketing + Sales Director |
| Drift alerts (event-triggered) | Slack DM | Slack DM to VP Marketing | VP Marketing |
| RtW statement proposed updates | Git PR against /rtw/statement.md | Brief Sync Agent + Section 4 owner | VP Marketing (final approval) |
| Trigger condition | Escalate to | Within |
|---|---|---|
| Win/Loss theme directly contradicts an RtW dimension | VP Marketing + CEO | Same business day |
| Quarterly pressure-test missed Q+21-day deadline | VP Marketing + CEO | Immediate |
| Segment win-rate drop > 15 pts with no clear cause | VP Marketing + CEO + CRO | < 7 days (immediate pressure-test) |
| AE talk-track audit shows < 70% adoption | VP Marketing + Sales Director | Same quarter (enablement gap) |
| CEO disagrees with the ‘state of RtW’ memo’s conclusion | VP Marketing + CEO | Same week (alignment session) |
| Platform / tool | Used for | Required? |
|---|---|---|
| Claude Project + Git | RtW statement versioning + reasoning surface | Required |
| Postgres | Pressure-test history + drift signal corpus | Required |
| GitHub / GitLab API | Filing PRs against the RtW statement | Required |
| Slack API | Weekly digest + drift alerts + escalation | Required |
| Interview transcription (Otter / Fireflies / Granola) | AE talk-track audit input | Required |
| Salesforce / HubSpot API | Per-segment win-rate + opportunity data | Required |
Evals — output quality checks:
Hallucination defense — specific checkpoints:
First-run checklist — 5 steps from spec to running agent:
What this unlocks
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.