Method

This is a working research record, not diligence and not legal advice. It was built on 5 October 2026 to answer one question from the ground up: what does the cold email software market look like to someone building a new platform in it, and where can that platform win?

#How it was built

Fifteen research passes ran in parallel. Each pass had a defined brief and a fixed list of pages to write. The passes covered:

• Instantly and Smartlead, plus the category's history.
• The volume challengers.
• The classic sequencers.
• The suites and enterprise tools.
• The AI wave.
• Inbox infrastructure.
• Deliverability.
• Global law.
• European law.
• Data and multichannel.
• Economics and pricing.
• Customers and distribution.
• Sending features.
• Workflow features.
• Technical architecture.

Each pass saved raw notes with every source URL to research/. Each set of notes ends with three sections: openings spotted, contradictions and unverified claims. Each pass then wrote its pages to a shared house style (AUTHORING.md).

Three synthesis passes followed. The first read all fifteen sets of notes and wrote the thirteen openings, each scored on six axes. The second compiled the Contradictions register, the Open questions and the Glossary. The third wrote the build plan and The read.

A consistency edit closed the loop. It resolved the cross-page conflicts the contradictions register found. One example: two pages had claimed German B2B email works on "presumed consent". It does not; see Germany. Each change is logged at the foot of Contradictions register.

An independent fact-check came last. A separate pass that had not written any page re-fetched the sources behind 52 load-bearing claims. It confirmed 44, corrected 7, and logged every grade in Verification log.

#Where the evidence comes from

• Vendor pricing pages, help centres, API docs and changelogs. These are the most reliable source for features, limits and prices, and the least reliable for traction claims. The pricing table and the feature matrix are built almost entirely from them.
• Founder posts, podcasts and interviews. These are where most revenue figures come from. Each one is labelled as claimed.
• Third-party estimates. GetLatka, Sacra and arr.club appear often and disagree often. They are always labelled as estimates.
• Primary law. Statutes, regulator decisions (FTC, CRTC, CNIL, ICO) and court rulings, plus law-firm country guides (DLA Piper, ICLG) for the country matrices.
• Mailbox-provider documentation. Google, Yahoo and Microsoft sender guidelines and admin documentation.
• Review sites. Trustpilot and G2, sampled for Customer voice.

The sources page lists every external link the hub cites, grouped by domain.

#Known biases and holes

• Private companies disclose nothing. Every volume sequencer is private and almost all are bootstrapped. Revenue, customer counts and margins are claims or estimates.
• Prices move monthly. Instantly raised its entry plan 27% in August 2026; EmailBison raised its plan in early 2026. Every price on the hub carries its date.
• Provider enforcement is unannounced. Google did not comment on its autumn 2025 suspensions, so Provider crackdowns rests on vendor and practitioner reports.
• Some pages are thinner than others. The Open questions page ranks the gaps that would most change the build decision.

Every page carries a confidence mark for the evidence, not the opinion: high, medium, low or contested.

#How to grow it

The hub is designed to be added to page by page:

1. Add a page. Write a markdown file in content/ with the frontmatter in AUTHORING.md. Add its slug to PAGES.md. It appears in its section index, search, backlinks and the sources page automatically.
2. Update a price. Edit data/pricing.json. Feature matrix rows live in data/features-*.json; any new features-*.json file is merged in.
3. Run npm run check before building. It validates frontmatter, sections, wikilinks, callouts, manifest coverage and JSON.
4. Log it in Changelog.

Good next passes are listed at the top of Open questions: customer interviews with agencies, a controlled deliverability test on owned infrastructure, a German-law opinion on the EU-native compliant outbound rule engine, and a CASA quote for OAuth verification and the end of basic auth.