One screen to run every account

The vendor's account roster with the selected account's full workspace inline — status, team and permissions, payments, contract, booking, integrations, comms, notes and correspondence — addressable by URL.

What it is

A two-pane operator surface: the roster on the left, and the selected account itself as the main area rather than a modal on top of it. Selection lives in the URL, so back, forward, refresh and shared links all land on the same account and the same tab, and switching accounts never reloads the page. Every panel is behind the capability gate.

Also called: sub-accounts · client list · tenant admin · account management console

See it
One screen to run every account
Prepared for
Ivy Brubaker
1140 Ridge Line Rd · Fair Play
Shell package$35,656
Concrete & site$10,352
Doors & windows$6,901
Trim & finish$4,601
Total
$57,510
Signature
The two-pane sub-accounts screen: roster left with status chips, the selected account's workspace right with its tab strip. src/app/platform/clients/page.tsx. Sample data — no customer information appears here.
How it works
  1. 1The account list comes from a capability-gated endpoint that aggregates age, last activity, member count, integration status and adoption counts.
  2. 2Selection and tab live in the query string (?org=…&tab=…).
  3. 3Panels cover overview and status, team and permissions, payment history, contract and exclusivity, booking, integrations, comms and margin, notes and conversation.
  4. 4Each screen paints its last good payload from the device instantly, then replaces it with the network answer.
  5. 5Revenue is zeroed server-side for callers without the billing capability.
Why we built it

The page header records a design correction: 'The first version led with the correspondence and hid the controls behind a button, which read as a chat app with a settings link. Operating an account is the job; talking to them is one part of it.' The governing principle is stated as Keith 08-15: 'THE account IS the page.' URL-addressable selection is justified operationally — 'back/forward, refresh and shared links all land on the same account and tab.' The cache-first paint has its own rule, Keith 08-19: 'every agency-panel page paints its last good payload from the device INSTANTLY, then the network answer (the database is always the source of truth) replaces it a beat later. A page that shows something immediately never reads as broken.'

The problem
  • Operating an account required jumping between disconnected screens.
  • A modal over a chat made the controls feel secondary to the conversation.
  • Losing your place on refresh or when sharing a link with a colleague.
Sound familiar?
What you get
One screen answers most questions about an account.
Links to a specific account and tab can be shared with a colleague.
Screens paint instantly and then correct themselves from the database.

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →