HOW IT WORKS  //  we build and run the private outbound engine, you close the businessApply
The GTM engineering service model

We build the engine.
You close the deals.

ReplyLead handles the entire go-to-market machine - strategy, data, dedicated domains, private sending infrastructure, deliverability, copy, automation and reply handling - and books qualified meetings onto your calendar. You run the sales calls.

See what your engine would look like Walk the 15 steps
15
steps before a meeting reaches you
2
sending systems, segmented & isolated
1
job that stays yours: the close

How does ReplyLead work?

ReplyLead is a done-for-you GTM engineering service. We build and operate a private outbound engine for your business - targeting, data, dedicated domains, segmented mailbox infrastructure, deliverability, copy, automation and reply handling - and book qualified meetings onto your calendar. You run the sales calls and close. It runs on a monthly infrastructure fee that pays for the private system, plus a revenue share on the business we help generate and you close.

Engine → ReplyLeadSales calls → YouInfrastructure fee + revenue share
01
The end-to-end workflow

From a blank slate to a booked meeting.

Fifteen deliberate steps sit between "let's do outbound" and a qualified prospect on your calendar. We run every one of them. Follow the current down the line.

Phase 1 · Strategy & targeting

Step 01

Campaign strategy

The angle, the offer and the plan to reach the market.

1
2

Step 02

ICP & signal definition

Who to target and the buying signals worth acting on.

Step 03

Company & decision-maker targeting

The right accounts, and the right people inside them.

3
Phase 2 · Data & infrastructure build
4

Step 04

Data sourcing & enrichment

Buying, scraping and enriching lists to a verified, send-ready state.

Step 05

Dedicated domain purchasing

Fresh domains bought for you - never shared, never borrowed.

5
6

Step 06

Mailbox infrastructure setup

Mailboxes provisioned and segmented across Google Workspace and Microsoft 365.

Step 07

Authentication & deliverability

SPF, DKIM and DMARC configured so mail lands in the primary inbox.

7
8

Step 08

Mailbox warmup

Weeks of reputation-building before your first campaign send.

Phase 3 · Copy, automation & launch

Step 09

Copywriting

Sequences written per prospect from real signals, not merge tags.

9
10

Step 10

Automation build

Sequencing, routing and reply logic wired end to end.

Step 11

Testing & launch

Rendered, deliverability-checked, then sent at controlled volume.

11
Phase 4 · Reply handling & booking
12

Step 12

Reply handling

Every response managed - answered, nurtured, kept warm.

Step 13

Qualification

Real interest separated from noise before it reaches you.

13
14

Step 14

Meeting booking

Qualified prospects placed directly on your calendar.

Your sales team takes over. A qualified meeting lands on your calendar. Everything above this line is ours to build and run. Everything below it is the conversation only you can have.

Phase 5 · You close

Step 15

Sales calls & closing

Discovery, proposal, negotiation and signature - your team, your process, your relationship.

15
02
The private infrastructure

Why this can't run on your existing setup.

Cold outbound at volume needs sending infrastructure that is bought, isolated, authenticated and warmed - built for one client and one campaign. We buy dedicated domains and fan mailboxes across two systems, Microsoft 365 and Google Workspace, because each behaves differently and each protects the other. Density is deliberate.

System A Microsoft yourbrand-mail.com System B Google Workspace yourbrand-team.com Option SMTP (optional) yourbrand-send.com sending pool

System A

Microsoft 365

~50 mailboxes per domain

Higher density where the platform supports it - many mailboxes on one dedicated domain, provisioned and monitored per client.

System B

Google Workspace

~2-3 mailboxes per domain

Deliberately low density to protect sender reputation - a handful of mailboxes on each domain, so more domains, fewer boxes each.

Option

Dedicated SMTP

added only where an architecture calls for it

Today every sender is a Google Workspace or Microsoft 365 mailbox. Where a design needs a third pool, an SMTP service can be added on its own domains, kept separate so one pool never drags down another.

This is why the setup is custom, and why it costs money. None of it is a shared account you can log into. Every domain is bought for you, every mailbox is provisioned and authenticated for you, and every system is warmed for weeks before it sends a single campaign. Segmenting across Microsoft 365 and Google Workspace isn't decoration - it's how deliverability is protected and how one client's sending never touches another's.

03
Who owns what

A clean division of labor.

