Title + picture

Layout 03 · title + picture

Pair a title
with a product.

Full-bleed image on the right half, title stacked on the left. The logo and page meta sit on top, unchanged.

Agenda

Only Title layout

What we'll cover.

01 / 06Brand markWordmark, contrast, clear space.

02 / 06ColourOne orange, seven neutrals.

03 / 06TypeNoto Sans, 28pt titles.

04 / 06LayoutsChapter, content, picture, data.

05 / 06ComponentsButtons, chips, KPIs, rules.

06 / 06VoiceQuiet confidence.

Chapter 01

Chapter opener · orange

01
Brand.

01 / 06

Chapter 02

Chapter opener · ink

02
Colour
& Type.

Company · 2025

Figures at a glance

The business in numbers.

62k

Employees

+3% YoY

14 bn

Revenue · EUR

+5.1% YoY

Factories worldwide

8 regions

100%

Green electricity

since 2020

Layout · 2 contents

Two columns

Two halves, one frame.

01 · Customer

Build around real day-to-day jobs, not corner-case specs.

Ship features customers actually touch — fewer settings, faster defaults, clearer feedback.

02 · Platform

A shared backbone across every product we ship.

One core means one update path, one data contract, and one place to measure real-world usage.

Layout · 3 contents

Three pillars

Consumer, commercial, platform.

Consumer.

The brands and products customers meet directly, every day.

Commercial.

Pro-grade products engineered for high-utilisation, multi-site environments.

Platform.

The shared software layer that ties consumer and commercial together.

Roadmap · 2026

Plan, build, pilot, scale

The year, in four quarters.

Q1 · Plan

Align the 2026 product roadmap across regions.

Finalise priorities, staff crews, lock budget.

Q2 · Build

Ship the platform foundations and first feature set.

New core services, updated developer SDK.

Q3 · Pilot

Field-test with 2,000 accounts in the lead region.

Instrument, measure, iterate weekly.

Q4 · Scale

Roll out globally with phased regional launches.

EMEA, then NAM, then APAC.

Layout · text + picture

Flagship · 2026

A flagship that
learns the
user.

Adaptive defaults that calibrate to the user's context automatically and hold steady within tight tolerances, across every workflow.

Read the brief Spec sheet

Cover

Layout · full-bleed cover

An image does
the talking.

Data · Q3 results

Share of revenue by region

EMEA still leads; NAM closing the gap.

EMEA

62%

NAM

24%

APAC

11%

LATAM

Figure 01 · Sample data, Q3 2025 · N = €14.1 bn

UI kit

UI library preview

Flat, sharp, quiet components.

Buttons

Primary Default Ghost

Adopting the new platform will lift per-account active time by ~18% within two release cycles.

Supporting narrative

In the regional pilot, accounts on the updated platform engaged 2.3× more often and completed guided workflows 41% more per week. The carry-over is strongest in the core segments; adjacencies show a smaller but steady lift.

+18%

Active engagement / week

vs. prior platform

2.3×

Active session rate

trailing 30 days

Source · Platform telemetry, Jun–Dec 2025 · N = 142k accounts

MCK · Horizontal bullets

Three forces

Context

Three forces pull the 2026 roadmap: regulation, margin, and shared software.

01 · Regulation

Compliance and disclosure rules are tightening across regions.

Reporting standards raise the bar one full grade in 2027.
Right-to-repair-style mandates expand across three core markets.
Sustainability phase-downs accelerate for the commercial portfolio.

02 · Margin

Component cost is stable but service cost is climbing.

Field-service activity up 7% YoY on premium lines.
Warranty reserve exceeds plan in 3 of 5 product lines.
Remote-diagnosis deflection saves an average 38 EUR / event.

03 · Platform

The platform is becoming the product, not an add-on.

New SKUs must ship with the platform from day one.
One update path cuts maintenance headcount 22%.
Shared telemetry unlocks usage-driven feature priority.

MCK · Vertical bullets

Five moves · H1

Plan of record

Five moves define the first half: consolidate, instrument, retire, pilot, publish.

Each move is owned by a single VP and reviewed at the monthly operating meeting — progress is measured against a metric, not an output.

Work that does not support one of the five is explicitly descoped, not paused.

01Consolidate the platform stack.Move the remaining three product lines onto the unified core by end of Q2.
02Instrument every SKU.Every production unit leaving the factory reports health and usage by default.
03Retire the legacy app.Archive the 2019 companion surface once the new platform reaches 70% coverage.
04Pilot guided workflows.Run a two-thousand-account test of the adaptive programme across the lead region.
05Publish the API.Open the developer preview to partners at the end of H1.

