If more than one person weighs in on a purchase at your accounts, an outbound plan that picks one title per account and stops there will miss people who can say yes, say no, or stall a deal. A plan that contacts everyone with the same note will annoy the same company several times.
This guide gives you a way to write the committee down, pick a first contact, set a cap per account, and keep the messages different. It does not give you a magic number of contacts or a fixed order of roles. This guide has no figure for either, and the right answer depends on your product and your past deals. It gives you a method for finding your own answer and recording it.
Who this is for
This guide is for founders and sales or marketing leads who run outbound at a B2B company and sell to accounts where more than one person weighs in. It is also for the person who approves the outbound rules.
It fits you if:
- You already have a list of target accounts and a rough idea of your ideal customer.
- Your reps or your tooling can reach more than one person per account.
- You want one written rule for who gets contacted, rather than each rep deciding alone.
If you are still working out which accounts to target at all, start with Fit first, timing second and the free ICP assessment. Committee mapping comes after account selection. For a broader view of a small team's setup, see early stage B2B outbound.
The four roles to map
Use four working roles. They are labels for what a person does in a purchase. They are not job titles, and one person can hold two.
- Champion. Someone who feels the problem and would push for a fix inside the company.
- Economic buyer. Someone who controls the budget or signs off on spend.
- Technical evaluator. Someone who checks whether the product works in your buyer's setup.
- Blocker. Someone who can slow or stop the purchase, such as a person who owns a competing tool, a security reviewer, or a manager whose team would change how they work.
The terms multi-threading and buyer persona cover the wider ideas. Here the point is narrow: for each type of account you sell to, write down which titles usually fill each role.
One rule matters before the steps. A role you assign from a guess is a hypothesis, not a fact. Outlevo labels guesses as hypotheses and never presents them as findings [[1]](#sources), and your own notes should follow the same habit. "Likely economic buyer" stays a hypothesis until something with a source and a date confirms it.
Steps
Step 1: Write the role map for one account type
Pick one segment of accounts that you sell to. Make a table with four rows, one per role, and three columns:
- Titles that usually fill this role in this segment.
- What this person cares about, in one sentence.
- Where you learned it: a won deal, a call, a page on the company's website, or a guess.
Write "guess" in the third column of every row you cannot yet trace to a won deal, a call or a page. Replace it only when you can point to a source. Do this for one segment first. Role maps may differ between segments, so consider one table per segment rather than one table for everything.
Step 2: Check the map against your won and lost deals
If you have past deals, use them. Deal fields such as stage, amount, outcome and loss reason can be imported from a CSV, or read from HubSpot or Salesforce, for win/loss analysis in Outlevo [[2]](#sources). The HubSpot connection reads companies, deals and owners [[3]](#sources). The Salesforce connection reads accounts, opportunities and users [[4]](#sources).
Contacts are separate. HubSpot contact import is optional. It brings in email, name, job title and email opt-out, and only after an admin turns it on with a stated purpose [[3]](#sources). Job titles on your won deals are the evidence you need for the role map, so decide whether that import is worth turning on, and write the purpose down.
Then be honest about sample size. Win/loss analysis in Outlevo counts companies, not deals, and fewer than 10 won companies is labeled very low confidence [[5]](#sources). If you are under that line, treat the pattern you see as a guess and keep the "guess" label in your table. Several deals at one company still count as one company.
If you have no past deals, your map is entirely hypotheses. That is fine at the start. Contact fewer people per account and learn from replies before you widen it.
Step 3: Choose who to contact first with a written rule
This guide does not give a universal answer to "which role first", so build the rule from your own evidence. Here is a way to do it.
- Look at your won deals, if you have enough of them. Ask which role first replied or first booked a meeting at those companies.
- If you do not have enough deals, pick a starting hypothesis for the segment. Label it as a hypothesis in your policy notes.
- Write the rule as a sentence a colleague could follow without asking you. For example: "At accounts in segment A, contact the title we listed as champion first. If there is no match on the account, contact the technical evaluator."
- Add a fallback for each account where the first-choice role has no named person.
Two practical tests for any first contact:
- Can you reach this person with verified data? Contact discovery costs 4 credits, volume contact discovery costs 2 credits, and email verification costs 1 credit [[6]](#sources). A first-choice role you cannot reach is a worse first choice than a second-choice role you can.
- Does the account have a timing reason to move now? Website visitor data identifies the company behind a network and never a person [[7]](#sources). Use it to decide which accounts to work this week, not to decide which individual to write to. The same holds for ads: LinkedIn Ads audiences are built from company names and websites, not from people [[8]](#sources).
Keep the rule short. A rule with many branches will not get followed.
Step 4: Set a cap on contacts per account
Pick a maximum number of people you will contact at one account in a given period, and write it down. This guide does not name a number, because it has no sourced figure for committee size or ideal contact count. Your number depends on account size, how many roles you have mapped, and how much volume your mailboxes and your team can handle.
To choose it:
- Start low for accounts where the role map is mostly guesses.
- Raise it only for segments where your own data shows more people means more replies, not more unsubscribes or bounces.
- Set separate caps for separate channels if you use more than one. Email and LinkedIn are different channels and can carry different limits.
Measure the effect at the right level. Smartlead's State of Cold Email 2026 measures reply rate per contact, so a person who replies once counts once. It puts the median at 0.74%, the top quarter at 1.43% and the top tenth at 2.63% [[9]](#sources). When you contact several people per account, look at replies per person and also at whether the account as a whole moved, such as a booked meeting. A rate that looks fine per person can hide five people at one company all ignoring you.
Step 5: Give each role a different message
Contacting several people at one account is only fair to them if each message is for them. Build a short message map with one row per role:
- The problem this role feels, in their terms.
- One proof point relevant to that role, taken from facts you can show.
- One clear ask.
Then apply three checks before anything goes out:
- No two people at the same account receive the same opening line or the same ask.
- No message names a fact about the account that you cannot source. Facts read from a website should come with a quote found on the page, which is how Outlevo keeps them [[1]](#sources).
- On LinkedIn, the invitation note is at most 300 characters, and Outlevo sends one message after the person accepts [[10]](#sources). Plan the note for each role within that limit.
Also decide in advance what happens when one person replies. On LinkedIn, a reply stops that lead's emails [[10]](#sources). That covers the lead who replied. Your own rules should say what the other contacts at that account do next, such as pausing, continuing with a different angle, or stopping for the account.
Step 6: Record the rules in an approved policy
Rules kept in a doc get ignored. Put them in the system that sends.
In Outlevo, policies set who can be contacted, on which channels, how often and with what budget. Nothing is sent outside a policy that a person approved [[11]](#sources). Every external action is checked against the approved policy before it runs, and recorded in a ledger [[11]](#sources). That makes the policy the right place for your per-account cap and your channel rules. The cap is a policy value a person approves, not a habit of one rep.
A policy draft for committee outreach should state:
- The roles you contact, by segment.
- The first-contact rule and the fallback.
- The maximum number of people per account and the period it covers.
- The channels allowed for each role.
- The person who approves changes.
Kill switches can pause a campaign, a channel or the whole workspace at once [[11]](#sources). Know who is allowed to press them and when. A kill switch stops all sending on that campaign, channel or workspace, not only for the one account, so keep it for problems wider than a single account's complaint.
If you work from a Gmail inbox, the Outlevo extension has a recipient guard that warns before you email a contact Outlevo should not reach [[12]](#sources). That helps catch manual one-off emails to someone outside your rules.
What to check
Run through this list before the first send and again after the first batch.
The map
- Every role in your table is labeled either "sourced" or "guess."
- Role patterns from past wins are marked low confidence if you have under 10 won companies [[5]](#sources).
- Each account has at least three dated, sourced observations on its Readiness Card, which is the minimum a card needs [[1]](#sources).
The limits
- The cap per account is written down as a number you chose, with a period.
- The policy is approved by a named person.
- Each channel has its own limit.
The messages
- No two contacts at one account get the same opening line or ask.
- Every account-specific fact in a message has a source.
- LinkedIn notes fit within 300 characters [[10]](#sources).
The send
- Bounces, replies and unsubscribes are read back per account, not only per person. Smartlead reports sent, reply, bounce, unsubscribe and category changes back to Outlevo by webhook [[13]](#sources).
- Someone reviews accounts where more than one person unsubscribed or bounced, and lowers the cap for that segment if it keeps happening.
The rules outside your tooling
Check the legal basis for each region where your contacts sit. Outlevo asks which countries you sell into and never proposes markets [[5]](#sources), so the market choice and its legal review are yours. Some starting points from primary sources:
- The FTC states: "The law makes no exception for business-to-business email." [[14]](#sources) Emailing several people at a company is still covered.
- The UK ICO says: "You can email or text any corporate body (a company, Scottish partnership, limited liability partnership or government body)." [[15]](#sources)
- GDPR Article 6(1)(f) allows processing that is "necessary for the purposes of the legitimate interests pursued by the controller or by a third party". [[16]](#sources)
- LinkedIn's User Agreement lists this among the things you must not do: "Use bots or other unauthorized automated methods to access the Services, add or download contacts, send or redirect messages". [[17]](#sources) Read how your own LinkedIn setup fits that before you add more people per account.
These are quotes, not legal advice. If you are unsure, ask a lawyer who knows the markets you chose.
Next step
Pick one segment and do the first three steps this week: write the role table, check it against any past deals you have, and write the first-contact rule with its fallback. Mark every guess as a guess.
Then write the cap and the message map, and put the cap into a policy a person approves. After your first batch, read the results per account, adjust the cap for that segment, and only then repeat the work for the next segment.
If you want a starting view of your accounts before you map roles, the free ICP assessment reads up to 5 public pages of your website and returns facts labeled as verified observations or AI inferences, plus up to 5 experimental segment hypotheses [[18]](#sources). To see how policies, approvals and the ledger fit together, read How Outlevo works. If you are weighing autonomous tools against approval-first ones, the SDR comparison lays out the difference.
Sources
- Readiness Cards
- CSV and Excel integration
- HubSpot integration
- Salesforce integration
- ICP from evidence
- Outlevo pricing
- Website visitors integration
- LinkedIn Ads integration
- Smartlead, The State of Cold Email 2026: reply rate per contact (top quartile; January to June 2026, more than 850 million emails)
- LinkedIn integration
- How Outlevo works
- Gmail extension integration
- Smartlead integration
- FTC: CAN-SPAM Act compliance guide for business
- ICO: Electronic mail marketing (PECR)
- GDPR Article 6(1)(f): lawfulness of processing
- LinkedIn User Agreement (section 8.2, Don’ts)
- Free ICP assessment