AnchorWorks ← The Briefing Room On the record
AnchorWorks
Executive Brief 021 · July 8, 2026

The Outbound Machine

system introduction
Prepared by Chris Campbell AnchorWorks
The Briefing Room · 2026
  • SMS consent gate§ Executive Decisions · Decision Log

    SMS consent gate hardened: a text goes only to a number the owner handed over, or after a written yes to a specific number — a positive email reply alone is not consent.

  • Repo governance§ Executive Decisions · Decision Log

    Repo governance: the outbound-machine repo holds playbooks and logs only; lead data and credentials never enter git, enforced by gitignore.

  • Copy voice division§ Executive Decisions · Decision Log

    Copy voice division locked: AI delivers skeletons, angles, merge logic, and compliance rails; Chris writes every customer-facing word. AI copy is never final.

See every standing order in the SOP Library →
01 · Executive Summary

The executive summary.

In a day and a half, AnchorWorks went from a one-page outbound SOP to a complete, evidence-backed market-contact system: a 17-agent research operation (~401 sources, every load-bearing claim adversarially fact-checked), an execution plan that survived three hostile reviews, a full outreach runbook awaiting the founder's voice, a governed private repo with an agent boot file, a brand-perfect interactive training site deployed to Cloudflare Pages, a live infrastructure audit that found A2P texting registration already approved, and Texas Wave-1 landed — 16,031 licensed HVAC companies with owner names, at a data cost of zero dollars.

Why it matters: July's constraint review named the company's binding constraint plainly — zero market contact. This machine is the fix, built the AnchorWorks way: Door #2 of the Four Lead Sources run as an installed system rather than a heroic effort, every decision written down, every number sourced, every risk gated. It is also the Category King ground war made operational — by Halloween the phrase "Revenue Engine" will have landed in tens of thousands of HVAC inboxes in the company's own voice.

The company now owns its first repeatable market-contact system: 30,000 doors mapped, the first 251 loaded, and every word, rule, and number written down where the team can run it without the founder.

Current stage: Launch — foundation poured in June; market contact begins now.

02 · Executive Decisions · Decision Log

What was decided.

  • Texas first — dominate one state before touching the next; the TDLR bulk license file makes TX the cheapest owner-name spine in America.

    locked

  • Territories locked: Chris — Sun Belt West (TX·CA·AZ) · Ethan — Southeast+NY (FL·GA·NC·SC·NY) · Les — Mid-Atlantic/Midwest (VA·PA·OH·IL·MI). A territory means build, QA, and every reply from those rows.

    locked

  • Copy voice division locked: AI delivers skeletons, angles, merge logic, and compliance rails; Chris writes every customer-facing word. AI copy is never final.

    locked

  • SMS consent gate hardened: a text goes only to a number the owner handed over, or after a written yes to a specific number — a positive email reply alone is not consent.

    locked

  • Repo governance: the outbound-machine repo holds playbooks and logs only; lead data and credentials never enter git, enforced by gitignore.

    locked

  • Facebook Page DMs tentatively approved as the second-channel fallback ("HVAC guys live on Facebook") — manual, founder profiles only; cold-opener scope expansion still awaits an explicit ruling.

    locked

  • Franchise and national rows stay on the master list, tagged and deprioritized — tags are angles, never filters (locked doctrine held under pressure).

    locked

  • Full-list detection passes (ServiceTitan, ad presence) stay call-gated at reactive tier — credit discipline beats curiosity until a flag ruling says otherwise.

    locked
03 · Major Accomplishments

What was done.

01Phase 1 · The Evidence Layer

The problemA high-ticket outbound campaign was about to be built on industry folklore — stale limits, secondhand prices, and legal "common knowledge" that changes yearly.
What was doneDecision: Run a 17-agent research fleet across seven lanes (Predictable Revenue, deliverability, Clay economics, LinkedIn, SMS/TCPA, competitor GTM, list sources) plus two gap lanes — then adversarially fact-check every load-bearing claim before believing it. Implementation: ~401 primary-source lookups; independent verifiers killed a fabricated HVAC case study, corrected the famous misattributed "Predictable Revenue email template," and refreshed stale 2024 pricing before any of it touched strategy. Dependencies: None — self-contained; feeds every downstream phase.
The impactEvery number in the plan traces to a source; the team can be shown WHY the strategy is sound, not asked to trust it. The offer economics ($15k / $50–100k LTV) clear Aaron Ross's outbound viability bar 2.5–5x — verified, not assumed.

02Phase 2 + 3 · Plan and Playbook

The problemPlans written by one mind ship one mind's blind spots — and outbound blind spots cost domains, deliverability, and statutory damages.
What was doneDecision: Every major deliverable faces hostile review before the founder sees it: independent critics for SOP compliance, quantitative consistency, and operator usability. Implementation: The execution plan absorbed 52 findings (including an honest month-one math correction); the outreach runbook absorbed 40 more — the biggest catch being a first-touch email that promised a per-state report cut that doesn't exist yet. Caught before a single send, not after. Dependencies: Runbook copy awaits Chris's voice pass and §11 sign-off — by design; the words are the founder's lane.
The impactThe company's first campaign whose failure modes were hunted in advance: send ramps with gates, deterministic template selection, CAN-SPAM on every touch, and a funnel model that tells the truth about month one.

03The Machine's Home

