Fourteen days of outbound, with the days written down before you pay

Sourcing from structured fields

The rule that keeps the segment honest is where the domain comes from. It has to sit in a field the owner filled in, not be extracted out of prose: a company registry's website, a package's projectUrl or homepage_uri, a repository's homepage, a launch post's canonical link. The last pass added 138 companies from two package registries (483 candidates checked live, 29% survived the product test). Slower to collect than a scraped list, and the reason less of it bounces back.

Verification before any send

Domains folded to their root, duplicates collapsed, rows without a domain dropped, each host fetched live, each address matched to the domain it claims, then an SMTP check. What does not survive is handed over as a separate file with the reason attached, so the count is auditable: you can see which column shrank and why.

Copy and sending infrastructure

A sending domain that is not your main one, warmed in the open, with SPF, DKIM and DMARC in place. Two or three touches, written for the segment rather than for the template. No purchased contact lists are mixed in: if a row is not in the working file, it is not in the batch.

Sends and the read-out

The batch goes out and replies are worked as they arrive. The read-out counts replies and conversations, not opens. It is written to be forwardable as it is: what was sent, to whom, what came back, and what the next cycle would change.

It is

• A segment of companies you can inspect, each with the source it came from.
• Addresses matched to their own domain and SMTP-checked before sending.
• Infrastructure warmed under a domain you control, so the setup stays with you.
• Copy written for one segment and one offer, not a template library.
• A read-out at the end, plus the working file and the method behind it.

It is not

• Not a guarantee of meetings. Reply rate depends on the segment and the offer, and it is measured, not assumed.
• Not sending from your main domain. If deliverability is damaged, it is damaged in a domain built for this.
• Not a scraped list with invented addresses: a row that cannot be traced to a source field does not enter.
• Not a retainer in disguise. Fourteen days, one batch, one read-out; continuing is a separate decision.
• Not a channel that reads your inbox: replies arrive at an address you can see at any time.

What exactly is handed over at the end of the fourteen days?

The working file (every row with its source column), the sending domain with its DNS records warmed in the client's name, the copy that went out, and a read-out counting replies and conversations with the next cycle's changes written down. The method is not withheld: the sourcing rule and the drop reasons are part of the read-out.

Do you send from my main domain?

No. The batch goes out from a separate sending domain that is warmed in the open, with SPF, DKIM and DMARC configured. If deliverability is going to be damaged, it is damaged in a domain built for outbound, never in the one the company answers email on.

What if the reply rate is zero?

Then the read-out says zero, and the reason is in the data rather than in an excuse: which family the segment came from, how many addresses survived the SMTP check, what was delivered and what bounced. A zero is a result. What it is not is a refund of the setup work, because the segment, the warm domain and the file stay with the client.

Which markets and languages can the pilot run in?

English-language segments are the default because the sourcing covers English-language sources: company directories, package registries, hiring threads and launch posts. A segment is built for one market at a time; running two markets in one fourteen-day pilot halves the volume in each.

Can the pilot run white-label for my agency?

Yes. The same run is available under an agency's own brand, at the same published cost basis, with the client relationship, the margin and the deliverable belonging to the agency. Exclusivity is agreed per vertical and per sending domain before the first run.