1 weekStart with a one-week proof on one processStart with a one-week proofWatch the latest Stanford AI & Investment session

Book a call
Book a call

DiagnosisSee how you really run

Reconstruct the company bottom-up, as built.

We start from the evidence at the bottom, the outcomes and the work that produced them, and infer upward to execution and strategy. The map keeps moving with the processes.

Bring us one process

Four layersHow the as-built map is built, from the bottom up

From what was produced to the strategy behind it.

Read from the bottom: outcomes are observed directly; each layer above is inferred from the one below. Red marks the work that never reaches a system.

  1. 01StrategySales · marketing · financial · operating · customer strategyInferred from execution
  2. 02Strategy executionDepartments · decisions · coordination · approvals · handoffsInferred from processes
  3. 03Detailed processesTasks · systems · exceptions · rework · hidden workInferred from outcomes and traces
  4. 04OutcomesForms · reports · BI dashboards · operational and customer outputsObserved directly

The evidenceWhat we read, and what we add where nothing is recorded

Gather what exists. Embed what is missing.

  • Corporate data

    Databases

    ERP, CRM and warehouses, read through read-only connections.

  • Hidden workflows

    Excel, e-mail, chat and paper

    Read by OCR and our reading models, so work outside the systems is counted too.

  • New data types

    Audio, video and photo

    Where a person fills the gap today, we embed the capture in its place. People handle only the exceptions.

Everything lands in one evidence base, which feeds every later step.

Hidden workThe work outside the official workflow

Find the work outside the workflow.

The gold line is the official path. The red detours are where the real work happens: they are mapped next to it, for processes and for data.

Process

Official path

  1. 1Request
  2. 2ERP workflow
  3. 3Control gate
  4. 4Outcome

Hidden path

  • Excel rework
  • Meeting decision
  • Chat approval
  • Manual upload

Data

Official path

  1. 1Source system
  2. 2Governed pipeline
  3. 3Warehouse
  4. 4Report

Hidden path

  • Unowned data flow
  • Access outside policy
  • Missing lineage

Data supply chainHow we map data as it moves through the business

Map data as it moves through the business.

Data inputs are processed into outputs; operations create new data that returns as new inputs. Governance sits under every layer of the loop.

L0 · Governance foundation

Policy · ownership · stewardship · quality · controls · privacy · sovereignty

  1. L1Data inputsERP · CRM · HRIS · sensors · documents · files
  2. L2Data processingCleaning · transformation · models · rules
  3. L3Data outputsForecasts · dashboards · scenarios · recommendations
  4. L4Operations-generated dataInteractions · automation outputs · support · feedback

L4 returns as new L1 inputs

What you receiveThe outputs of the diagnosis

What you hold at the end.

  • An as-built process map, hidden work included, kept current
  • As-built data governance: the full data supply chain, with an owner at every link
  • One evidence base that every later finding traces back to