B2B messaging by segment: one market, five different pitches
What changes when five different people sit in the same deal, which roles deserve their own pitch and how to check that each one is actually landing.
ON THIS PAGE · 8 SECTIONS
THE SHORT VERSION
- B2B messaging by segment means writing a different pitch for each role in the buying group, not one email you send to everyone with the title swapped out.
- A typical complex B2B deal involves 6 to 10 decision makers. Forrester puts the average closer to 13. One pitch cannot carry that many different reasons to care.
- Five segments cover most deals: the economic buyer, the champion, the technical evaluator, the end user and the blocker. Each one needs a different pain, a different proof and a different ask.
- Start with two or three segments you can write well, not five you write badly. A clear pitch for three roles beats a vague one for five.
- Check reply rates by segment, not in aggregate. A campaign that looks fine overall can be hiding one role that never replies at all.
B2B messaging by segment means the economic buyer, the champion and the person who will actually use what you sell each get a pitch built around what they personally stand to gain or lose, not a single email with the first name and company swapped in. The point is not more words. It is the right ten words for each reader, because the CFO and the sales rep underneath them are solving different problems even when they work at the same company and will sign off on the same deal.
This piece covers why one pitch stops working once more than two or three people touch a deal, the five segments that cover most B2B buying groups, how to build a pitch for each one without rewriting your whole message from scratch and where segmentation stops paying for the extra work it takes.
What messaging by segment actually means
Segmenting your messaging means grouping your prospects by something that changes what convinces them, then writing to that difference on purpose. That grouping is not always company size or industry, though those matter too. Inside a single deal, the grouping that matters most is often role: what this person loses if the deal goes wrong, what they get credit for if it goes right and what kind of proof actually moves them.
A VP of sales wants pipeline and will read a short email about a specific signal on one of their accounts. A RevOps lead wants to know it will not break their stack and will read three paragraphs about integration before they read your offer. Send the RevOps version to the VP and you lose them in line two. Send the VP version to RevOps and you sound like you have nothing concrete to say. Same deal, same company, two different emails.
Why one pitch fails a crowded deal
Deals used to close with one or two people in the room. That is not the deal size most B2B teams are selling into anymore. Gartner's research puts the typical buying group for a complex B2B purchase at 6 to 10 decision makers, each doing their own research before anyone talks to a supplier. Forrester's 2024 State of Business Buying report puts the average even higher, at 13 stakeholders across a purchase.
Source: TractionComplete, 2026
Write one message for a group that size and you are optimising for the average reader, which means you are optimising for nobody in particular. The champion who would push the deal forward does not feel understood. The blocker who could kill it does not get the one line that would have put them at ease. You end up with a pitch that nobody hates and nobody forwards either.
THE USUAL WAY
- One template, personalised with a name, a company and maybe an industry line.
- The same proof point and the same call to action for every role on the thread.
- Reply rate measured across the whole list, so one role's silence hides inside the average.
THE SYSTEM WAY
- A short list of segments, each with its own pain, proof and ask.
- The offer stays the same. The reason to care about it changes by role.
- Reply rate tracked per segment, so a dead role gets fixed instead of averaged away.
The five segments worth splitting by
You do not need twenty personas. Most B2B buying groups collapse into five roles and each one responds to a different kind of message. Once you have mapped the accounts worth pursuing, this is the next layer down, mapping the people inside each account the same way.
| Role | What they actually worry about | Proof that lands | Ask that works |
|---|---|---|---|
| Economic buyer | Budget risk and whether this ranks above other priorities this quarter | A number: cost, time saved or a comparable outcome from a similar company size | A short call to confirm priority and timeline, not a demo |
| Champion | Looking good for backing this internally if it goes sideways | Something specific to their account, a signal or a result they can repeat to their boss | A working session to build the internal case together |
| Technical evaluator | Whether it integrates, breaks something or creates extra maintenance work | Architecture detail, integration specifics, what changes in their stack | A technical walkthrough with their own systems referenced by name |
| End user | Whether this makes their actual day to day work harder or easier | A short before and after of the task they do every day | A hands on trial, not a slide deck |
| Blocker (security, legal, procurement) | Compliance exposure and whether this becomes their problem later | Certifications, data handling terms, references from a similar regulated buyer | A document, not a meeting, until they ask for one |
Five roles, five different reasons to say yes. The product underneath stays the same in every row.
Building the pitch for each segment
You do not rewrite the whole email five times. You rewrite the part that changes, the pain and the proof and keep the offer and the structure the same underneath. The changing part is small on purpose.
- Map the roles on this deal. Pull the actual titles from the account, not a generic org chart. A 40 person company might not have a dedicated RevOps lead at all, so do not write to a role that does not exist there.
- Write one sentence of pain per role. Not a paragraph. If you cannot say what this person loses sleep over in one sentence, you do not know them well enough to write to them yet.
- Pick the proof type each role actually trusts. A number for the economic buyer, an integration detail for the technical evaluator, a document for the blocker. Using the wrong proof type reads as noise even when the fact itself is true.
- Write a distinct opening line per role. The subject line and first sentence are the only parts that have to differ completely. Everything after can share a structure.
- Route each role into its own sequence branch. If your sending tool supports conditional branches by title or department, use that instead of hand picking who gets which version.
- Keep the ask proportional to the role. A blocker does not want a demo invite. An end user does not want a compliance document. Match the next step to what that person can actually say yes to.
The offer does not change by role. The reason to say yes to it does.
How many segments is too many
Five roles is a ceiling for most deals, not a floor. A ten person company selling to a ten person company might only have two real segments in the room: the founder who buys and the one person who will use the tool. Writing five versions for a two person buying group is wasted effort that could go into the two pitches that matter.
The failure mode runs the other way more often though. Teams write one version, call it personalised because it has a merge field and wonder why the blocker never replies. If you are already running an agent that pulls account and contact facts, use it to flag which roles actually exist on a given account before a rep decides how many versions to write. Writing to a role that is not there costs time for nothing. Skipping a role that is there costs you the one person who could have killed the deal quietly instead of raising the objection where you could answer it.
FROM THE YARD
Start with the economic buyer and the champion. Those two roles decide whether a deal moves at all. Add the technical evaluator and the blocker once the first two are replying, not before. The end user usually gets looped in once there is already a deal in motion, so write that version last.
Testing pitches with reply data, not opinions
The payoff for splitting a list this way is not theoretical. Across email marketing broadly, segmented and targeted campaigns account for 77% of total ROI, against 23% for everything sent as one blast to a whole list. That gap is the argument for building segments in the first place, even before you get to the specific reply rate on any one deal.
Source: HubSpot, 2026
Segment your reporting the same way you segmented the outreach. A campaign that shows a 9% reply rate overall can be hiding a champion segment at 18% and a blocker segment at 1%. The blended number tells you nothing about which one to fix. Pull reply rate, not just open rate, broken out by role every week, the same way you would review it by signal. We wrote about this in more depth in our piece on B2B buying signals that actually predict a deal, since the review habit is the same whether you are segmenting by trigger or by role.
Change one variable at a time inside a segment before you touch the next one. If the blocker segment is not replying, check the proof point first, since a blocker ignoring a message about a certification they do not need is a targeting problem, not a copy problem. If the champion segment is not replying, check the ask before the pain line, since champions usually understand the pain fine and stall on being asked for something too big too early.
Where segmentation breaks down
This does not work everywhere. On a small deal with one or two people in the room, five segments is overhead with no payoff, so skip straight to writing one good pitch to the person who decides. If you cannot tell who holds which role on an account, because the org chart is unclear or the company is too small to have clean titles, guessing a role and writing confidently to the wrong one is worse than writing one honest, general message.
Segmentation also breaks down when the underlying offer is weak. Five well targeted pitches for a product nobody wants still get five polite declines. Fix the offer and the proof before you fix the targeting, because no amount of role specific copy rescues a pitch that has nothing worth replying to behind it. And segmentation takes real time to build and maintain. If your team sends to the same twenty accounts every quarter, five versions of a message is worth the setup. If your list turns over every month, keep it to two or three segments you can actually maintain or the upkeep eats more time than the lift is worth.
Messaging by segment is one layer of a larger outbound system. It only pays off once the account list underneath it is already scored and the data behind each contact is current, otherwise you are writing five clear versions of a message to the wrong person.
Questions about B2B messaging by segment
How many message segments should a B2B company use?
Five roles cover most complex deals: the economic buyer, the champion, the technical evaluator, the end user and the blocker. Smaller deals with one or two people in the room need far fewer, sometimes just one pitch to the person who decides.
Is segmenting by role different from segmenting by industry?
Yes. Most teams need both. Industry segmentation changes the examples and the language you use. Role segmentation changes the actual pain, proof and ask inside a single deal. A VP of sales at a software company and a VP of sales at a manufacturer still both want pipeline, even though the examples you use to prove it differ.
Does messaging by segment mean writing five completely different emails?
No. The offer and the structure stay the same. Only the opening line, the pain and the proof point change by role. Writing five full emails from scratch does not scale and is not necessary.
What if I do not know who holds which role on an account?
Do not guess with confidence. A wrong guess reads worse than a general message. Use whatever contact data and signals you have to confirm a role before writing to it and default to a general pitch for the accounts where the buying group is still unclear.
How do you measure whether segmentation is working?
Track reply rate by segment, not as one blended number. A healthy overall reply rate can still hide one role that never responds. Reviewing by segment is the only way to catch that and fix the one pitch that is not working instead of rewriting all of them.
Sources: TractionComplete, mapping the B2B buying committee, 2026, HubSpot, email list segmentation, 2026