The operating surface for one customer. Tabs run Overview, Onboarding, Success, Team & Permissions, Payment history, Contract & Exclusivity, Booking, Integrations, Comms & Margin, Demo data, Notes and Conversation. Selection lives in the URL so back, forward, refresh and shared links all land on the same account and tab, and switching accounts never reloads the page.
Also called: client list · tenant list · account manager · customer accounts · my account file
- 1The roster shows status, demo badge, message count and the last thing said, with a live countdown on any account scheduled for deletion.
- 2Clicking an account writes the org and tab into the URL and paints the workspace beside it.
- 3The roster collapses to a thin rail so the account can take the width; the choice is remembered per browser.
- 4Each tab declares the capability it needs — a tab a staff member cannot use is not rendered at all.
- 5Every panel behind a tab is independently gated server-side.
- 6Last-known data is painted from a device cache immediately and replaced when the fetch lands.
The page header records the redesign: '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 tab gating carries its own reason: 'the alternative is a Payment-history tab that opens onto a 403, which reads as a broken product rather than as a boundary.'
- Account facts and account correspondence lived in different places, so neither told the whole story.
- Operating a customer meant opening a modal on top of a chat window.
- A shared link to 'that account, that tab' did not exist.
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 →