How it all fits
The inbound-led outbound engine
Content creates the demand. Signals set the priority. People advance the sale.
By Mike Hurley, founder of WarmUp. This is the system we run on ourselves. Capture, qualification, suppression, routing and the record are live; the weekly signal report and the automated Tier 3 nurture lane are drawn and not yet built.
Version 1.0. Last updated . About 8 minutes.
- Motion
- Inbound
- Channel
- LinkedIn, Website
- Steps
- 8
- Tools
- Apify, Freckle
The inbound-led outbound engine: the route
In order: what we make, what catches the response to it, one qualification step and one suppression step, then three tiers. Tier 1 and Tier 2 go to a person; Tier 3 goes to a sequence. Everything is written to the CRM, and the loop sends what the rep hears back to the start as next week's content. Each part is drawn in full beside its step under "How to build it". Go to the steps in detail
Signal creation
- What we make
- Daily GTM Standup
- Guide Library
- Money Pages
- Reddit, Founder Voice
- Reviews & Directories
- What we make
Signal capture
- One step per source
- LinkedIn Engagement
- Website Visitor ID
- Forms & Downloads
- YouTube Viewers
- Neglected CRM Inbound
- One step per source
Qualification
- Freckle
Scored against the ICP
- Freckle
Suppression
- Suppression and Ownership
- Open opportunities excluded
- Current clients excluded
- Recent activity carve-out
- Deduped against the book
- Single owner field
- Suppression and Ownership
Routing
Action
- The rep
Human judgment on every touch
Goes to: HubSpot
- Automated Nurture
Drawn, not yet built
Goes to: Weekly Signal Report
- The rep
System of record
- HubSpot
Accounts and contacts
Goes to: Weekly Signal Report
- Weekly Signal Report
Drawn, not yet built
- HubSpot
The loop: Sends what the rep hears back to the start as next week's content.
- Signal flow
- Qualified routing
- Worked by rep
- Reply promotes the record
- Written to system of record
- The loop
- Dashed box: drawn, not yet built
The same system we sell, pointed at ourselves
The client version of this engine assumed signal sources already existed. This version builds them. Same qualification, suppression, and routing layer as every deployment we sell.
- Dogfood is the demo
- This exact system is in the open guide library, the sales demo, and the proof point. When it books meetings, the case study writes itself.
- Two things swap per client
- Signal sources swap and the CRM swaps. Scoring, suppression, ownership, tiering, routing, and reporting carry over unchanged.
- The gates hold
- Agents draft, Mike posts, the rep works the tiers. Nothing external ships unattended. Numbers come from the scorecard, never invented.
Download the boardOpen it full sizeOne sheet, free to keep and share.
Why it helps
Most companies I talk to already create engagement. A founder posts, a page gets read, a video gets watched, someone fills in a form and never hears back. Almost all of it disappears, because nothing is watching it and nothing is deciding what it means. The sales team, meanwhile, works a cold list.
This engine closes that gap. It treats every reaction, visit, download and reply as a signal, puts each one through the same qualification and suppression it would apply to a cold account, and then routes it by tier so the warmest, best-fit people are in front of a rep the same day with the reason attached. The cold motion does not go away; it becomes the fallback instead of the whole job.
It is also the system we sell, pointed at ourselves. The client version assumed signal sources already existed. Ours builds them, because a founder's own content is the cheapest signal source there is. The qualification, suppression and routing layer is the same one in every deployment, which is why this guide can be specific about it.
The sources
Signal creation is the content: a short standup video most days, the open guide library, pages written to answer the questions buyers put to search engines and AI assistants, long-form teardowns, and reviews on the directories AI engines cite. Signal capture is one step per source. Our live ones are LinkedIn engagement (reactions, comments and reposts on our own posts and on posts from a few companies we watch, collected by Apify running through Freckle) and the site's own forms and booking page, where the source field now includes AI search. Identified website visitors and video viewers are drawn on the board and added the same way: one capture step each, the same shape downstream.
The three tiers
| Tier | What it means and who touches it |
|---|---|
| Tier 1, hot | An active signal on a high-fit account. The rep works it the same day: a call or a message, with the signal and the full engagement history already in front of them. |
| Tier 2, warm | Engaged and worth a touch. A sequence that references the signal: email, LinkedIn or a call, each on its own sender. A person still writes the first message. |
| Tier 3, fits, no signal yet | Today's cold motion, demoted to the fallback. A nurture sequence, never worked blind. A reply or a fresh signal promotes the record to Tier 2. |
Why we built it this way
- Build the signal sources; do not wait for them. The client version of this engine assumed signals already existed. For a small company they usually do not, and a founder's own content is the cheapest source to build. The standup, the guides and the search pages are on the board as parts of the system, not as marketing beside it.
- One qualification step, one suppression step, whatever the source. A warm signal is tempting to act on without checking. It is still scored against the same ICP facts and the same segments as a cold account, and suppression still runs first: open opportunities, current clients, recent activity, duplicates in the book. Warmth sets the priority, not the rules.
- Two things swap per client. Everything else carries over. Signal sources swap, and the CRM swaps. Scoring, suppression, ownership, tiering, routing and reporting are the same layer in every deployment, which is what makes the engine repeatable rather than a one-off.
- A reply promotes the record. Nothing else changes a tier. Fit belongs to the account. Timing belongs to the signal. A reply or a fresh signal moves a record up a tier; a sequence finishing, or time passing, never moves it down past where its fit puts it.
- The gates hold. Agents draft, a person posts, the rep works Tier 1 and Tier 2 by hand. Nothing external ships unattended, and every number on the report comes from the scorecard, never from memory.
- The loop is the content calendar. The questions a rep hears on calls and in discovery are next week's standups and guides. Replies and new engagement come back in at the left as signals. The engine feeds itself, so there is no separate content plan to maintain.
How to build it
- Make something, on a schedule you can keep. A short video most days, one open guide a week, or pages that answer the questions your buyers ask. The schedule matters more than the format: capture needs a steady stream to watch.
Daily GTM Standup
A few minutes, most days: the real build of the day. One recording becomes a LinkedIn post and a note on warmup.ai.
Guide Library
Open guides on warmup.ai/library: the diagram, the steps and a spec to copy. Nothing asks for an email.
Money Pages
Cost, comparison, and definitional pages built for search and AI answers (SEO/AEO).
Reddit, Founder Voice
Teardowns with the ugly parts left in. 30 min/week. Cited by AI answer engines.
Reviews & Directories
Clutch reviews and the Clay expert directory. Corroboration AI engines trust.
- Add one capture step per source. Start with the source you already have. For LinkedIn, a collector that runs on a schedule and returns everyone who reacted, commented or reposted. For the site, make sure every form carries a source field that includes AI search.
LinkedIn Engagement
Apify, through Freckle: reactions, comments and reposts on Mike's posts and the accounts we watch.
Website Visitor ID
RB2B: company and person-level traffic on guides and money pages.
Forms & Downloads
Contact forms and book-a-call. Source attribution includes "AI Search (ChatGPT, Claude)".
YouTube Viewers
UTM-tagged links from descriptions and the rep's outreach back to warmup.ai.
Neglected CRM Inbound
Aged, never-worked, no-shows, closed-lost sitting in HubSpot.
Out: Every captured signal passes through one qualification step and one suppression step. - Qualify every captured person and company the same way. Identify the company, enrich the few facts your ICP needs, score the fit, and store it in a database you own. A workflow builder does this in one step; the CRM gets the result, not the work.
Freckle
Scored against the ICP (four facts, five segments). Clay and our own database hold the facts. Reads and writes HubSpot.
- Suppress before anyone decides. Open opportunities out. Current clients out. Anyone with recent activity out, and anyone already in the book deduplicated. One owner field, so two people never work the same record.
Suppression and Ownership
Open opportunities excluded. Current clients excluded. Recent activity carve-out. Deduped against the book. Single owner field.
- Route into three tiers. Hot, warm, and fits-with-no-signal. Write the tier and the reason on the record so the rep sees why, not just who.
Tier 1
Hot: active signal, high fit
The rep works it same day: a call or a DM with the signal and the full engagement history attached.
Tier 2
Warm: engaged, worth a touch
A sequence that references the signal: email in Smartlead, LinkedIn in HeyReach, calls in Salesfinity.
Tier 3
Fits ICP, no signal yet
Today's cold motion, demoted to fallback. A reply or new signal promotes to Tier 2.
- Give each tier one kind of touch. Tier 1 is a person the same day. Tier 2 is a sequence that references the signal, with a person writing the first message. Tier 3 is a nurture sequence that is never worked blind.
The rep
Works Tier 1 and Tier 2 with the signal and full engagement history already in front of them: calls, DMs, and replies. Human judgment on every touch.
Drawn, not yet built
Automated Nurture
Smartlead email and HeyReach LinkedIn sequences for Tier 3. A reply or a fresh signal promotes it to Tier 2. Never worked blind.
- Write everything to the CRM. Every signal, score, source and tier goes on the account and the contact. Let your sender-sync tool write activity back, so the CRM is the record even though it is not the brain.
HubSpot
Accounts and contacts. Every signal, score, source, and tier written back to the record. OutboundSync writes sender activity back. Form attribution includes AI Search.
- Close the loop with a weekly report and next week's content. Who engaged, how they scored, what was worked, what booked, and what each source is worth. Then take the questions the rep heard and make next week's content from them.
Drawn, not yet built
Weekly Signal Report
Who engaged, how they scored, what was worked, what booked, and what each source is worth. Scorecard numbers only.
The loop
Questions from the rep's calls and discovery become next week's standups and guides. Replies and fresh signals promote records up a tier. The engine feeds itself.
Copy this
The tier and suppression rules
The rules the routing step applies to every signal, whatever its source. The tools in the comments are the examples we use; the rules are the part to copy.
# engine.yaml
suppress_first: # runs before any tier is assigned
- open_opportunity # anyone with a live deal
- current_client
- recent_activity: 14d # touched by anyone in the last two weeks
- duplicate_in_book # same company or person already owned
- do_not_contact # one list, one writer
owner: single_field # a record has one owner or none
tiers:
tier_1:
when: [fit: high, signal: active]
touch: person_same_day # a call or a message, history attached
tier_2:
when: [fit: ok, signal: engaged]
touch: sequence_with_signal # person writes the first message
senders: {email: one, linkedin: one, calls: one}
tier_3:
when: [fit: ok, signal: none]
touch: nurture_sequence # never worked blind
promote:
- on: reply -> up one tier
- on: fresh_signal -> up one tier
demote: never_below_fit # a tier can rise on timing; fit sets the floor
record:
write: [signal, score, source, tier, reason] # on the account and the contact
activity_back: sender_sync # the senders write their own activity into the CRM
loop:
weekly_report: [who engaged, how they scored, what was worked, what booked, source value]
next_content: questions the rep heard this weekThe same guide as plain Markdown, for an agent or a notes app: /library/inbound-led-outbound-engine.md
Words we use
- Signal:
- Something a company or a person did that gives a reason to reach out now: a job posting, a funding round, a visit to your site, a click on an ad, a contract award, a compliance date, an expansion, a comment on a post, a form, a reply.
- Tier:
- The rank a company holds on the map because of its fit. A signal moves a company up inside its tier and never changes the tier.
- Fit and timing:
- Two separate numbers. Fit is how well a company matches who we sell to, and it belongs to the account. Timing is how fresh the signal is, and it fades.
- Queue:
- The one ordered list a rep works from, with a score and a reason to call beside each name.
- Sender:
- A tool that delivers messages or calls on one channel: email, LinkedIn or the phone.
- Blocklist:
- The companies and people we must never contact. One tool writes it, and every sender reads the same copy.
- Router:
- The one step every signal passes through. It matches the signal to a company and a person and puts it in one shape before anything acts on it.
From the GTM standup
Want this engine pointed at your own content?
We build it in your tools and run it with your team.
30 minutes to scope it. Engagements are contracted through WarmUp, Inc.