Outbox›Campaign 01 · Draft
Request written scope
From
Your name <[email protected]>
Sent by you
To
Named buyer · researched contact context attached
Subject
A specific, inspectable reason to talk

Draft outreach, ready for your line-by-line approval.

Illustrative draft structure. Live copy is source-backed and scoped for one defined B2B offer. No invisible auto-send.

OP
Prepared by the campaign operator named in scopeFor your review · not yet sent
Opening lineHi Jordan, I noticed the handoff between your clinic billing team and external RCM partner.
✓ Approved
Relevance lineThat usually leaves one hard-to-see question: which denied claims are worth a second review?
✓ Approved
Offer lineWe can prepare a bounded evidence review before either side commits to a larger engagement.
• Edit or approve
Next stepWorth sending the one-page scope for you to judge?
✓ Approved
Best,Your nameYour role · your company
This message stays in your hands.You approve every line and send from your own account. Suppressions and the stop decision remain visible in the handoff.
Owner send only
Written scope firstBuyer, channels, exclusions and timing agreed before payment.
$1,500 onceOne campaign handover. No subscription.
No account accessYou keep credentials and sending authority.
No outcome guaranteeReplies, meetings and revenue depend on buyers.
Campaign attachments

The reasoning travels with the copy.

The handoff makes the work inspectable before you send and distinguishable afterward: delivered work stays separate from modeled downstream outcomes.

LIST

Named targets + contact context

Why each account and contact belongs in this campaign, with sources retained for review.

Delivered artifact
COPY

Editable opener + follow-ups

Messages shaped for the agreed channels and the voice source you provide.

Owner approval required
PLAN

Send order + stop path

Cadence, exclusions, suppressions and a sequence that stops properly.

Owner controlled
RPT

Fulfillment report

Approvals, completed work, exclusions and the evidence for deciding whether to run again.

Delivered ≠ modeled
Campaign controls

Plain authority, not automation theater.

The interface can recede because the accountable human and irreversible actions do not.

ApprovalEdit, approve, skip or stop every message before it leaves.
Sending identityThe named sender and owned account appear in the correspondence itself.
PermissionsNo direct account connection is required for this campaign handoff.
SuppressionsExcluded accounts, audiences and claims remain part of the brief and report.
Stop controlThe sequence ends at the agreed cadence, or sooner when you say stop.

One reviewed campaign. One written scope.

The payment link is sent only after inputs, agreed channels, deliverables and engagement window are written into your scope. Payment starts one campaign, not ongoing outreach software.

You approve every lineYou send from your accountNo performance guaranteeFulfillment report included