Stakeholder master deck

CreatorStudio Suite
One story · every audience

Product, operators, architecture, engineering, and commercial packaging — organised in chapters. Jump with the left rail, the chapter index, or keys 1–5.

Exec / Product / Sales

Operators

Architects

Software

Commercial

How to use this deck

Pick the chapter for your audience

Chapter A

Executive & Product

Why this exists, what it delivers, and why it matters for the Suite and operators.

Leadership

Product

Sales

A1 · The problem

Announcements are still tied to the vehicle box

Today

Content changes = firmware / field visits
Voice quality capped by onboard hardware
Hard to prove what a passenger heard
Signs and audio often separate workflows

CreatorStudio answer

One authoring tool + always-on engine
Vehicles stay thin MQTT clients
Cloud AI speech + fleet phrase cache
Proof-of-play + Matrix LED in one Publish

A2 · Capabilities

Six things, one platform

AUTHOR

Playlists

Text, {vars}, pauses, clips — browser authoring.

TRIGGER

33 + custom

Built-in transit events, fact logic, geofences.

SPEAK

AI TTS

Azure · ElevenLabs · Acapela · fleet cache.

SHOW

Matrix LED

Layouts, FNT, Ultima faces, mono/RGB FF.

PROVE

Proof of play

Dispatched vs confirmed — exportable evidence.

OPERATE

Live cockpit

Map, feed, health, simulator, passenger app.

A3 · Suite surfaces

Three apps, one portal

CreatorStudio — author announcements & LED
Engine Monitor — watch, prove, diagnose
Vehicle Player — any device as thin client

MQTT broker is the integration hub — topics are the API.

A4 · Outcomes

Why stakeholders care

Compliance you can prove

ADA / accessibility evidence with place, time, transcript.

Fleet content velocity

Publish → live in ~1 s. No per-vehicle reflash.

Suite attach

Software ARR next to Matrix / Ultima hardware.

Deploy anywhere

Cloud for the operator or edge container on the bus.

~1 s

Publish → fleet

2,000

veh / engine process*

≈2 ms

cache-hit render

9

license modules

*Measured planning figure — see ARCHITECTURE.md scaling section.

Chapter B

Operators & Experience

What people use day to day — authoring, monitoring, proof, and the passenger screen.

Operations

Training

CX

B1 · Authoring

Design what the fleet says

Playlist library

Editor — text, variables, voice, “also speak in”

B2 · Triggers

When it speaks — built-in, custom, geofenced

33 built-in transit triggers

Geofence zones as conditions

B3 · Voices & simulation

Pick a voice · test before the bus

Azure · ElevenLabs · Acapela A/B

GTFS route simulator

B4 · Live operations

Fleet cockpit & signs

Heading-up map + event feed

LED / destination / TFT preview

B5 · Proof & passenger

Evidence and the rider screen

Proof-of-play on the map

Browser passenger information app

Chapter C

Architecture & Integration

How the system fits together — for architects and vehicle / Suite integrators.

Architects

Integrators

Suite platform

C1 · System context

End-to-end architecture

C2 · Runtime path

From trip signal to sound & pixels

PIS-PT→Context→Triggers→ Pipeline→Render→MQTT out→Ack

Decide

Edge-detect · debounce · gates
33 built-in + custom + geofence
Priority per vehicle

Produce

{vars} → MP3 (cached fleet-wide)
Matrix Display→Cycles→Layout
FNT fonts · FF mono/RGB

C3 · MQTT contract

Topics are the integration API

Dir	Topic	Payload
IN	`…/pis/0/#`	Journey / sensors into engine
OUT	`…/pis/0/tts`	ADT 4.x audio
OUT	`…/display` · exterior · signs · ff	LED bitmaps + Mobitec FF
ACK	`engine/played`	Proof after clip ends
OPS	`engine/fleet` · health · metrics	Dashboard views

TCP 1883 · WebSocket 9001 · same contract for Go, Python, browser. No private Engine↔Dashboard API.

C4 · Deployment

Cloud or on-vehicle edge — same software

Central / cloud

Engine process per tenant
Thin clients on every bus
~2,000 vehicles / process (measured)

Edge container

Multi-arch, non-root
Local MQTT + last-known-good config
Optional cloud sync when online

Suite placement

MatrixRenderer Unit stays on-sign. CreatorStudio L4 publishes complementary FF / template content — hardware + software ARR on the same face.

Chapter D

Software Engineering

What we build, where code lives, and how to change it safely.

Developers

QA

Platform

D1 · Surfaces & stack

Repo map

Engine `src/`

Node ≥20 · TS ESM · MQTT · TTS · matrix/FF · history

