An engineering-led company with excellent products and almost no buyer-facing language asked me for a commercial growth system in one quarter. This is what I built, how I measured it, and what their marketing lead, sellers and leadership run today without me.
The client makes control, orchestration and analytics technology for mixed-brand generator fleets and other power assets. The engineering was ahead of the market. The commercial side was not. Buyers who already knew the name found it. Buyers who had the problem but not the name never reached the door. No shared buyer language, no competitive radar, no measured baseline of search and AI visibility, and nothing a sales engineer could hand to a prospect.
The Statement of Work lets me reference this engagement in general portfolio terms. The findings and figures, even anonymized, are the client's analyses and need their written permission. What I can say today: the client went from no instrument to a measured position on four readings, AI answer appearances, branded share of search, organic keywords and referring domains, each labeled Confirmed and traceable to one instrument and one date. The numbers go up the day the permission arrives.
| Reading | Baseline (July 2026) | Closing (30 Sep 2026) | Label |
|---|---|---|---|
| Appearances in AI answers, client vs direct rivals | Withheld | Withheld | Confirmed |
| Share of clicks from branded searches | Withheld | Withheld | Confirmed |
| Organic keywords | Withheld | Withheld | Confirmed |
| Referring domains and backlinks | Withheld | Withheld | Confirmed |
The gap did not close in 90 days, and I would rather say so here than have you find out later. The baseline moved the client from no instrument to a measured position. The roadmap is what closes the gap. Visibility figures come from one market intelligence dataset, search figures from Search Console, and the two are never added together.
| Role | What they own | With what |
|---|---|---|
| Leadership | Decisions on the revenue map, proof cases and names | Decision brief, revenue map in ranges, leadership inputs page |
| Marketing lead | The twelve-month roadmap, content waves, prompt wave 1, quarterly radar re-sweep | Roadmap, priority stack, briefs, radar update protocol, workbook |
| Web administrator | On-page pack, structured data, local profile, site health fixes | On-page pack, site health page, import guide |
| Sales | Battlecards, field-voice story, buyer worries in simple words | Battlecard, field voice, session kit |
| Engineering | Validation of the client's cells in the architecture matrix | Test protocol, nine-dimension matrix |
Again: freeze the baseline on one date before building anything; read rivals at the source rather than in summaries; write owners as roles from day one; label every claim.
Changed on the way: in week eleven a rival's documentation proved the exclusivity language wrong, so it went. The positioning moved to a question the client can win: who owns the site-control logic and what field results are proven. And I rebuilt the handover in the client's own brand, so it reads as theirs, not mine.