Mun Bock Ho•September 23, 2026•

Modular Prompt Snippets for Better Sales Prompts

Write better sales prompts by using sales prompt snippets for output formats, constraints and rules that keep replies consistent across reps, tools and campaigns.

Try to maintain the style of your sales copy? Use the prompt snippets below to keep your sales prompts with the consistent outputs.

Note

Snippets below follow the naming rule as topic.family.job. View the naming rule.

Sales Output Formats Snippets

These snippets lock structure so a reply can move from chat into CRM, email, or a deck without a rewrite.

1. {{snippet:sales.format.email_sequence}}

A three-touch outbound sequence with subject, body, and send-timing notes. Use when the model must produce copy a SDR can load into a sequencer.

Snippet	Value
sales.format.email_sequence	Return exactly 3 emails labeled Touch 1, Touch 2, Touch 3. For each touch output: Subject (max 7 words), Preview text (max 12 words), Body (80–140 words), CTA (one sentence), Send window (day + time band). Separate touches with a horizontal rule. Do not add a fourth email or a summary.

2. {{snippet:sales.format.discovery_notes}}

Turns a call transcript or raw notes into a CRM-ready discovery record. Use after discovery, demos, or inbound qualification calls.

Snippet	Value
sales.format.discovery_notes	Output these headings in this order: Account, Contacts, Stated goal, Current stack, Pain (ranked), Impact (revenue, cost, risk, time), Decision process, Timeline, Budget signal, Competitors named, Risks / blockers, Next step owner + date. Use bullets. Quote the prospect when a claim is attributed. Mark unknown fields as `Unknown — ask next`.

3. {{snippet:sales.format.objection_table}}

A compact objection-handling matrix. Use when a rep needs talk tracks that stay consistent across the team.

Snippet	Value
sales.format.objection_table	Produce a markdown table with columns: Objection, Likely cause, Clarify question, Proof to offer, Fallback close. One row per objection. Keep each cell to 25 words or fewer. No extra commentary above or below the table.

4. {{snippet:sales.format.proposal_outline}}

A buyer-facing proposal skeleton. Use before a commercial draft so pricing and scope stay attached to outcomes.

Snippet	Value
sales.format.proposal_outline	Output: 1) One-sentence problem, 2) Desired outcome in 90 days, 3) Scope (In / Out), 4) Approach in 4 numbered steps, 5) Success metrics, 6) Commercial options (Good / Better / Best) with what changes at each tier, 7) Assumptions, 8) Risks and how they are owned, 9) Ask. Do not invent prices. Leave price cells as `[PRICE]`.

Note

You can find out more snippets at Library.

Sales Constraint Snippets

Constraints shrink the search space. They stop the model from writing marketing copy when the job is a sales artifact.

1. {{snippet:sales.constraint.tone_guard}}

Keeps voice peer-to-peer and specific. Use on any outbound or follow-up draft.

Snippet	Value
sales.constraint.tone_guard	Write as a senior seller talking to a busy peer. Short sentences. Concrete nouns. No slogans, no exclamation marks, no “excited to”, “just circling back”, “hope this finds you well”, or “synergy”. Prefer “you / your team” over “we / our platform”. If a claim needs proof and none is provided, write the claim as a question instead.

2. {{snippet:sales.constraint.length_budget}}

Forces usable length for the channel. Use when Slack, email, and LinkedIn share the same base prompt.

Snippet	Value
sales.constraint.length_budget	Honor the channel cap: email body 80–140 words; LinkedIn message 50–80 words; Slack / Teams note 40–60 words; talk track 20–35 seconds when read aloud. If the user does not name a channel, default to email. Cut adjectives before cutting facts.

3. {{snippet:sales.constraint.no_hype}}

Blocks unearned claims. Use on product-led or competitive prompts.

Snippet	Value
sales.constraint.no_hype	Do not use: world-class, cutting-edge, game-changer, 10x, guaranteed, only platform, category-defining, AI-powered as a virtue word. Do not invent logos, win rates, ROI, case studies, or features. If a number is required and missing from context, output `[NEED DATA: what number and from whom]`.

4. {{snippet:sales.constraint.data_only}}

Restricts the model to supplied facts plus labeled gaps. Use for forecast notes, MEDDPICC fills, and legal-sensitive accounts.

Snippet	Value
sales.constraint.data_only	Use only facts present in the user input. Do not infer budget, authority, or close date. Every inference must be tagged `Hypothesis` and paired with the question that would confirm it. If input is thinner than 5 facts, return a gap list instead of a narrative.

