Jason runs four intertwined ventures out of one head and a very overloaded Asana. The pain isn't any single tool — it's that a single work order can touch a dozen disconnected systems, and nothing ties them together. That gap is the app.
In Jason's own analysis, you appear twice: bottleneck #10 (your HVAC coordination happens over Beeper texts, never reflected as a work-order status) and #21 (no system tracks your COI / W-9 / license expirations). You already feel the pain from the vendor side — which is exactly why you're a good person to build the fix.
All 30 bottlenecks, grouped by how much they cost him every week. Tap any card to flip it and see the evidence it's built on and an architect's note on how a well-built app would kill it for good. Flipping cards earns XP.
▸ audit note: the source doc's header says "29 bottlenecks identified" — but it numbers and lists 30 (10 + 12 + 8). We kept all 30.
Anyone can list features. The skill is reading the symptom and naming the root cause underneath it. Ten field calls — pick the real diagnosis, not the obvious one. Full XP the first time you crack each call; retries pay less.
You've got one 8-point MVP sprint and the doc's full roadmap: 35 features (5 summary foundations + 10 Good-to-Have + 20 Okay-to-Have — every card carries its doc reference). Each has a build cost, a leverage score, and dependencies. Pick your set, ship it, and see exactly which of the 30 bottlenecks your sprint kills.
The app is now actually being built — this tab tracks the real thing. Every phase below is a live long-horizon runbook in the repo (docs/phases/); milestones tick as they ship, and Build XP comes from shipped work, not studying.