The autonomy ladder

From functional automation to enterprise autonomy, in five levels.

Functional automation makes single tasks faster. Enterprise autonomy lets the connected business run routine decisions itself, inside limits your leaders set. Most companies sit at level 1. Hiyaku takes you up one level at a time, and you choose how far to go.

  1. Level 0

    Manual

    People copy, check and chase information between systems.

    Who decides
    People, every time
    Typical response
    Hours to days
  2. Level 1

    Functional automation

    Scripts and rules run single tasks inside one system.

    Who decides
    People, with faster tools
    Typical response
    Hours
  3. Level 2

    Connected

    One ontology links customers, orders, assets and money across every system.

    Who decides
    People, with one shared view
    Typical response
    Under an hour
  4. Level 3

    Intelligent

    The model notices, predicts and recommends, and shows its reasoning.

    Who decides
    People approve
    Typical response
    Minutes
  5. Level 4

    Enterprise autonomy

    Hiyaku acts on routine decisions within your guardrails, logs everything and can undo it.

    Who decides
    Leaders set the policy
    Typical response
    Seconds

Response times are illustrative for a typical operational decision such as a reroute, a stock reallocation or a payment hold.

How it's done

Four steps from functional automation to enterprise autonomy.

Hiyaku sits on top of the systems you already run. Nothing is ripped out. You start with one decision your team makes every day, prove it at each level, and only then hand it over.

  1. Step 1 · Connect

    Connect the enterprise

    Read-only connectors pull from your ERP, CRM, transport system, spreadsheets, email, chat and sensors. Agents match duplicates and resolve conflicting values.

    • No migration, no rip-and-replace
    • Every record and fix is traceable
    Typically weeks 1–4
  2. Step 2 · Understand

    Build a live enterprise model

    Records are mapped to business entities and the links between them: the ontology, one live model every team shares.

    • Versioned like code, owned by you
    • Dashboards and apps read the same model
    Typically weeks 3–6
  3. Step 3 · Reinvent

    Reinvent the process

    Using the model, the intelligence layer traces cause and effect, predicts impact and designs process changes, with its reasoning shown. In shadow mode, people still decide.

    • Every recommendation shows its evidence
    • You measure how often people agree
    Typically weeks 5–8
  4. Step 4 · Act

    Build agents to execute

    Once a decision type has proved itself, Hiyaku builds agents that carry out the new process within the limits your leaders set, writing back to the source systems.

    • One decision type at a time
    • Above the limit, it still asks first
    From week 8, decision by decision

Timelines are illustrative for a first decision type in a mid-sized company. Yours depend on your systems and how far up the ladder you choose to go.

Cost of manual work

What the seven gaps cost you each year

A rough estimate you can adjust. It counts only the time people spend chasing, checking and re-keying what your systems should handle themselves. Lost sales, spoilage and penalties come on top.

Estimated yearly cost

$0

Hours lost per year
0
Equivalent full-time people
0
If Hiyaku removes half of it
$0 a year

Assumes 48 working weeks and the hours per person per week shown next to each problem. These are planning assumptions, not measured benchmarks; replace them with your own.

The core entities

Every business is built from the same core entities.

The names change between a store, a port, a factory and an airline. The shape does not. Hiyaku models them once, links them, and gives every app and autonomous agent the same map to reason and act on.

Architecture notes

The engineering behind autonomy

Six ontology layers, the eight hardest problems in connecting an organisation's data, and four 3D models you can rebuild from ruins.

Read the architecture notes

780 → 40connections needed for 40 systems, point to point versus through one shared model
1.6 yr → 8 minto de-duplicate 10 million records, comparing every pair versus grouping them first
32ways a 5-system action can half-succeed, which is why every action can be undone

Contact us

Get started.

Tell us about one decision your team makes every day: a reroute, a stock move, a payment hold. We will show you how far toward autonomy it can go.

We use these details only to reply to you. See our privacy policy.