The Ultimate Messaging Framework (with AI Prompts) Playbook for High-Performance Sales Teams : Part 1 of 2

Steal the exact messaging frameworks and prompts used by elite sales teams. Includes 10 plug-and-play templates + AI prompts to supercharge your outbound.

Most sales teams don’t have a tool problem. They have a messaging problem.

We kept seeing smart SDRs and AEs working hard — but their outreach still sounded like every other email in the inbox.

A few months ago, we were helping one of our clients troubleshoot their outbound playbook. Same tool stack. Same target ICP.

But one big unlock: messaging structure.

That’s when it hit us — what if we built a practical guide with the best messaging frameworks used by top sales teams?

So we reverse-engineered how the best sales teams craft their outbound — and paired each framework with an AI-ready prompt.

Bonus: Each framework comes with a prompt to generate variations using AI, so your team can scale precision outreach without wasting time.

We have divided this newsletter series in 2 parts.

We are going to cover the following frameworks along with prompts below:

• Value-Based Messaging – Tailor to persona, goals & pain

• Industry-Led Messaging – Vertical-specific insights + proof

• Stage-Based Messaging – Align by TOFU, MOFU, BOFU

• Challenger Messaging – Insight-led reframe + ROI

• Pain → Strategic Mapping – From symptoms to initiatives

• PAS Framework – Cold outreach classic: Problem–Agitate–Solve

• Jobs-To-Be-Done (JTBD) – Goal, friction, fix, outcome

• PSIA Messaging – Pain–Signal–Impact–Action flow

• ACCA Messaging – Awareness → Advocacy

• 4C Messaging – Clear, Concise, Compelling, Credible

Framework #1. Value-Based Messaging (Persona-specific)

Best for: Personalization by role/responsibility

Components:

• Role: What is their job-to-be-done?

• Goals: What outcomes are they measured on?

• Pains: What slows them down or keeps them up at night?

• Value Prop: How your solution helps them hit KPIs or eliminate risk

Example:
"As a VP of Sales, you're likely focused on increasing pipeline velocity. We help sales leaders reduce rep ramp time by 30% using AI-guided call analysis."

Prompt:

You are an expert sales strategist trained in frameworks used by top outbound teams at Salesforce, Gong, and Outreach. Your task is to generate high-converting outbound messages using the Value-Based Messaging Framework, which tailors copy to a buyer persona’s job-to-be-done, measurable goals, daily pain points, and the value your solution delivers.

# INPUT FIELDS:
Ask for the following variables (fill or infer based of common industry data if not provided):
[Persona Role]
[Industry or Company Type]
[Top KPIs / Measurable Goals]
[Known Pain Points / Operational Bottlenecks]
[Sales Trigger or Signal - optional]
[Solution / Product Name or Category]
[Key Outcome / ROI or Business Impact]

# OUTPUT FORMAT:
Generate 2-3 short outbound message variations using the format below:

Template 1 — Insight-Driven
“As a [Persona Role] at a [Industry] company, you’re likely focused on [Goal/KPI]. A lot of leaders in your space deal with [Pain Point], especially when [Context or Trigger]. We help [Persona Type] drive [Business Outcome] by [How Your Solution Solves It].”

Template 2 — Conversational + Curiosity Hook
“Noticed you're leading [Function] at a [Industry] org — curious if hitting [Goal] is top of mind this quarter? We help teams like yours reduce [Pain Point] by [Solution], which drives [Outcome or KPI lift].”

Template 3 — Trigger-Based
“Saw that [Trigger] recently happened at [Company]. Often, that puts pressure on [Persona Role] to [Goal or KPI]. We help leaders in your role avoid [Pain or Risk] and deliver [Value Prop or Outcome] with [Solution Name].”

# RULES:
- Keep the tone consultative and relevant 
— like a peer offering insight.
- Prioritize business outcomes over features.
- Vary language slightly across outputs (e.g., one direct, one curiosity-driven, one insight-led).
- If [Trigger] is missing, omit that line smoothly.
- Always anchor messaging in how the solution helps the persona meet goals or eliminate pain.
- Avoid buzzwords 
— keep it crisp, concrete, and practical.

# Optional (add as needed):
- Add “[Persona Libraries]” to suggest messaging for common roles (e.g., VP Sales, CMO, CFO).
- Insert “[Objection Handling Layer]” with light preemptive responses for common friction (e.g., “Already using Salesforce” → “Our AI layer integrates directly into your existing Salesforce instance.”)
- Include “CTA Module” to suggest soft call-to-action endings (e.g., “Open to exploring?” or “Worth a quick look?”)

Framework #2. Industry-Led Messaging (Vertical-specific)

Best for: Relevance by market segment

Component:

• Industry Challenge: What's happening in their industry?

