Short answer: this playbook shows how Main Direct applies its own supply layer to itself. It is a methodology artifact, not a campaign log, customer case study or promise of replies.
Rule: a supply system is credible only if it can describe the route from market signal to validated contact without hiding the quality gates.
1. Target definition
Main Direct is useful to teams that already have a market but suffer after the send decision: stale lists, ambiguous titles, weak domain resolution, missing liveness checks, unsafe primary-domain sending or unstructured replies.
- Primary audience: technical founders and revenue leaders running professional B2B outreach.
- Secondary audience: fundraising teams that need investor-relevant filters rather than generic investor lists.
- Disqualifiers: consumer marketing, sensitive targeting, unlawful campaigns, purchased-list refresh requests, guaranteed-meeting requests.
2. Signal queues
A contact enters research only when at least one current, public signal can be stated.
- Fund or buyer publicly shifts thesis, stack or geography.
- A company launches, migrates, audits or expands into a new market.
- A competitor raises, is acquired or leaves a category gap.
- A hiring signal exposes a scaling or infrastructure bottleneck.
- A public post describes an outreach, deliverability or data-quality problem.
3. Audience filters
Each audience is stored as a filter set, not as a paragraph of intentions.
| Layer | Example filter | Failure mode prevented |
|---|---|---|
| Company category | B2B software or technical service company | Consumer or irrelevant outreach |
| Role family | Founder, GTM lead, RevOps, infrastructure lead | Titles without decision context |
| Geography | Approved market only | Jurisdictions outside campaign scope |
| Signal | Recent launch, hiring, migration or public thesis | Undated generic interest |
| Disqualifier | Guaranteed-result expectation, consumer list, unlawful use | Misaligned buyer |
4. Domain and contact resolution
The company name is resolved to an operating domain before person-level enrichment. This prevents a person from being attached to an unrelated subsidiary, legacy domain or lookalike company.
5. Validation gates
- Mailbox route check.
- Role and employer consistency.
- Independent profile or public-source cross-check.
- Duplicate and suppression review.
- Freshness timestamp.
- Final supply/readiness decision.
6. First-touch architecture
The first 80 words must answer why now, what changes, what is true today, why this recipient and what the low-friction next step is. The message is a diagnostic, not a volume test.
7. Operating output
The working output is not only a CSV. It is the route by which a row earned access to a campaign.
- Audience definitions and disqualifiers.
- Filter set used for retrieval.
- Validation and freshness state.
- Public evidence link.
- Suppression state.
- Next action and owner.
8. Boundary
This page does not expose private research, client data or a real contact export. It also does not promise replies, meetings, revenue, inbox placement or legal compliance.