The published packages: $900 Sprint one-time, $1,900 per month Engine, $2,900 Full Build. No media spend is included or marked up. Payable by card or USDT; the Engine can be cancelled with 14 days notice.

Vertical · local B2B · updated 19 September 2026

Marketing engineer for local B2B

The short answer: in local B2B the buyer pool is finite and countable — a metro area holds a few thousand companies that fit a segment, and roughly three reachable people each. That ceiling changes what the first deliverable should be. One strict two-variant test at a 3% base rate and a +20% relative lift needs 13,914 contacts per arm — 27,828 in total — so the asset that survives the budget is a verified list you own: every company in the segment, with a domain, a named person and a mailbox that answers SMTP. My packages are public: $900 Sprint, $1,900/month Engine, $2,900 Full Build.

Packages and what ships Describe the segment on Telegram

Serving a city, a region or a country — in English, from anywhere.

What changes when the market can be counted

Left: the lever. Middle: what local B2B outbound usually looks like. Right: what it becomes when the buyer pool is treated as a finite number instead of a feed.

Lever	The default in local B2B	What it becomes when the pool is counted
The unit	Leads bought per month from a directory or a marketplace	A row per company: domain, named person, role, mailbox status, source URL, date checked. Nothing without a domain
The asset	The subscription — stop paying and the pipeline stops	The list itself: a file that keeps working after the engagement ends, and keeps its check dates
The ceiling	“Scale the volume”	The enumeration: if the segment is 4,000 companies, the whole market is ~12,000 reachable people — that number caps every test you will ever run here
The first thing shipped	A sequence of emails and a CRM	The enumeration plus a sending domain that passes the deliverability checklist. Sequences before that are noise
The honest verdict date	“We’ll see in a month”	Computed from the enumeration: how much of the pool one arm can fund per month, and what can be read before that

Why a verdict is usually out of reach locally — and what to sell instead

Take a segment of 4,000 companies in one metro. Three reachable people per company gives 12,000 contacts — the entire market. One arm of a strict test needs 13,914. The pool is smaller than the test, and no amount of copywriting fixes arithmetic. Inside 6 months a readable segment needs 4,638 contacts a month; inside 3 months, 9,276. Most local segments sit far below both lines.

What is readable at local volumes is the diagnostic, and it is worth real money: 300–500 verified sends against a clean list measure whether the mailbox exists, whether the domain survives, and which of two angles gets replies. That is a decision you can act on inside three weeks, and it costs one arm of nothing. What is not readable at that volume is which variant wins on a 20% lift — so it is not promised. The rule that follows, the same one I put in writing for every engagement: declare the volume, run one variable, stop at the limit.

What that means in practice:

A list you can open: company, domain, person, role, mailbox status, source URL, date checked.
A sending setup that survives: SPF, DKIM, DMARC checked on the domain before the first send.
Two angles and a stop rule written before the test starts, with the volume limit named.
A reply log you keep: what was sent, what bounced, what answered, what it cost per reply.

If the segment is too small even for a diagnostic, the honest answer is a different geography or a different channel — and that answer is free. Ask on Telegram.

What ships in the first working weeks

Enumeration of the segment

Every company that fits the definition, with a domain and a source URL. The count is reported before the outreach starts — that number is the whole campaign’s ceiling, and you should see it on day one.

People and mailboxes

Named decision-makers with roles, then SMTP checks on the addresses: does the mailbox exist, is it a role address, is it a catch-all. Only checked rows go into the sending list.

Sending domain that passes the checklist

SPF, DKIM, DMARC, a warm-up schedule and a send ceiling per day. Cold outbound starts after this, never before it.

Two angles, one variable, a kill rule

Two sequences that differ in one thing, a declared volume limit and an explicit stop condition. The rule is written down before the first send.

Read-out and the file

A read-out of what was read and what was killed, plus the list and the log in a format you own. The subscription ends; the file stays.

Artefacts you can open before paying

Offer and packages — what each fixed package buys, and the scope behind the number.
Proof page — every shipped artefact with a link that opens.
Cases — what the work looked like in practice, with live pages.
npm package — the free tooling published under my name, installable with one command.
Articles on dev.to — the method written out, canonical back to this site.

The four decisions taken before the first contact

Decision	Why it cannot wait
Geography and segment definition	It sets the ceiling. A definition written as “small businesses nearby” cannot be counted, cannot be checked, and cannot be re-used next quarter
Who counts as a buyer	Owner, operations manager or procurement changes the list by a factor of two, and changes the angle completely
The unit you will judge	Replies per 300 checked contacts is readable in three weeks. Revenue per segment is not readable in a quarter at local volumes
The stop condition	Written before the send. Without it, every null result becomes a request for another month

Questions people ask before starting

Is a local B2B list really worth paying for?

Yes, and for the opposite reason to a big database: it cannot be resold to your competitors. Every row has a domain, a source URL and a date checked, so the same file can be re-checked in three months and still be right. A purchased list at local scale is usually two years stale by the time it reaches you.

Do you guarantee a number of leads?

No. What is guaranteed is the enumeration count reported before outreach, the checking of every address before sending, the published packages, and the kill rule written in advance. Anyone guaranteeing local B2B lead volume at a fixed price is selling a discount on their own credibility.

How big does the segment have to be?

For a diagnostic, 300–500 verified contacts is enough. For a statistical verdict on a 20% lift you need 13,914 per arm — 27,828 in total — which in one metro is usually the entire market. Below that line, buy the list and the kill rule, not a promise of significance.

Can this run next to an existing agency or a sales team?

Yes, and it usually should. The sales team keeps the calls and the relationships; this work produces the enumerated list, the verified mailboxes, the two angles and the reply log that tells the team which segment is worth a phone call at all.

What does it cost?

The published packages: $900 Sprint (one-time, the first live artefacts), $1,900/month Engine (the loop running month over month), $2,900 Full Build (the whole system plus handover). No media spend is included or marked up. Payable by card or USDT; the Engine can be cancelled with 14 days notice.

What do you need from me to start?

One sentence on the product, the geography you can serve, and the last thing you tried. The first answer is the honest ceiling of the segment — if it cannot fund a read-out, I will say so before taking the work.

Name the segment. I’ll tell you what can be read.

Send the segment and the geography. You get a straight answer on the countable ceiling, what a list of it would contain, and what could be judged inside three weeks.

Message on Telegram

Packages · Pricing · Scope · Proof

Marketing engineer for SaaS — the first successful call as the readable unit, and the volume a verdict needs.
Marketing engineer for agencies — white-label work, a floor per client, and the smallest client readable inside 6 months.
Marketing engineer for B2B — the general B2B case: lists, verification and the stop rule before the spend.
Done-for-you lead generation — what actually ships, and what is not promised.
Distribution service — making published work get read instead of buried.
Marketing automation engineer — capture, routing, suppression and alerts for the leads you already have.