Methodology · 11 min read · Updated May 2026
Off-brand sends. No governance layer. Inconsistent messaging at multi-rep scale. Three real management problems, one written framework. Steal it, edit it, ship it on Monday.
I am the founder of Prsona, which sells brand-voice rule enforcement as a feature. The framework below is the artifact, not the pitch — the seventeen rules work whether you encode them in software or in a Notion doc. The pitch only matters after a team has actually written rules of their own.
Most articles on brand voice open with “here are seventeen rules.” That gets the order wrong. The rules are the resolver; the problems are why a sales manager is reading at all. So before the rules: the three real management problems this framework exists to fix.
SDRs ramp at different speeds. Within six months a single team is sending five different versions of the same value prop, in five different tones, signed off five different ways. The director of sales cannot watch every email. The inconsistency compounds quietly because every individual send looks fine in isolation; only the aggregate exposes the drift. By the time somebody pulls a sample and lays the emails side by side, the team has been sending five voices for a quarter and the brand has lost shape on its own outbound channel.
Most sales orgs have brand guidelines on the marketing side and zero enforcement on the sales side. The CMO controls how the company sounds in advertising, on the website, in webinar decks. The VP of Sales has no equivalent control over how reps sound in cold email — the highest-volume channel by which the brand reaches new prospects. There is nowhere to write the rules. Nowhere to enforce them. Nowhere to audit drift. The governance layer that exists for paid media simply does not exist for outbound.
A prospect at a target account receives three emails in two weeks from three different reps, with three different framings of why your product matters. Internally this looks like coverage — three reps doing their jobs. Externally it reads as a team that does not know what it is selling. The prospect's honest read is that the company's pitch is unclear, and the prospect's honest reaction is to archive all three emails. ABM motions amplify this problem; the more reps work the same account, the more the inconsistency hurts.
The 17-Rule Framework is the resolver. Rules written once at the org level. Every rep's drafts follow them. No exceptions. No drift over time. The rest of this article lays out all seventeen rules with examples of what each one prevents.
Each rule comes with three things: the rule itself, a short reasoning paragraph, and a bad-versus-good example so the shape of the violation is visible. Steal the rules verbatim if they fit; edit any of them if your team operates differently. The exact contents matter less than the fact that they are written down somewhere reps can reference.
Three words that signal “automated outbound” to anyone who has worked in B2B for more than a year. Prospects archive on sight. The opener wastes the slot where a real signal would land.
Filler verbs that mean nothing and read as corporate boilerplate. They tell the prospect you are following a script. They also tell the prospect there is no actual reason for the email; you are just checking in because the cadence said to.
Last names plus titles plus phone numbers plus calendar links plus social links plus signature graphics signal corporate-template. First-name-only signals human. Trust the prospect to find your last name in the email address if they need it.
Mobile inbox previews truncate at roughly 35-40 characters. Subjects above six words get cut off. The cut-off version often reads worse than the original — sometimes worse enough that the prospect deletes without opening.
Cold emails over 100 words get scrolled past. The discipline of writing under 90 words forces the rep to remove the throat-clearing paragraph, the company-history paragraph, and the “here are five reasons we might be helpful” bullet list. What remains is usually the email the prospect would have replied to anyway.
The first sentence is the highest-attention real estate in the email. Burning it on a product description tells the prospect this email is about you. Burning it on a specific signal — funding round, hiring page, recent post, public role change — tells the prospect this email is about them.
Unsolicited competitor namedrops in cold email read as desperate. The prospect did not ask. The prospect did not signal interest in the category. Mentioning Outreach or Apollo in a first-touch email signals “I am trying to displace your existing tool” before any conversation has happened.
Two questions in one email is the fastest way to get zero replies. The prospect reads both, runs the cognitive cost of answering both, decides it is too much work, and moves on. One question — answered yes or no in five words — converts. Two questions wait for “a free moment to think,” which never comes.
Exclamation points in cold email read as performed enthusiasm. They lower trust. Sales-y email looks sales-y; calm email looks like a peer reaching out. The exclamation point is a tell that the writer is trying too hard.
Three words from the corporate-thesaurus list that signal the email was written by someone trying to sound more impressive than they are. Replace with simple verbs: use, combine, enable. The simpler verb is always more credible.
Specificity is the proof-of-research. A reference older than 30 days reads as “I scraped your LinkedIn profile.” A reference from the last 30 days reads as “I actually paid attention.” The 30-day window is tight enough to be honest signal and wide enough to be findable.
Em-dashes in subject lines render inconsistently across email clients — sometimes as the dash, sometimes as a question mark, sometimes as a literal “—” encoded badly. The risk is asymmetric: nothing is gained, occasional bad rendering is lost. Use a hyphen or a colon instead.
Both phrases are the canonical AI-cold-email tell. Prospects who have received fifty AI cold emails this month archive on the second-sentence pattern alone. Drop the throat-clearing transition and write the actual signal directly.
“Worth a chat?” pushes the cognitive cost back to the prospect — the prospect now has to decide if it is worth chatting, what time, what platform, what agenda. A specific CTA collapses all four decisions: a 15-minute call, Tuesday at 10 AM PT, here is a calendar link if useful, otherwise reply with a different time.
“Sorry to bother you” and “apologies for the cold outreach” lower the rep's authority before the email has earned anything. The rep is not bothering the prospect. The email is either useful or it is not; if it is useful, no apology is needed; if it is not useful, the apology does not save it.
Funding rounds are searchable in fifteen seconds. Opening with “congrats on the Series B” is the laziest research tell in the genre. Reference the funding only if the email payload depends on it; otherwise pick a different signal that took more than fifteen seconds to find.
The permission line lowers the cost of not replying. Prospects who feel guilty for not replying often reply with a polite no — which is fine, but the rep has burned a future cycle. Prospects who feel permitted to ignore often archive cleanly, which preserves the rep's next attempt at the same account three months later.
Writing the rules is the easy half. Enforcement is the harder half. Three options, ranked by what actually holds up at multi-rep scale.
The director of sales or RevOps configures the rules once in a tool that runs on every rep's drafts before the rep clicks send. Drafts that violate rules get rewritten automatically or flagged for review. New SDRs hired on Monday are sending on-brand cold email Monday afternoon — ramp time on voice goes from weeks to zero. This is what brand voice control is built to do, layered on top of per-rep conversation hooks so the house voice and the personal hook do not fight.
The SDR manager pulls a sample of every rep's last twenty sends each week and audits against the rule list. Violations get coached on Friday. This works for teams of three to five reps; it breaks at ten reps because the manager runs out of time. The signal-to-cost ratio degrades as the team scales.
Most sales orgs are here. The rules exist; the rules live in a Notion doc; the doc was last updated nine months ago; reps skim it during onboarding and forget it by week two. Better than nothing — at least new hires see the document. Worse than enforcement — drift continues unchecked because nothing actually checks the drafts against the rules.
Three things the framework intentionally leaves out, because every team has to fill these in for itself:
The framework looks like a consistency tool. It is also an onboarding leverage tool, which is the part most sales managers underestimate. When the rules are encoded once, time-to-first-good-email for new hires drops from two-to-four weeks to Monday afternoon. The new SDR does not have to learn what good cold email looks like at this specific company by osmosis over six weeks of failed sends and manager corrections. The rules tell them. The software runs the rules against their drafts. They send on-brand from day one.
That ramp-time effect is large enough to deserve its own article — coming in Month 2. In the meantime, the implementation lives on the brand voice control feature page; the broader sales-team buying motion lives on the sales leaders solutions page and the sales development solutions page.
Adjacent reading: the cold email reply rate collapse manifesto walks through the underlying market shift this framework responds to; the email outreach software 2026 buyer's guide compares the tools that can encode rules like these; the personalization at scale note covers how brand voice and per-prospect signal layer together without fighting.
A brand voice framework is a written set of rules governing how every rep on a sales team writes outbound email — what they say, how they open, how they close, what words they avoid, and how they format the ask. The framework lives at the org level rather than the rep level. Without a framework, voice is implicit and drifts as reps ramp at different speeds; with a framework, voice is explicit and every draft is auditable against the same standard.
Three structural reasons. SDRs ramp at different speeds, so within six months the same value prop is being sent five different ways across a five-person team. Sales orgs typically have brand guidelines on the marketing side but no governance layer on the sales side — the CMO controls advertising voice; nobody owns cold-email voice. And cold email scales fast enough that drift compounds before anyone notices: a prospect at a target account receives three emails in two weeks from three different reps with three different framings, and the team looks unfocused.
Long enough to be specific, short enough to be enforceable. The framework in this article is seventeen rules. That is a deliberate ceiling. Above twenty rules the framework becomes unreadable and reps start ignoring the bottom half. Below ten rules the framework is too vague to govern actual drafts. The seventeen-rule shape is the minimum count that covers opening, body, ask, sign-off, and prohibited language without overflowing what a new SDR can absorb in their first week.
In well-run teams, the director of sales or RevOps writes the rules, the VP of Sales approves them, and the SDR manager enforces them in coaching. Marketing should be consulted to keep the sales voice aligned with brand voice on the marketing side, but marketing should not own the cold-email rules — they will optimize for the wrong audience. The owner is whoever is accountable for cold email reply rates.
Three options ranked by effectiveness. Best: encode the rules in software that runs on every rep's drafts before the rep clicks send — drafts that violate rules get rewritten or flagged automatically. Middle: weekly draft audits where the manager reviews a sample of every rep's last twenty sends against the rule list and coaches on violations. Worst: a Notion doc that nobody reads. The first option is what the brand-voice-control feature in modern AI sales tools provides.
Materially. Most SDR ramp is the rep learning what good cold email looks like at this specific company — the tone, the words to avoid, the cadence the team has converged on. Without a written framework, that learning happens by osmosis over four to six weeks of failed sends and manager corrections. With a written framework that is enforced in software, a new SDR hired Monday morning can be sending on-brand emails Monday afternoon. Time-to-first-good-email drops from weeks to hours.
No. Brand voice is the consistent house style every rep operates inside. Personalization is the per-prospect signal each rep adds within the house style. The two layers are complementary: brand voice controls how the email reads; personalization controls what the email is about. A draft can be heavily personalized and still off-brand, or perfectly on-brand and entirely generic. Both layers need to work.
About the author
Dalton is the founder of Prsona. Eight-plus years across B2B sales, operations, client onboarding, and digital marketing — currently working in operations at a US-based agency. He wrote the seventeen-rule framework because he kept seeing teams generate consistent cold email for one rep and inconsistent cold email for five. Read the about page or follow Prsona on LinkedIn.
Brand voice control is configured by the director of sales or RevOps once at the org level. New SDRs hired Monday morning are sending on-brand cold email Monday afternoon. Free Solo plan, 10 lifetime credits, no card.
We read every message. If something in this guide raised a question, we'll answer it.
Prefer the full form? Visit /contact →