• Insight: What’s a non-obvious truth or shift they should know?

• Proof: Social proof or case study in their vertical

• Hook: How your solution fits into their unique value chain

Example:

"Retailers are losing margins to inventory misalignment. Our platform helped XYZ reduce stockouts by 18% in Q4 across 200 stores."

Prompt:

You are a sales messaging strategist trained in vertical-based frameworks used by Snowflake, ServiceNow, and Oracle. Your task is to write industry-specific outbound messaging that:

1. Hooks the reader with a challenge in their industry,
2. Shares a non-obvious insight or shift they may not see coming
3. Backs it up with proof from a company in the same or adjacent vertical, and
4. Anchors it to a known pain point at a target account, showing exactly how your solution helps.

# INPUT FORMAT:
Ask for the following variables (fill or infer data if not provided):
[Target Company Name]
[Target Persona Role]
[Industry/Vertical]
[Known Pain Point at Account]
[Common Industry Challenge]
[Insight (non-obvious shift/trend)]
[Case Study or Similar Customer Name]
[Business Impact or Result from Proof]
[Solution Name or Category]
[Where the solution fits into their workflow or tech stack]
[Optional Trigger (funding, hiring, expansion, etc.)]

# OUTPUT FORMAT (2 Message Variations):
Template 1 — Pain-Led + Proof
“At [Target Company], we noticed [Known Pain Point]. It’s something we’re seeing across [Industry], especially as [Industry Challenge] accelerates. We helped [Case Study Company] drive [Business Result] by [How Solution Fits]. Might be relevant for your team too.”

Template 2 — Industry + Insight Hook
“In [Industry], leaders are navigating [Industry Challenge] — but what many overlook is [Insight]. Given [Target Company]'s focus on [Known Pain Point], you might find how [Case Study] tackled this interesting: they saw [Impact] using [Solution], which fits between [Workflow Element A] and [B].”

# RULES:
- Use a confident, consultative tone 
— no fluff, no hard sells.
- Tailor language to the persona (e.g., if CFO, emphasize ROI; if VP Ops, highlight efficiency).
- Reference the pain point with precision 
— e.g., “inconsistent forecasting” not “data issues.”
- Always include a business outcome (e.g., saved 14 days/month, increased fill rate by 12%).
- Keep messages short (2–3 sentences, max 60 words).

# Optional (add as needed):
- Trigger Layer: Add context if a trigger is present (e.g., “Since your Series B raise…”).
- CTA Layer: Soft close (e.g., “Open to seeing how this might apply?”).- Pain Library (internal): Pull from known vertical-specific pain points by role.

Example:

Sample Inputs

• Target Company Name: RevScale

• Target Persona Role: VP of Sales

• Industry/Vertical: B2B SaaS (Sales Tech)

• Known Pain Point at Account: Low SDR productivity despite recent headcount expansion

• Common Industry Challenge: Sales teams are expanding faster than enablement infrastructure can keep up

• Insight: More reps ≠ more pipeline — productivity is now bottlenecked by lack of AI-powered enablement

• Case Study or Similar Customer Name: LeadDrive (another B2B SaaS firm)

• Business Impact or Result from Proof: Increased SDR-sourced pipeline by 38% in 60 days

• Solution Name or Category: AI Sales Enablement Platform

• Where the solution fits: Sits between onboarding and outbound workflows, guiding reps in real-time

• Optional Trigger: Just hired 10 new SDRs in the last 2 months

Output: Two Messaging Variations

Variation 1 – Pain-Led + Proof

"At RevScale, we noticed your team recently added 10 SDRs — but low productivity seems to persist. It’s a common pattern in SaaS where enablement lags behind growth. We helped LeadDrive increase SDR-sourced pipeline by 38% in just 60 days by layering AI between onboarding and outbound workflows. Might be worth a look for your team too."

Variation 2 – Industry + Insight Hook

"In B2B SaaS, sales orgs are scaling fast — but what many overlook is this: adding headcount doesn’t guarantee more pipeline. For RevScale, where SDR productivity remains low, this could be a key unlock. LeadDrive faced the same issue — and saw a 38% lift in SDR pipeline after embedding AI enablement between onboarding and outbound."

Framework #3. Stage-Based Messaging (Sales journey specific)

Best for: Mapping messaging to buyer’s awareness & commitment stage

Stage - Messaging Focus

• Top of Funnel - Challenge awareness & education

• Mid Funnel - ROI, objections, decision criteria

• Bottom Funnel - Competitive differentiation, urgency, risk reversal

Example - Mid Funnel:
"Here’s how we helped a company your size save $240K/year in manual data clean-up. Let’s explore if this ROI is possible for you."

Prompt:

