Cold email stopped working for a structural reason rather than a creative one. The filtering happens before a human is involved, which means a better subject line is an optimisation applied downstream of the thing that actually killed the channel. Contact forms get read because the filtering there still happens after a person has looked. This post is about why that gap exists, and about how quickly it could close.
01Cold email is filtered before a human sees it
Three filters run in series on any cold email, and only the last of them is a person.
- The provider. Reputation scoring, authentication checks and bulk heuristics decide whether the message reaches an inbox at all, and the sender rarely learns which test it failed or that it failed one.
- The tooling built to defeat the provider. Warmup services, rotating domains and inbox rotation exist because the first filter works, and the fingerprint they leave is itself something the first filter reads.
- The recipient. Anyone in a buying role has seen the same seven openings this week and can classify a message in under a second without reading a word of it.
Each of those is a response to volume, and none of them can be fixed by writing better, because none of them read the writing. That is the uncomfortable thing about the advice industry around cold email: it optimises the one stage that was never the bottleneck.
We are not making a deliverability argument here, and we should be plain about why. Knockwire does not send email. We have no warmup pool, no sending domains and no opinion worth paying for about inbox placement.
02A contact form lands in a queue somebody is paid to watch
The economics on the receiving side are different in one specific way. The form is an inbound channel, so the company built a process around it before anyone external ever used it.
A contact form submission is normally routed to sales, to support, or to a shared address with a named owner. Somebody has clearing it in their job description. There is often a response time attached, because the same form is where a prospective customer holding a purchase order also arrives.
That is the whole mechanism. Not that forms are special, but that ignoring the queue is a performance problem for the person who owns it, whereas ignoring a cold inbox is what competence looks like.
The second order effect matters more than the first. On a form, the message is read by a human before it is classified. On email, it is classified before it is read. Plenty of what we send is still classified as not relevant, and that is a fair outcome. It is being decided by a person, though, and a person can be wrong in your favour.
03The scarcity is the asset, and it is borrowed
Here is the part that does not flatter us. This works because the volume is low. If every outbound team pointed a sequencer at contact forms next quarter, the queue would grow a filter, then a challenge, then a triage rule sending anything unrecognised to a folder nobody opens. The channel would become email, on a slower clock.
So the honest position is that the advantage is borrowed from every company that has not yet decided to automate this, and the only way to keep it is to send less than the pipeline could technically justify.
This is not altruism, it is self interest with a longer horizon than a quarter. In six months of running this against our own business we read 4,182 companies and delivered 11 knocks. A tool built to deliver four thousand would produce a better looking dashboard for about a year and then destroy the reason the channel worked.
It also sets the standard for what goes in the message. If the count is small, every one has to carry a reason the recipient recognises as their own problem. Scarcity on the sending side is what makes that affordable to write.
04What a legitimate door is, and what it is not
We use "door" for a usable public contact route, and the definition is narrower than "a page with a form on it".
- Published by the company on its own site, for the purpose of being contacted by people who are not already customers.
- Reachable without an account, a login, or an existing ticket number.
- Routed somewhere with an owner. A general enquiries form beats a form whose destination nobody inside the company can name.
- Free of a challenge that says, in the only language a form has, that automated submissions are not welcome here.
What is not a door: a support portal for existing customers, a ticketing system behind authentication, a careers form, a press address for journalists, a partner application. Each of those states a purpose in writing. A message that ignores the stated purpose is precisely the behaviour that earned this whole category its reception.
Which brings us to CAPTCHAs, and it is worth being exact about the reasoning. A CAPTCHA is not a technical obstacle standing between us and a message we are entitled to deliver. It is the company saying that it wants a human on the other end. Treating that statement as a puzzle to be solved is how outreach tooling acquired its reputation, and solving it would make every other claim on this page worthless.
So we do not bypass CAPTCHAs or bot detection. A job that meets one parks in needs_review for a person to look at, which is the designed behaviour rather than a fallback. Over six months, 122 companies cleared fit and timing and were then turned down for having no legitimate door. We did not write to any of them by some other route.
05Why we cap sending per domain
Every tenant has a per domain cap and a suppression list, and both are enforced before delivery rather than reported afterwards.
The cap exists for three reasons and only one of them is about the recipient. The first is returns: a second message into the same domain inside a short window converts worse than the first, so the marginal value of volume into one company goes negative quickly. The second is the commons. The queue we depend on is a shared resource, and the fastest way to lose it is to be the sender who caused a triage rule to be written. The third is failure containment: when a pass returns forty plausible companies that all turn out to belong to one parent, a cap is the only thing standing between enthusiasm and a pattern.
Drafts that would breach a cap stay drafts. They are visible, they are counted, and they are not delivered. A draft is not a knock, and we never report one as the other, because the moment those two numbers merge the honest ones become impossible to find.
The summary is unglamorous. We chose the contact form because the recipient picked the address, somebody is paid to read what arrives there, and the volume is still low enough that one specific message stands out against the background. The first two of those are durable. The third is not, it belongs to everyone using the channel, and 11 knocks in six months is what treating it carefully looks like in practice.