YBA Empire — Strategy

YBA Empire — Strategy & Go-to-Market

Companion to Architecture (the WHAT) and Dev Plan (the HOW).

What this is: the strategic logic behind the empire — the path to market, the 7 measurable gates, the kill triggers, the Meta-Brain that captures cross-tenant patterns, and the de-risk experiments. This was previously embedded in Architecture v3.3; extracted into its own document on 2026-05-02 per the documentation audit.

TL;DR

Edge is the discovery engine for the whole empire — built first to solve Captain’s own problems, then sold as Concierge to clients, then as BYOK SaaS. Customer interactions become signal that informs Med, Terra, Realty designs.
The dogfood-discovery engine works for adjacent verticals (close to founder’s domain) and fails for distant verticals (Med, Terra, Realty) unless deliberately seeded with a real practitioner-client per vertical.
7 measurable gates — not timelines. Captain moves to the next stage only when triggers fire.
Meta-Brain captures patterns across tenants POPIA-safely and propagates them into Med/Terra/Realty designs.
Top 3 risks: Captain burnout, customer concentration collapse, learnings don’t transfer.

The Plan in One Picture

┌──────────────────────────────────────────────────────────────────┐
│ STAGE 1 — Captain dogfoods Edge on his own 10 portfolio brands   │
│  Spec is written by living it. He IS the first customer.         │
└──────────────────────────────┬───────────────────────────────────┘
                               ▼
┌──────────────────────────────────────────────────────────────────┐
│ STAGE 2 — Same tools sold as Concierge to agency-sector clients  │
│  R45k setup + R18.5k/mo. 5-15 client ceiling. Cashflow + signal. │
│  Every client interaction = customer-discovery research.         │
└────────┬─────────────────────────────────────────────┬───────────┘
         │                                             │
         ▼ (Edge stage 3 unlock)                       ▼ (Empire signal)
┌─────────────────────────┐                 ┌─────────────────────────┐
│ STAGE 3 — Edge BYOK     │                 │ Patterns extracted into │
│ self-serve SaaS         │                 │ the YBA Meta-Brain      │
│ R3.5k/mo, public.       │                 │ (anonymised, POPIA-safe)│
└─────────────────────────┘                 └────────┬────────────────┘
                                                     │
                                                     ▼
                                  ┌──────────────────────────────────┐
                                  │ Med, Terra, Realty designs are   │
                                  │ grounded in real Edge customer   │
                                  │ patterns, not specialist guesses │
                                  └──────────────────────────────────┘

Why This Works — With One Critical Caveat

This is the most reliable platform-business pattern in software history. Basecamp, HubSpot, Shopify, Atlassian all followed it. Yoco is doing it locally right now (built for SA merchants who needed a card reader; expanding to lending + payroll using merchant data as the discovery engine).

But every one of them learned the same lesson: the dogfood-discovery engine works for adjacent verticals (close to the founder’s domain) and fails for distant verticals. Edge’s buyer is a side-hustler / portfolio operator. Med’s buyer is a doctor. Different planets.

Concrete implication: Edge’s customer interactions surface deep insight on agency-adjacent verticals (coaches, course creators, consultants, small agencies). They surface shallow insight on Med, Terra, Realty unless Captain deliberately recruits a real practitioner-client in each vertical to dogfood with — one doctor, one farmer, one estate agent.

Captain’s confirmation (2026-05-02): “yes i intend to have a real client using YBA edge to help us build industry specific solutions.” This locks in the practitioner-per-vertical strategy. Med Layer 2 launch (Gate 4) is contingent on a real GP signing as concierge client + design partner. Terra and Realty plans don’t start until each has its own practitioner-client lined up.

The 6 Listening Surfaces

Every Edge customer interaction is captured + tagged + propagated:

#	Surface	What it captures
1	Onboarding interview (week 1, every concierge client)	90-min structured call. 20 cross-vertical questions about current tools, staff, compliance pain, customer flow
2	Support tickets + Telegram	Every “the agent didn’t do X” — auto-logged with which agent, expected vs actual
3	The customer’s brain — questions they type	Weekly anonymised scrape of question patterns (“what do clients ask their HR agent?”)
4	Agent failure logs	Monthly rollup of every agent error — failures are richer than successes for cross-vertical design
5	Monthly review meeting	30-min call per concierge client. 3 questions: what worked / nearly broke / missing
6	Churn-exit interview	Mandatory 45-min call when client cancels. Most expensive, most honest signal we get

