Outbound that starts with a reason to write.
Find a trigger. Check fit. Draft a short note. Hold the bad ones. Send only the ones worth sending. The page should feel like an active queue, not a sales brochure.
The message is the output of the system, not the headline of it.
Source → read → score → draft → stop if the fit is weak.
The system finds companies, reads the trigger, scores fit, and stops if the fit is weak. The note is short because the system did the work first.
Short opener. One question. No campaign fluff.
The strongest wedges are the ones with a clear trigger and a small ask. That is enough.
Hi — noticed a few missed calls and no treatment plan follow-up on the site. Worth a quick look at the reply path?
Send only if the clinic has a real front desk, a clear website, and recent signal that suggests active demand.
Why it works: the trigger is visible and the ask is tiny.
Hi — saw the after-hours window and thought I’d ask whether urgent enquiries are being routed to a live reply path yet.
Hold if the practice looks too small, has no obvious urgent demand, or is not likely to benefit from a live triage lane.
Why it works: one opener, one question, one obvious reason to write.
Hi — saw the tax season pages and wondered if late payer chase or self-assessment reminders are still manual there.
Hold generic firms. Send only when the fit is strong enough that a simple, practical email feels useful.
Why it works: the message matches a concrete job, not a promo campaign.
The page should show why a prospect was blocked.
Generic, weak-fit, or noisy accounts stay in hold or kill. That keeps the writing plain-text in feel and the queue honest.
- real trigger
- strong fit
- short opener
- weak signal
- generic company
- not enough context
- bad fit
- no trigger
- too noisy to touch
Tech-only or managed.
Keep the numbers grounded and the outcome framing concrete. Teams can run the engine themselves, or let the board run it.
Run the engine in-house.
Best when someone on the team owns the queue and wants the tooling, not the service.
Let the board run it.
Best when the queue needs weekly oversight, reply review, and steady output.
One clean run: 42 prospects → 11 held → 14 replied.
tech-only: the team owns the queue and the sends.
The human reply routes to CLOSER.
Positive intent gets logged, the thread moves on, and the next step lands back in the queue.
Outbound should feel like a queue with rules, not a blast tool.
That is the point of Prospect Stack: visible fit checks, clear hold logic, and a short note that only gets sent when the system earns it.