File: 2026.10.26 - Lumenwire Audio - 02 Gary Response to Challenge Notes.md
Lumenwire Audio: Gary's Response to Kewpie's Challenge Notes
From Gary to Adam and Kewpie. 26-Oct-26. Sample data. This answers the 6 corrections and 15 challenge notes in 2026.10.26 - Lumenwire Audio - 02 Challenge Notes.md. I haven't changed the Business Requirements. Every change to a KPI, target or threshold below is a proposal waiting for Adam's sign-off. Every new target and threshold is my proposal, labelled Working Hypothesis, unless it says otherwise.
The short version. Kewpie's numbers test Marcus's story, which is what the dashboard is for. Three things he believed don't hold up: software growth is one licence, about a third of design wins ship (not 80%), and hardware fell mostly because OEMs stopped buying ahead of installs, not because end demand fell. My response keeps all five KPIs. I've proposed new targets where the old ones fail the Attainable test, and I've added "with and without the one-off licence" wherever that licence distorts the picture.
1. Corrections to my draft measures
All six are accepted. They change how a KPI is measured, not what it is or its target. Kewpie's Before and After text stands in full as written in the Challenge Notes.
| # | KPI | Decision | Reason |
|---|---|---|---|
| A1 | Total revenue, last 12 months, against the path to A$115m (K1) | Accept | Developer kits and freight sit under "other" in the board plan and the forecasts. Total unchanged, and it reproduces A$118.4m and A$80.6m |
| A2 | New devices activated in the field (K2) | Accept | Earliest activation per device is what "first joins a network" means. The OEM backfill only affects the split |
| A3 | OEM stock on hand (K2.1) | Accept | Reels counted as units would overstate stock. The name change this leads to is under challenge note C14 |
| A4 | Design wins that ship (K4) | Accept | Rows without dates can't go in a cohort, and OEM-level invoices can't confirm that a product shipped |
| A5 | Months from design win to first shipment (K4.1) | Accept | Young cohorts only show their fastest shippers. Use the same 18-month window as K4 |
| A6 | Forecast accuracy (K5) | Accept | "On or before the quarter start" stops a forecast being taken after the quarter has begun. The signed figure shows bias, which is what Marcus's "arguing about whose number is right" is about |
↑ Back to top
2. Challenge notes
Total revenue, last 12 months, against the path to A$115m (K1)
C1: The FY27 board plan is already below the path. Accept, and Refer to the CFO. Reason: it doesn't make the threshold wrong. It shows the board's two numbers don't agree, which is how people get blindsided. Keep the A$115m path as the threshold, show the FY27 plan as a second line, and ask the CFO which one the board measures against (open questions Q-1 and Q-2).
| Text | |
|---|---|
| Before (K1 thresholds note) | "Gary's proposal, to agree with the CFO" |
| After (K1 thresholds note) | "Gary's proposal, to agree with the CFO. Measured against the straight-line path to A$115m. The FY27 board plan (A$92.7m, Finance, 15-Jun-26) is shown as a second line. It sits 5.2% below the path at Jun-27, so delivering the plan would read Red. CFO to say which line the board measures against (Q-1, Q-2)" |
C2: The FY27 plan repeats the one-off licence. Accept, and Refer to the CFO. Reason: a plan that counts an A$8.5m one-off twice overstates FY27. The board should see that.
| Text | |
|---|---|
| Before (K1 target rationale) | "The board wants revenue back to A$115m within two years. Date read as the year ending June 2028, to confirm with the board (Q-1)" |
| After (K1 target rationale) | "The board wants revenue back to A$115m within two years. Date read as the year ending June 2028, to confirm with the board (Q-1). Note: the FY27 plan is FY26 × 1.15 on every line, so it repeats the Mar-26 one-off licence. Without it, the plan is A$84.2m, not A$92.7m. CFO to confirm whether the plan should repeat it" |
C3: Volume rebates can pull hardware revenue into quarter-end months. Accept Kewpie's counter-metric. No new KPI. Reason: a rebate-rate tile would be an "accountant metric" with no owner action, and Marcus asked for none of those. Gross margin % is the counter-metric, and the quarter-end share goes in the calculation notes so Kewpie can watch for it. If it climbs above FY25's 46%, I'll bring it back as a sub-KPI.
New devices activated in the field (K2)
C4: The measure is only as good as the telemetry's coverage. Accept, and Refer to the Head of Platform Engineering (Q-4). Reason: this is exactly Marcus's condition. No change: K2 stays in the five, stays off page one, and keeps its target until Tomasz answers on coverage and the Jul-25 firmware.
Software revenue growth (K3)
C5: The +20% target fails the Attainable test because of one licence. Accept: change the headline. Refer the target to the VP Sales and CFO (Q-3). Reason: Marcus asked whether growth is "real and repeatable" and "how much comes from one big licence". A headline that includes a one-off A$7.4m licence can't answer that.
| Text | |
|---|---|
| Before (K3 name) | "Software revenue growth, last 12 months against the year before" |
| After (K3 name) | "Software revenue growth without one-off large licences, last 12 months against the year before" |
| Before (K3 measure) | "Software revenue over the last 12 months divided by the 12 months before, minus 1" |
| After (K3 measure) | "The same, leaving out any single licence worth more than A$1m (threshold to agree with the CFO). Total growth including it is shown alongside" |
| Before (K3 target) | "To be agreed (Gary's starting proposal: at least 20% growth year on year) by 30 Jun 2027" |
| After (K3 target) | "To be agreed by the VP Sales and CFO. Gary's starting proposal: back to growth (0% or more, without large licences) by 30 Jun 2027, against -15.6% now. Working Hypothesis" |
| Before (K3 thresholds) | "Green 20% or more; Amber 0% to under 20%; Red falling" |
| After (K3 thresholds) | "Green 0% or more; Amber -10% to under 0%; Red below -10%" |
C6: Annual subscriptions may be booked in full at the start date. Refer to the CFO. Reason: it's a revenue recognition question, and only Finance can answer it. If the CFO confirms it, I'll propose a repeat-revenue measure, such as renewal rate on annual subscriptions, as a sub-KPI. That would be a new measure, so it would come back to Adam.
C7: The largest licence holds Share of software revenue from the largest licences (K3.1) at Red until Mar-27. Accept. Reason: a tile that sits Red for 5 months with nothing anyone can do is noise. Keep the threshold, but say why it's Red. The customer name stays off the board page (Q-7).
| Text | |
|---|---|
| Before (K3.1 thresholds note) | "Gary's proposal" |
| After (K3.1 thresholds note) | "Gary's proposal. Shown with and without the largest licence. While the Mar-26 licence is in the 12-month window (to Mar-27), the tile says so in words. No customer names on the board page" |
C8: The 77% target for Gross margin % (K3.2) differs from the board's 76%. Accept: align to the board's figure. Refer to the CFO to confirm. Reason: two margin targets on one page is the "whose number is right" problem Marcus wants fixed. The board's 76% (BT-03, Finance) is the stronger source.
| Text | |
|---|---|
| Before (K3.2 target) | "At or above 77% by 30 Jun 2027. Hold the FY26 level as stated by Marcus. Working Hypothesis" |
| After (K3.2 target) | "At or above 76% for FY27 (30 Jun 2027), the board's FY27 gross margin target (BT-03, Finance, 15-Jun-26), to be confirmed by the CFO. Shown with and without one-off licences. Observed Fact (source); CFO to confirm" |
| Before (K3.2 thresholds) | "Green 77% or more; Amber 75% to under 77%; Red under 75%" |
| After (K3.2 thresholds) | "Green 76% or more; Amber 74% to under 76%; Red under 74%" |
Design wins that ship (K4)
C9: The 80% target fails the Attainable test (baseline 31.5%). Accept: reset the target. Refer to the VP Sales (with Q-11). Reason: 80% was Marcus's belief, never measured, and he said so. The oldest cohort levels off near a third. A target needing +5.4 points a month against a run rate of +0.08 is a wish, not a target.
| Text | |
|---|---|
| Before (K4 target) | "80% by 30 Jun 2027. Marcus believes about 80% ship but has never measured it. Reset once Kewpie sets the baseline. Working Hypothesis" |
| After (K4 target) | "35% by 30 Jun 2027, from a baseline of 31.5% (Sep-26). Gary's proposal, to agree with the VP Sales once the 18-month window (Q-11) and the CRM date back-fill are settled. Marcus's 80% was a belief, not a measure. Working Hypothesis" |
| Before (K4 thresholds) | "Green 80% or more; Amber 60% to under 80%; Red under 60%" |
| After (K4 thresholds) | "Green 35% or more; Amber 30% to under 35%; Red under 30%" |
C10: A third of CRM rows have no stage dates, and there's no product key to invoices. Accept, and Refer to the VP Sales and CFO. Reason: the data gap belongs in the Requirements, because the KPI can't be trusted without the fix. The baseline stays a Working Hypothesis.
| Text | |
|---|---|
| Before (data inventory, CRM quality notes) | "Design wins are logged here. Trusted less than the P&L because reps work to a bonus. Some rows have a stage but no stage dates" |
| After (data inventory, CRM quality notes) | "Design wins are logged here. Trusted less than the P&L because reps work to a bonus. 33% of rows (2,932 of 8,990) have no stage dates. Data requirements: VP Sales to back-fill stage dates; VP Sales and Finance to add a shared product or SKU key between the CRM and the ERP" |
C11: Reps are paid per design win with no clawback, and there are no reason codes. Accept: add the data request. Refer the incentive design to the VP Sales, CFO and People team. Reason: without a "reason lost" field, nobody can tell a real design win from one logged for the bonus. The bonus plan itself is outside this project.
| Text | |
|---|---|
| Before (Business Requirements, constraints) | (no line) |
| After (Business Requirements, constraints) | "Data request: add a required 'reason lost' field in the CRM for any opportunity lost after design win (owner: VP Sales). The design-win bonus (A$400 per win, no clawback) is referred to the VP Sales, CFO and People team, and is outside this project" |
Forecast accuracy (K5)
C12: Not yet one metric, and 5% is far from history. Accept. Refer the choice of forecast and the tolerance to the CFO (Q-5). Reason: neither forecast has been within 5% since FY24-Q4. I'll show both until the CFO picks one, and ease the starting target so it's hard but not hopeless. K5 stays off page one, as Marcus asked.
| Text | |
|---|---|
| Before (K5 target) | "Within 5% of actual by 30 Jun 2027. Gary's proposal; the CFO to give her view first (Q-5). Working Hypothesis" |
| After (K5 target) | "Within 10% of actual for FY27-Q4 (30 Jun 2027), on the forecast the CFO chooses. Until she chooses, Finance and Sales are both shown. Gary's proposal, CFO to set the tolerance (Q-5). Working Hypothesis" |
| Before (K5 thresholds) | "Green within 5%; Amber 5% to 10% out; Red more than 10% out" |
| After (K5 thresholds) | "Green within 10%; Amber 10% to 20% out; Red more than 20% out" |
C13: Data problems in the forecast table, and Finance's hardware forecast is 52% below its own plan. Accept the data-load check. Refer the gap to the CFO. Reason: that gap is the clearest sign yet that Finance and Sales aren't working from one number. No KPI change.
OEM stock on hand (K2.1)
C14: Only 35 OEMs report, and there's no target or thresholds. Accept: rename and measure as months of cover. Refer the thresholds to the VP Sales. Reason: "top 40" is wrong. Months of cover answers Marcus's question better than raw units: are OEMs still sitting on stock, or about to reorder? This is a new measure, so it needs Adam's sign-off.
| Text | |
|---|---|
| Before (K2.1 name) | "OEM stock on hand, top 40 OEMs" |
| After (K2.1 name) | "Months of stock cover at the OEMs that report (35 today, 46% of FY26 hardware revenue)" |
| Before (K2.1 measure) | "Total units on hand reported by the top 40 OEMs each quarter" |
| After (K2.1 measure) | "Units on hand at reporting OEMs (reels × 500), divided by those OEMs' average monthly units activated or invoiced (Kewpie to confirm which), each quarter. Units on hand shown alongside" |
| Before (K2.1 target and thresholds) | "To be agreed; Green, Amber and Red to be agreed" |
| After (K2.1 target and thresholds) | "Target: 6 months of cover or less by 30 Jun 2027 (9.3 now). Green 6 months or less; Amber over 6 to 9; Red over 9. Gary's proposal, to agree with the VP Sales. Working Hypothesis" |
Design wins per quarter (K4.2)
C15: Design wins have risen since the bonus, with no change in the shipping rate. Accept. No change. Reason: this is why it sits under Design wins that ship (K4), not on top.
↑ Back to top
3. For Adam's sign-off
These change a KPI, target or threshold. None is in the Business Requirements yet.
- Total revenue, last 12 months, against the path to A$115m (K1): add the FY27 plan as a second line in the threshold note (C1), and note in the target rationale that the plan repeats the one-off licence (C2)
- Software revenue growth (K3): rename to "without one-off large licences", show the total alongside, start the target at "back to growth (0% or more)" and move the thresholds to match (C5)
- Share of software revenue from the largest licences (K3.1): show it with and without the largest licence, and explain the Red in words until Mar-27 (C7)
- Gross margin %, last 12 months (K3.2): target from 77% to the board's 76%, thresholds moved down 1 point (C8)
- Design wins that ship (K4): target from 80% to 35% by Jun-27, thresholds 35 / 30 (C9)
- Forecast accuracy (K5): target from 5% to 10%, thresholds 10 / 20, both forecasts shown until the CFO chooses (C12)
- OEM stock on hand (K2.1): rename to "Months of stock cover at the OEMs that report", new measure, target 6 months or less, thresholds 6 / 9 (C14)
- Business Requirements data notes: CRM date back-fill and a shared product key (C10), and a "reason lost" field request (C11)
Referred, no change needed now: CFO on C1, C2, C6, C8, C12 and C13; Head of Platform Engineering on C4; VP Sales on C9, C10, C11 and C14; People team on the bonus (C11).
↑ Back to top