For owners whose salespeople work through one contact: your last 20 to 60 closed deals, with every role involved, when you first met them, who decided, who blocked and who arrived late; what went with winning, shown honestly and checked against how the deals were recorded; a card for each role that matters in each segment, from evidence, not invented personas; and a one-page map and a checklist for every deal.
Who is involved when we sell?Every role in your last closed deals, met or not.
Who decides and who blocks?Counted by segment, with who arrives late.
What goes with winning?Win rates side by side, as associations.
What do we do differently?Role cards, actions and a deal checklist.
Choose this if you sell to organisations where several people decide, but your salespeople talk to one contact and lose deals to "the board said no". The Target Market Map says which organisations to go after; this says who inside them buys, and the Proposal Rewrite, Objection Handling Library and Call and Appointment Scripts use it.
Founder pricing. The method, the calculation spreadsheet with 30 built-in checks, and a complete worked example are built and tested. The first client for this product gets the founder price, in return for permission to measure the results and, if they are good, write them up as a case study. After that, the price goes up. Book a call to take the founder place.
Unlocks: it gives the Call and Appointment Scripts who to ask for, the CRM Blueprint its contact roles and Stalled Deal Rescue who decides and blocks, and supplies part of what the Proposal Rewrite, Objection Handling Library, Account Review Pack and Win-Loss Review need (saying what else each still needs); the share of open deals with two or more roles met before the proposal is recorded now, with a two-way spot-check, and measured again six months after go-live, with the win rate as direction only and the extra meetings costed.
A Foundations product: the groundwork the money products depend on. Its value is shown this way rather than as a single headline figure, and every number in it is labelled counted, estimated or assumed.
Roles involved, when first met, decider, blocker, late arrivals, in a workbook with 30 built-in checks.
Meetings before the proposal, on all deals and on records alone.
Fears, evidence and questions, with the deals and interviews behind each.
Content, a meeting and the early question, each staged and owned.
And a deal checklist with a check before the proposal goes out.
Guided and done for you: an agent in your own accounts logs who was involved in each new deal for your salesperson to confirm, and reminds before a proposal goes without the right people met. Nothing leaves your business, and no decision changes, without one of your people approving it.
A fictional 74-person robot cell and line integrator selling to food producers and component makers, whose salespeople worked through the engineer who sent the enquiry and kept losing to "the board said no".
From its last 45 closed deals: 60% had one role met before the proposal, or none; where the decider was met before the proposal it won 65% of 17 deals, against 21% of 24 where not (85% against 36% on CRM and email records alone; an association, not proof). Each segment now has a one-page map, role cards built from the deals rather than invented personas, and a checklist with a gate before every proposal.
Your last closed deals, won and lost.
Who decides, who blocks, what goes with winning.
A card and actions for each role that matters.
The map and the checklist on every deal.
An agent logs each new deal's buying group and updates the map.
The same method and the same spreadsheet in every option. You choose how much of your own time goes in.
For owners comfortable with a spreadsheet and an AI assistant.
For owners who want a second pair of eyes on the data and the analysis.
For owners who would rather hand over the data and get the answer.
It is built on the open Agent Skills standard and designed for Claude (any plan, with code execution switched on). A paste-in version is included for ChatGPT, Gemini and Microsoft Copilot; it has not yet been tested on them.
The calculations live in the spreadsheet, not in the AI, so the numbers don't depend on which assistant reads them.
Book a short call to talk it through.
Book a call