Designs, builds and installs robot cells, conveyors and line control systems for UK manufacturers, from a build shop in Redditch. 74 staff.
Verdict: 45 closed deals across 2 segments won 36%. On average 3.3 roles were involved in a deal but we met 1.6 before the proposal; 60% of deals had one role met before it, or none. Where we met the decider before the proposal we won 65% (of 17), against 21% where we didn't (of 24): beyond chance; on CRM and email records alone it holds. An association, not proof: a meeting late in a deal can follow winning rather than cause it. Losses rest more on salespeople's recall than wins (52% against 0%), so read the comparisons on records only. The decider is most often Owner/MD (17); Finance (10) most often appears late. 11 role cards cover 10 of the 10 roles that need one, each with the content to prepare, the meeting to ask for and the question to ask early; 2 of 2 segments are ready to use. It feeds 8 catalogue products: of 9 uses, 5 are ready now and 4 partly ready (they need something else as well). Measure later: 20% of open deals have two or more roles met before the proposal now; by the re-measure it is borderline for a realistic change; the win rate can only show direction. Costs: £7,744 one-off and £11,138 a year of extra meetings. Measure again on 2 May 2027 (early read 31 Jan 2027).
Met before the proposal Met later Involved, never met Each bar is the number of closed deals the role took part in, split by when someone from the business first met them.
Before this, salespeople worked through the operations or engineering manager who sent the enquiry. The deals show finance, technical and the owner in most of the larger ones, usually met late or not at all, and purchasing in most automotive deals, arriving at negotiation.
33% of deals from recall: 0% of won deals, 52% of deals not won: a gap of 52 points, so read the comparisons on records only too.
Every won deal was rebuilt from the CRM and emails, while half the losses rest on salespeople’s memory, which tends to remember only the contact. So each comparison below is shown twice: on all deals, and on the 27 deals recorded from the CRM and emails alone.
| Comparison | With | Without | Gap ± give or take (points) | Result |
|---|---|---|---|---|
| Decider met before the proposal (decider known): all deals | 65% of 17 | 21% of 24 | 44 ± 28 | Beyond the give or take: an association, not proof |
| Decider met before the proposal (decider known): CRM and email records only | 85% of 13 | 36% of 14 | 49 ± 33 | Beyond the give or take: an association, not proof |
| Finance met before the proposal (finance involved): all deals | 100% of 3 | 28% of 25 | – | Too few to compare (fewer than 5 deals in a group) |
| Finance met before the proposal (finance involved): CRM and email records only | 100% of 3 | 50% of 14 | – | Too few to compare (fewer than 5 deals in a group) |
| Two or more roles met before the proposal, against one or none: all deals | 67% of 18 | 15% of 27 | 52 ± 26 | Beyond the give or take: an association, not proof |
| Two or more roles met before the proposal, against one or none: CRM and email records only | 71% of 17 | 40% of 10 | 31 ± 38 | Within the give or take: could be chance |
| New robot cell or line: decider met before the proposal (decider known) | 100% of 5 | 14% of 14 | 86 ± 19 | Beyond the give or take: an association, not proof |
| New robot cell or line: two or more roles met before the proposal, against one or none | 55% of 11 | 11% of 9 | 43 ± 37 | Beyond the give or take: an association, not proof |
| Upgrade or retrofit: decider met before the proposal (decider known) | 50% of 6 | 33% of 9 | 17 ± 52 | Within the give or take: could be chance |
| Upgrade or retrofit: two or more roles met before the proposal, against one or none | 86% of 7 | 0% of 10 | 86 ± 26 | Beyond the give or take: an association, not proof |
| Controls and software: decider met before the proposal (decider known) | 50% of 6 | 0% of 1 | – | Too few to compare (fewer than 5 deals in a group) |
| Controls and software: two or more roles met before the proposal, against one or none | 0% of 0 | 38% of 8 | – | Too few to compare (fewer than 5 deals in a group) |
| Roles met before the proposal | Deals | Won | Win rate |
|---|---|---|---|
| None | 0 | 0 | – |
| 1 | 27 | 4 | 15% |
| 2 | 11 | 5 | 45% |
| 3 | 5 | 5 | 100% |
| 4 or more | 2 | 2 | 100% |
The comparisons count only meetings before the proposal: a meeting with the owner or finance late in a deal can follow winning rather than cause it, because customers who have decided introduce the people who sign. Even so, deals that were going well may be the ones where we got to meet more people early. The decider comparison holds on records alone; the two-or-more comparison doesn’t (it could be chance there), and finance met before the proposal is too rare to compare. Small groups, including most splits by deal type, are suppressed or should be read as hints.
| Stage | Deals | Of which not won |
|---|---|---|
| Enquiry | 0 | 0 |
| Discovery or survey | 2 | 1 |
| Proposal | 10 | 9 |
| Negotiation | 11 | 9 |
| Sign-off | 3 | 3 |
Decides: Owner/MD (17). Blocks: Finance (7). Appears late: Finance (10), most often at negotiation.
24 closed deals, 9 won (38%). On average 3.1 roles involved and 1.6 met before the proposal; 33% of deals had two or more roles met before the proposal. Most often decides: Owner/MD (11). Most often blocks: Finance (4). Most often appears late: Finance (6).
| Role | In deals | Met when involved | Decided | Blocked | Late | Usually appears |
|---|---|---|---|---|---|---|
| Operations Operations manager; production manager; site engineering manager | 24 (100%) | 100% | 6 | 0 | 0 | Enquiry |
| Technical/H&S Technical manager; food safety or hygiene manager; health and safety adviser | 18 (75%) | 44% | 0 | 3 | 4 | Discovery or survey |
| Finance Finance director; financial controller; group finance in larger groups | 17 (71%) | 35% | 6 | 4 | 6 | Proposal |
| Owner/MD Owner; managing director (family-owned producers) | 12 (50%) | 50% | 11 | 1 | 2 | Proposal |
| End user Shift leaders; line operators; maintenance technicians | 2 (8%) | 50% | 0 | 0 | 0 | Discovery or survey |
| Procurement Purchasing manager in group-owned producers | 2 (8%) | 50% | 0 | 1 | 1 | Sign-off |
Deal checklist, S1
| When | Do this | Ask early | Bring |
|---|---|---|---|
| First meeting | Ask who else will be involved in deciding and who signs off; record each role against the deal in the CRM, and each meeting with its date | Who else will be involved in deciding, and who signs off? | – |
| By enquiry | Operations (usually appears at enquiry): Trial or simulation review with the operations manager | Who else will be involved in deciding, and who signs off spend of this size? | Trial or simulation results on the customer's own product; the installation timetable |
| By discovery or survey | Owner/MD (usually appears at proposal): Reference-site visit, or a 30-minute call with our managing director | Will the owner want to meet us before deciding, and at what stage? | Installation and fallback plan; two reference sites willing to host a visit |
| By discovery or survey | Technical/H&S (usually appears at discovery or survey): Technical review at the site survey | Who signs off food safety and machinery safety, and can they join the survey? | Hygiene and guarding pack: cleaning method, materials, risk assessment outline and the technical file contents list |
| By discovery or survey | End user (usually appears at discovery or survey): Ten minutes with a shift leader and a maintenance technician at the survey | Who will run and maintain it, and can we talk to them at the survey? | Short video of changeover and jam clearing on a similar cell; training plan by shift |
| By discovery or survey | Procurement (usually appears at sign-off): Call with purchasing before the proposal to agree whose terms apply | Does the order go through a group purchasing team, and whose terms will it be on? | Supplier approval pack: questionnaire answers, insurance certificates, accreditations and our usual positions on the terms |
| Gate: before the proposal goes out | Check that two or more roles have been met in a meeting, including the one that usually decides or blocks; if not, ask for that meeting before sending | What will the people who sign off need to see? | – |
| By proposal | Finance (usually appears at proposal): Payback review with finance before the proposal goes to the board | Who signs off spend of this size, and what does the board need to see? | One-page payback sheet from the customer's own figures, with a half-as-well case; payment schedule |
21 closed deals, 7 won (33%). On average 3.4 roles involved and 1.6 met before the proposal; 48% of deals had two or more roles met before the proposal. Most often decides: Owner/MD (6). Most often blocks: Procurement (4). Most often appears late: Procurement (6).
| Role | In deals | Met when involved | Decided | Blocked | Late | Usually appears |
|---|---|---|---|---|---|---|
| Operations Operations manager; manufacturing engineering manager | 21 (100%) | 100% | 5 | 0 | 0 | Enquiry |
| Procurement Purchasing manager; group procurement; supplier quality | 18 (86%) | 33% | 2 | 4 | 6 | Negotiation |
| Technical/H&S Quality manager; manufacturing engineer; health and safety manager | 14 (67%) | 64% | 0 | 1 | 1 | Discovery or survey |
| Finance Group finance; finance director | 11 (52%) | 27% | 5 | 3 | 4 | Proposal |
| Owner/MD Managing director; site general manager | 6 (29%) | 33% | 6 | 1 | 1 | Proposal |
Deal checklist, S2
| When | Do this | Ask early | Bring |
|---|---|---|---|
| First meeting | Ask who else will be involved in deciding and who signs off; record each role against the deal in the CRM, and each meeting with its date | Who else will be involved in deciding, and who signs off? | – |
| By enquiry | Operations (usually appears at enquiry): Trial review with the operations and quality managers | Who else will be involved in deciding, and is there a capital approval form? | Trial results on the customer's own parts, with cycle time and capability |
| By discovery or survey | Procurement (usually appears at negotiation): Call with purchasing before the proposal to agree whose terms apply | Are we on your approved supplier list, and whose terms will the order be on? | Supplier approval pack: questionnaire answers, insurance certificates, accreditations and our usual positions on the terms |
| By discovery or survey | Technical/H&S (usually appears at discovery or survey): Quality and safety review at the trial | Who approves quality and machinery safety on a new cell, and can they see the trial? | Capability results and the documentation list; risk assessment outline and guarding approach |
| By discovery or survey | Finance (usually appears at proposal): Thirty minutes with finance to check the approval form before it goes in | Is there a capital approval form and a payback limit, and who completes it? | Capital approval form completed with the customer's own figures and a cautious case |
| By discovery or survey | Owner/MD (usually appears at proposal): Short meeting between the two managing directors | Does the managing director sign this off, and when would they want to meet us? | Start-of-production plan with milestones; two references from similar component makers |
| Gate: before the proposal goes out | Check that two or more roles have been met in a meeting, including the one that usually decides or blocks; if not, ask for that meeting before sending | What will the people who sign off need to see? | – |
| Role | What they fear | Evidence they need | What they ask |
|---|---|---|---|
| S1 · Operations met in 24 deals; 4 interviews or notes | The installation running into production; the line not reaching rate; being blamed if it doesn't work | A trial or simulation on their own product; the installation timetable; what rate we commit to and how it is tested | How long will the line be down? What rate will it really run at? Who supports it at three in the morning? |
| S1 · Technical/H&S met in 8 deals; 3 interviews or notes | Equipment that can't be cleaned properly; a guarding or PUWER finding after installation; a non-conformance at the next audit | Hygienic design details and the cleaning method; the risk assessment and guarding approach; the declaration of conformity and technical file contents; references from other food sites | How is it cleaned, and how long does it take? Who signs the risk assessment? What do we get at handover? |
| S1 · Finance met in 6 deals; 3 interviews or notes | A project that overruns or pays back later than promised; committing cash before the order book supports it | Payback built from the customer's own figures (labour hours, giveaway, downtime) with a cautious case; staged payments; what is and isn't included | What is the payback if output is only half what you say? What does it cost us if it's late? Can the payments be staged? |
| S1 · Owner/MD met in 6 deals; 3 interviews or notes | Disrupting supply to a major retailer during installation; backing the wrong supplier; a project the staff won't accept | An installation plan built around production with a fallback; references from similar owner-run producers; who supports it after handover | What happens if it doesn't work on day one? Who do I call? Have you done this for someone like us? |
| S1 · End user met in 1 deal; 1 interview or note; thin evidence | Equipment that is hard to clear when it jams; more work at changeover; not being trained | Changeover and jam-clearing shown on a similar cell; a training plan by shift; the spares list | How do we clear a jam? How long is changeover? Who trains the night shift? |
| S1 · Procurement met in 1 deal; 1 interview or note; thin evidence | A supplier that isn't approved; terms that leave the group exposed; quotations that can't be compared | The supplier questionnaire completed; insurance certificates; our terms marked against theirs; a price breakdown | Are you on our approved list? Will you accept our terms? Can you break the price down? |
| S2 · Operations met in 21 deals; 3 interviews or notes | A cell that doesn't hold cycle time or quality; the changeover onto a new part taking weeks | Cycle-time and capability results from a trial on their own parts; the changeover plan for new parts | What cycle time will it hold? How quickly can we change it over for a new part? |
| S2 · Procurement met in 6 deals; 3 interviews or notes | A supplier that isn't approved; unlimited liability or warranty terms; prices that can't be compared like for like | The supplier questionnaire completed; insurance certificates and accreditations; our terms marked against theirs; a price breakdown | Are you on our approved list? Will you accept our terms? What are your payment terms? |
| S2 · Technical/H&S met in 9 deals; 2 interviews or notes | A cell that passes the trial but drifts in production; missing quality documentation; a guarding finding after installation | Capability results on their parts; the quality documentation the customer's own customers require; the risk assessment and guarding approach | What capability did it show on our parts? What documentation do we get? Who signs off the guarding? |
| S2 · Finance met in 3 deals; 2 interviews or notes | Payback beyond the group's limit; prices that change after approval | Payback in the group's own format from the customer's figures, with a cautious case; a fixed price and its validity | What is the payback on our numbers? How long is the price fixed for? |
| S2 · Owner/MD met in 2 deals; 2 interviews or notes | A cell that delays a new contract's start of production; a supplier the group hasn't heard of | The start-of-production plan with its milestones; references from similar component makers | Will it be ready for the start of production? Who else have you done this for? |
No invented people: no names, ages or hobbies. Each card counts the deals in which the role was met plus the interviews and notes behind it, and lists them in the workbook. Two cards (food producers’ end users and purchasing) rest on thin evidence. Full cards, with how to reach each role and the actions, owners, stages and dates, are in the workbook and the pack.
| Product | Segment | What it needs | What its own kit asks for | Status |
|---|---|---|---|---|
| Proposal Rewrite | All | Role cards: evidence each role needs | Proof for the template: case studies with the client's permission, CVs, insurance certificates, standard terms (its SKILL.md) | Partly ready: also needs the proof itself (case studies with permission and payback examples), made by the actions on the cards |
| Objection Handling Library | All | Role cards: fears and questions | The objections, with stage, deal reference and source; its defaults include "decision-maker not here" (its SKILL.md) | Partly ready: also needs a two-week tally of the objections the team hears |
| Value Proposition and Messaging | S1 | Role cards: who buys and what each cares about | Target segments (up to four) and who buys in each (its SKILL.md) | Ready now |
| Value Proposition and Messaging | S2 | Role cards: who buys and what each cares about | Target segments (up to four) and who buys in each (its SKILL.md) | Ready now |
| Call and Appointment Scripts | All | Checklist: who to ask for and the early question | A conversation is a call that reached the decision-maker (its method) | Ready now |
| Account Review Pack | All | Roles to keep in contact with | Who you deal with at each account, by role, with the last date spoken to or met (its SKILL.md) | Partly ready: also needs a contact log for each key account by role and date |
| CRM Blueprint | All | Buying roles for the CRM | A field dictionary with picklist values; its contact role picklist (its SKILL.md and worked example) | Ready now |
| Stalled Deal Rescue | All | Decider and blocker patterns | The six answers for each open deal, including no decision-maker, no budget holder and no champion (its SKILL.md) | Ready now |
| Win-Loss Review | All | Decider and blocker patterns | Six to ten customers (some who said yes, some who said no) willing to talk for about 15 minutes (its SKILL.md) | Partly ready: also needs six to ten customers willing to be interviewed |
Partly ready means this map supplies its part, but the product needs something else too: willing interviewees for the Win-Loss Review, a contact log for each key account for the Account Review Pack, the proof itself for the Proposal Rewrite, and a tally of objections for the Objection Handling Library.
Main measure: 8 of 40 open deals (20%, give or take 13 points); spot-check of 10 deals: 16 of 17 logged roles confirmed, 1 met but not logged. With 40 open deals expected, the smallest change it can show (80% power, at 20% and 50%) is 28 points against a realistic 30 (assumed): borderline, so read the result with care.
Win rate: 36% now; with 22 deals closing by the re-measure, the smallest change it can show is 36 points: direction only.
Counted like for like: open deals created in the six months before each count and at least 30 days old, from the CRM; a role counts as met only in a meeting or site visit before the proposal, and at least one of the roles must be one that decides or blocks. A spot-check against diaries and email both confirms what the CRM says was met and finds what it missed, both times. At the re-measure only deals created after go-live count. Go-live, early read and re-measure: 2 Nov 2026; 31 Jan 2027; 2 May 2027.
Costs: £7,744 one-off and £11,138 a year of extra meetings. Illustration only: £95,693 a year in gross profit at 40%; £47,847 if it moves half as far (what it would be worth if the owner’s target win rate were reached is an illustration, not a forecast).
The deals are 45 closed deals from the business's CRM, emails and quotation log, with the roles involved, the stage each was first met, who decided, who blocked and who appeared late as the business recorded or remembered them (33% from salespeople's recall, which forgets the people we never met: 0% of won deals and 52% of deals not won). The win rates side by side are associations, not proof: deals that were going well may be the ones where we got to meet more people, and a meeting late in a deal can follow winning rather than cause it, so the comparisons use meetings before the proposal and are shown on CRM and email records alone too; a comparison is shown only with at least 5 deals in each group. The role cards are the team's judgement from the deals where each role was met and 27 interview and note references, each card listing its evidence; which roles need a card (20% of a segment's deals, or any that decided or blocked) and the thresholds are assumed. The value case is Unlocks: it names what the catalogue products need from this map, and what else some of them need; it is not a forecast of sales. The measure-later share is counted from the source named on Inputs (CRM: contacts linked to each opportunity, with meetings and site visits logged against the opportunity by date), 40 open deals now, with a two-way spot-check; the realistic change (30 points), the extra meetings per deal and the owner's target win rate are assumed, so any £ figure is an illustration.
The deal and role records identify people at customers, including judgements such as who blocked a deal: they are kept under a legitimate interests assessment, business contacts and interviewees are told in a privacy notice, and they are kept for 36 months. Not legal advice. The map is finished when it is handed over. Add each closed deal as it closes and review the cards once a quarter.
Fictional, continuing the example: Wrenstall Automation, its deals and every figure here are invented. Deals are shown by reference and people by role. The counts were tallied from the story, not by rerunning the workbook; seven of the agent’s log rows are on the Agent sheet of the worked-example workbook.
Wrenstall chose done for you. At handover Geoff set up the buying group agent in Wrenstall’s own account, in an AI assistant the business already uses, with its IT’s agreement: connected read-only to the CRM’s opportunities, contacts and logged meetings, the quotation log and the sales team’s diaries, and writing only to the workbook and one shared drafts document. Before it ran, Wrenstall confirmed its legitimate interests assessment and privacy notice covered the agent and recorded a data protection impact assessment, because the deal records judge identifiable people at customers deal after deal (not legal advice). It started on go-live, Monday 2 November. The two agent settings are on Inputs: a deal flagged 5 working days before its proposal is due if the gate isn’t met, and every closed deal’s roles confirmed by its salesperson within 10 working days. The run details are on the Agent sheet: the managing director reads the weekly note, the sales director approves any change to a card, and the office manager, who logs no meetings, runs the spot-check. The salespeople sent their own meeting requests and confirmed every deal the agent logged. Nothing left the business, and no decision changed, without one of its own people approving it. At the check-in on Wednesday 2 December, 30 days after go-live, Geoff read the log with the managing director on screen in Wrenstall’s account; his upkeep of the set-up ended there.
| Date | What the agent logged or flagged | Confirmed or decided by | What happened |
|---|---|---|---|
| 2 Nov 2026 Flag | WA-26-081 (S1, new robot cell; open) Proposal due in 5 working days with only the operations manager met. Drafted a request for a payback review with the MD and the financial controller. | Sales director | Sent his own version; met both on 6 November; proposal went a day late, on 10 November. |
| 9 Nov 2026 Logged | WA-26-074 (S2, upgrade; lost 28 October) Logged from the CRM and diaries; who decided and who blocked left Not known. | Sales engineer (ran the deal) | Confirmed; procurement blocked on payment terms, from the customer’s loss email. |
| 16 Nov 2026 Logged | Card: S1 Procurement WA-26-078 logged: the card’s evidence rises from 2 items to 3, no longer thin. | Sales director | Card read against the new deal; no change. |
| 30 Nov 2026 Flag | WA-26-079 (S1, controls; lost 13 November) Roles not confirmed 10 working days after closing. | Sales director | Confirmed from the CRM and the loss email on 1 December. |
| 7 Dec 2026 Flag | WA-26-083 (S2, new cell; open) A contact’s name in the CRM notes kept out of the workbook: the row says “Finance”. | Sales director | Sales team asked to note roles, not names, in the CRM too. |
| 14 Dec 2026 Logged | WA-26-086 (S2, upgrade; open) Gate met before the proposal (procurement and operations). | Sales director | Proposal sent on 17 December. |
| 1 Feb 2027 Logged | Measure later: early read Open deals counted the same way as the baseline: 14 of 31 with two or more roles met before the proposal. Ten drawn at random for the spot-check. | Managing director | Spot-checked by the office manager; entered on the Value Case on 4 February. |
The early read is an early look, not a verdict. The share rose from 20% to 45%, a change of 25 points, but with about 40 deals at each count the smallest change it can show is 28 points: this is inside what chance could do, so it is read again at the re-measure on 2 May 2027. The spot-check found 21 of 22 logged roles confirmed and 2 met but not logged, so the rise is not the logging alone. Recall fell as a share of the deals logged, because every new deal came from the CRM and diaries. Confirming a deal took a salesperson about 5 minutes, and reading the weekly note the managing director about 10 (estimates). The months after add nothing to the value case above.