Skip to content
Rivet

How an engagement works.

From a 30-minute review to a system your team runs on its own. Every step ends with something in writing.

Three steps to start.

  1. 1

    Book a 30-minute review

    We map your revenue line and the places it breaks most. You get an honest answer on whether we're the right fit.

  2. 2

    Get a written scope

    Which system, which accounts, what you approve and how success is reviewed. Fixed before any work starts.

  3. 3

    Build, run, hand over

    We build in your accounts, review it with you weekly, then hand it over across 30 days.

Five phases, one written outcome each.

Hover a phase to see what happens and what you walk away with.

  1. Day one

    Diagnose

    A 30-minute review of your pipeline, from first touch to retention.

    You get: A written map of where it breaks and what we'd fix first.

  2. Before any work

    Scope

    We agree which systems to build, in which accounts, and how success is reviewed.

    You get: A fixed scope and price, in writing.

  3. In your accounts

    Build

    Data, targeting, sending, reply handling and CRM records set up in your accounts. New domains warm up for 2–4 weeks in parallel.

    You get: A working system, approved by you before it goes live.

  4. Every week

    Run

    Agents do the daily work. A named operator reviews it with you every week.

    You get: A weekly report on what moved and what's next.

  5. Final 30 days

    Hand over

    Documentation, a walkthrough and overlap while your team takes over.

    You get: A system your team runs without us.

What an engagement looks like over time.

Phases overlap. Domains warm up while we build, and handover starts while the system is already running.

  1. Diagnose
    30-minute review
  2. Scope
    Signed by you
  3. Build
    In your accounts
  4. Domain warm-up
    Outbound only
  5. Run
    Weekly review with your operator
  6. Hand over
    Final 30 days

A typical shape, not a promise. Your written scope sets the actual dates.

A person approves every step that matters.

Agents do the repeatable work. These four gates are where a person signs off before anything reaches a buyer.

Approval logYour campaign
  1. ICP and signal listIn review

    Your ICP and signal list are approved once per segment.

  2. New templatesWaiting

    Every new template is approved before its first send.

  3. First 30 daysWaiting

    Every message in a campaign's first 30 days is reviewed before it goes out.

  4. After day 30Waiting

    A weekly sample is reviewed. Any flagged message is pulled.

Who works on your system.

A small, named team, with you as the approver at the end of the line.

  1. Lead operator

    Owns your scope, runs the weekly review and is the name you call.

  2. Systems engineer

    Builds the data flows, sending setup, CRM rules and automations in your accounts.

  3. Agent operator

    Tunes the agents that research, draft, sort replies and update records, and checks their output.

  4. You

    Approve the ICP, templates and anything that reaches a buyer. You own every account.

What the agents do, and what they never do.

Agents handle the repeatable work inside your accounts. Rules set what they can touch, and a person decides anything that reaches a buyer.

Agents do

  1. 1Find accounts and check them against your approved ICP
  2. 2Research each account before anything is written
  3. 3Draft messages from templates you approved
  4. 4Sort replies and route them to the right person
  5. 5Update CRM records as the work happens
  6. 6Put together the weekly report

Agents never

  • Send wording you haven't approved
  • Answer pricing, complaints or legal questions
  • Contact anyone who has opted out
  • Change your pipeline rules on their own
  • Keep your data in accounts we own
  • Make a sales decision for your team

Agent work is recorded where your team can review it, and the weekly report shows what was done and what was approved.

See agents in pipeline generationSee agents in sales and CRM systemSee agents in revenue operations

Six commitments, in writing before we start.

Every engagement runs on the same promises. They're in the scope you sign, not on a sales slide.

Scope of work

Our commitments to you

  • A fixed scope, agreed before any work begins
  • Everything built in accounts in your name
  • No new template goes live without your approval
  • A person handles every sensitive reply
  • A weekly report from a named operator
  • An honest answer if we're not the right fit
Your signature
RivetFor Rivet
Handover overlap while your team takes over
30 days
Domain warm-up before any sending volume
2–4 wks
Approval gates before anything reaches a buyer
4
Accounts held in our name
0

What you get at handover.

Over the final 30 days, day-to-day running moves from us to your team. The goal is a system you run without us.

Who runs the system30-day handover
Rivet
Your team
Day 1Day 30
  • DocumentationEvery workflow, rule and integration written down in plain language.
  • A walkthroughWe show your team how to adjust targeting, templates and reports.
  • Everything in your nameDomains, inboxes, CRM records and copy stay in your accounts.
  • 30 days of overlapWe stay alongside your team while they take over day-to-day running.

Common questions about the process

Is this a one-time project or an ongoing retainer?
A one-time build. We scope it, build it, run it alongside your team and hand it over. If you'd like us to keep operating it afterwards we can, but the system doesn't depend on us to keep working.
How long until it's live?
Your written scope includes the timeline. New domains and inboxes need a 2–4 week warm-up before sending starts, and we run that in parallel with the rest of the build.
Do we still need a salesperson?
Yes. The system finds the accounts, starts the conversations and books the meetings. Your team takes those meetings and closes the deals.
Will AI-written outreach hurt our brand?
Not without a person seeing it first. You approve every new template before it sends, every message is reviewed for the first 30 days, and after that a weekly sample is checked. Any flagged message is pulled.
Who owns the accounts, data and workflows?
You do. Domains, inboxes, CRM records, campaign copy and the workflows we build all live in your accounts. Tools such as Clay and your sending platform are licensed to you directly.
What happens after the handover?
The system keeps running in your accounts. Your team has the documentation and the walkthrough to adjust targeting, templates and reports on their own.

Start with phase one.

Phase one is a 30-minute review. You'll leave with a written map of where your pipeline breaks.

Book a 30-minute review