I'll book you sales meetings with business owners who want what you sell. The first three are free.
You pick the kinds of businesses. I build the list, write the emails and handle every reply, and your team just takes the meetings. You bring no list and no SDR.
A meeting counts when it is booked with a decision-maker at the kind of company you chose and that person shows up. The first three are free, so you can see the quality and decide for yourself.
You see the list and the email copy before anything sends.
Two niches sourced and probed, 2026-09-16
222 companies sourced. 88 of the 130 I could verify came back with a finding.
222
companies sourced
software and marketing agencies, 11 to 50 people, US, sourced on founder and sales titles
130
resolved to a domain I could verify
the other 92 failed the name check and were dropped rather than guessed at
88
carried a finding worth a line
58% of the software companies, 76% of the agencies
137
automated tests, collected 2026-09-16
they do not exercise the probes’ network paths, which is one reason a person still reads every line
How It Works
What happens between your paragraph and the first meeting.
This is what happens after you send me that paragraph.
01
Define
It starts from your paragraph. We turn what you sell and who bought it into a definition a probe can act on: the stack a fit company runs and the roles it hires for.
02
Source
I pull real companies against that definition and resolve a named contact at each one. Address verification fails closed. A bad address is dropped.
03
Probe
Each company is checked from public sources, and which checks run depends on what you sell: the point is a fact that opens a conversation about your offer, not a fact about the company in general. No model runs in this path, so the hundredth company costs what the first one did.
04
Write
The line is a fixed template. The only words that vary are the contact's name and company from the vendor record, and the fields the probe wrote. Nothing else can enter the line. The renderer scans every line for the tells of generated copy and exits with an error on a hit. A person reads every line before it goes to you.
05
Send and book
The emails go out in my name, identified as working for you, from mailboxes on domains set up for your campaign. I read every reply. When an owner is interested, I ask a couple of quick questions and put the meeting on your calendar with a short note.
The part that matters
Every line starts from something a probe found.
A template cannot invent a company. It can still be pointed at the wrong one, and it can still say something true in a way that misleads. So the checks that stop both run before anything reaches you: the identity check that ties a company name to its domain runs before every render, and a claim is only written when the check behind it actually ran and returned something.
Two limits worth knowing before you ask for the meetings. The probes that fire on any domain read email posture: SPF, DMARC, DKIM, and which platforms send as you. Those are the ones behind the numbers above. Others are tuned to a particular kind of company and will not fire on yours, so the set gets rebuilt for your market before anything sends. And a company I cannot resolve to a domain with confidence gets dropped, not guessed at, which is why 92 of the 222 above are not in the count.
Probes also come back empty, and an empty result is reported per company. A company the probes found nothing on gets no finding and no claim. Its line is the plain generic opener, and it is reported to you as a miss.
How many of the last hundred companies you wrote to could you name one true thing about?
Who this is for
Is this for you?
A fit if
You sell to businesses, and a new client is worth a few thousand dollars to you in the first year.
You can name the kinds of businesses you want more of, even if it's one kind in one county.
Someone on your team can take a few meetings a week. I book them; the number you can take sizes the list.
You want to sit in three meetings before you decide anything.
Not yet if
You sell to consumers. The list starts from a company name, so there is nothing to build from.
You want a reply-rate promise. The only numbers I have are my own, and they are on this page.
The software behind it
The Outbound Engine, the system my own pipeline runs through.
Sourcing, address verification, reply triage and the funnel numbers in one system, with a log of why each reply went where it went. Built in your accounts and handed over as code, or run as a managed instance. There is no price on this page; it is scoped on a call.
Every reply is classified under one of seven labels, or flagged unknown and sent to a person: demo request, pain signal, curious, engaged, not interested, unsubscribe, auto-reply. The first four post to Slack the moment they land.
Funnel tracker
The send side pulled live from Instantly, the reply side grouped by label. A prospect who books straight off the calendar link never sends a reply, so reply counts alone undercount meetings; bookings come in by webhook and sit under them. A rate is only computed against emails sent, and it goes blank when the send count is missing.
Booking capture
Calendly bookings land by webhook in your own database, one row per event, signature-checked when the signing key is set.
Deliverability monitor
Flags a domain for rotation when replies sit under 0.7% across 300 or more sends. Bounce warns at 2% and stops at 3%. A mailbox whose warmup switched itself off shows up there too. A person reads the report and decides what rotates.
Sourcing pipeline
Import, dedupe against every contact already in the database, verify each address before it costs you reputation, push, then patch the probe line onto each lead. Today the patch is a second command; wiring it into the push is part of the build.
Audit trail
Every classification is logged with its confidence and a trace id under a client id with its own API key. A second client's replies never mix with yours.
Two parts call a model: the reply classifier, and the fallback opener the push step writes when no probe line exists. The probes and the probe-line renderer make no model calls; each model call is small and logged. Replies route in from Instantly today, and that is the only adapter, so triage and the funnel need your sending to run through it. LinkedIn has no reply hook, so triage there is by hand.
Pricing
You pay per meeting that shows up.
What a meeting costs depends on how many a week your team can take, so I set it on a 15-minute call. The first three are free.
The offer
Sales meetings
Business owners who want what you sell, on your calendar, with a short note on each one.
Per meeting that shows up
the first three are free
You pick the kinds of businesses before anyone is contacted.
I build the list, write the emails and handle every reply. Your team just takes the meetings.
A meeting counts when a decision-maker who agreed to talk shows up. A no-show is not a meeting.
Sending runs from mailboxes on domains set up for your campaign, so your own domain stays out of it.
It depends on how many meetings a week your team can take, so I set the rate on a 15-minute call rather than here. You pay per meeting that shows up, and the first three are free.
Because I can't tell you how your market will respond until I've run it. You sit in three meetings, then decide whether to keep going.
A decision-maker at the kind of company you chose, who agreed to talk about what you sell, at a set time on your calendar. It counts when that person shows up. If they don't show, it isn't a meeting and you don't pay for it.
You do. Roofing contractors, dental offices, trucking companies, law firms, whatever you want more of. You tell me the kinds of businesses and the area before anyone is contacted, and you see the list and the email copy before anything goes out.
No. It's the first thing we work out on the call. Bring what you sell and the names of anyone who has bought it, even if that's two customers.
Yes. Sending is included. Mailboxes go on domains set up for your campaign, sending is matched to where your buyers host their mail, and I read every reply myself. Your own domain stays out of it. If reply rate does not clear 1% across the first 200 sends, sending pauses and the volume moves to LinkedIn while I repair placement.
No model writes the line. The words that vary come from the vendor record (name, company) and from a DNS lookup or a job board's public JSON; the rest is a template I wrote and tested. That is why I can show you where every word came from.
Yes. It gets built in your accounts and handed over as code your team runs, or kept as a managed instance if you would rather not operate it. Either way the probe set is rebuilt for your market first.
Most data vendors gate the API that would automate a list pull, so that step is a web export. The review probe needs a browser, because the review sites block plain requests, so I run it by hand. I re-run the probes before anything goes out. After handover, the person reading the output can be you.
The first three are free
Tell me who you want to meet. I'll book the first three.
Fifteen minutes is enough to settle the kinds of businesses you want and how many meetings a week your team can take.