Strategy is documented, but nobody can tell whether it is being executed.

Every process as it really runs, gaps included.

Processes are assembled from two sources: what the systems record and what the people say in interviews and procedures. STRAX checks one against the other and marks each step automated, manual or missing on the diagram. Closing a gap becomes a decision, and the workflow, portal or report that closes it is tied back to the step.

Request a demo → All features →
A business process mined from systems and people, validated, then run by design Three sources (systems, workflows and data, people and documents) feed a process that draws itself. Each step is marked automated, manual or missing; the documented order is compared with the order the systems record and a credit check is found out of place; the steps are put in order, the gaps get workflows and a portal behind them, and coverage reads five of five, by design. Systems · 4 Workflows & data · 12 People & documents · 6 Coverage 3 of 5 steps covered 5 of 5 · by design Order in Credit check Pick & pack Invoice Deliver Automated Manual Automated Automated Automated Missing Confirmed As documented Order in Credit check Pick & pack Invoice Deliver As it runs Order in Pick & pack Credit check Invoice Deliver Out of order · credit risk Matches · runs as designed SOP updated · indexed for the assistant Mined from the systems and the people running them. Documented as it really runs. Each gap becomes a decision, with something built. The process as it really runs, and then as designed.

Mined from systems and people

The process is assembled from two sources that rarely agree: what the systems actually record (orders, tickets, invoices, and the workflows and data already flowing through the hub) and what the people say in interviews, standard operating procedures and the documents they work from. The result is a BPMN process of the business as it really runs, with the knowledge behind each step attached to it, so it is not lost in a shared drive.

  • Drawn from the systems' own records and the workflows and data behind them.
  • Interviews, SOPs and policies captured as knowledge documents and attached to the steps they describe.
  • Standard BPMN, validated as you edit, and exportable for anyone to read.
Live Mined from records and people Systems and people, one process
Mined from systems and people Records from the systems and knowledge from interviews and SOPs assemble into one BPMN process, with the documents attached to the steps they describe. What the systems record orders · tickets · invoices workflows and data already in the hub What the people say interviews · SOPs · policies captured as knowledge documents Order-to-cash, as it really runs standard BPMN · validated as you edit · readable by anyone Order taken Credit check Goods picked Delivered Invoiced attached to "Credit check": credit-policy.pdf · finance interview #3 attached to "Delivered": driver SOP v4 · proof-of-delivery flow nothing drawn from memory ✓ Two sources that rarely agree, both read. One process, with the knowledge attached to its steps.
Assembled from what the systems record and what the people say: the process as it really runs.

Validated against reality

A documented process is a claim about how work happens, and STRAX checks it against both sources: does a step have a system, a workflow and data behind it, or is it done by hand, and does the order the documents describe match the order the systems record. The differences appear on the diagram step by step: a manual step, a missing confirmation, a credit check that happens after the goods have left.

  • Each step marked automated, manual or missing against the workflows, data and people behind it.
  • The documented order compared with the executed order, with the differences named.
  • The assistant reads the same process, so its answer to "how does this work here" is the validated one.
Live The documented process, checked Automated · manual · missing, marked on the diagram
Validated against reality Each process step is checked against the systems and the documents: automated steps green, manual steps amber, a missing confirmation flagged before it costs anything. Order-to-cash, checked step by step Order taken automated ✓ Credit check AFTER goods leave! Goods picked automated ✓ Delivered manual — by hand Confirmation missing documented order vs executed order: the differences, named Found: credit is checked after the goods have left. shown on the diagram before it costs anything Each step checked against systems and documents. Gaps show up before they cost anything.
Every step checked against the systems and the documents, marked automated, manual or missing, with the differences named on the diagram.

Closing the gaps by design

A gap becomes a decision: automate this step, build a portal for that hand-off, retire this system. The decision becomes a workflow, a portal or a report that is tied back to the process step it fulfils. Coverage is visible on the diagram, and the SOP is updated and indexed for the assistant, so the business runs the way it was designed to run.

  • Each gap becomes a decision with something built behind it, tied to the step.
  • Coverage on the diagram shows which strategy is running and where it still is not.
  • Documents are updated with the process and indexed, so people and the assistant read the same version.
Live A gap becomes a decision Decide · build · tie it to the step
Closing the gaps by design The missing confirmation step gets a decision (automate it), a workflow is built and tied to the step, and process coverage fills. The gap "Confirmation": missing found by validation, on the diagram The decision automate it with a workflow a choice, made on purpose Built and tied to the step workflow "Delivery confirmation" → step 5 SOP updated · indexed for the assistant Process coverage every step has something running behind it ✓ With the gaps visible, decisions get made. A gap becomes a decision, with something built. The business runs as it was designed to.
Each gap becomes a decision with something built behind it, and coverage shows on the diagram.

Keep exploring

More in Build

Hand-offs and approvals that run on their own.

Approvals, follow-ups and cross-system updates run on their own, from a two-system relay to a nine-step process, with no middleware to write or maintain.

Workflow automation →

A working portal for customers, partners and field teams.

Customers, technicians and partners get a working portal over current company data, secured per site and published to web and mobile in one step.

Sites — portals →

Reports read the same data the business runs on.

Reports and queries read the same hub the systems write to, so every figure is current, and AI writes the insight paragraphs from the report's own numbers.

Reports & queries →

See it on your own systems.

A demo takes about an hour. Bring a process, a portal or a report you would like to see built on your own data.

Request a demo → Request a quote