AnchorWorks Executive Brief Cloud · 018 · Living Document
Board current as of July 6, 2026
AnchorWorks · Constraint Doctrine · Theory of Constraints

The Constraint Strategy

A business is a chain of dependent stages. At any moment, exactly one link limits the throughput of the whole system. Improving anything else is an illusion of progress.

For the next 90 days, everything serves the count of live conversations with qualified HVAC owners — and nothing gets built that a signed client didn't force us to build.

I

The constraint, named.

Policy Constraint

Nothing constrains this business except the founder's policy that the presentation must be world-class before a stranger sees the offer — a policy that kept market contact at zero for three months while consuming 100% of the founder's hours.

0
website commits in 27 days
0
cold emails sent in 3 months
0
founder hours of inventory built
$0
throughput produced
A fifth funnel × zero visitors= 0
A 40% close rate × zero calls= 0
Ten installs of capacity × zero signed clients= 0
Hired closers × zero leads= 0
A better wiki × a machine that produces nothing= 0

There is no counterargument to multiplication by zero. Any hour spent anywhere but opening the valve adds nothing. That is Goldratt's whole case — and the git history is the confession.

II

The pipeline — capacity everywhere, flow nowhere.

Mapped July 6, 2026 — the night before launch. Every downstream stage is built and idle. The valve at the front has never been opened.

THE VALVE — NEVER OPENED ATTENTION ~4,500 touches/mo [planned] actual · 0 LEADS 5–9/day booked, at full ramp actual · 0 CONVERSION ~3/wk founder calendar cap actual · 0 DELIVERY 4/mo installs [est., n=0] actual · 0 RETENTION · 10% $5k/mo assumed · $0.8–1.2k proven actual · $0 CASH ≈ 2 mo runway · $25k bank burn · $5–13k/mo Gold flow = planned capacity. Red = the actual number on July 6, 2026. The chain is only as fast as the valve.
StageActualCapacity [planned]Evidence — founder's words
Attention0~3,700 emails + ~800 LinkedIn/mo + $6k ads [soft]"We are not live yet."
Leads0~5–9 booked/day at full ramp [est.]"3–6% reply rate" — his own history
Conversion010–15 shows/wk × 25% ≈ 3 deals/wk"I only want 2–3 live calls per day."
Delivery04 installs/month [est., n = 0]"One revenue install per week."
Retention / 10%$0$5k/mo/client assumed · $800–1,200 evidenced"About 20% of monthly revenue came from that."
Cash–$5–13k/mo$25k bank ≈ 2 months runway"Let's give ourselves two months."
Founder hours0 on outreachPledged: ≥20 hrs/wk on outreach + sales"Zero hours with strangers."

The message test

Within 2 weeks of launch: does the offer book calls at ≥3–6% reply? The cheapest, most valuable data $0 can buy.

The founder's calendar

10–15 shows/week is the hard ceiling while Chris closes, builds, and records.

Delivery

4 installs/month, n = 0. The exact cliff where Grit & Gains fell — 80% of clients got no results.

Cash timing

First performance dollars are 75+ days out. Upfront fees are the only oxygen inside the runway window.

III

The five focusing steps — Goldratt's order, no shortcuts.

1

Identify done — July 6, 2026

The constraint is zero market contact, caused by the polish-before-contact policy and founder hours defaulting to building. Classified: policy constraint — the cheapest kind to fix.

2

Exploit squeeze the constraint · costs $0 · in force now

  • The protected block: 4 hours every weekday morning — outreach and sales conversations only. 20 hrs/week on the constraint, up from zero.
  • The Daily 30+30: 30 manual emails + 30 LinkedIn touches per day, personally. Every reply answered within 5 minutes.
  • Spend inventory, don't build it: 30 shorts banked, 2 VSLs live. Scheduling is a 2-hour task, not a 10-hour creative block.
  • Stop-doing: Brain harvesting, wiki filing, dashboard polish, funnel #5, website commits, hiring conversations.
3

Subordinate everything runs at the constraint's pace

  • Team owns all building and delivery questions — nothing interrupts the morning block.
  • Sales throttles to delivery: close 2 → pause → install to first client sale → reopen.
  • $0 cold ad spend. Retargeting only after ~500 pixel visitors, capped at $50/day.
  • reply.io stays holstered until manual sends prove the message (≥5% reply).
  • First $30k collected goes to reimbursement + runway, not hires or tools.
4

Elevate only when exploit maxes out — ranked by throughput per dollar

InvestmentTriggerCostGain
reply.io ramp 100→300/dayManual reply rate ≥5%~$0 — already built10× volume, zero founder hours
Commission setter (triage)>12 shows/wk, 2 wks straight$0 fixedFrees ~8 hrs/wk of constraint time
Retargeting $50–100/day500+ pixel visitors~$2–3k/moWarm bookings at ~$200/booking
Commission closer2 closed + calls recorded$0 fixedDoubles conversion capacity
5

Repeat the constraint moves — don't let inertia hold the old fix

  • Booked sessions ≥12/wk for 2 straight weeks → constraint is the calendar → activate setter + closer.
  • 2 clients signed → constraint is delivery → sales pause; install #1 writes the SOPs.
  • Replies <3% after 300 sends → constraint is the message → iterate copy, don't buy volume.
  • Both installs at first client sale ≤45 days → constraint returns to lead flow → full ramp + retargeting.
IV

The 90-day campaign — three moves, nothing else.

Move 01

The Daily 30+30

