The Stateless Founder

Build an AI Org Chart That Works While You Sleep

Listen Later
Build an AI Org Chart That Works While You Sleep
The Oaxaca Disaster

Kira's 11 PM wake-up call in Oaxaca: contractor in Lagos finished fourteen blog posts, but the Berlin editor was on PTO with no backup assigned. Result? Nine posts reviewed while falling asleep at a tiny Airbnb desk, five shipped unreviewed, and one had the wrong client name in the headline. The 7 AM apology call from a mezcal hangover was the moment she realized her agency didn't have an org chart—it had her.

The Four-Role Framework

Not four people—four roles. One person can hold multiple roles when you're small:

  • Builder: Ships the thing. Writes drafts, builds automations, pushes code
  • Operator: Owns quality, schedules, budgets, client communications
  • Reviewer: Independent check. Cannot be the Builder on the same task
  • Agent/Dispatcher: Routes work, maintains schedules, pages people when things break
    • Three Scalable Patterns
    Pattern 1: Solo + Contractors
    • Founder: Builder + Operator
    • Contractor 1: Secondary Builder
    • Contractor 2: Reviewer
    • Make automation: Dispatcher with 30-minute human backstop
      • Pattern 2: Pod Model (3-5 people)
      • Lead writer (Builder)
      • Ops person (Operator)
      • Rotating editor (Reviewer)
      • Published SLAs: 24h priority campaigns, 48h everything else
      • Auto-approve on silence if automated checks pass
        • Pattern 3: Agency Cell + Dispatcher
        • Multiple pods handling different clients/products
        • Traffic Manager routes work and maintains coverage
        • UTC coverage grid shows overlap windows
          • SLA Matrix & Escalation
          Response Time Targets
          • Revenue-critical leads: 15-minute acknowledgment during sender's business hours
          • Code reviews: 4-hour first look during business hours
          • Content approvals: 24-48 hours
          • Support requests: Same business day
            • Severity Tiers (Atlassian Framework)
            • SEV 1: Revenue impact now → immediate paging
            • SEV 2: Major degradation/deadline today → 30-60 minute window
            • SEV 3: Normal work → business hours
              • Two-Layer Escalation
              1. On-call Agent (15-minute acknowledgment window)
              2. Auto-escalate to Operator if missed
                3. Coverage Grid & Handoffs
                UTC Coverage Grid

                Spreadsheet with columns: name, role, UTC offset, work start/end, PTO dates. Calculate overlap hours between Builder in Bogotá and Reviewer in Bangkok.

                Five-Field Handoff Packet

                Before passing work across time zones:

                1. Context: What we're doing and for whom
                2. Constraints: Deadlines, budgets, brand rules
                3. Last good output: Most recent working version
                4. Budget left: Hours or dollars remaining
                5. Fallback: What to do if blocked for 12 hours

                  6. Receiving person must comment "I own it" and restate next checkpoint in UTC.

                  The Lisbon Test for Handoffs

                  Could this work keep moving for 24 hours while you're offline? If any of the five fields is blank, you don't have a handoff—you have a hope.

                  Reviewer Rotation

                  GitLab's "Reviewer Roulette": Random assignment from a pool. For small teams, use a shared doc rotating weekly assignments with visible backup coverage.

                  Blameless Postmortems

                  Google SRE template: What happened, timeline in UTC, root cause, what worked, what failed, three ranked fixes with owners and due dates. Run within 72 hours while details are fresh. Goal: fix the system, never punish.

                  EU AI Act Compliance Ready

                  August 2, 2026 applicability date for most provisions. Named Reviewers, documented approval chains, and evidence logs aren't just good ops—they're compliance readiness for human oversight requirements.

                  Minimum Viable Process

                  Start with:

                  • One-page RACI per offer (not per task)
                  • UTC coverage grid in Google Sheets
                  • Five-field handoff packet
                  • Two-tier escalation (15-minute window only for revenue-critical leads)
                  • Pilot on one client for two weeks, then iterate
                    • This Week's Action
                    1. Download the AI-Augmented Org Packet (RACI template, SLA matrix, coverage grid, escalation tree, handoff checklist)
                    2. Duplicate and fill in roles for one client/product
                    3. Assign backup for every single role
                    4. Run one red-team handoff—hand real task to backup overnight
                    5. If it ships without you touching it, your org chart works

                      6. Resources:

                      • AI-Augmented Org Packet - Complete templates and frameworks
                      • GitLab Reviewer Roulette - Rotation system reference
                      • Atlassian Incident Response - Severity framework
                      • Google SRE Postmortem Culture - Blameless postmortem template
                        • ...more
                        View all episodesView all episodes
                        Download on the App Store
                        The Stateless FounderBy Santi, Kira