Sample views · Five workflows
The sales workflow, from call preparation to renewal.
The toolkit is the manual version. A rep pastes notes or an export into a chat, reads the draft and fixes it. These static examples show how a connected workflow could gather those inputs and present the result with an owner and a next step. The design calls for a person to approve work before it is sent or saved. These pages do not connect to a CRM or perform those actions.
01 / The views
One page per moment in the sale.
Each view opens with what the system already did and what still needs a person. The detail comes after that.
Pre-call brief — Hartley's Home & Garden
Built from the account record and public sources before a priority call, and short enough to read in two minutes. Every fact carries its source and its type. Hypotheses are labeled as hypotheses.
Open the brief → Follow-through · After the callFollow-through record — Hartley's Home & Garden
The call record, the actions with their owners and dates, the proposed CRM changes and a draft follow-up email. Anything the call didn't settle stays blank and is marked open.
Open the record → Retention · Every weekRenewal watch — the team's book
The manager's weekly list: which renewals need a look this week, the dated fact behind each one, the seller who owns it and the first question to ask. It points to signals and makes no predictions.
Open the watch list → Inbound · When an inquiry landsInbound packet — Summit Powersports
A vague email becomes a same-day reply and a proposal packet built only from approved packages. The reply goes out first. The price waits for the sales manager.
Open the packet → Practice · Before the hard conversationRehearsal — runs in your own chat
Practice has no system view here. It works as a conversation: the buyer pushes back, coaching is kept separate, and the seller tries again. The toolkit has the instructions and a scripted example to run in any approved AI chat.
Open the practice workflow → Running for real · Follow-through after a conferenceFrom card to follow-up — how I followed up after the SLC roundtables
The views above are illustrations. This one is in use: everyone who attended my three roundtable sessions at SLC had their own follow-up page within about four hours. Each page was drafted from the session recording and my notes, then edited and sent by me. The walkthrough shows the printed card, the capture on my phone and each review screen, with fictional names in the screenshots.
See how it works →02 / What changes
Same jobs, less copying and pasting.
The instructions, rules and review step are the same as in the toolkit. The difference is in how the inputs are gathered and where the result goes.
| Manual (the toolkit) | Run as a system (the design shown here) | |
|---|---|---|
| Inputs | The rep copies notes, CRM history or an export into a chat. | The account record, call notes or transcript, and billing status are pulled in for the rep. |
| Where it lands | A chat reply, in a different shape each time. | A page for the account, in the same shape every time, that the manager can open too. |
| Review | The rep reads it and decides what to keep. | Each item carries a state: done, needs you, or waiting on someone else. Nothing is sent or saved without approval. |
| After approval | The rep re-keys the parts that matter into the CRM. | Approved changes go back to the account record, with a note of who approved them. |
| Measure | Counted by hand for the 30-day test. | Counted from the record: time from call to follow-up, and renewals contacted before the window. |
A person checks every fact, supplies every price and decides what goes to the customer. The system handles the assembly and keeps the record.