$ platform
The diagnostic runs on a platform, not a slide deck.
In week one of Phase 1 we deploy Baseline — our internal diagnostic platform — inside your estate. It instruments the workflows, maps the data landscape, scores the automation candidates, and holds every baseline and delta the gates decide on.
From raw events to gate decisions.
Each layer feeds the next. Instrumented events become a living workflow map; the map scores the candidates; the candidates carry their baselines into the build gates. Nothing in the diagnostic is an opinion — it's a query.
- Every workflow, time-tracked at the source./01
Instrument
In week one, read-only connectors and structured time capture go in across your delivery lines. Baseline ingests events from the systems your teams already use — nothing migrates, nothing is replaced.
- Read-only connectors to the systems of record — ERP, PLM, TMS, ticketing, content stores
- Structured time capture per workflow step and document type: the baseline instrument
- Your tools stay the system of record; the diagnostic observes, it doesn't interfere
- A living map of workflows and data./02
Map
A system-agnostic graph of how work actually moves: steps, handoffs, waiting states, rework loops — and the data each step touches, with its owner and its quality. The Phase 1 data-landscape deliverable, kept live instead of drawn once in a workshop.
- Workflow graph built from observed events, not workshop recollection
- Data landscape: where each dataset lives, who owns it, whether it can carry an agent
- Every claim in the diagnostic traces back to instrumented evidence
- The top ~15 candidates, ranked by evidence./03
Score
The candidate engine scores every automation opportunity on annualised hours saved against ease of automation — data readiness, validation-gate design, integration surface. The ranking is generated from measured hours, not estimates in a slide.
- Annualised hours saved computed from the captured baselines
- Ease-of-automation scored on data readiness and the human validation gate each workflow needs
- Decision material generated for the steering cadence, not assembled the night before
- Baseline → delta → decision, in one place./04
Decide
When build opens in Phase 3, every agent reports into the same platform it was scored in: measured baseline, live delta, gate status. Below ~20% productivity gain, the kill/pivot flag raises itself.
- Per-agent baseline and delta, on the same instrument that set the baseline
- The ~20% kill/scale rule computed, not debated
- A full audit trail behind every gate decision
Deployed, not sold.
Baseline isn't a product you licence. It ships with the Phase 1 team, does the diagnostic's work, and leaves a complete handover behind when the engagement ends.
- Runs in your tenancy — client-data isolation by default
- Read-only connectors; automotive-grade security posture
- Everything exportable: graphs, baselines, scores — a full handover pack
- No licence fee. The platform is part of the Phase 1 engagement
- SAP ECC / S4HANA
- Teamcenter · Windchill (PLM)
- Trados · Phrase (TMS)
- Jira · Azure DevOps
- SharePoint · Confluence
- Git repositories
- CMS / CCMS (DITA)
- Data warehouses · flat files
Read-only by design. Two-way integrations belong to Phase 3, behind the gates — the diagnostic never writes into your systems.
The diagnostic's output isn't a report. It's a live system your steering committee can interrogate — and the same instrument later decides what scales and what gets killed.
See Baseline inside your estate.
The paid two-week discovery sprint deploys the first connectors and time capture on a live delivery line.