Does the Hub replace our orchestrator?

For rebuilt processes, yes. Processes still on the legacy platform keep running there until they are rebuilt or retired.

What does our team actually see?

A run log in plain language: every run, its inputs, its decisions, its outputs, and the approval trail. If a run needs a person, it appears with the evidence attached and waits.

Who owns what the Hub runs?

You do. The automations are code built for your business, and the documentation from the assessment stays yours whichever way the engagement goes.

How does the engagement run over time?

A standing arrangement sized to the estate: operating what runs, improving what needs it, and building what comes next. We review it with you before each renewal.

AI Operations Hub

Every automation, run and approval in one place.

See the Hub on your processes See how the work runs

What it looks like

A window into every automation you run.

Empire Automate AI Operations Hub

Overview

01Dashboard

Automations

02Report automationReady

03Excel automationReady

04Report draftingDraft

05Review queue3

Administration

06Admin dashboard

OL

Operations leadYour team

Dashboard

Run every automation from one place.

The Hub keeps everyday work simple: choose the automation, review what it produced, and keep moving.

All systems running

Quick accessPinned sections

01

Report automationDrop in source files and generate a report from a saved template.

Open

02

Excel automationTurn documents, notes and exports into the workbook your team already uses.

Open

03

Report draftingWrite sections with review flags, notes and source references visible.

Open

04

Review queueApprove prepared outputs before they are moved, sent or exported.

Open

Quick actionsStart here

+

Start a report runChoose files, select a template, then generate a draft.

✓

Review waiting outputsOpen drafts that need approval before they move.

⇆

Check connected systemsSee whether files, email and storage are syncing normally.

Recent runsToday

Board report draft generatedBuilt from 3 source files, waiting on review.

11:42

Workbook preparedSource notes mapped into the operations tracker template.

10:18

Source files checked2 notes attached, 1 register parsed, no upload errors.

09:55

Illustrative screens. Every Hub is built around the processes it runs.

01 / Why visibility

An orchestrator shows you queues. The Hub shows you decisions.

Run detail / Supplier invoice matching · illustrative

Awaiting review

09:12
Invoice received
Fields read and matched to purchase order
09:14
Variance found
Routed for review with the evidence attached
09:16
Awaiting review
Approval requested from operations
Next:
Post to finance system
Held until a person approves

02 / How it is built

One application, four layers.

03 / After the build

The Hub is a working relationship, not a handover.

We operate the estate with your team: watching the runs, tuning the judgement steps, and adding the next process when the business is ready. For estates assessed but not yet rebuilt, the quarterly re-assessment keeps the map, the risks and the rebuild order current.

The Estate Assessment in full

04 / Ownership

You own what we build.

The Hub is deployed into your environment, on your infrastructure and your accounts. The workflows, integrations, configuration and data are yours, your data stays in systems you control, and there is no per-seat fee and no licence that expires.

Ongoing support is available as a monthly retainer: monitoring the runs, maintenance when a connected system changes, fixes, and enhancements as the business finds more to automate. Businesses that would rather run the Hub themselves can, and the documentation is written for that.

FAQ

05 / Contact

See your work on a Hub.

Tell us the process that costs the most manual hours. We will tell you what it would look like running here.

See the Hub on your processes

Every automation, run and approval in one place.

A window into every automation you run.

Run every automation from one place.

An orchestrator shows you queues. The Hub shows you decisions.

What the Hub is.

Why the run history matters.

What your team actually does with it.

One application, four layers.

Connections Authenticated integrations into the systems that hold your data

Process logic Predefined logic carries the deterministic steps

Review and approval Configurable gates that hold outbound work until a person approves it

Run history Every execution recorded with its inputs, decisions, outputs, approvals and errors

The Hub is a working relationship, not a handover.

You own what we build.

Support, if you want it

Does the Hub replace our orchestrator?

What does our team actually see?

Who owns what the Hub runs?

How does the engagement run over time?

See your work on a Hub.