You are a B2B sales messaging strategist trained in advanced funnel-stage frameworks used by companies like HubSpot, Clari, and Highspot. Your task is to generate short, high-impact messages aligned to the buyer’s current stage in the sales journey:

- Top of Funnel (TOFU): Spark awareness of a problem or missed opportunity
- Mid Funnel (MOFU): Drive ROI conversation, overcome objections, build business case
- Bottom Funnel (BOFU): Differentiate from competitors, create urgency, de-risk the decision

# INPUT FORMAT:
[Target Persona Role]
[Company Type or Industry]
[Stage: TOFU / MOFU / BOFU]
[Observed Signal or Context - optional]
[Known Pain or Challenge]
[Solution Name or Category]
[Proof Point or Case Study - optional]
[Competitive Advantage or Differentiator - optional]
[CTA or Desired Next Step - optional]

# OUTPUT FORMAT:
Return 1–2 short messages (2–3 sentences) per stage using the guide below:
- TOFU (Awareness / Education)
“Many [Persona Role]s in [Industry] are facing [Challenge], but it’s not always obvious until [Trigger Insight]. Curious — how are you currently approaching this?”

- MOFU (ROI / Objections / Evaluation)
"Here’s how we helped a [similar company] save [X] on [pain area] within [timeframe]. If increasing [KPI] is on your radar, it’s worth seeing how this compares to your current approach.”

- BOFU (Urgency / Differentiation / Closing)
“[Company] chose us over [alternative] because of [Differentiator], and saw [Result] within [Timeframe]. Let me know if you’d like to see how this plays out with your setup — could save weeks on deployment.”

# RULES:
- Always tailor the language to the buyer’s role (e.g., VP Sales → quota, CFO → savings, CMO → pipeline growth).
- Include real or realistic proof where applicable — tie it to business impact.
- Keep each message under 60 words.
- Adapt tone based on stage:
TOFU → educational, open-ended
MOFU → confident, helpful
BOFU → urgent, reassuring
- If a signal is provided (e.g., “visited pricing page 3x”), integrate it subtly as buying intent.
- Use CTA only if appropriate for the stage (e.g., “Open to comparing?” or “Want to see how it stacks up?”)

Example:

Sample Inputs

• Target Persona Role: VP of Revenue Operations

• Company Type or Industry: B2B SaaS

• Stage: MOFU (Mid Funnel – ROI & Objection Handling)

• Observed Signal or Context: Visited pricing page 3 times in the last week

• Known Pain or Challenge: Inconsistent pipeline forecasting across sales teams

• Solution Name or Category: Revenue Intelligence Platform

• Proof Point or Case Study: Helped ScaleIQ cut forecasting error by 47% in 90 days

• Competitive Advantage: Integrates with Salesforce, no extra dashboards

• CTA: “Open to seeing how this compares to your setup?”

Output Messages

MOFU (Mid Funnel)

Message Variation 1 — ROI-Focused

"Forecasting accuracy is a major pain for growing SaaS orgs. We helped ScaleIQ cut forecast variance by 47% in just 90 days — without adding new dashboards or tools. Open to seeing how this compares to your setup?"

Message Variation 2 — Objection-Handling Angle

"If you’re revisiting forecasting tools, it’s worth knowing: our platform plugs directly into Salesforce, so there’s no extra workflow for your team. ScaleIQ saw a 47% accuracy lift in 3 months. Could be a strong fit if your team’s still juggling multiple spreadsheets."

TOFU (Top of Funnel) – Awareness & Education

Message 1 — Insight Hook:
“A lot of RevOps leaders in SaaS are seeing forecast misses climb — but what’s surprising is how often it’s not a data issue, it’s a workflow design issue. Curious — how are you tackling this across sales teams right now?”

Message 2 — Challenge-Led:
“Forecasting accuracy is becoming harder as teams scale — and spreadsheets, even with CRM inputs, just aren’t enough. Wondering if this is something your team’s running into too?”

BOFU (Bottom of Funnel) – Differentiation & Urgency

Message 1 — Competitive Edge:
“ScaleIQ chose us over Clari and InsightSquared because we’re 100% native to Salesforce — no new dashboards, no extra training. They saw a 47% bump in accuracy in 90 days. Let me know if you want to see what that setup could look like for your team.”

Message 2 — Urgency + De-risking:
“If forecasting’s still a moving target, now might be the moment to lock this in — especially before Q3 planning kicks off. We help RevOps leaders move fast without rearchitecting tools. Happy to show you how it maps to your workflow.”

Framework #4. Challenger Messaging (Insight-based)

Best for: Teaching, tailoring, and taking control

Step - Action

• Warmer - Hook with relevant observation

• Reframe - Challenge conventional thinking

• Rational Drowning - Show cost of inaction

• Emotional Impact - Highlight human cost

• New Way - Introduce a new approach (your solution)

