Mechanical, electrical and public health engineering consultancy designing heating, cooling, ventilation, power, lighting and water systems for hospitals, universities, schools and commercial buildings, from offices in Leeds, Manchester and Sheffield. 240 staff.
Verdict: 12 sellers in two waves each have a profile to the standard (12 of 12 meet it), 60 target accounts of their own with enough people to ask until the re-measure, and a weekly routine of about 1.7 hours that fits the time each agreed; 13 approved items to share over 13 weeks; 11 of 11 policy items agreed by go-live, those covering the tally before it began, with no tool that automates or scrapes. Measure later: conversations per request 2.9% now (main): by the re-measure a real change of the target's size would be seen four times in five; acceptance 27.1% (process), a real change of the target's size would be seen four times in five; meetings direction only; the early read nets wave 1 against wave 2 (direction only). Different times of year, and the tally ran through the summer holidays. The re-measure isn't netted, so read it with the early read's netted change. To cover the cost in full takes about 19 extra social-sourced meetings a year, 82% more than today's 23; by the re-measure a rise under 311% could be chance, so a rise that just pays its way couldn't be told from chance. Illustration only: £87,400 a year from 23 extra meetings (capped at the owner's meetings target; 41 if the main target were reached in full), not a forecast. Unlocks: Target Account List: 12 of 12 Tier 1 accounts have 3 or more people connected; Buying Group Map: 48 of 60 accounts have someone connected in two or more roles. Early read 8 Mar 2027; measure again 7 Jun 2027.
| Seller | Wave | Requests a week | Routine minutes (needed of agreed) | Profile items (before → after) | Tally: conversations of requests | Accepted | Accounts | People left for requests needed |
|---|---|---|---|---|---|---|---|---|
| Idris Business development manager, health | 1 | 5 | 104 of 120 | 3 → 10 | 1 of 40 | 11 | 5 | 120 for 110 |
| Morwenna Business development manager, education | 2 | 5 | 104 of 120 | 2 → 10 | 1 of 40 | 10 | 5 | 120 for 110 |
| Folake Business development manager, commercial | 1 | 5 | 104 of 120 | 3 → 10 | 2 of 40 | 12 | 5 | 120 for 110 |
| Sorcha Associate director, mechanical (health) | 2 | 4 | 101 of 110 | 2 → 10 | 1 of 32 | 9 | 5 | 94 for 88 |
| Esme Associate director, electrical (health) | 1 | 4 | 101 of 110 | 3 → 10 | 1 of 32 | 8 | 5 | 94 for 88 |
| Kwame Associate director, mechanical (education) | 2 | 4 | 101 of 110 | 4 → 10 | 0 of 32 | 8 | 5 | 94 for 88 |
| Bartek Associate director, public health (commercial) | 1 | 4 | 101 of 110 | 2 → 10 | 1 of 32 | 9 | 5 | 94 for 88 |
| Elspeth Associate director, sustainability | 2 | 4 | 101 of 110 | 3 → 10 | 1 of 32 | 8 | 5 | 94 for 88 |
| Anjali Associate director, electrical (commercial) | 1 | 4 | 101 of 110 | 2 → 10 | 1 of 32 | 9 | 5 | 94 for 88 |
| Rhodri Regional director, Leeds | 2 | 3 | 98 of 105 | 3 → 10 | 1 of 24 | 7 | 5 | 71 for 66 |
| Joel Regional director, Manchester | 1 | 3 | 98 of 105 | 1 → 10 | 1 of 24 | 6 | 5 | 71 for 66 |
| Zara Regional director, Sheffield | 2 | 3 | 98 of 105 | 3 → 10 | 0 of 24 | 7 | 5 | 71 for 66 |
Each seller's acceptance in the tally (the process measure), asking the way they do now. The last column shows the people still to ask at their accounts against the requests they need until the re-measure. At a few dozen requests each, a seller's own figure shows direction only, and is for their development with their manager, never for discipline (policy items P10 and P11).
| Activity | What it means | Minutes each (assumed) | Times a week |
|---|---|---|---|
| R1 · Find | Search the seller's target accounts for people in the buying-group roles and add them to the seller's list, in list order | 3 | 5 |
| R2 · Connect with a personal note | A connection request to a person at a target account, with a note that says why (one line about them or their work, never a pitch) | 3 | each seller's requests |
| R3 · Engage | A thoughtful comment on a post by a person at a target account (adds something; never 'great post') | 4 | 6 |
| R4 · Share | One approved item from the content plan, with a line of the seller's own | 10 | 1 |
| R5 · Move to conversation | A message to an accepted connection with something useful to them, saying who it's from and offering an easy way to say no more messages; a call offered where it fits; no sequences | 6 | 3 |
| R6 · Log it in the CRM | Each accepted connection, conversation and meeting recorded, with the source field set to the social value | 2 | 6 |
| Review · Weekly review with the manager | The seller's numbers for the week and one thing to do differently (from Inputs) | 10 | 1 |
Every request goes to a person at the seller's own target accounts, drawn in list order, with a personal note; every message is written by the seller. No tool sends, connects, comments, likes or messages for them, and nothing copies profiles or contacts in bulk: the platform's user agreement forbids it, and the policy says so. Every message says who it is from and offers an easy way to opt out, and sole traders and partnerships are left out (PECR treats a direct message as electronic mail). All twelve sellers have the platform's paid seat (from the client's quotation), because a free account allows only a handful of personal notes a month.
| Module | Hours | What each seller produces | Wave 1 | Wave 2 |
|---|---|---|---|---|
| M1 The profile standard | 1.5 h | Profile rewritten to the standard and scored by both scorers | 02 Nov | 08 Feb |
| M2 Finding the right people at your accounts | 1.5 h | Forty people found in the buying-group roles at the seller's target accounts, in list order | 09 Nov | 15 Feb |
| M3 The personal note, the platform's rules and our policy | 1.5 h | Three notes of their own; the policy signed | 16 Nov | 22 Feb |
| M4 Engaging and sharing | 1.5 h | First comments and the first approved share | 23 Nov | 01 Mar |
| M5 From connection to conversation to meeting, and logging it | 1.5 h | First conversations and meetings logged with the source field | 30 Nov | 08 Mar |
| M6 The weekly routine: owning it | 1 h | Routine and minutes agreed with their manager | 07 Dec | 15 Mar |
| Seller | Before | After |
|---|---|---|
| Idris Business development manager, health | Business Development Manager at Ellerholt 3 of 10 (A), 3 (B) | Business development, Ellerholt Building Services Engineers | Helping hospital estates teams plan heating, ventilation and power upgrades they can deliver around patients 10 of 10 (A), 10 (B, blind) |
| Joel Regional director, Manchester | Director 1 of 10 (A), 2 (B) | Regional director, Ellerholt Manchester | Building services engineering for clients and contractors across the North West 10 of 10 (A), 10 (B, blind) |
| Sorcha Associate director, mechanical (health) | Associate Director 2 of 10 (A), 2 (B) | Associate director, mechanical, Ellerholt | Ventilation and heating design for hospitals, including theatres and isolation rooms 10 of 10 (A), 10 (B, blind) |
12 of 12 meet the standard; 2.6 items before, 10.0 after; scored by marketing manager and, blind, bid manager; 0 more than 1 item apart. The standard: 1. A current photo of the seller's face, taken professionally or to the same standard; 2. Headline says who they help and with what, not just a job title; 3. Current role names the business and says what it does in one line, in the customers' words; 4. About section says who they help and how, with no claim beyond the business's approved wording; 5. Experience: the current role described and the dates right; 6. One way to get in touch that works (tested); 7. Featured or pinned item points to something useful that exists, approved by marketing; 8. Background image is the business's current approved version; 9. Nothing confidential about clients; no client named without the client's permission; 10. Headline within the character limit (counted).
| Segment | Accounts | Tier 1 | People in the roles (estimate) | Found | Asked in the tally | Tier 1 with 3+ connected | Two or more roles connected |
|---|---|---|---|---|---|---|---|
| Health | 20 | 4 | 507 | 205 | 128 | 4 of 4 | 16 of 20 |
| Education | 20 | 4 | 507 | 210 | 128 | 4 of 4 | 16 of 20 |
| Commercial | 20 | 4 | 507 | 209 | 128 | 4 of 4 | 16 of 20 |
Accounts are described by kind here; the client's own sheet names them. The roles come from the Buying Group Map: estates or facilities director, capital projects lead, project manager and procurement.
| Week | Kind | Title | Writes it | Approves it |
|---|---|---|---|---|
| 1 | Company article | Five questions to ask before a hospital ventilation upgrade | Marketing manager | Technical director |
| 2 | Someone else's article or guidance | Published guidance on heat networks, with our associate director's two-line view | Associate director, sustainability | Technical director |
| 3 | Case study | A university library moved from gas boilers to heat pumps, with the building open claim: evidence on file client named: permission | Marketing manager | Technical director |
| 4 | Seller's own post | What a standby generator test taught us about hospital resilience | Associate director, electrical (health) | Technical director |
| 5 | Thought leadership piece | Why we think estates teams should plan for the building they run, not the one on the drawings | Managing director | Technical director |
| 6 | Company article | Electric vehicle charging in logistics schemes: what the power supply needs | Marketing manager | Technical director |
| 7 | Event or webinar | Webinar: planning ventilation work in occupied schools | Marketing manager | Technical director |
| 8 | Someone else's article or guidance | Published research on overheating in schools, with our view on what to check first | Associate director, mechanical (education) | Technical director |
| 9 | Case study | An office refurbishment that kept its existing risers claim: evidence on file client named: permission | Marketing manager | Technical director |
| 10 | Seller's own post | Water hygiene in hotels after a long closure: what to check | Associate director, public health (commercial) | Technical director |
| 11 | Company article | Heat pumps in older teaching buildings: three things that decide it | Marketing manager | Technical director |
| 12 | Thought leadership piece | What we've learned from designing services for buildings that stay open | Managing director | Technical director |
| 13 | Company article | Laboratory ventilation: the questions developers ask us most | Marketing manager | Technical director |
The approver is never the writer. The two case studies make claims backed by evidence on file and name clients who gave permission (CAP Code 3.7 and 3.50 where it applies, a house rule everywhere). The managing director's pieces come from the Thought Leadership Programme; sellers reshare them with a line of their own.
| Item | Reference (checked 16 October 2026) | Status |
|---|---|---|
| P1 Social media policy for selling | The client's own HR policy; the solicitor where it touches the employment contract | Agreed 09 Oct 2026 HR manager |
| P2 Who owns contacts made for work, and what happens when a seller leaves | The employment contract and confidentiality terms: for the client's solicitor (not legal advice) | Agreed 09 Oct 2026 HR manager |
| P3 Lawful basis for recording contacts in the CRM | ICO, A guide to lawful basis: legitimate interests (updated 23 March 2026) | Agreed 10 Jul 2026 Finance director (data protection lead) |
| P4 Telling contacts we hold their details | UK GDPR Article 14(3) (legislation.gov.uk) | Agreed 10 Jul 2026 Finance director (data protection lead) |
| P5 Emails and direct messages to contacts found on the platform | ICO, Electronic mail marketing (PECR): direct messages via social media are covered | Agreed 09 Oct 2026 Marketing manager |
| P6 No automation or bulk copying on the platform | The platform's user agreement (LinkedIn's effective 3 November 2025, section 8.2), checked against the live version on the date on Inputs | Agreed 09 Oct 2026 Sales director |
| P7 One real account per seller | The platform's user agreement, checked against the live version | Agreed 09 Oct 2026 Sales director |
| P8 Claims in posts and shares | CAP Code rules 3.7, 3.47, 3.50; scope clause I h (asa.org.uk) | Agreed 09 Oct 2026 Marketing manager |
| P9 The regulator's rules on social media | For example the FCA's FG24/1, Financial promotions on social media (26 March 2024); otherwise the business's own regulator | Not regulated: doesn't apply |
| P10 Measuring the sellers themselves | ICO, Employment practices and data protection: monitoring workers | Agreed 10 Jul 2026 HR manager |
| P11 Per-seller results never used for discipline unless the policy says so | House rule; ICO monitoring workers guidance | Agreed 10 Jul 2026 HR manager |
| P12 How long the tallies and per-seller figures are kept | UK GDPR storage limitation; the retention period on Inputs | Agreed 10 Jul 2026 Finance director (data protection lead) |
Not legal advice. The five items covering the tally itself (the lawful basis and notice for contacts recorded, telling sellers what is counted, discipline and retention) were agreed before it began. The client's solicitor reviewed who owns contacts made for work when a seller leaves; their fee is the client's cost, paid directly.
Sized before the tally:
| Measure | Sizing |
|---|---|
| Conversations per request (main) | Enough: 384 requests planned against 258 needed |
| Acceptance (process) | Enough: 384 requests planned against 153 needed |
| Meetings | A snapshot, direction only: about 4 expected in the tally weeks against 25 needed |
| Measure | Now | Smallest change it could show (80% power) | What it can show |
|---|---|---|---|
| Main: conversations per request to people at target accounts (a reply within 28 days) | 2.9% (11 of 384) | 4.6 points (target gap 5.1) | A real change of the target's size would be seen four times in five |
| Process: acceptance (within 14 days) | 27.1% (104 of 384) | 9.5 points (target gap 12.9) | A real change of the target's size would be seen four times in five |
| Third: social-sourced meetings (CRM source field) | 4 in 8 weeks | a rise of 455% | Direction only: too few meetings to say more (a snapshot) |
| Early read: wave 1's conversations per request net of wave 2 | 3.5% and 2.2% | 9.2 points | Direction only: the target gap is smaller than the smallest change it could show |
3.5% wave 1 and 2.2% wave 2 now; direction only: the target gap is smaller than the smallest change it could show (smallest change 9.2 points). Tally 20 Jul to 13 Sep 2026; re-measure window 15 Mar to 9 May 2027. Different times of year, and the tally ran through the summer holidays. The re-measure isn't netted, so read it with the early read's netted change. 12 sellers have a manager who also manages the other wave: managers are asked not to pass the routine to wave 2 early; wave 2's paid seats start with its first module. Requests are counted once each has had its full 14- and 28-day windows, and meetings come from a CRM source field set up before the tally. The re-measure compares everyone with the tally and isn't netted. A change shows what the profiles, notes and routine did together, never one alone.
Unlocks: Target Account List: 12 of 12 Tier 1 accounts have 3 or more people connected; Buying Group Map: 48 of 60 accounts have someone connected in two or more roles. The routine builds both: people found and connected at each account feed the Target Account List's mapping and the Buying Group Map's roles met before a proposal.
Cost in full: £71,390 (£6,500 fee ex VAT; £39,026 sellers' routine time; £4,284 modules; £5,336 managers' reviews; £1,740 setting up; £3,596 content; £8,064 tools; £744 source field and counting; £1,200 solicitor and £900 other specialists, paid directly).
Break-even: To cover the cost in full takes about 19 extra social-sourced meetings a year, 82% more than today's 23; by the re-measure a rise under 311% could be chance, so a rise that just pays its way couldn't be told from chance. Illustration only: £87,400 a year from 23 extra meetings (capped at the owner's meetings target; 41 if the main target were reached in full), not a forecast.
The profile standard is judged by marketing manager and, blind, by bid manager, neither a seller nor a writer of the rewrites. The routine's minutes are estimates (assumed) checked against the minutes each seller agreed; the platform's limits are assumed until checked on its help pages, and its terms were read against the live user agreement on 14 Oct 2026. The baseline is a 8-week tally of 384 requests to people at the sellers' own target accounts (the same requests as on Targets), drawn in list order (not chosen), sent the way they do now and counted once each had its 14- and 28-day windows; meetings come from a CRM source field set up before the tally, and the policies covering the tally were agreed before it began. The tally was sized before collecting. The main measure is conversations per request; acceptance is a process measure. At the early read wave 1 is compared with wave 2, which hasn't started, over the same weeks, so the season and any platform change are netted out; the re-measure compares everyone with the tally and isn't netted, and falls at a different time of year from the tally. A change shows what the routine, profiles and notes did together, never one alone. The targets, the expected rates used for sizing, the people in the roles at each account, the 50% counted as truly extra and the minutes are assumptions; the tally, meetings, conversion, gross profit, rates and costs are from the records and quotations. Per-seller figures are for development only. Policy items are not legal advice: the client's solicitor reviews contact ownership. The break-even and any £ figure are illustrations, not forecasts.
The programme is finished when it is handed over: the six modules and the weekly routine, the profile standard with each seller's scored rewrite, the 13-week content plan with its approval rules, the signed policy and the tracking sheet.
Fictional, continuing the example. Ellerholt chose the guided route. The agent was set up in an AI assistant the business already uses, connected read-only to the CRM (its IT confirmed this before it committed); it never touches the platform, where the sellers act and log their own activity. Every Monday it reads what each live seller logged with the social source the week before, enters it in a new dated copy of the workbook, runs the checks, and sends each seller and their own manager a short note on their own figures only. It uses the lines on Inputs: a week below 50% of the requests a seller agreed counts as missed, and 2 missed weeks in a row are flagged; any seller over the platform's limit of 100 requests a week is flagged the same week. Every four weeks it reports what the routine brings, direction only until the early read. Measuring the sellers was agreed and they were told (policy P10); the results are for development only (P11). Nothing left the business, and no decision changed, without one of its own people approving it.
| Date | What the agent flagged | What was decided |
|---|---|---|
| 14 Dec No flag | The first week after go-live: the six wave 1 sellers logged 25 requests with the social source, against the 25 they had agreed. | Nothing needed. Each seller and their manager read their own note. |
| 18 Jan Flag | Joel logged 1 request and then none, against 3 a week, while he wrote the hospital framework bid. | His manager agreed the bid came first; Joel restarted at 3 a week from 1 February. Nothing changed on the Sellers sheet. |
| 1 Feb Flag | Folake logged 112 requests in one week, over the platform’s limit of 100. | A browser extension had been sending requests from a saved list, which the policy forbids. The sales director had it removed the same day and the marketing manager checked every seller’s browser. |
| 22 Feb Flag | Kwame logged no requests in the first two weeks of wave 2. | His paid seat had not been assigned. The marketing manager assigned it and his manager booked a short catch-up; he logged 4 the next week. |
| 1 Mar No flag | The four-weekly summary: 14 conversations from 296 requests since go-live (4.7%), against 2.9% in the tally, and 3 meetings booked. | Nothing needed. The sales director will judge it at the early read on 8 March, netted against wave 2, as planned. |
At the 30-day check-in on 15 December, the day after the first run, Geoff and the sales director read the first notes and the log together. No rule needed changing. What the agent added. The method is unchanged: same routine, same tally, same reads. The agent made sure the routine was checked every week, seller by seller, which managers' weekly reviews were meant to do and often skipped. One flag stopped automated requests that put a seller's account and the policy at risk; two restarted a routine that had lapsed for a reason someone could fix. Conversations per request since go-live look higher than in the tally, but that is direction only: the early read, netted against wave 2, is the measure, and no £ figure is claimed.