KanbinaLUMINACASE STUDY
Industrial power technology · North America and Europe · 90 days

The task was to build the commercial foundation. The result is a system the client's team can run.

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.

12 deliverablesLandscape, buyer segments, digital authority, positioning, messaging, channel architecture, AI and search content, partner map, revenue map, roadmap, priority stack, handover.
24 rivals trackedFive tiers, one evidence standard: every claim labeled Confirmed, Working Hypothesis or Needs Validation, with source and date.
3 readingsBaseline in July, mid-point in September, closing reading at Day 90. Same instruments each time, never mixed.
1 handoverA navigable repository with owners by role, a twelve-month roadmap, KPI board, data workbooks and a Confluence import guide.

The situation

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.

You cannot manage what you have not measured. So the first four weeks went to measuring. Nothing was built yet, on purpose.

What I did, in five moves

  1. Baseline. Search Console, analytics, one market intelligence dataset and a recorded panel of AI answers, all frozen on one date. Every later reading compares to that one.
  2. Gap. Twenty-four rivals in five tiers, read at the source: datasheets, release notes, press rooms, event agendas. The question was never "who is bigger" but "who owns the site-control logic, how the site behaves offline, how commissioning works, and what field results are proven".
  3. Build. Positioning and approved language, ratified by the commercial team. Then the messaging system, the on-page pack, battlecards, a live radar, a field-voice story in the sellers' own words, case-study templates, FAQ and structured data so AI engines can read the site.
  4. Implement. A twelve-month roadmap: what, who, how, support and why for every line, owners by role. A priority stack and a capacity read, so the team could decide what ships now and what waits.
  5. Measure. A closing reading on the same instruments. A KPI board. A protocol for the next wave of AI prompts. And a handover the marketing lead can import into the company wiki in an afternoon.

Why this is not another strategy deck

Owners are roles, not consultantsEvery task in the roadmap names a role inside the client: leadership, marketing lead, web administrator, engineering, sales. Nothing depends on me staying.
One number, one sourceFigures are written once, in a baseline table, with instrument, date and scope. Every other page links to it. Two instruments are never summed.
Claims carry their labelConfirmed, Working Hypothesis or Needs Validation, on every competitive statement, including the client's own. I retired the exclusivity wording the week a rival's documentation contradicted it.
Built to be auditedThe package went through three external audits before delivery. Findings were applied with a reproducible script, not by hand.
Withheld until the client's written permission is on file

Results at Day 90

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.

ReadingBaseline (July 2026)Closing (30 Sep 2026)Label
Appearances in AI answers, client vs direct rivalsWithheldWithheldConfirmed
Share of clicks from branded searchesWithheldWithheldConfirmed
Organic keywordsWithheldWithheldConfirmed
Referring domains and backlinksWithheldWithheldConfirmed

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.

What the client's team runs today

RoleWhat they ownWith what
LeadershipDecisions on the revenue map, proof cases and namesDecision brief, revenue map in ranges, leadership inputs page
Marketing leadThe twelve-month roadmap, content waves, prompt wave 1, quarterly radar re-sweepRoadmap, priority stack, briefs, radar update protocol, workbook
Web administratorOn-page pack, structured data, local profile, site health fixesOn-page pack, site health page, import guide
SalesBattlecards, field-voice story, buyer worries in simple wordsBattlecard, field voice, session kit
EngineeringValidation of the client's cells in the architecture matrixTest protocol, nine-dimension matrix

What I would do again, and what I changed

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.

Talk to Kanbina Lumina about a 90-day commercial growth system
Kanbina Lumina · Case study, anonymized edition, October 2026 · The client is not named and rival brands are replaced by neutral labels at the client's request. Industry descriptors and dates are kept so that the method can be judged. The client’s figures and findings are not shown; they publish only once written permission is on file.