The 7 Gates — Measurable Triggers (Not Timelines)

A gate is a measurable condition, not a date. Captain moves to the next stage only when the trigger fires. The realistic calendar (at 18 hrs/week) is guidance — the triggers are the contract.

#	Gate	Trigger condition (must ALL be true)	Realistic range
1	Edge Stage 1 → Stage 2	5+ of Captain’s brands fully on platform 30d · 0 P1 bugs · synthetic Tenant B test passed · onboarding <30 min · indemnity bound	3-5 months (Aug-Oct 2026)
2	Edge Stage 2 → Stage 3	8+ paying clients × 3 months · churn <5% over 90d · Captain <6 hrs/wk per client · Layer 1 stable 14d · self-serve tested by 5 betas · LLM cost guard proven	9-15 months
3	Med PLANNING starts	15+ Edge clients OR 50+ BYOK · 3 unprompted “do you have something for doctors?” · Edge MRR R150k+ × 2 months · Healthbridge NDA signed · 1 SA GP design partner	6-9 months
4	Med LAUNCH	Healthbridge contract signed · all 10 safety rails wired · Practice B isolation test passed · Rejection Auto-Fix shadow mode 30d at ≥85% accuracy · POPIA IO appointed · DPA + MSA signed · indemnity scaled	12-18 months
5	Terra planning	2+ Med tenants stable 60d · Captain provides Terra vision · agri design partner volunteered	18-24 months
6	Realty planning	Same shape as Gate 5 — Med stable + Realty vision + design-partner estate agency	18-24 months (parallel with 5)
7	Per-vertical launches	Vertical contracts signed · safety rails · shadow mode · synthetic Tenant B · insurance	24-30 months

Hard blocks: Gate 4 cannot fire without Healthbridge contract. Gate 7-Realty needs FICA + EAAB pack. Gate 7-Terra needs commodity-data feed contract. Gate 3 needs Edge MRR ≥R150k for 2 months — Med dev burns ~R300-420k.

The Kill Triggers (when to pause/abandon)

Stop and re-audit if any of:

Edge S2 churn > 15% over 3 months
Edge S3 BYOK acquisition cost > 1× lifetime value after 6 months public
Med shadow-mode Rejection Auto-Fix accuracy < 70% after 30 days
Any cross-tenant data leak in production, ever → all stages freeze, full audit
Captain’s hours-per-client on concierge climb past 8/week
Healthbridge contract not signed within 9 months of Gate 3 firing
2 consecutive months of Edge MRR decline → freeze all non-Edge work

The YBA Meta-Brain (the empire’s institutional memory)

A NEW top-level vault, peer to Richards Brain, that captures patterns across all Edge customers (and later Med/Terra/Realty) and propagates them into the platform’s design.

Where it lives: /opt/claude-workspace/projects/yba-meta-brain/ — same Richards Brain markdown wiki structure + two new folders:

yba-meta-brain/
├── CLAUDE.md          # POPIA-strict variant of Richards Brain schema
├── index.md
├── log.md
├── raw/               # anonymised intake (sanitised excerpts only)
└── wiki/
    ├── patterns/      # NEW — one page per cross-tenant pattern
    │   ├── universal/   # patterns that hold across ALL verticals (Layer 1 candidates)
    │   ├── edge/
    │   ├── med/
    │   ├── terra/
    │   └── realty/
    ├── decisions/     # NEW — every empire design call, links the patterns that drove it
    ├── verticals/     # one page per vertical — rolled-up state
    ├── concepts/      # cross-cutting concepts (e.g. "WhatsApp 24hr window")
    ├── analyses/      # "Layer 1 v2 readiness," etc.
    └── meta/

POPIA-safe extraction (the load-bearing rule): tenant data NEVER leaves the tenant brain. Only PATTERNS derived from tenant data move. The Pattern Extractor agent reads tenant brains weekly and produces anonymised observations (no names, no exact numbers, bucketed counts). Niki audits every draft before it lands.