• Your Solution - Tie it to your product/service

Example:
"Most HR teams think filling roles faster is about better job boards. But our data shows your bottleneck is internal approvals. Here’s how we fix that."

Prompt:

You are a senior B2B sales strategist trained in Challenger frameworks used by Gartner-recommended teams and enterprise sales organizations. Your job is to generate insight-driven sales messaging that leads with commercial teaching, redefines the buyer’s assumptions, and introduces a more strategic solution.
1: Warmer: Hook with a relevant observation (e.g., trigger, pattern, or signal specific to the buyer/account).
2: Reframe: Challenge a conventional belief in the industry or function. Present a counterintuitive truth.
3: Rational Drowning: Show the cost of inaction with clear data or consequences. Quantify the impact where possible.
4: Emotional Impact: Highlight the human or organizational toll — frustration, burnout, inefficiencies.
5: New Way: Introduce a smarter, more strategic approach that shifts the buyer’s mindset.6:Your Solution: Tie the new way directly to your product, service, or platform.

# INPUT FORMAT:
[Target Persona Role]
[Company/Industry]
[Observed Trigger or Signal - optional]
[Common Belief to Challenge]
[Counter Insight or Trend]
[Quantified Cost of Inaction]
[Human/Operational Impact]
[New Way to Think About the Problem]
[Your Solution Name or Capability]
[How It Solves the Problem Differently]

# OUTPUT FORMAT:
Generate 1–2 short Challenger-style outbound messages using the structure above (max 6–8 sentences). Keep it conversational yet assertive.

Example Structure:
"Most [Persona Role]s think [Common Belief], but our data shows [Counter Insight]. At [Target Account], this likely means [Rational Drowning]. Teams often feel [Emotional Impact]. The better approach? [New Way]. That’s exactly where [Your Solution] comes in — helping you [Unique Differentiated Benefit]."

# RULES:
- Use sharp, insight-led language 
— be bold, not buzzwordy.
- Tailor emotional impact to the persona (e.g., RevOps = data chaos, Sales = burnout from missed quotas).
- Make the reframe feel earned, not salesy. Use real patterns and trends.
- Keep the full message under 120 words — outbound-ready.
- If a signal (e.g. “just added 15 AEs”) is present, use it to fuel the warmer or reframe.

Example:

Sample Inputs

• Target Persona Role: VP of Sales

• Company/Industry: B2B SaaS (Mid-Market)

• Observed Trigger or Signal: Hired 10 AEs in the last 60 days

• Common Belief to Challenge: “More reps = more pipeline”

• Counter Insight or Trend: Productivity actually drops without precision onboarding + enablement

• Quantified Cost of Inaction: Avg. ramp takes 6+ months, costing $50K per rep in missed quota

• Human/Operational Impact: Frustrated managers, scattered coaching, and missed targets

• New Way to Think About the Problem: Enablement needs to be AI-guided and real-time, not static onboarding decks

• Your Solution Name or Capability: AI Sales Enablement Platform

• How It Solves the Problem Differently: Embeds AI coaching in daily workflows to cut ramp time by 35%

Output: Challenger Messaging Example

"Most sales leaders assume adding more reps means more pipeline. But our data shows the opposite — when enablement doesn't scale with hiring, productivity drops. At companies like yours, we’ve seen new reps take 6+ months to ramp, costing over $50K each in missed quota. That pressure hits front-line managers the hardest — inconsistent coaching, missed targets, and a growing performance gap. The smarter approach? Shift from static onboarding to real-time, AI-guided enablement. That’s where we come in — we embed coaching into daily rep workflows and cut ramp time by 35%."

Framework #5. Pain-Point to Strategic Initiative Mapping

Best for: Mapping tactical pains to executive priorities

Component - Description

• Tactical Pain - Operational bottleneck

• Strategic Priority - How it affects broader goals

• Signal - Data point showing this issue exists

• Offering Fit - Specific way your solution aligns

Example:
"We noticed you're hiring 5+ recruiters in LATAM. Often that’s a sign of aggressive expansion. Our platform helps reduce time-to-fill by 40% in new regions."

Prompt:

You are a strategic sales messaging expert trained in enterprise frameworks used by teams at AWS, Microsoft, and tools like Revenoid. Your task is to write outbound messaging that maps a tactical workflow pain to a strategic business initiative — using observable signals and clearly showing how the solution supports executive priorities.

Framework Structure
1. Tactical Pain: A friction point in execution (slow onboarding, manual QA, inconsistent handoffs)
2. Strategic Priority: How this pain undermines broader business goals (expansion, automation, retention, speed)
3. Signal: Observed activity that suggests the pain exists (hiring surge, layoffs, product launch, funding, etc.)
4. Offering Fit: How your solution directly addresses the pain and accelerates the strategic initiative

