--- name: build-a-sales-enablement-framework title: Build a Sales Enablement Framework description: A ChatGPT prompt for sales enablement that maps the buyer journey to a sales enablement content map plus coaching, then proves impact with a four metric funnel. cluster: b2b-product-marketing version: 1.1.0 --- # Build a Sales Enablement Framework This prompt turns a scattered pile of decks, scripts, and trainings into one coherent enablement operating system. It maps every stage of the buyer journey to the four services a customer facing team actually needs (customer facing content, internal enablement content, field training, manager coaching), grades what you have against what the framework demands, and hands you a prioritized build list with owners. It closes by wiring in a four metric funnel so you can prove the program is working instead of guessing. ## When to use this → You are launching an enablement function from scratch and need a single master artifact everything feeds into → Your reps have content and training but win rates are flat, and you suspect the pieces are not connected to what buyers are trying to do at each stage → Leadership is asking you to prove enablement impact and you have no funnel that ties training to revenue ## The prompt ```text You are a senior sales and customer success enablement architect. You design enablement as a strategic, cross functional operating function, not a content dump: consistent, scalable services that help customer facing professionals add value in every interaction. Your output is a build plan a team can execute, not generic advice. CONTEXT → Company and what it sells: {{COMPANY_AND_OFFERING}} → Motion (sales, customer success, or both): {{MOTION}} → Field roles in play (BDR, AE, CSM, solutions consultant, onboarding, etc.): {{FIELD_ROLES}} → Current buyer journey stages and CRM stage names if any: {{CURRENT_STAGES}} → Existing assets, trainings, and tools: {{EXISTING_INVENTORY}} → Tech in place (CRM, LMS, content platform, conversation intelligence): {{TECH_STACK}} → Biggest known problem in the field today: {{KNOWN_PROBLEM}} → Launch timeline and named build owners, or "unknown": {{TIMELINE_AND_OWNERS}} If any of these are missing or vague, especially the buyer journey stages, the field roles, and the existing inventory, ask me clarifying questions one at a time, waiting for my answer before asking the next, until you have what you need or you have asked five. Do not invent stages or assets. OPERATING PRINCIPLES (hold these throughout) 1. The buyer has the power; your process conforms to the buyer, not the reverse. 2. Buying is hard. The real competitor is inertia (do nothing). Every artifact must make it easier for the customer to buy. 3. Be the conductor, not the orchestra. You build the framework and tap the real expert in each area; you do not author everything yourself. METHOD Step 1. Build the top line with the Three Whys. Write, in one sentence each: Why should I do anything (the macro problem, absent your product); Why should I do anything right now (the cost of doing nothing, quantified per day or quarter); Why should I do anything with you (your differentiators). Sort differentiators into comparative (you do it better), unique (only you, provable), and holistic (who you are). Comparative and unique matter early in the journey; holistic matters late. Step 2. Align a sales process to the journey. Treat the sales process and the buyer journey as the same span: awareness through implementation and value (include post purchase). For each stage fill five components: key activities (2 to 5 discrete seller actions in common language), one milestone (the highest leverage crux move), roles (owner mapped to real resources), exit criteria (definition of done, customer verified, not just rep notes), and a simple CRM stage name. Step 3. Layer the four enablement services onto every stage. For each stage produce: (a) customer facing content the buyer sees; (b) internal enablement content, purpose built cue cards and scripts for reps, never repurposed customer assets; (c) field training tied to when and how it is used; (d) manager coaching artifacts. Do not conflate a customer facing business case deck with an internal ROI calculator, or a long form case study with an internal customer story. For internal stories use the STAR arc in 3 to 4 sentences: Situation, Task, Action, Result. Step 4. Specify certification on the milestones. For each milestone define a certification with four parts: consumable content (video under 10 minutes, one or two points each), a knowledge check with viable wrong answers, a pitch submission in simulation, and measurement and badging in a central place leadership can inspect. Step 5. Build manager coaching per motion. For each milestone motion define three artifacts on the same points of performance: a points of performance checklist, a role play scorecard (score each point 0 or 1, add soft skill rows for confidence, simplicity, credibility, conversational, pass at 90 percent), and a live action scorecard applied to a real call. Flag that lack of management support is the top reason enablement fails. Step 6. Run a gap analysis and prioritize. Rate every cell as green (exists, fit for purpose), amber (exists but needs a serious level up), or red (missing). Only rate an item green or amber if it appears in the existing inventory I gave you; anything not listed there is red. Prioritize using two rules: start at the beginning of the journey and move forward, and cover milestones before micro activities. Output a build list of the reds as "must complete before launch" with an owner and due date each. Use the named owners and dates I supplied; where I supplied none, assign owners by role or function and sequence due dates relatively (week 1, week 2, and so on). Never invent a person's name. Step 7. Wire the measurement funnel. Define four metrics with a source of truth for each: does the team know what to do (certification rate, LMS); are they using the right resources (content usage rate, content platform); are they executing in the field (call scores on the same points of performance, conversation intelligence); is it working (pipeline, stage progression, wins, CRM). For each metric, set a current benchmark only if my inputs contain one; otherwise write "baseline TBD" and name the exact report or dashboard in my stack to pull it from. Set a tracking cadence for all four. OUTPUT FORMAT 1. Three Whys summary (three sentences plus a differentiator classification). 2. A stage by stage table: stage name, key activities, milestone, role, exit criteria. 3. A four service grid per stage (customer facing, internal, training, coaching). 4. A certification and coaching spec for each milestone. 5. A prioritized build list (red items) with owner and due date columns. 6. The four metric funnel with source of truth and starting benchmark (or "baseline TBD" plus where to pull it) per step. 7. A fact check list: every assumption you made about my stages, assets, or stack; every green or amber rating I should confirm against the real asset; and every claim in the Three Whys (differentiators, quantified cost of inaction) I must verify before circulating the plan. SELF CHECK before finishing → Verify every exit criterion is customer verifiable, not a rep assertion. → Verify each internal enablement item is purpose built for reps, not a relabeled customer asset. → Confirm certifications sit on milestones, and coaching scorecards reuse the exact points of performance from training. → Failure modes to avoid: inventing stages or assets not supplied; treating the sales process as first meeting to signed contract and dropping implementation; overloading the field through many channels at once (route communication through one trusted field voice); launching gated on a large software purchase rather than starting with tools you already have. ``` ## Prompt versions The standard prompt above works on any model. Use these variants when you want a different tradeoff. ### Frontier model version Built for the most capable models (Claude Opus and beyond). States the goal, constraints, and quality bar up front, then trusts the model to choose its path. ```text You are a senior sales and customer success enablement architect. Enablement is a strategic operating function, not a content dump. GOAL: Turn my scattered assets into one coherent enablement operating system, and hand me a prioritized build plan a team can execute. Lead your output with the single build list of "must complete before launch" red items (owner and due date each); put the framework, specs, and funnel after it. CONTEXT (intake, do not proceed on guesses): → Company and offering: {{COMPANY_AND_OFFERING}} → Motion (sales, success, or both): {{MOTION}} → Field roles: {{FIELD_ROLES}} → Current buyer journey stages and CRM stage names: {{CURRENT_STAGES}} → Existing assets, trainings, tools: {{EXISTING_INVENTORY}} → Tech in place (CRM, LMS, content platform, conversation intelligence): {{TECH_STACK}} → Biggest field problem today: {{KNOWN_PROBLEM}} → Timeline and named build owners, or "unknown": {{TIMELINE_AND_OWNERS}} PRINCIPLES (load bearing, hold throughout): → The buyer holds the power; your process conforms to the buyer. The real competitor is inertia, so every artifact must make it easier to buy. → Treat the sales process and the buyer journey as one span, awareness through implementation and value; never drop post purchase. → Open with the Three Whys: why do anything (macro problem), why now (cost of inaction, quantified), why you (differentiators, sorted comparative, unique, holistic). → Per stage, define key activities, one milestone (the crux move), roles, customer verifiable exit criteria, and a CRM stage name. Layer four services on each stage: customer facing content, internal rep only content (purpose built cue cards, scripts, STAR stories, never relabeled customer assets), field training, manager coaching. → Certify on milestones (short video, knowledge check with viable wrong answers, simulated pitch, central badging). Coaching scorecards reuse the exact points of performance from training. → Gap grade every cell green, amber, or red; only green or amber if it appears in the inventory I gave you, else red. Prioritize forward from the start of the journey, milestones before micro activities. → Close with a four metric funnel, each with a source of truth in my stack: certification rate (LMS), content usage (content platform), call scores (conversation intelligence), pipeline and wins (CRM). Benchmark only where I supplied one, else "baseline TBD" plus the exact report to pull it from. QUALITY BAR: Every exit criterion is customer verifiable, not a rep assertion. The internal column is clearly distinct from the customer facing one. The build list is sequenced from the journey start and anchored on milestones first. The plan ends with a fact check list of assumptions, ratings to confirm, and Three Whys claims to verify. DO NOT: invent stages, assets, or a person's name; pad with generic advice; treat the process as first meeting to signed contract; overload the field across many channels at once; gate launch on a large software purchase. If a required input, especially stages, roles, or inventory, is missing, ask one focused question instead of guessing. ``` ### Quick version Five lines or fewer, for when speed matters more than rigor. ```text You are an enablement architect. For {{COMPANY_AND_OFFERING}} with roles {{FIELD_ROLES}} across stages {{CURRENT_STAGES}}, and given my inventory {{EXISTING_INVENTORY}}, map each buyer journey stage to a milestone plus four services (customer facing content, internal rep content, training, coaching). Grade each cell green, amber, or red (green or amber only if it is in my inventory), then give me a prioritized build list of the reds, sequenced from the journey start, milestones first. Every exit criterion must be customer verifiable, not a rep assertion. Do not invent stages, assets, or names; ask me if stages or inventory are missing. ``` ## How to customize → `{{COMPANY_AND_OFFERING}}`: what you sell and to whom, for example "AI conversational marketing platform sold to B2B demand gen leaders." → `{{MOTION}}`: sales, customer success, or both. The framework is agnostic; naming the motion sharpens the roles and stages. → `{{FIELD_ROLES}}`: the specific roles you actually staff, for example "SDR, AE, solutions consultant, CSM." Some orgs run one role across all stages; some split stages 1 to 4 and 5 to 6. → `{{CURRENT_STAGES}}`: any stage names already live in your CRM, so the model refines rather than reinvents. → `{{EXISTING_INVENTORY}}`: your current decks, scripts, trainings, and calculators, so the gap analysis grades against reality. → `{{TECH_STACK}}`: your CRM, LMS, content platform, and conversation intelligence tool, so the funnel points each metric at a real source of truth. → `{{KNOWN_PROBLEM}}`: the sharpest field pain today, which the model uses to bias prioritization. → `{{TIMELINE_AND_OWNERS}}`: your launch date and the people who own builds, for example "launch September 1; content owned by Priya, training by Marcus." Write "unknown" if you have neither; the build list then uses roles as owners and relative weeks as dates instead of inventing names. ## What good output looks like → Every stage has a single named milestone and a customer verified exit criterion, not a vague "moved to next stage." → The internal enablement column contains rep built artifacts (scripts, ROI calculators, STAR stories), clearly distinct from the customer facing column. → The build list is a prioritized set of red items sequenced from the start of the journey and anchored on milestones first; owners and dates come from your inputs, and where you gave none they appear as roles and relative weeks, never invented names. → The gap grid only marks green or amber what you actually listed in your inventory; everything else is red, so the plan grades reality instead of flattering it. → The measurement funnel names a real source of truth for all four metrics and either a starting benchmark or "baseline TBD" with the exact report to pull it from, so progress is trackable next quarter. → The output ends with a fact check list of assumptions, ratings to confirm, and Three Whys claims to verify before the plan circulates. ## Related prompts → [Plan a Product Launch End to End](./plan-a-product-launch.md): once the framework exists, use it to enable the field ahead of a launch. → [Build Competitor Battle Cards](./build-competitor-battle-cards.md): feed the internal enablement column with the competitive intelligence reps need at each stage. → [Run a Win Loss Program](./run-a-win-loss-program.md): source the exit criteria and perceived barriers that make your stages and coaching honest.