No ambiguity. We own the machine that produces qualified conversations. You own the conversations.

ReplyLead handles

The full outbound engine, built and operated for you.

  • 01Campaign strategy
  • 02Data, scraping & enrichment
  • 03Dedicated domains
  • 04Private mailbox infrastructure
  • 05Authentication & deliverability
  • 06Warmup
  • 07Copywriting
  • 08Automation & testing
  • 09Reply management
  • 10Qualification
  • 11Meeting booking

You handle

The revenue conversation, start to finish.

  • —Sales calls
  • —Discovery
  • —Proposals
  • —Closing
  • —Collecting payment

This is the part of the deal that lives with your team, your product knowledge and your relationships. We don't take it from you - we feed it.

Booked meeting → your calendar
04
The commercial model

Two parts, and each one earns its place.

A fee builds and runs the private engine. A revenue share aligns us with the outcome. Neither replaces the other.

The infrastructure fee

Builds and runs your private engine

We're not sending a few emails from a tool - we're building and operating a private outbound system for one client, and that carries real cost before a single deal exists.

The fee covers the work and the spend that happen whether or not anyone has closed yet - the same cold email infrastructure and deliverability setup that makes campaigns land:

Dedicated domainsMailbox provisioningInfrastructure segmentationDeliverability setupWarmupData acquisitionAutomation buildTooling & operating cost
The revenue share

Ties our upside to yours

Once the engine is running, our incentive should point at exactly one thing: business you actually win. So the revenue share applies to the business ReplyLead helps generate and you close - not to activity, not to sends.

The fee keeps the private engine built and running. The revenue share makes us a growth partner with skin in the game - motivated to put better meetings in front of you, not just more email into the world.

In one line: the fee is for the machine. The share is for the outcome. That's why "work for free until we close" isn't the model - the machine has to be built and paid for before it can produce anything. See how it plays out on pricing.
The model at a glance
What ReplyLead does
Builds & runs the full outbound engine, then books qualified meetings on your calendar.
What you do
Run the sales calls, discovery, proposals and closing.
Infrastructure fee
Monthly. Pays for domains, mailboxes, deliverability, warmup, data & tooling - charged whether or not a deal closes.
Revenue share
On the business generated and closed - performance-aligned, on top of the fee.
Infrastructure
Dedicated & private - your domains and mailboxes, never pooled across clients.
Sending systems
Microsoft 365 (~50/domain), Google Workspace (~2-3/domain) - segmented & isolated. Dedicated SMTP can be added as an option.
05
Straight answers

The questions worth asking us.

Can we just use your system on our own infrastructure for free until deals close?
No - there's no shared, pre-built system to borrow. Every campaign runs on infrastructure we buy and build for you specifically: dedicated domains, provisioned mailboxes, authentication and weeks of warmup. That's real, up-front cost and labor before a single email sends, which is what the infrastructure fee covers. The revenue share is what ties our upside to yours after the engine exists.
Why is there an infrastructure fee?
Because we're building and operating a private outbound system for one client, not sending from a tool. The fee covers dedicated domains, mailbox provisioning across segmented systems, deliverability configuration, warmup, data acquisition, the automation build, tooling and the setup labor - real costs we carry whether or not a deal has closed yet.
Can we skip the private setup and go faster?
Skipping the setup is skipping the thing that makes outbound land in the inbox. Fresh domains need warmup, authentication has to be configured, and mailboxes have to be segmented across systems. Sending before that is how a domain's sender reputation deteriorates. The build is the reason it works.
Is the infrastructure shared or dedicated?
Dedicated. Your domains and mailboxes are yours, sending only your campaigns. We never pool sending reputation across clients - that's how one bad sender would sink everyone. Isolation is the point.
Do you also close deals?
No. We generate qualified interest and book meetings onto your calendar. You run the sales calls, discovery, proposals and closing. Our revenue share applies to the business we help generate and you close.
Why is the setup custom for each client?
Because your ICP, your signals, your data and your sending reputation are yours alone. The domains carry your brand, the copy speaks to your market, and the reputation being built belongs to your campaigns. A generic, shared setup would dilute all four.

Go deeper on any part of the engine

Each stage of the system has its own page. Here's where the workflow above connects to the rest of ReplyLead.

