Who Owns Cold Outreach: Roles in a B2B Team

Cold outreach into Russia and CIS breaks down between reply and meeting. Here are the four roles that keep a lead from going cold.

In cold outreach aimed at Russia and CIS, almost nobody should be running the whole chain alone — and when one person does, the lead usually goes cold within the first week. The setup that holds together has four roles: an owner who decides who to write to and why, a researcher who builds and cleans the list, an outreach manager who runs the sequence and watches the sending domain, and a sales rep who picks up a warm reply and turns it into a meeting.

The usual failure isn't a shortage of emails. It's that nobody is explicitly on the hook for the gap between "someone replied" and "someone is on a call." In this market, the person who answers your email is often the founder or commercial director themselves, and they can reply within the hour. If nobody picks up that reply quickly and personally — not through a faceless call center queue — a warm lead cools faster than the message can travel from an inbox to a sales rep's task list.

The four roles that keep the process from leaking

Here's the minimum set of roles for a chain where a lead doesn't fall between stages. In a two-person team, one person can cover two roles, but the responsibilities still need to be kept separate on paper — otherwise nobody can tell why the chain stalled.

The owner here is more than the person who signs off on budget. They hold the compliance line: in Russia, sending a promotional blast to a personal email address without consent is treated differently from sending a targeted, relevant note to a specific company about its own business — the second isn't classified as advertising the way a mass campaign is. In practice, that means the owner's job is to keep the team's copy reading like a specific, relevant proposal to one business, not a promotional mailer dressed up as a personal note.

The researcher owns where contacts come from. Tools like Apollo or ZoomInfo don't have meaningful coverage here, so list-building leans on public company registries and generic corporate mailboxes such as info@ or sales@ rather than scraped personal profiles. A named person's title and work email counts as personal data in this market, so it's safer and more reliable to pull what a company has published itself than to hand-collect it from social media. The researcher also owns the opt-out list and drops a contact the moment someone asks to stop hearing from you.

The outreach manager covers what the owner and researcher don't see day to day: SPF, DKIM and DMARC on the sending domain, warm-up pace, spam-complaint rate, and the order and content of the emails in the sequence — more on building that sequence in what to send after the first touch. One local wrinkle to plan for: Yandex 360 and Mail.ru, not Gmail or Outlook, are the dominant inboxes here, so warm-up and authentication need tuning for how those providers score senders. The outreach manager is also first to see a reply and decides where it goes: discard, another warm-up touch, or straight to sales.

How a lead moves from email to meeting

1. The researcher builds the list against the ICP the owner signed off on, and cleans it before the sequence starts.
2. The outreach manager launches the sequence and watches deliverability and domain health.
3. A reply lands in the outreach manager's inbox, and they tag it: a real question, a decline, an auto-reply, or genuine interest.
4. A warm reply or a direct request for a call goes to the sales rep the same working day, with the full thread attached — not a summary of it.
5. The sales rep carries the conversation to a call or meeting and logs the deal in the CRM.
6. A decline or a removal request goes back to the researcher, into the opt-out registry.

This only works if it's clear, at every step, who owns the next move. Skip that, and step 4 is usually where things break: the email sits in the outreach manager's inbox because "sales will pick it up," and sales never finds out it exists.

Where the lead usually falls through

Three gaps show up in almost every team that starts outreach without splitting these roles.

The first is a blurred line between research and writing: when the outreach manager also hunts for contacts, emails go out later and less often, because time goes into search instead of into replying to people who are already warm.

The second is a silent handoff. A sales rep picks up a thread with no context — doesn't know the person replied personally to the founder, hasn't seen the earlier emails, and restarts from zero. To the recipient, it reads like talking to someone new who remembers nothing.

The third is no deadline for the handoff itself. Without a rule like "a warm reply reaches sales within the same working day," messages settle into whoever's inbox they landed in, and the lead cools with no bad intent behind it.

The local twist: when the owner answers personally

Most Western playbooks are built around an SDR who qualifies a lead and an AE who closes it, with a clean handoff through a shared call queue or support inbox. That model works less well here: at a small or mid-sized Russian company, the founder or commercial director often reads their own email and personally replies to a message that caught their attention. They don't expect a stranger with a script to pick up the thread after that.

That changes step 4 above. Handing the conversation to a sales rep has to be fast and personal — the rep introduces themselves, references what the colleague already wrote, and avoids anything that feels like a transfer to another department. Sometimes it's better for the outreach manager who sent the first email to keep going, with the sales rep joining only for the call — so the recipient keeps talking to the person who already answered them once.

If you have fewer than four roles

In a one- or two-person team, the roles inevitably overlap, and that's a normal starting point. What matters isn't headcount — it's not blending the functions inside one person's day at the same time as selling: while someone is on a sales call, they're not also writing new emails or watching the domain. The working minimum is splitting "who researches and writes" from "who runs the meeting," even if it's the same person on different days. If an in-house team for these roles isn't affordable yet, research, deliverability and sequence management are the functions most teams hand to an outside partner first, keeping meetings in-house — that trade-off is covered in in-house, agency, or hybrid.

FAQ

Can one person run the whole outreach process alone at the start?

Yes, but it helps to fix which hours they're a researcher writing emails and which hours they're a sales rep running meetings. Blending the two in the same stretch of time is a common reason warm replies sit unread for weeks.

Who should own the opt-out list and remove contacts on request?

Usually the researcher, since they're the one building and updating the list. A request to remove a contact or stop emailing them should be acted on immediately, not queued for the next list cleanup.

Does the sales rep need to write the first cold emails?

Not usually — a sales rep's hours are worth more on calls and deals than on drafting subject lines and follow-up touches. Bring them in once a thread is already warm.

How fast does a warm reply need to reach the sales rep?

Aim for the same working day, while the exchange is still fresh for the person who wrote it. The longer the gap between their reply and your team's response, the more likely they've already written to someone else.

What if the owner replies personally and doesn't want to talk to someone new?

Keep the conversation with whoever already has the history, at least until the call or meeting happens. A clean handoff that loses the thread's context usually costs more than a little flexibility in who owns what.

If your process keeps snagging at the handoff between a reply and your sales team, send us your current setup or a target list and we'll look at where it's leaking. See how engagements run at How the engagement runs, or bring a specific case through Contact.