DroneBlocks

Operations Map

Every business domain, scored by pain — the first analysis from the Fathom notes, and the prioritization input for what we build.

prepared 2026-06-22for Henrypain 1 (works) → 5 (on fire)

// the map

Domains, ranked by pain

[SoR] = system-of-record — recurring state (stock, orders, cash), wants a purpose-built tool/sheet, not a task board. Everything else is task-shaped. Owners aligned to the DRI map.
DomainCurrent stateOwnerPainNext step
Inventory / stockSoRNone — bin-check / memoryEric5Min-viable stock sheet
Fulfillment & shippingSoRAd hoc — caused a $6k order swapEric5One order-status sheet
Action-item / task trackingFathom→email→ignored; items recur for weeksDennis5Board + Inbox triage
Procurement / suppliersTribal — quotes/POs/lead-times in headsEric4PO / open-quote tracker
Production / build trackingSoRVerbal ("33 of 50 built")Eric / Aziz4Build-status lane
Demo / loaner hardwareSoRInformal — Kerrigan unit chased downRyan4Loaner log (+ CC hold)
Sales pipeline / CRMHubSpot mid-overhaul; deal bloatLindsey / Ryan3Finish field cleanup
Quoting / estimatesIn transition QBO → HubSpotLindsey3One estimate system
CommissionsBroken — QBO credits estimate creatorEric / Ryan3Manual off HubSpot
Weekly sales reportingBeing built (quoted-vs-sold, YoY)Henry / Lindsey3Ship v1
Lead capture / attributionQR → 0 signups; CAC unknownLindsey3One intake + CTA fix
Finance / cash / AR-APSoRWeekly call exists; manualTAG / Eric2Keep; revisit wire friction
Curriculum / contentAd hoc but movingDennis (int.) / Marisa2Light content calendar
Customer support / repairsReactive; repairs killed (units smoked)Ryan2AI agent + repair policy
Dev / engineeringIn GitHub; healthyDennis2Fold into board as eng

// signal

What the map reveals

The top-3 pains are operational, not engineering — inventory, fulfillment, and task-tracking, not the dev work. The deeper pattern (Eric as the bus factor; items floating across meetings for weeks; mid-transition on three systems at once) is detailed in Key Findings. This map's job is the pain ranking above and the build order below.

// sequence

Suggested build order

After a one-time "backlog bankruptcy" pass. Don't open new fronts on the pain-3-and-below rows until these are real.