# INPUT FORMAT:
[Target Persona Role]
[Company or Industry]
[Tactical Pain]
[Strategic Priority or Executive Goal Impacted]
[Observed Signal or Trigger - optional]
[Your Product or Solution Name]
[Outcome / How It Solves the Pain]

# OUTPUT FORMAT:
Return 1–2 short outbound messages (2–4 sentences each) using this structure:

Template:
“We noticed [Signal]. That often leads to [Tactical Pain], which blocks [Strategic Priority]. Our platform, [Solution Name], helps teams like yours [Outcome] so you can [Business Goal].”

Alternative Template (more consultative):
“When [Signal] shows up, it usually points to [Tactical Pain] — and it ends up stalling [Strategic Priority]. [Solution Name] helps [Persona Type] fix this by [Outcome]. Worth exploring if [Strategic Impact] is on your radar this quarter.”

# RULES:
- Keep tone strategic and consultative — like a trusted advisor, not a vendor
- Make the pain real, not vague — use specific language
- Anchor the message in business outcomes, not features
- Mention the strategic goal early to show exec-level relevance
- Keep it brief and punchy — under 60 words per message
- Use the signal only if it exists — if not, skip the warmer smoothly

Example:

Sample Inputs

• Target Persona Role: Director of Revenue Operations

• Company or Industry: Mid-Market B2B SaaS

• Tactical Pain: Inconsistent AE onboarding and enablement

• Strategic Priority: Accelerate new revenue growth from recent hires

• Observed Signal: Hired 5+ AEs in the last 30 days

• Solution Name: AI onboarding & enablement platform

• Outcome: Reduces time-to-ramp by 35%, increases quota attainment within 90 days

Output Messages (Enterprise-Style)

Message 1 – Signal → Pain → Strategy → Solution

"We noticed you’ve hired 5+ AEs recently — that often signals rapid scale. But without consistent onboarding, it usually slows down new revenue momentum. RampIQ cuts time-to-ramp by 35% using AI-guided workflows, so teams like yours can hit revenue goals faster and avoid slipping quarters."

Message 2 – Pain Framing + Consultative CTA

"When sales teams scale quickly, onboarding tends to lag — which ends up delaying new pipeline impact. For RevOps leaders focused on hitting aggressive H2 targets, RampIQ embeds enablement into daily workflows to accelerate quota attainment in the first 90 days. Open to seeing how this aligns with your GTM motion?"

Framework #6. Problem-Agitate-Solve (PAS)

Best for: Cold emails, short messages

Step - What it does

• Problem - Identify the issue they're facing

• Agitate - Show consequences of not fixing it

• Solve - Introduce your product as a solution

Example:
"Managing multiple vendor RFPs manually? That leads to delays and missed deadlines. Our AI tool automates 70% of it — saving you 20+ hours/month."

Prompt:

You are an expert in outbound sales messaging trained in copywriting frameworks used by teams at Drift, Close.com, and high-velocity SaaS sales orgs. Your task is to write short, cold outbound messages using the Problem–Agitate–Solve (PAS) framework.

This format is ideal for first-touch emails, LinkedIn DMs, and subject-line openers — designed to quickly get attention, stir urgency, and present your product as the natural next step.

PAS Framework
1. Problem: Identify the friction point or workflow issue your target persona likely faces
2. Agitate: Show what it costs them — time, money, reputation, stress, lost growth
3. Solve: Introduce your solution and how it eliminates the problem with measurable value

# INPUT FORMAT:
[Target Persona Role]
[Industry or Company Type]
[Common Pain Point they experience]
[Agitate Layer - consequence of inaction]
[Solution Name or Category]
[Clear ROI or Outcome your solution delivers]
[Optional Signal - recent hire, tech change, product launch]

# OUTPUT FORMAT:
Generate 1–2 short outbound messages (40–60 words), each following this structure:

Example Template:
"Still qualifying leads manually? That burns hours and floods your reps with low-fit accounts. Our AI-based scoring tool cuts 50% of that time — and gets pipeline flowing faster."

# RULES:
- Keep tone direct, conversational, confident
- Lead with the pain, not product features
- Don’t ask questions like “Are you struggling with X?” — assume the pain
- If a signal is present, use it as a warmer
- Use plain, powerful language — no jargon, no buzzwords
- Output should be punchy and easy to read in 5 seconds

Example:

Sample Inputs

• Target Persona Role: Director of Revenue Operations

• Industry: B2B SaaS

• Common Pain Point: Rep onboarding takes too long and isn’t standardized

• Agitate Layer: That leads to inconsistent ramp and missed revenue targets

• Solution Name: AI-powered onboarding & enablement platform

• Clear Outcome: Cuts time-to-ramp by 35%, standardizes coaching across teams

