KanbinaLUMINA
Commercial Growth Intelligence · EKU Power Drives · Continuity annex

The next six months, on one page

What operating the system looks like from October 1: the weekly rhythm, the Q4 2026 sprint, the 2027 horizon, the numbers that get reviewed in every QBR, and the governance that keeps every claim honest. This page assumes a six-month structure (door B or C); scope executes differently per door, the plan and the KPIs stay the same.

Companion to the Day 65 readoutOct 2026 to Sep 2027Working plan · targets pending D09 inputs
The operating rhythm · what happens when

Three loops, one system

Weekly

Content piece per the rollout calendar · site and release QA · field-input intake into battlecards · event follow-through in season.

Monthly · command review

One hour with Edward and Amanda: search and site read, AI-answer panel re-run (defined prompt set, logged), benchmark pull (adding MTU and Cummins rows), claims register review, next month's queue.

Quarterly · QBR

Before-and-after board against the Day 65 baseline, roadmap re-sequence, budget and capacity check, team training refresh, competitive re-sweep of the full tier map.

What you are seeing

The same discipline that ran the 90 days, made permanent: every number keeps its instrument and date, every claim keeps its label, and every month closes with a written summary the same day.

Q4 2026 · October to December · the proving quarter

First the unlocks, then the engine, then the evidence

Sprint 0 · October week 1 to 2: the cheap unlocks

Open the AI door

The site currently tells AI crawlers not to read it (a one-toggle website setting). Fixing it is the single cheapest visibility unlock in the whole plan.

Structured data

Organization, Product and FAQ markup on key pages, so search and AI systems can read what EKU is without guessing.

Directory presence

The standard industry directories where buyers and AI systems check that a vendor exists. EKU is absent from them today; four listings close it.

Measurement live

GA4 key events verified (from the Day 65 sign-off), so every Q4 result reports business signals, not visits.

The engine · October to December: the 12-week content rollout

Eighteen pieces are already defined and sequenced; the first is drafted. The queue leads with what converts fastest: comparison and alternatives pages nobody in the category has, the industrial idle-reduction pillar, the Houston local play, and the oilfield vertical, then the paralleling FAQ and the mixed-fleet intercept pages built from what buyers actually type.

Rollout blockWhat shipsWhy this order
Weeks 1 to 4Comparison and alternatives pages · industrial idle-reduction pillarBottom-of-funnel with zero competition; the pillar brief is already written
Weeks 5 to 8Houston local landing and profile · oilfield vertical page · paralleling FAQFastest conversion, highest ticket, and the question set buyers already ask
Weeks 9 to 12Fleet-analytics repositioning · mixed-fleet intercept pages · category educationDefends the analytics ground and captures brand-qualified monitoring searches

The stage · events and proof

Las Vegas data-center event follow-through (Sep 28 to 30 leads worked in October) · mining tech talk · Germany event follow-up · the Maximus reference case published with numbers (the proof asset from the Day 65 sign-off). Quarter closes with the December QBR against the Day 65 baseline.

2027 · from proving to owning

The year the category gets a default answer

Q1 to Q2 2027ConsolidateSecond content wave on what Q4 proved · data-center vertical if EKU confirms the segment · positioning narrative validation completes with field evidence · two more reference cases.
Q2 to Q3 2027AmplifyTrade-magazine features and tech talks from the category-leadership calendar · partner co-announcements · event circuit with language intelligence per event.
What you are seeing

Q4 proves the engine works. 2027 compounds it: by mid-year the goal is that when a buyer or an AI assistant asks the mixed-fleet question, EKU is part of the default answer, and every step of that path is measured the same way it was measured on Day 65.

KPIs · reviewed in every command review and QBR

The scoreboard: baseline, 12 weeks, mid-2027

Metric (instrument stays fixed)Baseline today12-week targetMid-2027 target
Informational pages indexed014+30+
Page 1 to 2 rankings on the three named target terms0 of 32 of 33 of 3 + next set
AI-answer mentions, 7-prompt battleground panel0 of 72 of 74 of 7
US organic keywords ranked2955 to 70100+
Industry directory listings~04maintained + reviews
Houston local pack, "generator retrofit"absenttop 3held
Named reference cases published013
GA4 key events (once configured)not configuredreportingquarter-over-quarter growth
Baselines: Day 65 readout and program baseline, Sep 2026, each with its own instrument and date. Targets are working targets: evidence-based, revisited at every QBR, refined once D09 pipeline inputs land. Lead-quality and revenue-linked KPIs are added the moment GA4 key events and the D09 inputs exist; nothing here is a revenue forecast.
QBR · the quarterly business review, one hour, four boards

What Edward sees every quarter

1 · Before and after

Every KPI against baseline and against last quarter, same instrument, same scope, dated. What moved, what did not, and why.

2 · Claims register

What got validated to Confirmed, what is still Working Hypothesis, what new claims the quarter produced and need sign-off.

3 · Field re-read

Competitive re-sweep highlights: who moved into the territory, what the benchmark rows say, where the next window is.

4 · Re-sequence

Next quarter's queue re-ordered by what the data said, with owners, capacity and an explicit "not now" list.

What you are seeing

The QBR is the renewal argument doing its own work: every quarter closes with evidence on the table and the next quarter already sequenced. Checkpoints at month 3 and month 6 make the structure easy to continue and easy to stop, which is exactly why it is easy to sign.

Governance · the rules that do not change

Same rules that ran the 90 days

Evidence discipline

Every figure keeps source, date and scope · instruments never merged · like-for-like comparisons only · claim labels (Confirmed / Working Hypothesis / Needs Validation) on everything client-facing.

Language governance

Buyer-facing language stays "mixed-brand generator fleets" with the named controllers list · compatibility is never claimed for a manufacturer EKU has not validated and signed · competitor names appear in market description and comparison architecture, never as attacks: several are also potential channel partners.

Companion page to the EKU Day 65 readout · Working document, not approved external copy · Prepared by Kanbina Lumina · Sep 2026