Skip to content
EMPRAOUTBOUND
EngineMethodDeliverabilityIntentReply agentAutomationsMonitored markets
Apply
EngineMethodDeliverabilityIntentReply agentAutomationsMonitored marketsApply

EMPRA

EMPRA

Outbound

RUN BY HUGO DUPONT & GEORGE LEVESON
LONDON

WHAT WE RUN

  • The engine
  • Deliverability
  • Intent signalling
  • Reply agent
  • Automations
  • Method
  • Monitored markets

FREE TOOLS

  • Grade my email
  • Deliverability test
  • SPF checker
  • DKIM checker
  • DMARC checker
  • Subject line tester
  • Spam checker

THE PLAYBOOK

  • Playbook overview
  • Subject lines
  • The ask
  • The sequence
  • Follow-ups
  • Identify your ICP
  • Infrastructure

COMPANY

  • Cold email agency
  • Agency shortlist
  • Agency vs DIY
  • Blog
  • About
  • Start a build

Every figure on this site is a count of work we have done. Pipeline and closed revenue are our clients’ results, and results vary. Replies are shown as they arrived, with senders blurred at source.

01 Deliverability

We build the stack. We do not rent it.

Most agencies run your campaign on somebody else's platform. When it degrades, they have nothing to pull. We own the path from our server to your buyer's inbox.

The stack

Six layers, sized to your volume.

How many domains and how many mailboxes depends entirely on how much you send. The shape stays the same. The count is yours.

  • 01

    Domains

    Lookalikes of your primary, never the primary itself. Your main domain is never the thing at risk.

  • 02

    Mailboxes

    We build them and warm them before anything sends. A cold mailbox poisons a campaign before it starts.

  • 03

    Custom SMTP

    Our own sending path for the bulk of the volume, at a low enough rate per inbox to stay invisible.

  • 04

    Our own servers

    We run the sending infrastructure ourselves rather than reselling somebody else's platform.

  • 05

    Google and Microsoft

    A second and third provider alongside the custom path, so one provider's bad day is not your bad month.

  • 06

    Reserve

    A slice of capacity that never sends. The moment an inbox dips we rotate it out and the send rate does not move.

Warmup

Nothing sends until it is warm.

A new mailbox has no reputation. Send campaign volume through it on day one and the provider decides what you are before the market does.

Weeks 1 to 2TrickleA handful a day, real threads, real replies. The inbox learns to trust it.
Weeks 3 to 5RampVolume climbs only as fast as the reputation does. Never faster.
Week 6 onFull paceNow it carries campaign volume. Skip the first five weeks and it never gets here.

Why reserve exists

A third of it never sends.

Sending Reserve, never sends Dipping, rotated out

Reserve is not caution. If a domain degrades in the middle of a test, capacity swaps in and the send rate does not change.

That is the whole point. Delivery is held constant, so it can never be the thing that explains a result. When a message fails, you know it was the message.

The domains and the mailboxes are registered to you. If we stop working together, the assets stay with you.

Check your own stack

The DNS half, tested in seconds.

Everything on this page about records, you can verify right now. Free, instant, nothing stored.

Full deliverability testSPFDKIMDMARCSpam tells

Next

The rest of the engine.

  • 00The engineA model trained on four million sent emails learned the science of cold email. Subject, length, the right ask per persona. It writes with it.
  • 02Intent signallingAn engine built around your ICP that watches for the moment a company becomes worth contacting.
  • 03Reply agentAn agent trained on your voice, your product and your customers. Every reply answered within 30 minutes.
  • 04MethodDefine the ICPs. Write many variants per ICP. Measure on reply, meeting and close rate. Scale only the one that wins.
  • 05AutomationsWhat happens the second a reply lands. Interested leads reach your CRM and your team without anyone copying anything.
Start a build