Full-cycle outbound sequences that triple reply rate.
Builder’s outreach agent runs end-to-end cold email: it segments the list, writes personalised openers referencing each prospect’s recent news, schedules sends at peak times, auto-follows up non-openers on day 3 and 7, and escalates warm replies to a human rep. Reply rate triples; SDR capacity holds flat.
Run Builder- 1
Describe the task
Builder can run a full outbound cold-email motion end to end: segment the list, write openers that reference each prospect’s recent news, send at each segment’s peak window, follow up non-openers on day 3 and 7, and hand warm replies to a human rep. The same headcount runs a much larger, better-timed sequence.
The clearer your segments and your handoff rule, the better the sequence performs. Tell Builder how to segment, what a warm reply looks like, and when to stop chasing, and it will run each persona’s track on its own cadence without stepping on your reps.
Run a cold-email sequence against prospects.csv (~4,000 contacts). Steps: - Segment by persona and industry (see personas.md) - For each contact, write a personalised opener referencing a specific recent signal (funding, launch, hire, post) - Send each segment at its peak open window - Follow up non-openers on day 3 and day 7, new angle each time, not a bump - Detect warm replies (interested, question, "who handles this?") and escalate to a human rep immediately - Suppress anyone who unsubscribes or bounces Cap it at 3 touches. Report reply rate, warm replies, and unsubscribes by segment.
- 2
Give Builder context
Point the run at your prospect list, connect the sending mailbox and your CRM, and give Builder a persona doc so each segment gets its own angle. Builder writes and sends against your domain’s sending limits and warms the cadence so volume doesn’t torch deliverability.
Be explicit about the escalation rule. "Warm reply" means different things to different teams, spell out what should land in a rep’s inbox versus what Builder can handle (an out-of-office, a "not now") so nothing warm slips through and nothing trivial interrupts a closer.
Required contextA prospect list with name, email, company and at least one enrichment field to personalise onA connected sending mailbox and a rule for what counts as a warm reply worth escalatingOptional contextA persona document, so each segment gets its own angle instead of one generic templateA CRM connector (HubSpot or Salesforce), so replies and statuses sync back automaticallySend-window preferences per segment, if you already know when each audience opensprospects.csvpersonas.mdHubSpot (optional) - 3
What Builder creates
Builder segments the list, drafts and sends each track, follows up non-openers with a fresh angle, and pulls warm replies out into a rep’s queue in real time. You get a live sequence plus a per-segment scoreboard showing reply rate, warm replies and unsubscribes, so you can see which persona and angle is actually landing.
From Builder: Ran a 3-touch sequence against 3,914 deliverable contacts from prospects.csv.
3.1×Reply rate vs prior baseline214Warm replies escalated0.4%Unsubscribe rateTop-performing segments214 warm repliesSegment Contacts Reply rate Best-performing angle Ops leads, apparel DTC 862 9.2% Referenced their recent 3PL switch Founders, home goods 744 7.8% Referenced a new retail partnership Growth leads, beauty 691 6.5% Referenced a just-launched subscription line Needs a new angle2 segmentsSegment Contacts Reply rate Note Marketing, general retail 918 2.1% Opener too generic, no strong recent signal to hook Ops, food & bev 699 2.4% Peak send window looks off, most opens came late evening "The apparel-DTC segment is carrying the sequence at 9.2%, general-retail is dragging at 2.1% because there’s no strong signal to reference. Want me to rewrite that segment’s opener around a different hook, or pause it and reallocate the volume to the segments that are landing?"
- 4
Follow-up prompts
Sync replies and statuses into HubSpot
With HubSpot connected, Builder logs every send, open and reply against the contact record and moves warm replies into a dedicated pipeline stage, so reps work them without leaving the CRM.
Sync this sequence to HubSpot: log each touch as an activity, and move any contact that sends a warm reply into the "Outbound, Warm" pipeline stage assigned to a round-robin rep.
Rewrite the underperforming segment
When a segment stalls, Builder can rebuild just that track, new hook, new angle, new send window, without touching the segments that are already converting.
Rewrite the "Marketing, general retail" segment around a pain-point hook instead of a recent-news hook, and move its send window to Tuesday 10am. Leave the other segments as-is.
Turn it into an always-on runbook
Once the segments and cadence perform, save the setup as a Builder saved runbook so every new batch of prospects drops into the same tested sequence automatically.
Save this as a runbook called "outbound-sequence-v1" and run it automatically against any new rows added to prospects.csv, using the same segmentation and 3-touch cadence.
- 5
Tips and troubleshooting
A fresh angle beats a "just bumping this"
Follow-ups that only say "checking in" get ignored. Tell Builder to change the angle each touch, a new signal, a different pain point, a short case reference, so day 3 and day 7 earn their own opens instead of annoying the inbox.
Protect deliverability with volume caps
Blasting 4,000 emails from a cold domain tanks your sender reputation. Let Builder warm the cadence and stay under your daily sending limit, a slightly slower ramp keeps the whole sequence out of spam folders.
Make the escalation rule unambiguous
If "warm" is vague, reps either get flooded or miss real interest. Spell out exactly what escalates, a question, a "who owns this?", explicit interest, and let Builder auto-handle the out-of-offices and soft no’s.
Ready to try it yourself?
Hand Builder the list, the personas and one escalation rule, and it runs a personalised, well-timed outbound sequence that triples reply rate while your closers only ever see the warm ones.
Run Builder