One saved session per call, opened from the deal card and pre-filled with the builder's name and contact. Every capability is a box on the panel carrying the casual question to ask, four buttons for what they hear, and the tools they name. Everything on screen derives from the whole session on every render, because a sales conversation goes wherever the prospect takes it.
Also called: discovery call · sales call guide · what do you use today · qualification · call script · discovery call tool · capability gap map · where is this shop losing money
- 1Answer any box in any order with one of four states: none, manual, siloed, connected.
- 2Naming a tool attaches it to the call from the provider library, with what they pay and how confident that figure is.
- 3Views switch between the panel, the buyer read, the web, the money paths and the brief.
- 4Saving is a debounced background write, not a button — the server recomputes every score on write so the roster can never disagree with the panel.
- 5Closing the tab mid-debounce triggers a last-chance save.
- 6Starting a discovery call from a deal card links the session and moves the card to the Discovery stage.
The panel states the constraint it is built for: 'a sales conversation goes wherever the prospect takes it, so the panel can never assume boxes get ticked in any particular order.' Auto-save exists because 'a rep on a live call will not press save, and the one thing worse than an unsaved call is a rep thinking about saving while a prospect is talking.'
- Reps led with the module they personally liked rather than the prospect's real gap.
- Notes taken on a call were unstructured and unusable afterwards.
- What a prospect currently pays for tools was never captured.
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 →