Creator `web/creator/`

Angular 20 + PrimeNG — author & publish

Monitor `web/`

Angular 20 — cockpit, proof, sim

Portal

scripts/dashboard-server.ts — one origin

Clients

clients/go · python · public/player.html

Contracts

shared/payloads.ts · topic patterns · FNT/FF

D2 · Feature → code

Where to look first

Capability	Primary modules
Triggers & gates	`pis/ptEngine.ts`
Playlist → MP3	`engine/playlistRenderer.ts` · `pipeline.ts`
TTS + cache	`tts/*` · `tts/cache.ts`
Matrix LED / FF	`engine/matrix/` · `engine/ff/`
Config hot-swap	`config/pgConfigSource.ts`
Proof of play	`engine/history.ts` + `engine/played`

D3 · Guardrails

Change safely

Config

Content must hot-swap (~1 s). Keep file fallback for edge.

MQTT

Public API — prefer additive payload/topic changes. Ack required for proof.

TTS / LED

Cache keys and FF encoding are fleet-visible. Measure hit-rate before synth path changes.

Docs of record

ARCHITECTURE.md · FUNCTIONAL-SPEC.md · OVERVIEW.md

Quality bar

1336 tests (engine 581 · front-end 755) · 2k-veh load as regression gate · npm run docs

Chapter E

Commercial Packaging

Modular SKUs, bundles, and illustrative revenue scale. Planning figures — not list price.

Sales ops

Finance

Product

E1 · Modules L1–L9

Core required · rest attach

SKU	Module	Value	Example*
L1	Core Engine	Triggers → ADT · thin clients	€8 / veh / mo
L2	Creator Studio	Ops change wording without releases	€120 / seat
L3	Cloud AI Speech	Neural TTS + fleet cache	€4 / veh / mo
L4	Matrix LED	Layouts / Ultima / FF	€6 / veh / mo
L5	Proof of Play	Compliance evidence	€3 / veh / mo
L6	Ops Dashboard	Live cockpit	incl. ≥50 veh
L7	Passenger App	Browser PIS	€1.5 / veh / mo
L8	Multi-tenant	OEM host many fleets	€2.5k + €400 / ten
L9	Edge Engine	On-vehicle container	+€3 / veh

*Illustrative planning figures. Full brief: LICENSE-PACKAGING.md

E2 · Bundles & scale

How revenue grows

Bundles (example / veh / mo)

Starter Audio → ~€12
Audio + Signs → ~€18
Compliance → ~€21
Full PIS → ~€22.5
OEM Hosted → platform + vehicle ARR

Illustrative ARR paths

Operator Y1→Y5: 200→1,800 veh · ~€34k→~€475k
500-veh mix: ~€10.3k / mo · ~€124k ARR
OEM host: 3k veh + L8 · ~€829k / yr

Primary scaler = vehicles under management · Secondary = module attach (LED, Proof, Passenger).

Next steps

Same product.
The right depth for each room.

Specialised leave-behinds remain available: Leaflet · One-pager · Architecture overview · Software team · License packaging · full ARCHITECTURE.md.

M · chapter menu

1–5 · jump chapter

← → · linear

F · fullscreen

CreatorStudio SuiteOne story · every audience

Pick the chapter for your audience

Executive & Product

Operators & Experience

Architecture & Integration

Software Engineering

Commercial Packaging

Full linear run

Executive & Product

Announcements are still tied to the vehicle box

Today

CreatorStudio answer

Six things, one platform

Playlists

33 + custom

AI TTS

Matrix LED

Proof of play

Live cockpit

Three apps, one portal

Why stakeholders care

Compliance you can prove

Fleet content velocity

Suite attach

Deploy anywhere

Operators & Experience

Design what the fleet says

When it speaks — built-in, custom, geofenced

Pick a voice · test before the bus

Fleet cockpit & signs

Evidence and the rider screen

Architecture & Integration

End-to-end architecture

From trip signal to sound & pixels

Decide

Produce

Topics are the integration API

Cloud or on-vehicle edge — same software

Central / cloud

Edge container

Suite placement

Software Engineering

Repo map

Engine src/

Creator web/creator/

Monitor web/

Portal

Clients

Contracts

Where to look first

Change safely

Config

MQTT

TTS / LED

Docs of record

Quality bar

Commercial Packaging

Core required · rest attach

How revenue grows

Bundles (example / veh / mo)

Illustrative ARR paths

Same product.The right depth for each room.

CreatorStudio Suite
One story · every audience

Engine `src/`

Creator `web/creator/`

Monitor `web/`

Same product.
The right depth for each room.