MCK · 2×2 matrix

Prioritisation

Portfolio

Invest in the top-right quadrant first: high impact, low lift, and already shippable.

High impact · low lift

Guided workflows on the flagship.

Ships on existing infrastructure; telemetry already collected; known user need.

High impact · high lift

Full remote diagnosis across every product line.

Large prize; requires platform convergence and a new field-service workflow.

Low impact · low lift

Cosmetic refresh of onboarding.

Cheap to do; metrics rarely move meaningfully.

Low impact · high lift

Voice control expansion.

Significant engineering and QA cost; adoption has plateaued.

Impact →

← Effort to ship

Reading the grid

Each quadrant holds one representative initiative. The orange marker flags where a 2026 dollar is best spent first.

24 initiatives scored; full list in appendix A3.

MCK · Waterfall

FY25 bridge

Revenue bridge · EUR bn

Revenue grows 5.1% YoY; platform and services offset a mild decline in legacy lines.

13.4

0.6

0.4

0.3

0.2

14.1

FY24 base Consumer Platform Services Legacy FX FY25 total

Source · Sample data, preliminary FY25 · EUR bn · variances rounded to 0.1

MCK · Process flow

18-week rhythm

Delivery flow

A five-stage rhythm moves a feature from sketch to scaled rollout in 18 weeks.

Stage 01 · Wk 1–2

Frame

Write the one-page brief and the measurable outcome.

Stage 02 · Wk 3–6

Prototype

Build the thinnest shippable version and test internally.

Stage 03 · Wk 7–10

Pilot

Ship to ~2,000 accounts in one region; instrument everything.

Stage 04 · Wk 11–14

Harden

Close the top three issues; freeze scope; get sign-off.

Stage 05 · Wk 15–18

Scale

Phased rollout — EMEA first, then NAM and APAC.

Source · Product delivery playbook v3 · measured against 11 shipped features in 2025

MCK · Stacked bar

Revenue mix

Mix · FY21–FY25

Platform revenue is the fastest-growing share; legacy hardware is flat in absolute terms.

0481216

11.9

6.8

3.2

1.6

0.3

FY21

12.4

6.7

3.5

1.7

0.5

FY22

12.9

6.6

3.7

1.8

0.8

FY23

13.4

6.5

3.9

1.9

1.1

FY24

14.1

6.4

4.2

2.1

1.4

FY25

Segment

Legacy hardware−6% · 5y

Consumer products+31% · 5y

Commercial+31% · 5y

Platform & services+367% · 5y

Source · Sample data · EUR bn

MCK · Table

Performance by line

FY25 preliminary

Across five product lines, only the two flagship lines beat both revenue and margin plan.

Product line	Revenue · €m	vs. plan	Margin	vs. plan	Verdict
Flagship APremium tier strong	3,240	+3.8%	14.2%	+0.6 pt	Ahead
Pro linePremium edition strong	2,910	+2.2%	13.5%	+0.4 pt	Ahead
Standard line	3,480	+0.3%	11.1%	−0.2 pt	On plan
Compact line	2,610	−0.9%	10.4%	−0.3 pt	Below
Accessories	1,860	−1.4%	9.2%	−0.7 pt	Below
Source · Sample data, FY25 preliminary · EUR m · plan set Oct 2024

MCK · Pyramid

Value hierarchy

Customer value

Three tiers of value: a solid product, an honest relationship, a measured experience.

Tier 03A measured experience

Tier 02An honest relationship

Tier 01A solid product

Tier 01 · Foundation

A solid product.

Things that work, for years, in any context — solid, reliable, supportable.

Tier 02 · Trust

An honest relationship.

The product tells you the truth about itself — status, usage, when to act.

Tier 03 · Meaning

A measured experience.

Time given back; one less thing to think about.

MCK · Key takeaways

Three to remember

Key takeaways

Three things to remember: platform first, measure the experience, write plainly.

Platform first.

Every new SKU ships on the unified OS core from the first production run. No line-specific forks after Q2.

Owner · Platform VP

Measure the experience.

Telemetry is the product, not an add-on. Every feature must ship with the metric that proves it worked.

Owner · Data lead

Write plainly.

Release notes, app copy, service sheets — all authored in the Feinschliff voice. Short sentences. Concrete nouns.

