Business Process Tracker
Request accessSign in

Run the whole business. Prove it ran the way it should.

One ERP for buying, stock, service, finance and people, built to be provable against SOC 2, ISO 27001, NERC CIP, HIPAA and 21 CFR Part 11.

Request accessSign in

Access is by invitation.

Interface 1 of 29

The overview of Sierra Ridge Manufacturing: cash in the bank by the ledger across three accounts, $108,934 invoiced in October day by day, seven open sales orders, two pieces of the person’s work overdue, seventeen open risks by band after treatment, compliance coverage of 87 per cent across six frameworks, stock on hand at standard cost, and service levels with open incidents by priority, each a tile leading to its module; beneath, the person’s own work, soonest first.
Executive dashboard: the organisation today from its own records, each figure a link into its module and shown only to somebody who may see that module.

Counted from the code, at every build

  • 4,674

    automated tests

    test cases, 134 of them browser specs

  • 76

    controls as code

    each with its owner, mappings and evidence

  • 151

    working screens

    in the application’s navigation today

  • 159

    requirements mapped

    across 6 frameworks

From day one

From a company profile to a working organisation

Most systems start empty. BPT drafts how the business works from a description of it.

  1. 1

    Describe the company. Its industry, people, products, suppliers, assets and accounts.

  2. 2

    Draft the landscape. Every process, value chain to work instruction, in BPMN.

  3. 3

    Review what follows. One change set of records; nothing is written until a person accepts it.

The process landscape of Sierra Ridge Manufacturing as a house: eleven value chains as pillars, each with its owner and how much is drawn, and their processes at levels 2 to 5 as tiles coloured published, in review, draft, or outlined where not yet drawn.
The landscape of a demonstration organisation: 107 processes in eleven value chains, five levels deep.

The whole business

Every record the processes produce, in the same system

One audit trail, one way of signing and one separation of duties, across every module.

  • Finance

    General ledger · Payables · Receivables · Cash and banking · Fixed assets · Budgets

  • Supply chain

    Procurement · Punchout catalogues · Inventory · Manufacturing · Quality · Fleet

  • People

    Human resources · Employee portal · Training · Performance · Time off · Identity and access

  • Customers

    CRM · Sales · Marketing · Market research · Commerce

  • Service and delivery

    IT service management · Projects · Field service

  • Governance

    Risk · Compliance · Contracts · Legal and eDiscovery · Documents · Audit

  • Architecture and data

    Master data · Enterprise architecture · Analytics · Integrations

The overview of Sierra Ridge Manufacturing: cash in the bank by account, invoiced this month, open sales orders, overdue work, open risks by band, compliance coverage by framework, stock on hand and service levels, each a tile from its module's own records.
The overview: each figure read from its module’s own records.

Controls and evidence

Controls enforced by the system, with evidence kept as it happens

What stops a mistake, and what shows it did not happen, is in the software.

  • Segregation of duties

    Whoever drafts a record never approves it.

  • Electronic signatures

    Part 11 signatures, bound to a hash of exactly what was signed.

  • An audit trail that cannot be edited

    Append-only and hash-chained, written with the change itself.

Mapped once, to many frameworks: SOC 1 · GDPR · ISO 27701 · ISO 42001 · EU AI Act · PCI DSS · WCAG 2.2 AA

The audit trail's latest sixteen events as a chain, each with its number and the start of its hash, joined to the one before, beside a button to verify the whole chain.
The audit trail as a hash chain: change one event and the chain breaks there.
Compliance coverage for six frameworks, each a ring: SOC 2, ISO 27001, NIST 800-53, HIPAA, NERC CIP and Part 11, with how many requirements are covered and how many are gaps.
Each framework’s requirements, covered by controls tested effective.

AI

AI proposes, and people commit

Models draft processes and records. They never write to the system of record on their own.

  • Your data stays yours

    Local models by default; hosted ones only if an organisation chooses.

  • Regulated fields held back

    Health, grid-security and personal data never reach a prompt.

  • Marked where it came from

    Which model drafted it, when, and what a person changed.

A process drafted by a model, awaiting a decision: the four questions it was asked, each answered in two and a half seconds, and the drafted diagram in three swimlanes, requester, procurement and finance.
A drafted process waits for a person to accept it; nothing is kept until they do.

Deployment

Runs wherever your data has to stay

One container image and PostgreSQL. Nothing proprietary sits in the way, which makes the air-gapped edition real.

  • Hosted

    Shared, each organisation’s data in its region.

  • Dedicated

    A network and database of your own.

  • On premises

    Inside your boundary, air-gapped if need be.

Request access

Sign-up is closed. Say who you are and what you would like to do, and a person will answer. Have an account? Sign in.

We keep your name, work email, organisation and what you write, to answer you and for nothing else, and delete them 90 days after you send them. Your network address is never stored: a one-way digest of it is kept for a day, to limit how often requests can be sent.