Layer 1 promotion gate: when a pattern shows up in patterns/universal/ from 3+ tenants × 2+ verticals, Niki proposes a Layer 1 change. Captain signs off. Decision lands as a dated decisions/ page that supersedes the previous version.

Worked example: an Edge tenant hits the WhatsApp 24-hour reply-window stall (queue stalls Monday morning, costs R380/mo extra). Three Edge tenants show the same pattern → universal pattern landed → Layer 1 readiness proposes the Customer Care agent track reply-window expiry per channel. By the time Med Layer 2 is designed 90 days later, the Med WhatsApp Portal inherits this fix from day one — no doctor pays the R380 lesson Edge already paid for.

The Top 3 Risks (honest)

Specialists explicitly told to be brutal:

Captain burnout / day-job collision (severity 5 × probability 4 = 20). Concierge is high-touch. Day job + 5 clients + dogfooding 10 brands = three full-time jobs. Mitigation: hard cap 5 concierge clients before quitting day job; document Niki vs Captain responder boundary; build “Captain offline 7 days” runbook before client #2.
Concierge customer concentration collapse (5 × 4 = 20). Lose 2 of first 5 → MRR drops 40% overnight, BYOK build stalls. Mitigation: don’t take 5 in 90 days — take 3, stabilise, then 4. First client (the R6k Flow concierge client) is safe; pick next 2 from same industry before going cross-sector.
Edge learnings DON’T transfer to Med/Terra/Realty (4 × 4 = 16). Agency buyers ≠ medical/farm/realty buyers. Mitigation: Edge is the cashflow product; Med/Terra/Realty are PARALLEL R&D efforts that share infra, not natural extensions. Recruit 1 GP, 1 farmer, 1 estate agent as concierge clients EARLY to test transfer per vertical.

Specialists’ single most underrated risk: the 8 universal agents + markdown-brain decision is locked in too early based on Richards Brain (n=1, Captain himself). Markdown has no concurrency model, no enforced schema, no row-level security. By the time these constraints are visibly wrong with 5+ tenants running, migrating is a 3-month engineering project nobody is paying for. Treat both as tentative for the first 3 paying clients; write down explicit kill criteria.

The 5 De-Risk Experiments (do these in months 1-6)

Recruit ONE practising doctor as concierge client #2 or #3 — onboard them using ONLY the 8 Layer 1 agents, no Med-specific Layer 2. Document every gap they hit in 30 days. Those gaps ARE the Med Layer 2 spec, derived from real signal.
Hard ceiling at 5 concierge clients for first 6 months. Use slack hours for pattern-spotting + Niki/agent automation, NOT for selling more.
Build a vertical-fit scorecard before Med/Terra/Realty start. Score each candidate vertical on (a) buyer similarity to Edge buyers, (b) regulatory load fit, (c) practitioner-partner availability. Any “no” → vertical is parked.
Month 4 founder-transfer test. Take Captain’s most painful workflow (e.g. cross-posting clip approvals across 10 brands), sell it as a STANDALONE product to a stage-2 client. If transfer is clean → dogfood-to-product pipeline works. If it’s a slog → architecture has more friction than it appears.
Set kill criteria for the markdown-brain + 8-agent assumptions IN WRITING NOW — e.g. “if any tenant brain experiences a write conflict in production OR if any Med pilot reveals 50%+ of its needs aren’t covered by Layer 1, revisit foundations.”

What’s Locked in v3 (the strategic decisions, recap)

See Decisions Log for the full list. The 5 most-load-bearing strategic decisions:

D-008 Stay hybrid (rent ERPNext + Postiz + n8n; build Flow Core + LLM Router + agents)
D-009 Concierge tier launches before BYOK
D-010 Gates not timelines (the 7 measurable gates above)
D-011 One real practitioner-client per vertical (de-risk experiment #1)
D-016 Documentation cleanup approved + executed

Extracted from Architecture v3.3 on 2026-05-02 per the documentation audit. Maintained alongside Architecture and Dev Plan as a third canonical document.