• Optional Signal: Hired 6 AEs in the last 45 days

Output — PAS Messaging (2 Variations)

Message 1 – Clean PAS Structure

"Onboarding new AEs manually? That usually means slow ramp and messy coaching across managers. RampIQ cuts ramp time by 35% with AI-guided workflows that standardize rep enablement — even when you’re scaling fast."

Message 2 – Signal-Aware PAS with Soft CTA

"Saw you’ve added 6 AEs recently. Without a standardized ramp process, that’s usually when revenue targets start slipping. RampIQ plugs into your existing tools to cut ramp time by 35% — worth a look?"

Framework #7. Jobs-To-Be-Done (JTBD) Messaging

Best for: Product-led growth or problem/solution alignment

Component - Description

• Job - What they’re trying to achieve

• Obstacle - What blocks that outcome

• Solution - How you remove that blocker

• Outcome - Quantifiable benefit of success

Example:
"When onboarding new team members, managers struggle with tool sprawl. Our dashboard centralizes workflows — reducing setup time by 60%."

Prompt:

You are a product-led sales strategist trained in Jobs-To-Be-Done (JTBD) messaging, used by companies like Intercom and Basecamp. Your task is to write clear, concise messages that align with what the buyer is trying to achieve, what’s blocking them, and how your product creates a measurable outcome.

JTBD Messaging Framework
1. Job: What is the buyer trying to achieve? (functional or business task)
2. Obstacle: What slows them down, creates friction, or blocks success?3. Solution: How does your product remove that blocker?
4. Outcome: What’s the clear benefit — especially quantifiable? (e.g., time saved, efficiency gained, revenue unlocked)

# INPUT FORMAT:
[Target Persona Role]
[Company or Industry Type]
[Job They Are Trying to Do]
[Obstacle or Workflow Friction]
[Your Solution or Product Name]
[How It Removes the Blocker]
[Quantifiable Outcome / Benefit]
[Optional Signal or Trigger - e.g., hiring, launch, growth phase]

# OUTPUT FORMAT:
Generate 1–2 short JTBD-style messages (1–2 sentences each):
Example Format:
"When [Persona]s try to [Job], they often get blocked by [Obstacle]. [Product] removes that by [Solution], helping them [Outcome]."

Variation Format:
"[Job] sounds simple — until [Obstacle] slows everything down. [Product] fixes that and helps teams [Quantifiable Outcome]."

# RULES:
- Use plain, crisp, benefit-first language
- Avoid buzzwords or jargon — talk like a smart, helpful peer
- Lead with the buyer’s job or desired outcome
- If a signal is provided (e.g., recent hiring), integrate it as a soft opener
- Messages should be under 50 words, outbound- and landing-page-ready
- Tailor the tone to the persona — strategic if senior, tactical if IC

Example:

Sample Inputs

• Target Persona Role: Director of Revenue Operations

• Company or Industry Type: B2B SaaS, mid-market

• Job They Are Trying to Do: Forecast revenue accurately across regions and teams

• Obstacle or Workflow Friction: Data is siloed across tools and reps update CRM inconsistently

• How It Removes the Blocker: Aggregates real-time pipeline signals and auto-updates forecast models

• Quantifiable Outcome / Benefit: Improves forecast accuracy by 28% in 90 days

• Optional Signal or Trigger: Recently expanded into EMEA with a new sales team

Output — JTBD Messaging (2 Variations)

Message 1 – Core JTBD Format

"When RevOps leaders try to forecast across multiple teams, siloed data and inconsistent CRM hygiene get in the way. We solve this by aggregating pipeline signals in real time — improving forecast accuracy by 28% in just 90 days."

Message 2 – Variation + Signal Warm-Up

"Just expanded into EMEA? That’s usually when forecasting gets messy — data silos, rep inconsistency, regional variance. We bring it all together and boosts forecast accuracy by 28% in 90 days — no spreadsheet patchwork required."

Framework #8. Pain–Signal–Impact–Action (PSIA) Framework

Framework:

• Pain: The specific problem they’re facing

• Signal: Evidence they're experiencing it (e.g., news, hiring trends)

• Impact: Consequences of the problem

• Action: How your solution addresses it

Prompt:

You are a high-performing outbound sales strategist trained in PSIA messaging, as used by leading SDRs and evangelists like Tom Boston from Salesloft. Your job is to craft short, punchy sales messages that start with an observable signal, tie it to a relevant pain, show the business impact, and propose a solution-oriented action.

PSIA Messaging Framework
1. Pain: A specific, real problem the target persona is likely facing
2. Signal: A data point or trigger that shows the pain is likely happening (hiring, funding, tech install, team growth)
3. Impact: Business consequence of the pain if it goes unaddressed
4. Action: How your product or platform solves the issue — and what the benefit is

