The engine
First signal to first invoice.
Every box below is something that runs without a person in it. This is the map we walk clients through on a call, rebuilt as a page: five stages in order, each one readable, then the whole thing at once.
Stage 01
Outbound Sales
Eighteen buying signals in four groups, six of them scraper-led and invisible to most agencies. When one fires, the account is enriched into one record through a waterfall of providers, contacted across email and LinkedIn, and every reply is read and classified into one of six statuses.
The decisions this stage makes
- Which signal fired, and whether it is worth reaching this account now
- Which of six statuses the reply belongs to, and where that status routes
- When an out-of-office or not-now should re-enter the sequence
A booked meeting hands the deal to Discovery Call.
Data Captured and Enriched
Prospect Contacted
Prospect Responds
Lead Status Changed
Interested
Information request
Out of office
Not now
Unqualified
Do not contact
Message Replied To
Send Booking Link
Contact, Company, Deal Created in CRM
18 buying signals in four groups
Competitor, account, buyer, fit
TriggerSystem stateDecisionPositive pathNegative path
Cut from the full map. Scroll sideways on a phone.Stage 02
Discovery Call
Reminders go out the day before and the day of the call. Then two gates: did the call happen, and did it qualify. A no at the first gate asks whether it was rescheduled and, if not, drops the prospect into an automatic reactivation sequence. A yes at the second writes the transcript, the close likelihood and an estimated deal date into the CRM.
The decisions this stage makes
- Did the call happen, and if not, was it rescheduled
- Did it qualify, which decides whether the deal moves or returns to outbound
- What the transcript says the close likelihood and deal date should be
A qualified discovery call books the Demo. An unqualified one lands in Closed Lost with its reason.
Reminders Sent
Reminders Sent
Did the call happen?
Yes
No
Was the call qualified?
Yes
No
Was it rescheduled?
Yes
No
Marked as Qualified in CRM
Transcript and Notes Added to CRM
Closed Won Likelihood Added to CRM
Follow-Up Email Drafted and Sent
TriggerSystem stateDecisionPositive pathNegative path
Cut from the full map. Scroll sideways on a phone.Stage 03
Demo
The same two-gate shape as discovery, one stage further along. A qualified demo moves the deal to the demo-complete stage, adds the new transcript, raises the closed-won likelihood and recalculates the deal date. Nobody types any of it.
The decisions this stage makes
- Was the demo booked, or does it need rescheduling
- Was it qualified, which moves the stage and the forecast
- What the follow-up says, drafted from the transcript
A qualified demo moves to Closed Won. An unqualified one to Closed Lost.
Was the demo booked?
Yes
No
Was it rescheduled?
Yes
No
Was it qualified?
Yes
No
Moved to Demo Complete Stage
New Transcript and Notes Added to CRM
Increased Closed Won Likelihood in CRM
Follow-Up Email Drafted and Sent
TriggerSystem stateDecisionPositive pathNegative path
Cut from the full map. Scroll sideways on a phone.Stage 04
Closed Won
Billing details collected, contract generated, signature chased until it lands, contract stored, stage moved, first invoice generated and sent. The only lane where nobody has to remember to follow up, which is the lane where forgetting costs the most.
The decisions this stage makes
- Has the contract been signed, and if not, when to remind
- When the first invoice goes out
First signal to first invoice, with no person in the loop.
Collect Billing Details
Generate Contracts
Contract signed?
Yes
No
Send Reminders
Store Contract in CRM
Move to Closed Won
Generate First Invoice
Send First Invoice
TriggerSystem stateDecisionPositive pathNegative path
Cut from the full map. Scroll sideways on a phone.Stage 05
Closed Lost
Every loss lands here, and the reason is the pivot. Budget cut, champion left, lost to a competitor, missing feature, too early, timing: each one arms a live trigger from the outbound stage. When the condition changes, the account re-enters outbound on the same reactivation path already used for out-of-office and not-now replies. The map is a loop, not a funnel.
The decisions this stage makes
- Which loss reason applies, written from the transcript
- Which live trigger that reason arms
- When the trigger fires, and the account goes back to outbound
A fired trigger re-enrolls the account in the outbound reactivation campaign.
Transcript and Notes Added to CRM
Closed Lost Reason Added
Marked as Closed Lost in CRM
Loss reason picks the trigger that reopens it
BudgetFunding raised
Champion leftNew decision-maker hired
Lost to a competitorCompetitor repriced or acquired
Missing featureTech stack change
Too earlyHeadcount growth by department
TimingThe date already calculated
Reactivation Trigger Armed
TriggerSystem stateDecisionPositive pathNegative path
Cut from the full map. Scroll sideways on a phone.Closed lost, still watched
Shaking the tree, not burning the bridge.
When a deal dies, the loss reason becomes the trigger. Budget cut, champion left, wrong timing. The system keeps watching. When the condition changes, the account re-enters outbound on the same reactivation path already used for out-of-office and not-now replies.
Each record carries the prospect's LinkedIn profile, their company's LinkedIn page and the company website.
Closed-lost ledgerWatching
- Priya Raman, VP Revenue Operations at Verimark Health. Reason on record. Lost reason: Budget cut for the quarter. New signal 02 Aug: Raised $10M Series A. Action: Enroll in funding campaign.
- Daniel Osei, Head of Growth at Northbeam Logistics. No reason on record. Lost reason: Four touches, nothing back. New signal 29 Jul: Visited your site, checked out pricing page. Action: Enroll in pricing-page visit campaign.
- Sofia Lindqvist, Chief Revenue Officer at Halden Robotics. Reason on record. Lost reason: Champion left mid-cycle. New signal 11 Aug: Hired a new VP Sales from Stripe. Action: Enroll in new decision-maker campaign.
- Tomas Vieira, Director of Demand Generation at Cindermill Analytics. No reason on record. Lost reason: Six touches across email and LinkedIn. New signal 18 Aug: Liked and commented on your post about outbound. Action: Enroll in post-engagement campaign.
- Aisha Nakamura, VP Sales at Larkspur Freight. Reason on record. Lost reason: Went with a competitor. New signal 03 Aug: Competitor raised mid-tier pricing 18%. Action: Enroll in competitor campaign.
- Elias Brandt, Head of Revenue Operations at Steelyard Interactive. No reason on record. Lost reason: Sequence completed, no reply. New signal 21 Aug: Hiring for CISO; JD cites SOC-2. Action: Enroll in hiring campaign.
- Marta Kowalczyk, Director of Sales Operations at Ravenna Bioworks. Reason on record. Lost reason: Missing a feature they needed. New signal 09 Aug: Switched from HubSpot to Salesforce last week. Action: Enroll in tech-stack change campaign.
- Owen Achebe, VP Marketing at Pinecrest Labs. Reason on record. Lost reason: Too early for them. New signal 16 Aug: RevOps team grew from 4 to 11 in six months. Action: Enroll in headcount-growth campaign.
- Hannah Iversen, Chief Operating Officer at Wexford Systems. Reason on record. Lost reason: Not now, revisit after the migration. New signal 01 Sep: Revisit date hit: migration marked complete in their CRM. Action: Enroll in reactivation campaign.
Illustrative records. People and companies are fictional.
Zoom out
The whole map, at once.
Every node from the five stages above, with the connectors between them. Pan, zoom, and hover a tool family to see where it is used. On a phone, read it as a list.
Written walkthrough
60%
TriggerEnrichmentSystem stateDecisionPositive pathNegative pathTime marker
Tool families
The engine, stage by stage
The same system as the map, written out in order. Every step below runs without a person in it, and every branch has somewhere to go.
Outbound Sales
Eighteen triggers in four groups, enriched into one record, worked across email and LinkedIn, then routed on how the prospect replies.
Competitor signals
Custom-builtScraper-led. The six signals most agencies cannot detect.
- Follows a competitor pageAnchor, Firecrawl, Apify, n8n
- Commented on their postAnchor, Firecrawl, Apify, n8n
- New connection of their repAnchor, Firecrawl, Apify, RapidAPI
- Competitor testimonial postedAnchor, Firecrawl, Apify, Clay
- Named on a competitor siteAnchor, Firecrawl, Apify, Clay
- Competitor repriced or acquiredAnchor, Firecrawl, Apify, n8n
Account signals
What the target company did.
- Hiring for rolesClay, RapidAPI, n8n
- New decision-maker hiredClay, LinkedIn, BlitzAPI
- Funding raisedClay, BlitzAPI, n8n
- Tech stack changeClay, n8n
- Product or pricing changeAnchor, Firecrawl, Apify, n8n
- Headcount growth by departmentClay, LinkedIn, RapidAPI
- Compliance milestoneClay, Anchor, Firecrawl, Apify
Buyer signals
What a specific person did.
- Engaged with your postRapidAPI, n8n
- Champion changed jobsClay, LinkedIn, BlitzAPI
- Attending an eventClay, Anchor, Firecrawl, Apify
- Deanonymized site visitClay, MoltSets, n8n
Fit signals
Not an event. A scored resemblance to your best customers.
- Lookalike to best customersClay, Prospeo, DiscoLike
- 01Enrichment
Data Captured and Enriched
ClayLinkedInBlitzAPIMoltSetsRapidAPI
Prospeo
Findymail
Icypeas
ZeroBounceGPT-5.4 NanoGLM 5.2DeepSeek V4 FlashThen Prospect Contacted
- 02System state
Prospect Contacted
ClayHeyReach (LinkedIn)Smartlead (email)Instantly (email)VapiGPT-5.4 MiniClaude Sonnet 5
Kimi K3GLM 5.2DeepSeek V4 ProThen Prospect Responds
- 03Trigger
Prospect Responds
GPT-5.4 NanoGLM 5.2DeepSeek V4 FlashThen Lead Status Changed
- 04System state
Lead Status Changed
ClayHeyReach (LinkedIn)Smartlead (email)Instantly (email)- InterestedGoes to Message Replied To
- Information requestGoes to Message Replied To
- Out of officeGoes to Days Between Today and Return Date Calculated
- Not nowGoes to Days Between Today and Reactivation Date Calculated
- UnqualifiedGoes to Prospect Marked as Unqualified
- Do not contactGoes to Prospect Marked as Do Not Contact
- 05Positive path
Message Replied To
ClayHeyReach (LinkedIn)Smartlead (email)Instantly (email)Then Send Booking Link
- 06System state
Message Replied To
ClayHeyReach (LinkedIn)Smartlead (email)Instantly (email)One-pager, case studies, deckThen Send Booking Link
- 07System state
Days Between Today and Return Date Calculated
ClayGPT-5.4 NanoDeepSeek V4 FlashfxDaysThen Prospect Re-enrolled in Campaign
- 08System state
Days Between Today and Reactivation Date Calculated
ClayGPT-5.4 NanoDeepSeek V4 FlashfxDaysThen Prospect Enrolled in Reactivation Campaign
- 09Negative path
Prospect Marked as Unqualified
ClayHeyReach (LinkedIn)Smartlead (email)Instantly (email)Then Removed from Campaign
- 10Negative path
Prospect Marked as Do Not Contact
ClayHeyReach (LinkedIn)Smartlead (email)Instantly (email)Then Removed from Campaign
- 11Positive path
Send Booking Link
DefaultCalendlyCal.comThen Contact, Company, Deal Created in CRM
- 12System state
Prospect Re-enrolled in Campaign
ClayHeyReach (LinkedIn)Smartlead (email)Instantly (email) - 13System state
Prospect Enrolled in Reactivation Campaign
ClayHeyReach (LinkedIn)Smartlead (email)Instantly (email)Also the re-entry point for closed-lost accounts
- 14Negative path
Removed from Campaign
- 15Positive path
Contact, Company, Deal Created in CRM
ClayZeroAttioHubSpotThen Team Updated
- 16Positive path
Team Updated
Clay
SlackThen Reminders Sent in Discovery Call
Discovery Call
Reminders on a schedule, then two gates. Whether the call happened, and whether it qualified. Everything after either gate writes itself into the CRM.
- 01Time marker
Day before call
Then Reminders Sent
- 02Trigger
Reminders Sent
DefaultCalendlyCal.comHeyReach (LinkedIn)Smartlead (email)Instantly (email)Then Reminders Sent
- 03Time marker
Day of call
Then Reminders Sent
- 04Trigger
Reminders Sent
DefaultCalendlyCal.comHeyReach (LinkedIn)Smartlead (email)Instantly (email)Then Did the call happen?
- 05Decision
Did the call happen?
- YesGoes to Was the call qualified?
- NoGoes to Was it rescheduled?
- 06Decision
Was the call qualified?
- YesGoes to Marked as Qualified in CRM
- NoGoes to Transcript and Notes Added to CRM in Closed Lost
- 07Decision
Was it rescheduled?
- YesGoes to Reminders Sent
- NoGoes to Auto-Reactivation Sequence
- 08System state
Auto-Reactivation Sequence
ClayHeyReach (LinkedIn)Smartlead (email)Instantly (email)Re-enters outbound
- 09Positive path
Marked as Qualified in CRM
ClayZeroAttioHubSpotThen Transcript and Notes Added to CRM
- 10Positive path
Transcript and Notes Added to CRM
ClayZeroAttioHubSpotFireflies
Granola
FathomThen Closed Won Likelihood Added to CRM
- 11Positive path
Closed Won Likelihood Added to CRM
ClayZeroAttioHubSpotFirefliesGranolaFathomThen Estimated Deal Date Auto-Calculated
- 12Positive path
Estimated Deal Date Auto-Calculated
ClayZeroAttioHubSpotFirefliesGranolaFathomThen Follow-Up Email Drafted and Sent
- 13Positive path
Follow-Up Email Drafted and Sent
ClaySmartlead (email)Instantly (email)GPT-5.4 MiniClaude Sonnet 5Kimi K3GLM 5.2DeepSeek V4 ProFirefliesGranolaFathomOne-pager, deckThen Was the demo booked? in Demo
Demo
The same two-gate shape as discovery, one stage further along. A qualified demo moves the deal and updates the forecast without anyone typing.
- 01Decision
Was the demo booked?
- YesGoes to Was it qualified?
- NoGoes to Was it rescheduled?
- 02Decision
Was it rescheduled?
- YesGoes to Was it qualified?
- NoGoes to Auto-Reactivation Sequence
- 03System state
Auto-Reactivation Sequence
ClayHeyReach (LinkedIn)Smartlead (email)Instantly (email)Re-enters outbound
- 04Decision
Was it qualified?
- YesGoes to Moved to Demo Complete Stage
- NoGoes to Transcript and Notes Added to CRM in Closed Lost
- 05Positive path
Moved to Demo Complete Stage
ClayZeroAttioHubSpotThen New Transcript and Notes Added to CRM
- 06Positive path
New Transcript and Notes Added to CRM
ClayZeroAttioHubSpotFirefliesGranolaFathomThen Increased Closed Won Likelihood in CRM
- 07Positive path
Increased Closed Won Likelihood in CRM
ClayZeroAttioHubSpotFirefliesGranolaFathomThen Estimated Deal Date Auto-Calculated
- 08Positive path
Estimated Deal Date Auto-Calculated
ClayZeroAttioHubSpotFirefliesGranolaFathomThen Follow-Up Email Drafted and Sent
- 09Positive path
Follow-Up Email Drafted and Sent
ClaySmartlead (email)Instantly (email)GPT-5.4 MiniClaude Sonnet 5Kimi K3GLM 5.2DeepSeek V4 ProFirefliesGranolaFathomThen Collect Billing Details in Closed Won
Closed Won
Billing, contract, signature chase, then the first invoice. The only lane where nobody has to remember to follow up.
- 01Positive path
Collect Billing Details
ClaySmartlead (email)Instantly (email)DeepSeek V4 FlashThen Generate Contracts
- 02Positive path
Generate Contracts
ClayPandaDocDocusignThen Contract signed?
- 03Decision
Contract signed?
- YesGoes to Store Contract in CRM
- NoGoes to Send Reminders
- 04System state
Send Reminders
ClayHeyReach (LinkedIn)Smartlead (email)Instantly (email)Then Contract signed?
- 05Positive path
Store Contract in CRM
ClayPandaDocDocusignThen Move to Closed Won
- 06Positive path
Move to Closed Won
ClayZeroAttioHubSpotThen Generate First Invoice
- 07Positive path
Generate First Invoice
ClayStripeThen Send First Invoice
- 08Positive path
Send First Invoice
ClayStripe
Closed Lost
Every loss lands here, and the reason is the pivot. It picks which live trigger reopens the account, so the map is a loop rather than a funnel.
- 01Negative path
Transcript and Notes Added to CRM
ClayZeroAttioHubSpotFirefliesGranolaFathomThen Closed Lost Reason Added
- 02Negative path
Closed Lost Reason Added
ClayZeroAttioHubSpotFirefliesGranolaFathomThen Follow-Up Email Drafted and Sent
- 03Negative path
Follow-Up Email Drafted and Sent
ClayHeyReach (LinkedIn)Smartlead (email)Instantly (email)GPT-5.4 MiniClaude Sonnet 5Kimi K3GLM 5.2DeepSeek V4 ProThen Marked as Closed Lost in CRM
- 04Negative path
Marked as Closed Lost in CRM
ClayZeroAttioHubSpotThen Loss reason picks the trigger that reopens it
- 05Decision
Loss reason picks the trigger that reopens it
- BudgetFunding raised
- Champion leftNew decision-maker hired
- Lost to a competitorCompetitor repriced or acquired
- Missing featureTech stack change
- Too earlyHeadcount growth by department
- TimingThe date already calculated
Then Reactivation Trigger Armed
- 06System state
Reactivation Trigger Armed
Clayn8nAnchorFirecrawlApifyThen Prospect Enrolled in Reactivation Campaign in Outbound Sales. The loss reason arms a live trigger and the account re-enters outbound
The full map is a 4,400-pixel-wide diagram, so it opens on a laptop or desktop. The five stages above are the same system, cut to fit a phone.
How the build runs
Three months to get there. Then we keep it there.
The map is where you end up, not where you start. Getting there is a three-month build with a defined end. Keeping it there is a different job, and it is the one most systems die from.
The buildTypically three months
- 01
Current state review
We go through the revenue stack you already have and check what is true in the data, then trace one lead from first touch to closed won. The gaps show up in that trace: fields nobody fills, two sources of truth for the same number, handoffs that only work when someone remembers.
You get A build list ranked by revenue impact. Every item has an owner, its prerequisites, and a definition of done.
- 02
System design
We write down how you sell before we automate any of it. What counts as a lead, when it becomes qualified, who owns it, where it routes, what happens when it goes quiet. That becomes the data model: objects, properties, stage rules, scoring, and the triggers that fire off them.
You get A blueprint with nothing left to interpretation. If this appears, that happens, every time.
- 03
Build and launch
We build it in HubSpot or Attio, with Clay running enrichment and list logic and n8n running orchestration and alerts. Routing, scoring, sequencing, dashboards, QA and documentation ship together. This is the point where the map starts running on your data.
You get A production system your team can use in week one without being walked through it.
Then we run itFor as long as you want us on it
Data decays, sequences go stale, and routing rules stop matching how you sell. We watch data quality, enrichment accuracy, routing drift, and scoring calibration, then ship small changes on a steady cadence with a rollback path on each one.
Some clients are into a second year. Others take the system in-house sooner, which is the point of building it properly. The handover happens whenever you ask for it, and the documentation is written as we go rather than assembled at the end.
Show us your current outbound and we will mark up this map with what is missing.
Thirty minutes with Macklin. We do it live on the call, and you keep the marked-up map either way.
Book a CallOr email macklin@harochi.io
Macklin Buckler, Co-Founder. Takes the first call on every engagement.