· revenue engineOutbound, done properly, is ten jobs. Not one job split ten ways. Ten different jobs, each with its own discipline, its own software, its own ways of going wrong on a Tuesday morning. Research. List building. Persona work. Copy. Sequence ops. Landing pages. LinkedIn. Meeting booking. Coaching. Follow-up. Hyper covers all ten as a managed service. This piece walks through what each one is, what it looks like when it's done well by a real human at scale, and how the platform now does it.
I've hired into every one of these jobs. Paid the salaries. Signed the wage bill. Watched some of them work beautifully and watched others quietly fall over. Twenty-five years of running outbound at the kind of scale where you eventually staff up to ten people because that's what the job requires. None of these roles is hard in isolation. A good SDR can build a list. A decent copywriter can draft an email. The trick is doing all ten well, every week, against an account list big enough to matter. That's the job most companies under two hundred people simply cannot staff, because ten heads at $150k each is $1.5M before you've booked a meeting.
So here's the ten. Read the ones you currently staff, and the ones you don't. The honest comparison between Hyper and what you're running today sits in the gap between those two lists.
- Job 01
SDR research
Done well, this is an analyst sitting next to the rep, reading earnings calls, regulatory filings, hiring patterns, LinkedIn activity, product launches, every Monday morning. The output is a one-page brief that lands on the rep's desk before they pick up the phone, with the three things that have changed since last week and the one signal worth opening the call on.
Done badly, the rep does it themselves between calls. Twenty minutes a head, fifty heads, that's a full-time job nobody's being paid for and quality that drops the moment quota pressure rises.
Hyper runs the analyst job continuously across every account on the list, ranks them on a freshness score, and writes the brief straight into the CRM. Your reps read the same intelligence we use to write the outbound.
- Job 02
List building
The list is not the ICP. The list is who, inside the companies that match the ICP, has the title, the budget authority and the recent context to actually buy. Done well, this is continuous: titles change, companies get acquired, people leave, headcount jumps. Done badly, the list is a CSV from two quarters ago and your reps are spending half their week emailing maternity covers.
Hyper builds the list at onboarding, weighted by ICP, and re-scores it weekly against fresh signal. New joins, promotions, departures push contacts in and out automatically. Your CRM holds the canonical list and we write to it. We don't build a parallel one.
- Job 03
Persona work
A CFO at a portfolio business reads a different sentence from a CRO at a private equity firm. Persona work is the writing of those variations: what hooks each role, what they already think they know, what objection they reach for first. Most outbound tools skip this and ship one cadence regardless of who's on the receiving end. The reply rates tell you they did.
Hyper carries persona variants for every messaging hook and recombines them per account. When we're writing to the COO of a £40m logistics business, that's not the same email we sent the VP Sales of a New York fintech. The brief and the recipient travel together.
- Job 04
Copy drafting
The job most outbound tools claim to do, and the one they do worst. A drafted email that earns a reply has a hook from the brief, a single sentence of relevance to that specific company, a short claim, and one light ask. That's it. Stamping it out of a template is not the job. Writing it is the job.
I've sat behind plenty of copywriters. The good ones can do five accounts an hour at the standard I'm describing. Five accounts an hour, eight hours a day, against a list of ten thousand. The maths doesn't close. Which is why most of the market settles for templates and pretends the reply rate isn't the consequence.
Hyper writes every email, every LinkedIn DM and every landing page from the per-account brief. Same hook runs through all three, so whichever surface the prospect opens first, the argument continues. Your reps can read the output before it sends and edit it if they want.
- Job 05
Sequence ops
The unglamorous one. The job nobody wants to own. Cadences fire, an inbox warms up, a domain's reply rate dips, deliverability drifts, somebody's out of office and the follow-up stacks. Sequence ops is the operations job that keeps the cadence sane and the deliverability honest. Done badly, it's the reason your last campaign suddenly stopped landing in week six.
Our team runs sequence ops on every engagement, end to end. You don't configure cadences, manage warm-up pools or re-route around bounced domains. You take the meetings.
- Job 06
Landing pages
The cleanest signal a prospect is interested is that they clicked. The cleanest way to lose them after that is to land them on a generic homepage. A per-account landing page repeats the email back at them, expands one claim, and gives them a single thing to do next. At enterprise scale that's a designer plus a CMS plus a tracking layer, and a marketing manager with a roadmap.
Hyper builds a landing page per prospect, hosted under our domain or yours, on the same hook the email and the DM opened on. The page tracks the visit and files it against the contact in your CRM, so your reps see the click signal next to everything else on the account.
- Job 07
LinkedIn outreach
LinkedIn is a different muscle from email. Connection requests need a sentence, follow-ups need not to feel automated, and the platform polices volume aggressively. At scale this is a dedicated SDR running it from a personal account with proper warm-up, proper inbox handling and proper escalation when somebody says they're not the right person but here's who is. Most founders try to add LinkedIn outreach to an existing SDR's job description and watch quality collapse on both sides.
Hyper runs LinkedIn from your reps' own accounts, paced inside platform limits, with reply handling routed back through the same CRM record as the email. The hook that opened the email opens the DM. Your rep sees both threads in one place.
- Job 08
Meeting booking
The job between "they replied" and "there's a meeting on the rep's calendar." This is one of the quiet places SDR pipelines leak: a yes-but-next-week that nobody chases, a calendar link that breaks, a reschedule that disappears into a thread. Done well, this is a BDR working a triaged inbox with a clear escalation path. Done badly, it's the rep finding out at standup that three replies got missed.
Hyper triages every reply, classifies it, books the meeting where it can, and escalates to your rep where a human is needed. The thread, the call link and the reminder all file under the contact, with a one-line summary of why this meeting matters waiting in the rep's calendar invite.
- Job 09
Coaching
Every meeting your reps run is a piece of evidence. The coaching job is reading that evidence, scoring it on consistent dimensions, and giving each rep one specific thing to do differently next week. At enterprise scale that's a sales enablement lead with weekly one-to-ones and a defined competency framework. At smaller companies it almost never happens, and your better reps stop growing about eighteen months in. I've watched that pattern repeat at every business I've ever staffed.
Hyper scores every call against six dimensions: rapport, discovery, problem diagnosis, value framing, objection handling, closing. Each rep gets a keep, stop, start summary every week and a development plan quarter-on-quarter. Their managers see the team view. The scorecard piece goes deeper.
- Job 10
BDR follow-up
The longest job. Most replies say not now, not me, or nothing. The compounding work is the second-, third- and twelfth-touch follow-up months later, when the trigger event you forecast actually happens. The companies that win mid-market deals are the ones still in the inbox when the buyer is finally looking.
Hyper runs follow-up indefinitely, watches the account for the next signal, and re-engages on the back of it. A prospect who said not yet in February gets a different email in October, written to the new context. The CRM holds the entire history. Your rep walks into a warm conversation a year later with full notes on why.
What changes when these jobs are run together
The reason to do all ten in one place isn't headcount arithmetic. It's that each job feeds the next. The research is sharper when it's shaped by what last week's replies told us. The copy is tighter when the persona work has already done its job. The coaching is better when the call recordings file under the same account record as the meeting that produced them. Cut any one of the ten out and the others get duller.
The other reason is the failure mode I've watched on repeat. Most companies have an SDR running a list, sending sequences, with a copywriter showing up in retainer hours to draft new emails when somebody complains. The research, the persona work, the landing pages, the coaching, the follow-up: those jobs don't get done at all, or they get done by the SDR in spare moments, badly. The pipeline number is the result.
The argument for Hyper is not that one piece of software beats the ten you might assemble yourself. The argument is that the ten people you'd otherwise hire to do this properly aren't on your org chart, and the work without those ten people is the half-job currently disappointing your board.
Read next
On why the platform is sold as a managed service rather than self-serve software, read why we don't sell a DIY tier. On the meetings target inside every contract, read what the meetings guarantee actually buys you. On where each of these ten jobs files inside the CRM your reps already use, read how we plug into your CRM.