GTM

How to Write an Outbound Sequence for a Second Buyer Persona

Written by
Pravin Kumar
Published on
Oct 16, 2026

How do you write an outbound sequence for a second buyer persona?

Start from the second persona's own problem, not your first persona's sequence with the job title swapped. Interview a few of them, find the pain they own and the words they use, then write a new sequence around that. Keep the proof and offer that work, but change the angle, the evidence, and the ask.

Most small B2B teams reach a point where outbound works for one buyer, say a head of marketing, and leadership asks for the same results with another, like a revenue operations lead or a finance director. The fast move is to copy the winning sequence and change a few words. It rarely works, because the second persona cares about different things.

This article is for founders and go-to-market leads expanding outbound to a new buyer within the same target companies. It explains how the two sequences should differ, how to research the new persona quickly, and how to tell whether the new sequence is working.

Why does copying your first sequence fail for a new persona?

Because the first sequence was tuned to one person's priorities, vocabulary, and objections. A marketing leader may care about pipeline and campaign speed. A revenue operations lead may care about data quality and fewer manual fixes. The same product, described the same way, sounds irrelevant to the second person.

The symptoms are easy to spot. Open rates look fine, because the subject line is generic enough. Reply rates are low, and the few replies are polite redirections like "you probably want to speak to our marketing team". The sequence is reaching the right companies but saying the wrong thing to the person who reads it.

The fix is not better copywriting in the abstract. It is understanding what the second persona is responsible for and what keeps them up at night, then writing to that.

How do you research a second persona quickly?

Talk to five people in that role, ideally at existing customers or friendly companies. Ask what they own, what they get blamed for, which tools they live in, and what a good week looks like. Then read their job postings and LinkedIn posts for the words they use. Two weeks of this beats months of guessing.

Existing customers are the best source. If your product is already used by your first persona, someone in the second role is often nearby and has opinions about it. Ask your champion for an introduction. Some will say yes, because it helps their own internal case for your product.

Job postings are an underrated research tool. A posting for the role lists what the company expects that person to do, in the company's own words. Read ten of them and patterns jump out. I used the same idea for list building in how to build an outbound list from job postings.

What should change between the two sequences?

Change the problem you lead with, the evidence you show, the words you use, and the ask you make. Keep what is true for both: your company, your core product, and your best customer proof, reframed for the new reader. The product stays the same. The reason it matters changes.

The problem is the biggest change. For a marketing leader, the opening might be about leads that never get followed up. For a revenue operations lead, the same product might be framed around routing rules that break every time the team changes. Same tool, different pain.

The evidence changes too. A marketer wants to see pipeline outcomes. An operations lead wants to see how the system works, how it fails, and how much maintenance it needs. A finance leader wants cost and payback. Pick proof that answers the question each persona actually asks.

The ask may change most of all. A marketer may happily take a demo. An operations lead may prefer a short technical walkthrough or documentation first. A finance leader may want a one-page business case before any call. Match the first ask to how that person likes to evaluate.

Should the two personas get separate sequences or a coordinated one?

Run separate sequences at first, so you can learn what works for each persona without the results blending together. Once both work on their own, coordinate them at the account level so people at the same company hear a consistent story and nobody gets contacted twice in one day.

Separate sequences make learning clean. If the new persona's reply rate is low, you know it is that sequence, not the account selection or the first persona's messaging. Mixing them early hides the signal you need.

Coordination matters later. When two people at the same account receive outreach, their messages should support each other. A light reference like "I have also been speaking with your marketing team about this" can help, as long as it is true and appropriate. Log every touch in your CRM so reps can see who has been contacted at each account.

Which channel should the second persona's sequence use?

Use the channel where that persona actually responds, which may differ from your first persona. Some roles live in email. Others are more reachable on LinkedIn or through a warm introduction from a colleague. Test the channel as deliberately as you test the message.

The same logic I use for choosing a first outbound channel applies here. Look at how existing conversations with this persona started, ask a few of them directly, and commit to one channel before adding another. I laid out that decision in how to pick your first outbound channel, email or LinkedIn.

Warm introductions deserve extra weight for a second persona. If your first persona is already a champion at an account, a short introduction to their operations or finance colleague is often more effective than any cold sequence.

How do you measure whether the second sequence works?

Measure positive replies and qualified meetings per hundred contacts, just as you do for the first persona, but set your own baseline rather than expecting the same numbers. A new persona often starts lower. What matters is whether the rate improves as you refine the angle over a few rounds.

Agree on what a good meeting looks like for this persona before you start. A meeting with an operations lead who will never influence the buying decision may look like progress but lead nowhere. My notes on defining what counts as a good outbound meeting help set that bar.

Read every reply, including the negative ones. Objections from a new persona are research. If several say "the CRM already handles this", that tells you how they see the problem and what your next message needs to address.

When should you stop and rethink the second persona entirely?

Rethink it if, after a few rounds of real changes, replies stay near zero and the few you get keep redirecting you elsewhere. That usually means the persona does not own the problem you solve, or does not have buying influence. Sometimes the right move is to reach them through your first persona instead.

This is a legitimate outcome, not a failure. Some roles influence a purchase without ever starting one. For them, the right motion is enablement: give your champion the material they need to bring the second persona in, rather than cold outreach that interrupts someone who does not see the problem as theirs.

What should you do next?

Interview five people in the new persona's role this month. Write down the problem they own and the words they use. Draft a fresh sequence around that problem, with proof and an ask that fit how they evaluate. Run it separately, measure it on its own baseline, and refine it twice before deciding.

I help founders and small revenue teams design and build the outbound systems behind this, from persona research and list building to sequencing and CRM tracking. If you are expanding outbound to a new buyer, reach out and let's chat.

Get found, cited and the back office automated

Let's make your site the source AI engines quote and wire up the systems behind it.

Contact

Let's get your website found and cited by AI

Tell me what you're working on, whether AI search is skipping your product, your back office is buried in manual work, or you need a build that does both.

Got it, thanks. I read every message personally and reply within 1-2 business days.
Oops! Something went wrong while submitting the form.