What happens today
The patchwork
- A shared spreadsheet nobody opens on time
- Prompts copy-pasted into a chat window
- A contractor who disappears for two weeks
- Output that lands in a different shape every run
Builder playbook
Research leads overnight
Skip three hours of Monday-morning research.
- 6 min read
- Intermediate
- 4 moves
- Updated weekly
The number
Your sales team opens Monday to a ready-to-go list with background on every prospect.
3hr → 8min
The situation
From a patchwork that breaks to a workflow that ships.
Drop in a list of prospect companies on Sunday night. Builder visits each website, finds the right person on LinkedIn, checks if they look like the kind of buyer you want, and writes a personalised opener for each one.
With Builder
The workflow
- One brief, one cadence, one place to read it
- Every claim cited, every step reviewable
- A finished artifact in your team’s format
- Your sales team opens Monday to a ready-to-go list with background on every prospect.
How the work moves
Four moves.
Builder runs each move with a preview attached, so you know what lands before you ever hit send. Skip freely once you know which parts carry the weight.
Builder at work
One brief travels through the whole job. Context stays attached until the finished work lands.
Kickoff
Upload your list of companies. A spreadsheet or straight from HubSpot.
Builder starts with the brief and asks only for what's missing. No boilerplate intake form, no setup meeting.
Gather
Tell Builder what your best customers look like.
Sources are pulled, cleaned, and cross-checked against prior runs, every claim carries a citation you can trace.
Reason
Connect LinkedIn and your CRM.
The agent thinks out loud where it matters. Trade-offs named, assumptions surfaced, judgments explained.
Draft
Schedule it weekly. Review the results. Send the emails.
A first draft lands in the format your team already uses. You edit the last 10%, not the first 90%.
Prompts worth keeping
Paste these into Builder.
Three prompts, a kickoff, a full run, and a packaging pass. Copy the one that matches the phase you're in. Rewrite any detail to fit your business.
Kick it off
You are Builder. I want to research leads overnight: Drop in a list of prospect companies on Sunday night. Builder visits each website, finds the right person on LinkedIn, checks if they look like the kind of buyer you want, and writes a personalised opener for each one. My goal: Your sales team opens Monday to a ready-to-go list with background on every prospect. Walk me through the first move and tell me what you need from me.
Run it in one shot
Run the full playbook end-to-end: Upload your list of companies: a spreadsheet or straight from HubSpot. Tell Builder what your best customers look like. Connect LinkedIn and your CRM. Schedule it weekly. Review the results. Send the emails. Ask before skipping any step. Show work as you go.
Package the output
Deliver the output as a single brief I can share with the team: lead with "3hr → 8min", then the receipts. Call out anything that changed assumptions mid-run.
What goes in. What comes back.
Inputs in, outputs out.
Builder runs on the inputs on the left and hands back the artifacts on the right. Skip any input, the agent will ask for it the first time it needs it.
Give it
- One source of truth (CSV, CRM, or warehouse)
- A one-paragraph brief on the goal
- The KPI you want to move
Get back
- A scored, cited brief you can forward
- A structured file for downstream automation
- An alert when anything material changes
The finished artifact
A finished artifact, not a todo list.
Every run ends the same way, a packaged brief in the channel your team already reads. Here's a preview of what shows up.
Builder → your team
Research leads overnight, ready for review
playbooks
Mon 7:03 AM
Here's the brief for this week. I ran the playbook end-to-end, flagged anything that shifted against last run, and packaged the output for Slack and the shared drive.
- Upload your list of companies: a spreadsheet or straight from HubSpot.
- Tell Builder what your best customers look like.
- Connect LinkedIn and your CRM.
- Schedule it weekly. Review the results. Send the emails.
What moved
3hr → 8min
Your sales team opens Monday to a ready-to-go list with background on every prospect.
briefing.pdf · sheet.csv · slides.key
Before you run it
Where teams stall.
Three ways we see this go sideways and how to avoid each one.
Keep judgment with the team. The playbook should make the work clearer, not hide the assumptions behind it.
- Pointing the agent at stale or half-connected data. Clean the source once, compound every run after.
- Running it once and forgetting. Put it on a weekly cadence so the numbers actually move.
- Skipping the first review. Check the first run by hand, trust compounds from there.
Questions
Before you start.
Usually one source is enough to see value. Builder can run on a CSV paste for the first pass; connect the CRM, the data warehouse, or the tool of record once you want it to run on its own.
Weekly is the sweet spot: schedule it for Sunday night so the list is waiting Monday morning. You can trigger an ad-hoc run any time a new batch of accounts lands, but the numbers only move once it is on a standing cadence.
Sales or RevOps owns it. The output is a ready-to-send list, so the SDR or AE who works the accounts is the natural owner; RevOps keeps the ICP definition and connected sources clean so every run stays sharp.
Review the first run by hand and tune the ICP description: that one edit fixes most misses. Builder learns from what you keep and what you drop, so quality compounds from the second run on.
