Write stakeholder talk tracks: CFO vs end user vs IT
Produces three genuinely distinct talk-track cards — CFO, end user, and IT by default — each with a 60-second conversational pitch, vocabulary to use and avoid, the role's signature objection, and the type of proof that actually moves them. Ends the one-pitch-fits-all habit that quietly loses two of every three stakeholders.
You are a sales messaging strategist who builds role-based talk tracks. Your operating principle: the same product is three different purchases depending on who's listening. To a CFO it's a financial instrument with a payback period. To an end user it's a change to their workday that had better be worth the disruption. To IT it's an attack surface, an integration burden, and a migration project. Reps who deliver one pitch to all three lose two of them. Build me a talk-track card for each of three stakeholder types. For EACH stakeholder: 1. WHAT THEY'RE ACTUALLY BUYING: one sentence reframing my product in their terms. 2. THE 60-SECOND TRACK: a conversational pitch I can deliver naturally — their metric or concern first, product second. Written the way people talk, not the way slides read. 3. THREE PHRASES TO USE: vocabulary that signals I understand their world. 4. THREE PHRASES TO NEVER USE with this stakeholder, and why each backfires — e.g., 'disruptive innovation' to a CFO signals risk, 'automation' to an end user signals replacement. 5. THEIR LIKELY PUSHBACK: the one objection this role raises most, with a two-sentence response. 6. THE PROOF THAT MOVES THEM: which kind of evidence this role trusts — payback math for CFOs, a peer reference for users, documentation and a security posture for IT. Rules: the three tracks must be genuinely different, not one pitch with swapped nouns. Each 60-second track must open with THEIR world, never with my product. Before you write anything, interview me. Ask me these questions ONE AT A TIME, waiting for my answer each time: 1. What does your product do, and what does it replace or change? 2. What are the honest numbers — cost, typical payback or ROI story, implementation effort? 3. Which three stakeholder roles do you face most? (Default: CFO/finance, end user, IT — correct me if yours differ.) 4. What integration, security, or change-management realities should I know about? Once you have my answers, write the three cards. If my ROI story is vague, ask one follow-up — a CFO track without numbers is dead on arrival.
How to use it
- 1
Copy the prompt into Claude, ChatGPT, or any LLM.
- 2
Correct the default roles in question 3 if your deals involve different functions — clinical vs admin, ops vs finance.
- 3
Rehearse each 60-second track aloud once; they're written for speech and reading them silently hides the clunky spots.
- 4
Keep the never-say lists visible on group calls — one wrong word to the wrong stakeholder undoes a good pitch.
- 5
Combine with the stakeholder demo personalization prompt when the talk tracks need to become a demo.
Best practices
The never-say phrases are the fastest win — most reps have no idea 'automation' terrifies end users.
Match the proof to the room: sending a CFO a feature sheet or an end user an ROI model wastes both.
If two tracks sound similar, the model defaulted to noun-swapping — reply 'make the IT track about risk and migration, not benefits' and regenerate.
Update the cards quarterly with real objections your team hears; the pushback section improves with field data.
Example: what this looks like in practice
A sales leader at a 45-person document-automation company preps her team for a mid-market push where deals now involve finance sign-off. She answers the interview: the product replaces manual contract assembly, pays back in about four months, and requires a two-week CRM integration. The cards come back sharply different — the CFO track opens on cost-per-contract and payback, the paralegal (end user) track opens on 'the 11 PM formatting scramble' and explicitly avoids the word 'automation', the IT track leads with the integration scope and SOC 2 posture. She drills the tracks in role-plays for a week. On the next three-stakeholder call, her AE switches tracks mid-meeting when the CFO joins late, and the CFO's first comment is 'you're the first vendor to lead with payback.'
Best fit
This prompt is one gear in a bigger machine. We orchestrate 20+ tools into outbound systems our clients own — and guarantee the results.
Apply for a Pilot Spot → →Frequently asked questions
Reframe what's being bought, don't just reword the pitch. A CFO is buying a payback period, an end user is buying a better workday, IT is buying (or blocking) a migration and an attack surface. Each needs its own opening, vocabulary, and proof type. This prompt forces three genuinely different tracks and bans the noun-swapped single pitch that loses rooms.
More discovery calls & demos prompts
Build a discovery question bank tailored to one persona
Generates a 15-question discovery bank built around one persona's actual responsibilities and failure modes, organized by call stage, with listening notes on what strong and weak answers sound like. Beats generic question lists because the interview forces your product, competitor, and deal-death context into every question.
Write a post-discovery summary email that mirrors their words
Produces a sub-180-word summary email built on the prospect's verbatim phrases, with impact-paired bullets, an invitation to correct you, and next steps with your commitments listed first. Mirroring their language proves you listened in a way no template can, and the email becomes the artifact your champion forwards internally.
Build a demo storyline from your discovery notes
Converts raw discovery notes or a transcript into a three-act demo storyline that opens on the prospect's problem in their own words, sequences scenes by deal importance, tells you what NOT to show, and scripts the close. It's the difference between a feature tour and a demo the champion replays internally.