The problemThree operators on three machines running AI agents in parallel is how the 140-days-unread failure happens again — unless the knowledge travels with the work.
What was doneDecision: A private GitHub repo (anchorworkshq/outbound-machine) as the department's shared brain, with a CLAUDE.md boot file so every agent session on any machine starts already knowing the locked rules, territories, and red lines. Implementation: SOP, research, plan, runbook, and agent handoff versioned; daily self-check logs committed per operator; an interactive brand-exact training site (three competing designs, founder picked the winner) deployed to Cloudflare Pages, auto-updating on every push. Dependencies: Collaborator invites (Ethan, Les); Cloudflare Access lock + training.myanchorworks.com pending Chris's clicks.
The impactOnboarding an operator is now three commands; the training page makes the whole system teachable in twenty minutes; institutional memory can't walk out the door. This is also the reusable template for every future department page.

04Ground Truth · The Infrastructure Audit

The problemThe plan assumed "five warmed domains" and an A2P registration to-do — assumptions, not audits, and outbound dies on assumptions.
What was doneDecision: Audit the live accounts (Reply.io, Cloudflare, GoHighLevel) in the browser before Day 1, and write findings into the plan as verified fact. Implementation: Found: 3 sending domains with 9 warm Google inboxes and zero sends ever; 14 owned domains inventoried (5 spares for the cold pool, 2 protected); A2P 10DLC brand and campaign already Approved since May 5 with a verified number — an entire prerequisite deleted. Also surfaced: 5 of 9 mailboxes still carry unknown sender identities from a prior arrangement. Dependencies: Mailbox renames + password rotation; warmup-history confirmation with Ethan; domains 4–5 into warmup this week.
The impactWeek-one capacity is nearly double the plan's assumption; SMS is legally ready months early; and a real security question (who holds credentials?) got asked before pipeline value existed to lose.

05Texas, Day One

The problemOwner names are the most expensive field in B2B data — and the field the whole founder-signed strategy depends on.
What was doneDecision: Public records first: pull the Texas TDLR license file (updated that morning) before spending a dollar with data vendors. Implementation: 16,031 distinct active TX A/C contractors with owner names, license numbers, and expirations — same day, $0. Cross-matched against the existing list: 401 rows enriched, 251 now hold owner + email (the first-send cohort). A 19-agent web hunt then measured the channel reality — 46% of owners findable on LinkedIn, 93% of companies on Facebook — and a new 29-lead batch was deduped (10 caught) and merged into a browsable 270-row Sun Belt Market Room. Dependencies: Email verification pass (MillionVerifier) before any send; approved copy.
The impactMonth one's entire lead requirement exists today at near-zero data cost; the channel mix is now measured fact, not estimate; and the founder can see his marketplace — names, emails, licenses, profiles — in one room.

06Business Impact

What was doneThe machine is IP: A transferable, documented revenue system — research, playbooks, rails, and training — that exists outside any one person's head. It practices what AnchorWorks sells. Reports that announce failure: Daily self-check logs commit to the repo; a bad list-build day flags itself. The 140-days-unread failure mode is structurally closed. Three lanes, no collisions: Territories, staging tables, and dedupe gates let three operators and their agents build in parallel — 42,000 raw doors across thirteen states without stepping on each other. Every batch makes the asset bigger: New lists dedupe into one master; enrichment survives; hooks merge instead of duplicate. Today's 29-lead CSV proved the loop in minutes.
The impactA company that can create revenue conversations on demand — with a documented system anyone on the team can run — is worth structurally more than one that waits for the phone to ring. That capability was designed, evidenced, and largely built this week.
04 · Metrics

By the numbers.

16,031
TX companies, owner-named · $0
251
first-send cohort (owner + email)
270
Sun Belt Market Room rows
93%
companies with Facebook pages
~401
sources behind the strategy
92
critic findings fixed pre-launch
100%
System deliverables (research · plan · runbook · repo · training site)
75%
Infrastructure (domains · inboxes · A2P · deploy)
40%
First-send readiness (copy · verification · blockers)
05 · Current Company Stage

Where we are.

01
Foundation
02
Launch
03
Scale
04
Expansion
05
Acquisition

June poured the foundation — doctrine, systems, the Category King strategy. July is Launch: the constraint is market contact, and the machine that creates it now exists. The honest clock from the research applies: outbound systems mature over four to six months; the 90-day Category King window is the first full evaluation cycle, ending October 31 with a ten-client target and the Pantheon lightning strike.

06 · Open Decisions

Decisions still required.

  • Copy approval — Chris's voice pass on the runbook, §11 sign-off, and the five send blockers (postal address, benchmark asset link, booking link, T2 stat, escalation channel).
  • Flag rulings — Facebook cold-opener scope, Custom Audience upload, franchise exclusion, full-list detection pass, LinkedIn invite form.
  • Access + domain — Zero Trust lock on the training site and the training.myanchorworks.com confirmation (the page is public until then).
  • Identity hygiene — who are the Alexander/Shine mailbox identities, rename to real senders, rotate credentials; general access audit across Cloudflare, Workspace, and Reply.
07 · Next Priorities

What comes next.

  1. 01
    The words, in Chris's voice
    Founder rewrite of the runbook templates from his 20 years of sales — plus his own cold-email library folded in — then §11 sign-off.
  2. 02
    Clear the five send blockers, verify the 251
    Postal address, asset link, booking link, T2 stat, escalation channel; MillionVerifier pass on the cohort — then first 30/day, founder eyes-on.
  3. 03
    Hand the team the keys
    Credential locations, company card, suppression export, GitHub invites, the announce email, and the Friday review on every calendar.
  4. 04
    Harden the send fleet
    Rename/rotate the unknown mailboxes, confirm warmup history, start domains four and five warming for the September ramp.
  5. 05
    Lock the surfaces
    Cloudflare Access on the training site, the custom domain, and the weekly self-check rhythm running across all three territories.
Executive Brief · Nº 021 · July 8, 2026 · Canonical