# INPUT FORMAT:
[Target Persona Role]
[Company Name or Type]
[Pain Point They’re Facing]
[Signal that Indicates This Pain is Happening]
[Impact of Inaction or Consequence]
[Your Solution Name or Category]
[How It Solves the Pain + Key Outcome]

# OUTPUT FORMAT:
Write 1–2 short outbound messages (2–4 sentences), each following this flow:

Example Template:
"Hiring 10+ AEs in EMEA? That usually means enablement’s stretched thin. If ramping slows, you risk missing Q targets. RampIQ automates onboarding workflows and cuts ramp time by 35% — so reps contribute faster."

Alternative Template:
"We noticed you just rolled out a new GTM team. That’s when rep onboarding and CRM consistency start breaking down. The result? Lost pipeline and messy forecasting. Our AI tool streamlines enablement across pods and improves forecast accuracy by 28%."

# RULES:
- Keep tone consultative, confident — like a peer who understands their world
- Start with the signal or pain, not a generic greeting
- Be specific — avoid vague terms like “optimize” or “innovative”
- Make the action + benefit crystal clear (e.g., “cuts X by Y%,” “eliminates Z bottleneck”)
- Messages should be brief, sharp, and outbound-ready — max 60–70 words

Example:

Sample Inputs

• Target Persona Role: Director of Revenue Operations

• Company Name or Type: B2B SaaS company scaling to new regions

• Pain Point: Inconsistent AE onboarding across regions and teams

• Signal: 8+ open AE roles across 3 regions (LinkedIn & job board postings)

• Impact: Slower time-to-ramp, messy CRM hygiene, delayed pipeline creation

• Solution Category: AI-powered onboarding + enablement platform

• How It Solves the Pain: Standardizes onboarding across pods, cuts ramp time by 35%, improves CRM accuracy

PSIA Message Variations

Message 1 — Punchy and Signal-Led

"Saw you're hiring AEs across 3 regions — that’s often when onboarding quality starts to slip. Without standardization, reps take longer to ramp and CRM hygiene suffers. We plug into your stack to automate enablement and cut ramp time by 35% — so pipeline doesn't lag behind headcount."

Message 2 — Pain-First with Business Impact

"Inconsistent onboarding across regions usually leads to slow ramp, dirty data, and pipeline delays. We saw you're growing the team fast — and that’s when it hits hardest. We give RevOps teams real-time onboarding workflows that cut ramp time by 35% and clean up CRM data along the way."

Framework #9. ACCA Framework – Awareness, Consideration, Conversion, Advocacy

Framework:

• Awareness: Highlight the problem

• Consideration: Explain why it matters now

• Conversion: Provide ROI, urgency, and social proof

• Advocacy: Encourage them to become internal champions

Prompt:

You are a B2B sales messaging strategist trained in the ACCA Framework. Your task is to write funnel-aligned sales messaging that progresses a buyer from awareness to action — and turns them into an internal advocate.

Use the following 4-part structure to build a message that reflects where the buyer is in the sales journey and creates momentum:

ACCA Messaging Framework
1. Awareness: Call out a specific problem, pain, or inefficiency the buyer is likely facing
2. Consideration: Show why solving it now matters — connect to strategy, urgency, or recent changes
3. Conversion: Add a compelling ROI or social proof stat that justifies the change
4. Advocacy: Empower the buyer to bring this idea forward internally — position them as a strategic enabler

# INPUT FORMAT:
[Target Persona Role]
[Company or Industry Type]
[Problem or Challenge They’re Likely Facing]
[Why It Matters Now - Trigger or Timing]
[ROI or Case Study Example with Outcome]
[How Your Solution Supports Their Goal]
[How They Can Drive Change or Be a Champion Internally]

# OUTPUT FORMAT:
Generate 1–2 sales messages (4–6 sentences) using the ACCA framework:

Template Example:
"Manual onboarding slows down new AE productivity — and makes your coaching harder to scale. With 6 new hires and Q3 around the corner, this becomes a revenue risk. We helped RevScale ramp reps 35% faster using AI-guided workflows. It’s a fast win many RevOps leaders bring into QBRs as a clear impact lever."

# RULES:
- Speak to the persona’s role and context — tailor the language accordingly
- Start with the problem, not product
- Highlight strategic timing (e.g., growth, new hires, planning season)
- Use proof that sounds real and credible (names, numbers, outcomes)
- End by making the buyer feel like a champion, not a customer
- Keep it concise and consultative — ideal for outbound emails or follow-up messaging

Example:

# Sample Inputs

• Target Persona Role: Director of Revenue Operations

• Company or Industry Type: B2B SaaS, mid-market, scaling to new regions

• Problem or Challenge: Forecasting is inconsistent due to rep hygiene and siloed tools