InfrastructureCold email infrastructureDomains, mailboxes, authentication and the segmented sending systems behind the engine.Explore Inbox placementDeliverabilityHow warmup, reputation and isolation keep campaigns landing in the primary inbox.Explore DataLead list buildingSourcing, verifying and enriching the targeting data the sequences run on.Explore CopyCold email copywritingThe messaging and follow-up framework that turns targeting into replies.Explore CommercialsPricing & the modelHow the infrastructure fee and revenue share fit together on a real engagement.Explore ProofCase studies & resultsWhat the engine has produced for real clients - pipeline, meetings and reply rates.Explore

From the dashboard to your sales process

Export a lead without losing the next step

ReplyLead's selected-lead export keeps status, pipeline stage, meeting notes and deal value in separate columns. Use the editable field map to decide where each belongs in your receiving system before importing the file.

  1. Select the intended records. Review the selected rows, then use Export in the dashboard's selection controls. Keep a private copy of the original export.
  2. Map the fields before import. Preserve Lead ID as a source reference; map Status and Pipeline Stage separately. Keep Meeting Date, Meeting Time and Meeting Notes together.
  3. Resolve identity and missing values. Check source IDs for duplicates within the organization before using them as import keys. Confirm missing stages and amounts against the original record; a default label or blank amount is not a reviewed sales outcome.
  4. Assign the next action. Carry the buyer's request, responsible owner and due date into the receiving record. After the call, record attendance and the sales owner's acceptance decision.

Download the sales follow-up worksheet (.csv)

Which export details need review?

The selected export fills a missing pipeline stage with Lead and renders a numeric zero deal value as blank. It exports an activity count rather than the activity history, and formats some timestamps as dates. Retain original dated evidence when those distinctions matter to a sales decision. The field map leaves receiving-system fields editable; it does not assume a native CRM connection.

Export-method check: 11 September 2026. The selected-export routine and its generated Excel file were tested against retained records, with every exported cell re-read and compared. This validates the export output, not a receiving CRM's import or a sales owner's acceptance.

See how this applies to two documented paths from a reply to a booking, or use the completed campaign-review workbook to keep booked, held and accepted outcomes separate.

What your sales team needs to follow up

Take a completed campaign review into your next meeting

A sales team needs more than an interested label: which company fits, what the person asked for, what remains unknown and who owns the next action. The workbook below provides a completed example, a blank weekly report and an acceptance checklist.

ReplyLead's lead dashboard has separate fields for lead status, pipeline stage, meeting notes, activities and deal value. The example below shows how to use those distinctions. It is fictional; it is not a customer record or a claim that an external CRM is synchronized.

Example: a dispatch manager requests a worksheet

Company fit: a commercial maintenance firm with multiple field technicians.

Observed need: the manager asks how schedule changes are confirmed by technicians.

Next action: send the requested change-log worksheet and record the responsible owner.

Stage: positive response. No meeting has been booked; no sales opportunity has been accepted.

This record gives the next person enough context to continue without inflating the pipeline.

Download the campaign review workbook (.xlsx)

The reporting questions to settle before launch

  • Which cohort? Name the campaign and reporting window. Keep its contacted population and outcomes aligned.
  • What counts as qualified? Agree the company, role and need criteria with the sales owner. Requesting information is not enough by itself.
  • Was the meeting held? Track booking, rescheduling and attendance separately. One rescheduled meeting is not two meetings.
  • Who accepted the opportunity? Record the sales owner's decision and next step, rather than inferring acceptance from sentiment.
  • What revenue is attributable? Use the agreed attribution rule and supporting won/financial records. Unknown amounts stay unknown.
Read the completed weekly example

In the fictional workbook cohort, 500 people are contacted and 20 people reply. Three replies are automatic-only, leaving 17 human replies. Four show positive interest; two meetings are booked, one is confirmed held and qualified, and one opportunity is accepted. Revenue is not recorded.

These stages overlap. Do not add them to claim 45 leads, and do not turn the unheld meeting into a failure before its outcome is known. The workbook names the evidence and action for each measure.

Use the cold email metric definitions alongside the report, and the completed campaign resources to connect the promised asset to the actual reply. For source-backed outcomes, read our case studies.

See what your private GTM engine would look like.

We'll walk you through the exact setup for your market - the infrastructure, the data, the copy and the meetings it's built to produce.

Talk through your campaign setup

Compare providers. Compare how this differs from the outsourced SDR companies and the appointment setting companies we track.