KitFire Fleet ConsoleInstagram · Agency Control Plane
SIM —FLEET —PROTOTYPE · MOCK DATATEXT SIZE100%
Single points of failure?
Every tile above counts accounts. None of these do — each one takes the whole fleet down at once, and no per-account row could ever show them.
Onboarding?
The invite link is the front door: sent → opened → authorised → live. A stalled invite is revenue sitting in an inbox.
The Wire?
Everything a human must touch, ranked by consequence ÷ the hours a human is actually available before the deadline — not wall-clock hours. Healthy accounts render zero pixels.keys: ↑↓ · Enter · ←→ in panel · / find
Client rooms?
Where the trainer, the client, Tom and Chris actually talk. The desk does not
relay these — it supervises them. — waiting on us.
Support desk?
Account issues, which are a different animal from content problems: they have a
contract behind them and a clock that a client counts. — open.
Quiet risk?
The blind spot in an exception queue: churn is not an event, so an account on its way out looks exactly like a healthy one. Nothing here is broken and nothing is overdue — these are accounts going cold. — in scope.
The Book?
This console could rank 1,200 accounts by what they need and never say what
one of them was worth. Cost to serve is computed from work the desk actually did —
creator minutes, wire rows, room time, tickets. Price is not set here. That is Chris’s
ruling, and every figure downstream of it reads blank until he makes it.
Fleet Radar?
One cell per account, canvas-rendered — the same view holds 5,000 accounts on one screen with no pagination.
Assignto
Content Team?
Who writes what, when they work, and how loaded they are. Demand is the cadence of the accounts they own — nobody gets loaded past the sheet, and specialty mismatches surface before they become bad content.
Why this shape — the four decisions the layout encodes
The primary object is the exception, not the post
At five accounts you are a creator and the calendar is home. At five hundred you are an air-traffic controller, and any screen that renders one card per client has handed a human the filtering job a machine should have done. The calendar still exists — it is one click deep, inside an account.
Rank by time-to-irreversible, not recency
A DM at hour 23 of Meta's 24-hour messaging window outranks a token expiring in nine days, because one closes forever tonight and the other has 216 hours of slack. Severity is impact / desk_hours_left — hyperbolic, so a nearly-gone deadline dominates the board. S365: the divisor is the hours a human is actually rostered before the deadline, not wall-clock hours, because a DM at hour 8 on a Friday evening is worse than one at hour 20 on a Tuesday morning. The availability was already in the Content Team board; nothing had joined it to the ranking.
API budget is a visible object
Instagram's non-messaging call budget is 4800 × impressions/24h. Accounts with reach have enormous headroom; the cliff is at the bottom, where zero impressions buys zero calls — and Meta documents a floor for Threads but none for Instagram. That lands on newly-onboarded accounts, the ones an agency creates most. Every cell carries its budget so the cliff is seen before it becomes a failed publish.
Bulk is a query, never a checkbox
Nobody ticks four hundred boxes. You name a set — "dental cohort, queue dry before Friday" — and act on the set. Sorting the radar by cohort or program is the selection gesture; the grouping you see is the batch you operate on.