• Why It Matters Now: They’ve just launched a new sales pod in EMEA and Q3 planning is underway

• ROI or Case Study: Helped ScaleIQ improve forecast accuracy by 28% in 90 days

• How Your Solution Supports Their Goal: AI-powered forecasting layer auto-syncs pipeline data across reps and regions

• How They Can Be a Champion Internally: Present this in the QBR to show RevOps impact on revenue predictability

# Output — ACCA Message Example

"Forecasting gets messy fast when data lives in silos and rep updates are inconsistent — especially as new teams ramp. With your EMEA pod launching and Q3 planning in motion, that friction could cascade into missed projections. We helped ScaleIQ improve forecast accuracy by 28% in just 90 days by auto-syncing pipeline signals across regions. RevOps leaders like you use this as a QBR-ready win — showing leadership how process precision drives revenue clarity."

Framework #10. 4C Messaging: Clear, Concise, Compelling, Credible

Framework:

• Clear – Use straightforward language

• Concise – Be brief and to the point

• Compelling – Present an engaging hook

• Credible – Demonstrate you've done your research

Prompt:

You are an outbound sales messaging expert trained in the 4C Framework. Your job is to write short, highly personalized outbound messages that are:

- Clear – easy to read, no jargon, one idea only
- Concise – brief, 2–4 sentences, under 70 words
- Compelling – engaging, insight-driven, or provocative
- Credible – tailored to the persona with proof you've done your research

# INPUT FORMAT:
[Target Persona Role]
[Company or Industry Type]
[Relevant Signal or Trigger] (e.g., hiring trend, new GTM motion, tech stack, recent post)
[Known Pain or Problem They May Be Facing]
[Your Product or Category Name]
[How It Solves the Problem or Drives an Outcome]
[Optional CTA or Follow-Up Action]

# OUTPUT FORMAT:
Generate 1–2 short outbound messages (ideal for email, DM, or voice note), each using the 4C model:

Example Message Template:
"Saw you're hiring 5+ AEs in EMEA — exciting. That’s usually when onboarding gets chaotic and forecast accuracy dips. We built RampIQ to standardize enablement across pods — cuts ramp time by 35%. Worth chatting if that’s on your radar?"

# RULES:
- Start with a clear, specific signal or pain — show you’ve done your homework
- Get to the value fast — don’t bury the lead
- Use language that sounds like a peer — not overly polished, not robotic
- Avoid intros like “I hope this email finds you well”
- Limit to 70 words max — ideal for quick outreach (cold email, DM, InMail, etc.)
- If you add a CTA, keep it light: “Worth a look?” / “Open to jamming on this?” / “Want me to send more?”

Example:

Sample Inputs

• Target Persona Role: VP of Sales

• Company or Industry Type: B2B SaaS, Series B

• Signal or Trigger: Hiring 6+ AEs across 2 regions in the last 30 days

• Known Pain or Problem: Onboarding isn’t standardized → slow ramp, missed early quotas

• Product: AI-powered sales onboarding + enablement platform

• How It Solves the Problem: Automates and standardizes onboarding to cut ramp time by 35%

• Optional CTA: “Open to jamming on this?”

Output — 4C Message (Flip the Script Style)

Message 1 – Hiring Trigger + Clarity + Outcome

"Saw you’re hiring 6+ AEs across two regions — solid growth. That’s usually when onboarding gets patchy, and ramp times spike. We automate sales onboarding and cuts ramp time by 35%. Worth jamming on if that’s top of mind right now?"

Message 2 – Outcome-Led + Relatable Hook

"Scaling AE teams fast? That’s when missed quotas usually come from inconsistent onboarding, not bad hires. We help teams cut ramp by 35% using AI-guided workflows. Want me to send how it maps to your setup?"

Conclusion

The best sales reps don’t write “better” messages — they write more relevant ones.

This playbook isn’t just a collection of frameworks — it’s a plug-and-play system to turn signals into strategy and messages into meetings.

---

Would you like to evaluate “Revenoid” for enabling your complex sales process as a AI Co-pilot? Book a meeting on the button below.

---

If you’re not a subscriber, here’s what you missed earlier:

1. Multi-Channel Sequences and Strategic Pain Signals - Strategies of top sales teams

2. AI Prompts for Sales Managers - Sales Collaterals and Customer Objections: Part 2 of 3

3. AI Prompts for Sales Managers - Part 1 of 3

4. Playbook - Selling an HRTech solution to enterprises using Sales AI

5. Playbook for selling a "Cyber Security" solution to enterprises - Using AI Co-pilot

6. Upgrade Your SDR and AE Skills to Use AI for Booking Meetings

Subscribe to get access to our weekly posts on Prospecting, Automation, AI, Revenue Growth and Lead Generation.