The methodology
How the engine works.
An agent workforce, three layers deep. WhatsApp at the front, structured data in the middle, pattern memory at the bottom. The same engine powers our client commissions and our in-house bets.
The three layers
Picture the engine as three concentric layers. From the outside in.
Surfaces
What you touch. WhatsApp on your phone, the portal in your browser, email digests, ship-day calls. You don't need to know it's AI — you just experience a buddy who texts and a guide who shows up.
Agent workforce
The brains. Eight specialised agents — one per job — with defined tools, memory, and escalation rules. They communicate through a shared state store and are orchestrated by a thin coordinator.
Foundation
The data and infrastructure. Engagement state, artefact store, playbook library, outcome history, pattern memory across all prior engagements. Invisible to you, but where the labs' compounding value lives.
The agent workforce
Eight specialised agents. One per job. Specialisation produces predictability; generalisation produces drift.
Triage
Pre-program qualification
Runs the intake conversation, recommends the right track, gates entry.
Coach
WhatsApp-first day-to-day
The persona you build a relationship with. 5 touchpoints/day in month 1, 3/week after.
Builder
Drafts every artefact
Landing pages, email sequences, framework PDFs, decks. Edited by you, reviewed by us.
Reviewer
Quality gate at Ship Hour
Final check against archetype-specific rubrics before anything goes public.
Distributor
Public launch + outreach
Drafts your ship post, your named-five outreach, and follow-up reminders.
Conversion
First-customer arc
Monitors replies and Stripe events, drafts follow-ups, helps you close the first ten.
Concierge
Tight-stack setup
Stripe, Calendly, ConvertKit, domain. Eats four to eight hours of historical setup pain.
Retention Watcher
The infrastructure tail
Months 4–12: monitors graduate health, flags upgrade or rescue moments.
Autonomy ladder
Agents earn autonomy as the data justifies it. Two non-negotiable rules: autonomy is per-domain, not global, and autonomy is reversible.
If a metric drops, the operator pulls the rung back. This is normal and expected, not a failure.
Six design principles
The constitution. When in doubt, we return to these.
WhatsApp is primary, the portal is the artefact surface
Conversation, accountability, and decisions happen where you already live. The site is where the work is built and shipped.
Agents are specialised, not general
One agent per job. Specialisation produces predictability; generalisation produces drift.
Humans at high-leverage moments, not as fallback
Scheduled into three points where their presence raises ship rate by 15 percentage points. Outside those, the engine is autonomous.
Every interaction produces structured data
A voice note becomes a transcript becomes an extracted commitment becomes a row. No conversation is lost.
Memory of every prior engagement
Each new customer benefits from the patterns of the fifty or five hundred who came before. Memory is the moat.
Failure modes detected by agents, not humans noticing
When a customer goes silent for 14 hours, an agent flags it. Most engagement failures are visible 24 hours before the human catches them.