Owner · Content lead

MCK · Executive summary

One page · the year

Executive summary

Four moves, four metrics, one target — the 2026 year summarised on one page.

Move · Consolidate

Unify the platform across product lines.Retire the last two forks and move every SKU onto the shared core.

Shipping from Q1; remaining lines cut over in Q2.

100%SKU coverage · EOY

Move · Instrument

Default-on telemetry.Every unit reports usage and health from day one.

Rolling across factories; data contract is locked and versioned.

95%Opt-in target

Move · Pilot

Guided workflows in 2,000 accounts.Lead-region field test, Q3, with weekly instrumented readouts.

Recruitment open; instrumentation shipped in the March release.

+18%Active engagement / wk

Move · Publish

Open the developer API.Preview for partners end of H1; GA at end of year.

Partner list signed; documentation drafted and under review.

30Preview partners

MCK · Line chart

Per-account metrics, FY21–FY25

Trend — active time vs platform spend

Per-account active time grew 43% while platform cost per account declined — economics are turning.

Active time per account Minutes per week+43%

Platform cost per account Euro per month, indexed−38%

FY23 is the inflection — the shared core launched mid-year and new accounts were onboarded on the common platform. Cost fell as utilisation rose.

Source · Internal platform analytics, FY21–FY25
    

MCK · Scorecard

Platform option assessment

Build–buy–partner assessment

Partnering with a cloud provider wins on speed and capex; building in-house wins on control — recommend a hybrid split.

Option

Speed

Cost

Control

Talent fit

Risk

Commentary

Build in-house24-month programme, new platform group

Long runway; highest TCO; retains full IP.

Buy managed platformLicense a leading white-label stack

Fastest to market; vendor lock-in risk.

Partner hybridCore built in-house, cloud & ML partner-operated

Recommended. Balances speed and control.

Acquire a platformShortlist of 3 targets, 200–400 FTE

Deal risk high; integration drag on FY26.

None Low Mid High Very high

MCK · Gantt

Platform programme · FY25

Workstreams — FY25 delivery plan

Platform consolidation lands in Q2; the developer API goes GA in Q4, dependent on telemetry rollout.

Q1 FY25

Q2 FY25

Q3 FY25

Q4 FY25

Platform consolidationOwner · Platform

Cutover · all SKUs

Default-on telemetryOwner · Data

Factory rollout

Regional pilot · 2,000 customersOwner · Consumer

Instrumented study

Developer APIOwner · Platform

Preview

Retail & service partnersOwner · GTM

30 preview partners

Committed Critical path Dependency window Milestone

MCK · Funnel

App activation funnel · Q4 FY25

First-run activation funnel

One in three buyers never activates their account — first-run setup is the largest and most fixable drop-off.

Product sold

Shipment, any SKU

2.4 M 100%

App installed

Within 30 days of purchase

2.0 M 84%

Account activated

First-run setup completed

1.5 M 62%

Feature used

At least one active session

1.2 M 50%

Active at 90 days

≥4 cycles in last month

870 K 36%

−22 pt

Trial → activate

Activation fails on mixed-SSID routers and Wi-Fi 6 backward compatibility. Fix is scoped for the Q1 release.

−14 pt

Feature → 90d active

Accounts try one workflow then default to the panel. Cadence nudges in-app are live in Q2.

MCK · Venn

Where the three businesses meet

Where consumer, platform, and services meet

The connected account is the intersection — only the company sits in the product, the platform, and the service relationship at once.

01 · Consumer × Platform

Smart product

The platform turns the object into an addressable node — the basis for every service we layer on.

02 · Platform × Services

Remote diagnostics

Telemetry lets service pre-triage a call; first-time-fix rate rises, truck rolls fall.

03 · Consumer × Services

In-home install

Existing service relationship carries trust; we extend it into the subscription tier.

Center

Connected account

Only the company sits in all three sets at scale — the moat no single-category competitor can cross.

V-Model

SDLC · V-model

Verification · Validation

Every design step on the left has a matching test on the right — the V-model pairs them.

Validation Phase

Verification Phase

Phase 01 Requirement gathering

Acceptance plan

Test 01 Acceptance testing

Phase 02 System analysis

System test plan

Test 02 System testing

Phase 03 Software design

Integration

Test 03 Integration testing

Phase 04 Module design

Unit tests

Test 04 Unit testing

Pivot Coding & implementation