Action30 emails + 30 LinkedIn per weekday, personally, sent by noon. Ramp via reply.io only if replies ≥5%.
OwnerChris
DeadlineStarts July 7, 10:00 AM ET
MetricOutbound touches/week → 300+ by day 14
2-wk signal≥5% replies · ≥3 booked sessions by July 20
Move 02

Close 2, then deliver like hell

ActionClose 2 clients personally; sales pause; both engines to the client's first tracked sale.
OwnerChris closes · Ethan leads install
DeadlineCloses by Aug 5 · first sales by Sep 19
MetricSignature → client's first sale ≤75 days
2-wk signalInstall #1 hour-log vs the 40-hr estimate
Move 03

The building freeze

ActionZero commits to Website / Brain / dashboard repos except client-forced work, until 100 market conversations.
OwnerChris — it's a policy; only he can break it
DeadlineIn force since July 6
MetricCommits/wk to non-client repos = 0 · constraint hours ≥20/wk
2-wk signalWeek-1 time log: outreach + sales ≥20 hrs (was 0)
The Covenant

Close two. Stop. Deliver both to their first sale. Then — and only then — reopen the pipeline.
This is the anti–Grit-&-Gains clause. Breaking it is how the 80%-failure cohort gets rebuilt at 3× the price.

V

Parked — attractive, and useless to the constraint.

Every one of these multiplies by zero right now. They are parked, not killed — the triggers in Step 5 decide when any of them wakes up.

Parked

The 5-man sales team

Closers × 0 leads = 0. Commission chatter burns focus; salaries burn runway.

Parked

Cold ads at any budget

History says cold ads pull broke buyers. The bank says the lesson can't be afforded twice.

Parked

Funnel #5 · website polish

Four funnels already sit at 0% utilisation.

Parked

Brain / wiki harvests

Documenting zero throughput produces documented zero.

Parked

Full reply.io blast, week 1

An untested message would burn 3 months of domain warming in days.

Parked

Webinar machinery

A free live hour in the Facebook group is fine. Building production around it is not.

Parked

Niche expansion planning

HVAC only in 2026 — the founder's own words.

Parked

100-client math

Fantasy column until n ≥ 2 installs and one client has paid a performance fee.

VI

The lightning strike — Pantheon Week, earned in gates.

The strike amplifies what exists. Case studies, cash, and a warm invite list are the ammunition — the 90-day campaign is how they get earned. The strike scales with proof, never with hope.

Jul 7

Launch

First 30 emails. The valve opens.

Aug 5

Gate 1 · re-map

2 clients closed → book travel + private dinner (≤$3k, from fees).

Sep 19

Gate 2

Both clients at first sale → greenlight event buildout.

Oct 5

Gate 3 · re-map

Actuals set the strike's final scale.

Late Oct

Pantheon Week

Revenue Engine Live — invite-only executive briefing. Orlando.

Gate 1 · Aug 5

Proof of demand

Pass: 2 clients closed. Book travel; reserve a private dinner — ≤$3k, paid from collected fees, never from runway.

Fail → Pantheon = tickets and handshakes. Keep selling.

Gate 2 · Sep 19

Proof of delivery

Pass: both clients at first tracked sale. Greenlight Revenue Engine Live buildout (Sep 22 – Oct 24). Budget cap: 25% of cumulative upfront collections. Case-study assets are client-forced work — freeze-compliant.

Fail → no production spend. The category launches at the next gathering, with proof.

Gate 3 · Oct 5

Scale by actuals

Pass: the re-mapped pipeline table sets the final scale — warm invitees × case studies × cash.

Fail → dinner-scale guerrilla presence. Zero shame; zero production spend.

Standing order — in force since launch

Every outbound reply, show, and polite "no" gets tagged in GHL as a Pantheon invite candidate. The invite-only room in October is built one cold email at a time. The event goes into the outbound copy: "private executive briefing at Pantheon Week — invite-only."

100+ tagged 30 invites 15 in the room

Category discipline — one term, relentlessly

Outbound teaches one term: Revenue Engine. The other nine lexicon terms stay internal until proof exists. From the founder's own Play Bigger notes: "too many branded concepts dilute the mental association." Teaching happens through channels that already exist — new teaching infrastructure is polishing with a syllabus.

VII

The weekly scorecard — five minutes, every Friday.

MetricThis weekTarget
Throughput — $ collected (upfront + 10%)>$0 by week 4
Constraint hours (outreach + sales)≥ 20
Queue — sessions booked next week5–12
Sent → replies → booked → shows → closeswatch the ratios
Commits to non-client repos (lie detector)0
Fed the constraint, or polished?the honest answer
  1. Pull the numbers — reply.io sends/replies, GHL bookings/shows, collections. (3 min)
  2. Constraint hours vs 20. Under? Name what stole them — by name. (2 min)
  3. Queue check. Under 5 booked next week = the constraint is starving; feed it Monday. (2 min)
  4. Run the lie detectorgit log --since="1 week ago" on Website + Brain repos. Non-zero = you polished. (3 min)
  5. Check the triggers — ≥12 shows/wk ×2 weeks → setter. 2 signed → sales pause. <3% replies after 300 sends → fix the message. (3 min)
  6. One sentence in the brief cloud: what the constraint was this week; what feeds it next week. (2 min)

"Did I feed the constraint this week — or did I polish something comfortable?"

Step five never ends

Re-map the pipeline on August 5, 2026.

Fill the same table with actuals — sends, replies, bookings, shows, closes, install hours, dollars collected. The constraint will have moved. Find where, reclassify it, rebuild the three moves. Yesterday's fix must never become today's sacred cow.

Executive Brief 018 · Living Document · v1.0 · July 6, 2026