The inbox is organised by person, not by message. One customer and one topic split across four list rows was the biggest defect in the old design. Own / Shared sits at the top with the account itself printed, because the classic accident on a shared mailbox is replying from the wrong identity. The right column is the bridge to Leads: state belongs to Leads, action belongs to the Inbox.

A queue, not a board. The first cut is whose turn it is — a brand-new enquiry and a customer reply are the same job: both are on your desk today. The discrete stage was absorbed into the completeness meter. Click any row to open it.

The checklist is laid out as a spec sheet, not a to-do list. The dashed gaps in the value column are the completeness reading. Anything the AI extracted from an attachment is a distinct third state — it holds a place and prompts you, but does not count toward completeness. Machines misread hand-drawn dimensions; that human gate cannot be skipped.

Each row encodes two separate things. The grouping says who owes an action (it oscillates); the four-pip meter says how far the money has committed (it only moves forward). The first row has three things open at once — first batch shipped, customer added windows needing a re-quote, and stage 2 still with the customer. A single-column board cannot express that.

The document ledger is the reason the container model exists. Three quotations sit side by side, superseded ones carrying the reason they were superseded. Six months later, "why did this drop from 203k to 184k" is answered here rather than by digging through email. The variation hangs indented under the order, because it supersedes nothing — it adds.

Grouped by job, not by date. A date view already exists on their phone, so repeating it adds nothing. Grouping puts clashing dates next to each other — and more importantly it is the only way to show a date that should exist and does not (the hatched rows). An event with no date has no position on a timeline, so a date view physically cannot display it.

This page is designed backwards. The first block is not "how many documents do we have" but "where does the agent keep getting stuck". The lead checklist tracks what we do not know about the customer; these gaps track what the agent does not know about us. Same device, opposite direction.