--- title: Lean Team Structure — $51.7k/mo Payroll Model type: article created: '2026-02-20' updated: '2026-02-20' source_docs: - raw/2026-02-20-check-in-124049001.md tags: - team-structure - payroll - operations - account-management - staffing - revenue layer: 2 client_source: null industry_context: null transferable: true --- # Lean Team Structure — $51.7k/mo Payroll Model ## Overview In response to a projected revenue drop to ~$60k/mo against a payroll that exceeded that figure, Asymmetric finalized a lean team restructure on 2026-02-20. The guiding principle: **dependability over capacity**. A small team that executes reliably is preferable to a larger team that creates client risk. The decision was reached after Mark modeled six staffing scenarios ranging from $37k to $65k/mo in payroll. The selected structure lands at approximately **$51.7k/mo**, leaving a narrow buffer against the ~$60k revenue baseline. See also: [[clients/advanced-health-safety/_index]] and [[clients/sam/_index]] for concurrent client retention actions taken the same day. --- ## The Revenue Problem Recent client losses and scope reductions created the shortfall: - **Lost entirely:** Axley, Adobacare, Tracti, Sonaplot - **Scope reduced:** Aviary ($8,500 → $5,000), Flynn (→ ~$1,000) - **At risk:** Advanced Health & Safety ($3,000/mo) - **Transitioning:** Paper Tube (at $3,000 for one more month) Conservative revenue projection: **~$60k/mo**. Prior payroll exceeded that figure before tools or operating expenses — making restructuring unavoidable. --- ## Final Team Structure ### Core Account Management Team | Person | Role | Status | |---|---|---| | Mark | Principal / account involvement | Retained | | Karly | Senior account manager | Retained | | Melissa | Account manager (ops → AM transition) | Retained with pay cut | | Sebastian | Account manager | Retained on strict notice | ### Staff Departures - **Ben** — let go - **Asalia** — let go ### Contractors All retained; design team and Gilbert adjusted down modestly. The goal was for everyone to absorb some pain rather than concentrating cuts on one person. --- ## Key Decisions ### 1. Keep Melissa, Put Sebastian on Notice The core tension was Melissa vs. Sebastian. The deciding factor was **reliability**: > "You can count on Melissa to the death. I don't think you can totally count on Sebastian." — Mark Sebastian has stronger technical skills and is younger/more tech-adept, but personal instability has affected his work (the Advanced Health & Safety service failures were a direct example). The resolution: retain both, cut both salaries, but make clear to Sebastian that one more reliability failure removes him from the team. If AHS churns, that is treated internally as the trigger. Melissa transitions out of the Director of Operations role and becomes a hands-on account manager like Karly. ### 2. Two Account Managers Per Client Rather than single ownership, every client will have **two assigned account managers**. Rationale: - Redundancy if someone is sick, on leave, or eventually let go - Stronger client-facing presence ("they want a team") - Cleaner handoffs if staffing changes again The two managers per account will not be the same pair across all clients — assignments will be distributed based on workload and trust level. Karly will model the full distribution before the 2:00 PM all-hands call. Notable constraint: Melissa should **not** be reassigned to Bluepoint (prior delivery issues damaged that relationship). ### 3. Mark's Account Involvement Mark is not counted as a formal account manager but will be actively involved in five key accounts: Paper Tube, Aviary, Bluepoint, Citrus, and Doodla Farms. ### 4. Cordwainer Flagged as High-Priority Cordwainer ($4,000–$4,500/mo) was already raising concerns about visible output. Mark and Karly will both be on this account. Needs immediate attention heading into spring. --- ## Payroll Scenarios Considered | Scenario | Structure | Monthly Payroll | Notes | |---|---|---|---| | 1 (prior plan) | Let Melissa + Ben go, keep Sebastian + Asalia | ~$48k | Too thin on reliability | | 2 | Let Sebastian + Ben go, keep Melissa | ~$47k | Loses tech skills | | 3 | Keep only Mark + Karly + Asalia | ~$42k | Numbers good, operationally harsh | | 4 | Mark + Karly only, cut one dev + one design | ~$37k | Best number, worst model | | 5 | Mark + Karly + Melissa, let Raphael + Asalia + Ben go | ~$45k | Loses automation/email capacity | | **6 (selected)** | **Keep Melissa + Sebastian, let Ben + Asalia go, adjust all pay** | **~$51.7k** | Chosen — best balance of stability and capacity | The selected scenario is the least disruptive to client continuity and preserves the team's skill coverage, at the cost of a tighter margin. --- ## Operational Change: GoHighLevel Scope Restriction Decided in the same meeting. GHL has been operating as a "black hole" — broken forms cause silent lead loss that is difficult to diagnose. **New policy:** - GHL restricted to **email marketing only** - All **forms** → Gravity Forms on client websites - All **landing pages** → built directly on client websites, not in GHL A specific example: a Reynolds form-to-Google-Sheet integration broke inside GHL and went undetected. This is the failure mode being addressed. --- ## Action Items from This Decision - [ ] **Mark** — Call Melissa: explain pay cut, transition from ops director to account manager role, before 2:00 PM call - [ ] **Mark** — Call Sebastian: set explicit reliability expectations, frame as "on notice" - [ ] **Karly** — Model two-person account assignments across all ~17 active clients; present at 2:00 PM - [ ] **Karly** — Schedule 2:00 PM all-hands with Mark, Karly, Melissa, Sebastian --- ## Related - [[clients/advanced-health-safety/_index]] — Concurrent retention risk; Sebastian's reliability failures are a direct cause - [[clients/sam/_index]] — Separate retention action; performance-hybrid retainer proposal - [[knowledge/agency-operations/gohighlevel-scope-restriction]] — GHL policy change decided in same session - [[knowledge/agency-operations/two-am-account-model]] — Two-account-manager structure rationale