How to Sequence Outbound to a Buying Committee of Five

How do you run outbound to five people at the same company without it feeling like spam?

Give each person a different reason to reply, stagger when they hear from you, and run the whole thing as one account plan instead of five separate sequences. Start with the people who feel the problem daily, bring in the budget holder once you have proof, and save procurement and technical reviewers for later.

Most outbound still treats a company like a list of individuals. Five contacts go into the same sequence, get the same three emails on the same days, and compare notes in a shared Slack channel. The result looks less like research and more like a blast.

Multi-threading is the fix most sales leaders recommend, but the hard part is not deciding to contact more people. It is deciding who hears what, and when. That is the part I want to walk through here, from the angle of someone who builds the outbound systems behind it.

Why do B2B deals need more than one contact?

Because the decision is not made by one person. Forrester's State of Business Buying 2026 report, released in January 2026, found that the typical buying decision includes 13 internal stakeholders and nine external influencers. A single-threaded deal depends on one person carrying your story to everyone else, accurately.

That is a lot to ask of a stranger who has never bought from you. Even a strong champion will retell your pitch in their own words, drop the parts they did not understand, and lose the thread when a colleague raises an objection you never heard.

There is also a risk issue. If your only contact changes roles, goes on leave, or loses interest, the deal goes quiet with no way back in. I covered the late-stage version of that problem in what to do when your champion leaves mid-deal. Multi-threading from the first touch is the cheaper prevention.

Which five roles should you target first?

For most B2B software and services deals, the five roles that matter early are the day-to-day user lead, the champion who owns the problem, the economic buyer who owns the budget, the technical evaluator who checks fit and risk, and procurement. Titles differ by company, so map roles to people, not titles to templates.

The user lead is the person whose team does the work your product changes. They feel the pain first and can tell you if your framing is real. The champion is often their manager, the person who would have to defend the purchase internally.

The economic buyer signs off on spend. The technical evaluator might be IT, security, or a RevOps lead who has to connect your tool to HubSpot or Salesforce. Procurement handles terms and vendor risk. Forrester reports that procurement professionals are decision-makers in 53 percent of business buying cycles and engage from the start, which is a strong argument for knowing who they are early, even if you do not email them first.

I build this map with an enrichment table in Clay or Apollo, then confirm each person by hand. A wrong title on a committee map is worse than a missing one, because it sends the wrong message to the wrong person.

What should each person hear from you?

Each person should hear about the outcome they are measured on. The user lead hears about the daily work you remove. The champion hears about the result they can take credit for. The economic buyer hears about cost and risk. The technical evaluator hears about integration and security. Procurement hears about terms and simplicity.

This sounds obvious, but most sequences fail it. They write one strong email for the most likely buyer and then swap the first name for everyone else. The technical evaluator gets a pitch about pipeline growth they do not own. The economic buyer gets feature detail they will never read.

I keep one shared account narrative, a few sentences on why this company, why now, and what changes if they act. Every message pulls from that narrative, then translates it into the reader's terms. The facts stay consistent across the committee, which matters when people forward your emails to each other. The angle changes per role.

In what order should you contact the committee?

Start with the user lead and the champion in the first week, because they feel the problem and can tell you if you are wrong. Bring in the economic buyer once you have a signal of interest or a relevant proof point. Contact technical and procurement roles only after someone inside has engaged.

This order follows how trust moves inside a company. A budget holder who gets a cold email with no context has every reason to ignore it. The same person who hears, from their own manager, that a vendor had a useful conversation is far more likely to read your next message.

Timing matters within the order too. I stagger first touches by a few days so nobody receives the same day's email as their colleague. If two people at the same company compare inboxes, they should see a thoughtful approach, not a mail merge. Your sequencing tool can handle the delays. The thinking behind them has to come from you.

There is one exception. If a trigger event makes the economic buyer the obvious first contact, such as a new executive who publicly owns the problem, start there and let them pull in the team.

How do you keep five sequences from colliding?

Run the committee at the account level, not the contact level. One owner, one account plan, and one rule: when anyone at the company replies, every other active sequence pauses until the owner decides the next move. Without that rule, a reply from the champion can land the same morning the CFO gets your third follow-up.

This is where GTM engineering earns its keep. Pausing one contact after a reply is common. Pausing the whole account is a separate rule, and how you set it up varies by tool and configuration, so check your own setup against the vendor's documentation rather than assuming it works.

In HubSpot, I would use the company record as the home for every touch at an account. In a custom stack, I would write every outbound touch to an account-level log, whether that log lives in the CRM or an Airtable base, so whoever owns the account can see the whole conversation before sending anything else.

The same discipline applies to signals. If the economic buyer visits your pricing page, that is useful for the whole account plan, not just their sequence. I wrote about filtering those signals in which buying signals are noise in outbound, because a committee approach multiplies the number of signals you will see.

How many touches should each person get?

Fewer than you think. With five people in play, the account as a whole already hears from you often. I would give each person a short sequence of three to four messages over a few weeks, with at least one touch that adds something new, such as a relevant example or a short teardown.

The total number of touches at the account is the number that matters. Five people times six emails is thirty messages hitting one company in a month. Even if each email is good, that volume reads as pressure, and it raises the chance that someone flags you to IT or marks you as spam.

I would rather send fewer, better messages and use the extra time on research. One accurate observation about a company's hiring, their product launch, or a gap on their website is worth more than three generic follow-ups to someone who never replied.

What changes when the buyer is a larger enterprise?

The committee gets bigger and the order gets stricter. In large companies, procurement, security, and legal reviews can each add their own steps, so you want the champion to map the process for you early. Your job is to equip the champion with material they can forward, not to email every reviewer yourself.

Forrester's 2026 research has a useful note on group size. It found that 94 percent of buyers with buying groups of six or more report clear benefits. Read that as a reason to respect the committee rather than fight it. Bigger groups are not just friction. They are how buyers reduce their own risk.

In practice, that means building assets for each reviewer: a one-page security summary, a short integration note, a pricing explanation procurement can follow without a call. When the champion asks what to send, you have it ready.

How do you measure whether committee outbound is working?

Measure at the account level. Track how many target accounts have two or more engaged contacts, how long it takes to reach the economic buyer, and how many meetings include more than one person from the buyer side. Reply rate per contact still matters, but it hides whether the committee is actually forming.

I like a simple weekly view: accounts in play, contacts engaged per account, and the role of each engaged contact. If every engaged contact is a user lead and nobody with budget has replied after a month, your messaging to the economic buyer needs work, or you are targeting accounts where the problem is not a priority yet.

The other metric is collisions. Count how often two people at the same account received messages on the same day, or how often a sequence kept running after a colleague replied. That number should trend to zero. If it does not, the system needs fixing before the copy does.

What should you do next?

Pick ten target accounts, map the five roles at each one by hand, and write one account narrative per company. Then build role-specific messages from that narrative, stagger first touches, and set an account-level pause rule before you send anything. Review the engaged-contacts-per-account number weekly for the first month.

If you are deciding who in that committee to win over first, my take on whether to sell to the champion or the budget holder first goes deeper on that choice.

I design and build outbound systems like this for B2B teams, from enrichment and routing to the CRM rules that stop sequences from colliding. If you want help setting up committee outbound that does not feel like a blast, reach out at pravinkumar.co and let's chat.