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 as an AI Tool

Don't just copy prompts. Turn this into a real, monetizable AI application with Appaca. No coding required.

Start Building Free

Or Quick Run In

Related Topics

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

All you need to launch your AI products and start making money today

Appaca provides out-of-the-box solutions your AI apps need.

Monetize your AI

Sell your AI agents and tools as a complete product with subscription and AI credits billing. Generate revenue for your busienss.

Monetize your AI

Trusted by incredible people at

AntlerNurtureEduBuddyAgentus AIAona AICloudTRACKMaxxlifeMake Infographic
AntlerNurtureEduBuddyAgentus AIAona AICloudTRACKMaxxlifeMake Infographic
AntlerNurtureEduBuddyAgentus AIAona AICloudTRACKMaxxlifeMake Infographic
AntlerNurtureEduBuddyAgentus AIAona AICloudTRACKMaxxlifeMake Infographic

Frequently Asked Questions

We are here to help!

What is Appaca?
Appaca is a no-code platform for creating end-user AI agents and tools that you can monetize. It allows you to deliver AI solutions to your customers faster without requiring developer help.
What are AI Credits?
AI credits are the currency to bill AI usage. Appaca uses that AI credit for the usage of different large language models (LLMs). You can use any LLM from different providers. For the cost of AI credit for different AI models, please see our pricing page.
Can I make money with the app I built on Appaca?
Yes, you can monetize your AI app easily. All you need to do is to enable monetization in your app with one click. You will be prompted to set up Stripe account easily. Once you have enabled your monetization, you can create subscription plans for your app. For the usage of AI, our AI credit system allows you to bill your customers. You can simply set how much credit you want to charge for your customers. It all comes out of the box.
Can I get more credits?
Absolutely. You can top up AI credits as much as you want if your credits are low.
Can I connect my custom domain to my app?
Yes, you can use your own custom domain name as long as you are on any paid plan.
Are there integrations?
Yes. You can integrate with other third-party tools via API or Webhook in your action workflows builder. We are frequently shipping native integration as well.
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.