Sales Rule Snippets

Rules tell the model how to decide, not just how to write. They are the difference between a draft and a sales system.

1. {{snippet:sales.rule.qualification_gate}}

Stops the model from pitching unqualified accounts. Use at the top of outbound and inbound reply prompts.

Snippet	Value
sales.rule.qualification_gate	Score Fit, Pain, Timing, Access on 0–2 each. If total < 4, do not write a pitch. Write: score table, missing proof, and the single next question that would raise the lowest score. If total ≥ 4, write the requested sales asset and keep the score table above it.

2. {{snippet:sales.rule.revision_pass}}

A second-pass editor the model must run on its own draft. Use on customer-facing text.

Snippet	Value
sales.rule.revision_pass	After the draft, run this checklist silently and return only the revised version plus a 4-line change log: 1) Remove any claim without a source in context. 2) Replace weak verbs (help, enable, empower) with the buyer action. 3) Put the ask in the last sentence. 4) Confirm the first line names the buyer’s problem, not the product. Change log format: `Cut / Swapped / Moved / Unchanged`.

3. {{snippet:sales.rule.cta_priority}}

Chooses the smallest honest next step. Use on emails, voicemails, and meeting recaps.

Snippet	Value
sales.rule.cta_priority	Pick one CTA using this order: 1) confirm a fact the buyer already offered, 2) book a working session with a named owner, 3) send a scoped artifact by a date, 4) intro to a missing stakeholder, 5) permission to follow up on a dated trigger. Never stack CTAs. Never use “let me know if you have questions”. Name the day, duration, and owner in the CTA.

4. {{snippet:sales.rule.evidence_first}}

Requires proof before persuasion. Use on competitive swaps, pricing defense, and late-stage recaps.

Snippet	Value
sales.rule.evidence_first	Structure every persuasive block as: Evidence -> Implication for this account -> Ask. Evidence must be a named customer pattern, a metric from context, or a product behavior the user supplied. If evidence is missing, skip persuasion and output the discovery question that would produce it. Do not lead with product categories or feature lists.

Prompt with The Use of Sales Snippets

Example of a sales prompt that stacked with 3 variables and 5 snippets.

Prompt Template

CONTEXT:
Buyer: {{audience}}
Channel: Email
Product: {{product}}
Goal: {{goal}}
Task: Write the email sequence for the buyer and goal.

OUTPUT FORMAT:
- {{snippet:sales.format.email_sequence}}

CONSTRAINTS:
- {{snippet:sales.constraint.tone_guard}}
- {{snippet:sales.constraint.length_budget}}
- {{snippet:sales.constraint.no_hype}}
- {{snippet:prompt.constraint.filled_fields_only}}

In this example, we used prompt.constraint.filled_fields_only which is a general snippet for any topics.

Snippet	Value
prompt.constraint.filled_fields_only	Use a field only if it has a value. Ignore empty fields. Do not invent substitutes.

Prompt Example

CONTEXT:
Buyer: AI Creator
Channel: Email
Product: Acluebox
Goal: Drive signups to Acluebox with a 50% off promo code for their first 3 months to monetize their AI prompts.
Task: Write the email sequence for the buyer and goal.

OUTPUT FORMAT:
- Return exactly 3 emails labeled Touch 1, Touch 2, Touch 3. For each touch output: Subject (max 7 words), Preview text (max 12 words), Body (80–140 words), CTA (one sentence), Send window (day + time band). Separate touches with a horizontal rule. Do not add a fourth email or a summary.

CONSTRAINTS:
- Write as a senior seller talking to a busy peer. Short sentences. Concrete nouns. No slogans, no exclamation marks, no “excited to”, “just circling back”, “hope this finds you well”, or “synergy”. Prefer “you / your team” over “we / our platform”. If a claim needs proof and none is provided, write the claim as a question instead.
- Honor the channel cap: email body 80–140 words; LinkedIn message 50–80 words; Slack / Teams note 40–60 words; talk track 20–35 seconds when read aloud. If the user does not name a channel, default to email. Cut adjectives before cutting facts.
- Do not use: world-class, cutting-edge, game-changer, 10x, guaranteed, only platform, category-defining, AI-powered as a virtue word. Do not invent logos, win rates, ROI, case studies, or features. If a number is required and missing from context, output `[NEED DATA: what number and from whom]`.
- Use a field only if it has a value. Ignore empty fields. Do not invent substitutes.

Tip

Use Acluebox to manage your snippets and variables.