Build AI powered apps for your work

Get started free
Back to Business
Businesssales

Sales Language Style Guide

Generate a sales language style guide so your team writes consistent outreach with approved phrases, tone rules, and examples.

The Prompt

You are a sales enablement lead and brand copy editor. Your job is to create a **Sales Language Style Guide** that makes outreach consistent, clear, and on-brand across SDRs, AEs, founders, and partners.

## Your Task
Create a **one-page style guide** for sales messaging: email, LinkedIn, and call notes.

## Inputs
- **Brand voice (3–5 adjectives):** {{voiceAdjectives}}
- **Audience / ICP:** {{audience}}
- **Offer & positioning:** {{positioning}}
- **Common objections:** {{objections}}
- **Words/phrases to avoid:** {{avoid}}
- **Approved proof types:** {{proofTypes}} (metrics, customer names, industries, etc.)
- **CTA preference:** {{ctaPreference}} (reply, short call, send case study, etc.)

## Guide Requirements
Include all sections below, using bullet lists and short examples.

### 1) Voice & Tone Rules (Do/Don’t)
- Do: ...
- Don’t: ...

### 2) Message Principles (5 max)
- Example: “Be specific over clever.”

### 3) Approved Vocabulary
Provide:
- **Preferred phrases** (10–15)
- **Swap list** (“Instead of X, say Y”)
- **Outcome > Feature translation table** (at least 6 rows)

### 4) Personalization Rules
- What counts as “real personalization”
- What to never pretend (avoid fake familiarity)
- How to reference research in 1 sentence

### 5) Proof & Credibility Rules
- How to use numbers safely (no invented metrics)
- How to phrase proof when you can’t name customers

### 6) CTA Library (10 options)
Grouped by channel: Email / LinkedIn / Call

### 7) Objection Language
For each objection in {{objections}}, provide:
- Bad response (what NOT to say)
- Better response (what to say)
- 1 follow-up question

### 8) Examples (Before/After)
Provide 3 quick “before/after” rewrites:
- Generic → Specific
- Feature-led → Outcome-led
- Pushy → Collaborative

## Output Format
Return a single, clean guide with headings and bullets. Keep it copy/paste-ready into a Notion page.

Now generate the Sales Language Style Guide.

Variables to Customize

{{voiceAdjectives}}

How the brand should sound

Example: Direct, warm, pragmatic, confident

{{audience}}

Who you sell to

Example: CFOs at 200–1000 employee manufacturing companies

{{positioning}}

Your offer and differentiation in one short paragraph

Example: We provide a spend visibility platform that automates vendor consolidation and reduces month-end close chaos without replacing the ERP.

{{objections}}

Common objections you hear (list)

Example: “We already have a tool”, “No budget”, “Not a priority this quarter”, “Send info”

{{avoid}}

Words/phrases your team should not use

Example: synergy, disrupt, world-class, best-in-class, game-changer, “just checking in”

{{proofTypes}}

What proof you can use safely

Example: benchmarks, anonymized metrics, industry examples, process proof

{{ctaPreference}}

Preferred CTA type for your outreach motion

Example: Low-friction reply CTA first, then 15-minute call

Example Output

### 1) Voice & Tone Rules (Do/Don’t)
- Do: Sound like a peer; short sentences; name the tradeoff.
- Don’t: Overpromise; use buzzwords; guilt the prospect.

### 2) Message Principles
- Be specific over clever.
- One idea per message.
- Outcome first, then “how”.

Pro Tips

  • 1Treat this guide as your “single source of truth” for SDR onboarding and QA reviews.
  • 2Update the guide every 4–6 weeks based on what actually gets replies.
  • 3Add real customer language by copying phrases from call transcripts and reviews.

Build this into your own tool

Stop running this prompt manually. Appaca turns it into a dedicated app you can reuse, share with your team, and access from anywhere — free to start.

Build it on Appaca →

Related Topics

sales style guide promptsales messaging guidesales enablement promptoutreach tone guidesales copywriting prompt

Frequently Asked Questions

How do I keep a sales team’s writing consistent?

Create a short style guide, enforce it with weekly QA reviews, and provide swap lists + examples. Consistency comes from constraints and shared templates.

Turn this into your own app

Instead of running this prompt every time, build a personal business tool on Appaca. Describe what you need - your app is ready in minutes.

Build it on Appaca - free