blue angels
A revenue pipeline tracker — because new business deserves the same governance as delivery.
team one internal tool, deployed in production on the agency's internal aws/eks platform. client names and dollar targets withheld.
Revenue pipeline tracking for Team One — opportunities, stages, and reporting in one governed system, replacing the spreadsheet-of-record pattern that new-business tracking always decays into. Behavior parity with the original prototype was documented as acceptance criteria before any code; the June verification run passed 67 of 67 executable assertions, and the auth system was distilled into a reusable blueprint for the tools that came after.
Two August batches from the new-business lead, shipped as PRs with before/after diffs of production data: client grouping normalized so the same client typed two ways stops appearing twice; a “parent | sub-brand” convention with family rollups and subtotals; and delete replaced by a won/lost/canceled close-out with notes, a removed tab, restore for editors, and permanent delete admin-only with an audit snapshot — won-but-removed items still count toward earned totals. It is also the app where the fleet's rotation-proof credential pattern was first built and then, in August, where its dead-code bug was found (see rotation-proof).
Full case study in progress — artifacts pending clearance or writing time. The insight below is already earned.
Pipelines are platforms too. Revenue tracked in a governed system beats revenue tracked in whoever's spreadsheet was open — and a delete button is a governance hole until it becomes a close-out with a reason.
the insight