OPERATING MODEL INTELLIGENCE

See how work really moves through your business.

Alescentrix measures the distance between how your business is designed to run and how it really runs, from data you already hold.

We are taking on a small number of design partners for the first Baselines. Join the list and we will write to you when places open.

ORDER TO CASH, AS WORKED

Sales Order desk Credit Control Fulfilment Pricing lead spreadsheet email chase
As documented As worked Not in the SOP

Cycle time, median

11 working days

19 days at P90. 214 cases, high confidence

Flow efficiency

36%

Active share of elapsed time. 214 cases, medium confidence

Illustrative example of a Baseline finding. Not client data.

THE PROBLEM

Every organisation runs two operating models. Nobody can say how far apart they are.

Process mining reads what systems record. Workplace analytics reads how busy people are. Workshops record what people say. Alescentrix measures the distance between the designed model and the real one, then measures whether it closed after a change.

As documented

The designed one

It lives in SOPs, policies, job descriptions and process maps. It is what the business case, the audit and the automation plan are built on.

As worked

The real one

How work actually moves, which roles it really depends on, where it waits, and which spreadsheet the process quietly runs through.

Three people, three answers

Ask three senior people how a process works and each describes a different one. Weeks of workshops produce a map that is already out of date.

Bottlenecks are folklore

Everyone knows the work depends on one role. Nobody has the evidence, so it never gets fixed.

Spend is approved on estimates

Automation and AI business cases rest on someone's best guess of how long work takes, and nobody checks the result afterwards.

THE UNWRITTEN OPERATING MODEL

Most of how a business works was never written down.

The workaround everyone uses. The role everyone asks. The unwritten rule. This knowledge is hard to capture and very valuable, and it lives where the work actually happens: in email and chat, not in process documents.

Where the knowledge sits

Which role is always asked, and which team the answer really comes from.

How the work really routes

Where cases go when the SOP names one role and practice uses another.

What the process depends on

The single role a process quietly runs through, shown with evidence so the risk can be dealt with.

The organisation keeps what it knows. The point is resilience: knowledge that survives moves, retirements and restructures, and new joiners who learn how the work really runs. Alescentrix shows how the work runs. It never profiles what any one person knows.

HOW IT WORKS

Four steps, from how work runs today to proof that it changed.

Alescentrix reads data you already hold. Nothing is installed on anyone's desk.

01

Observe

Map how work moves between roles and teams: where it starts, where it waits, and where it loops back because something was missing.

02

Trace

Follow one real case from start to finish, every handoff included, in front of the people who own the process.

03

Compare

Set your SOPs, policies and job descriptions beside what was observed, and see where practice and documentation part.

04

Measure

Run it again after the change. The same method, the same measures, so the improvement is a number and not a claim.

Works with Microsoft 365 today. More systems follow, tested on client data first.

WHAT IT MEASURES

Flow analytics for the work that isn't on a board.

Onboarding, procurement, claims and applications have no board. The work lives in email, chat, spreadsheets and systems that never meet. A Baseline rebuilds the cases for one process family, then measures the flow in terms operations leaders already use.

01

Cycle time

End to end, as a median and a P90, so the slowest cases stay visible.

02

Throughput

How many cases are completed each week.

03

Work in progress and aging

What is open now, how long it has been open, and what is stuck today.

04

Flow efficiency

How much of the elapsed time is work and how much is waiting. Waiting is measured on the case, never as a person's idle time.

05

Handoffs and returns

How often a case changes hands, and how often it comes back to a team it has already left.

06

Cost per case

From your own rates by role band, never individual salaries. Reported as a range.

How the figures are reported

Coverage and confidence on every figure

Each number says how many cases it rests on and how reliably they were linked.

Unknown stays unknown

Time we cannot observe is flagged as unknown. It is never counted as zero effort.

Capacity is not cash

Released hours are reported as capacity until spend actually falls. Your finance team signs off the benefit.

Open cases count too

Open, abandoned and cancelled cases are shown alongside completed ones.

HOW TO START

The Operating Model Baseline

One process family, measured, with the evidence attached. You keep the findings and the baseline.

1

process family

2 to 3

weeks

Fixed

fee

No percentage promises. We measure the starting point, point the change at the right place, then measure the result. The number is whatever the measurement says.

What you get

  • 01 A measured baseline. Cycle time, waiting, handoffs and cost per case, with bottlenecks, loops and single points of failure named. Start and end of a case are agreed with you in the first week.
  • 02 A picture of the unwritten process. How the work really runs, and which roles it quietly depends on.
  • 03 A findings report. Every figure shows how many cases it rests on and how confident the reconstruction is.
  • 04 A ranked list of what to fix or automate first. Based on where the time actually goes.
  • 05 Proof after the change. An optional re-run, measured the same way as the baseline.

BUILT FOR TRUST

It looks at patterns in work, not at people.

By team and role

Results are reported by team and role, never by individual.

Never performance management

That is a term of the contract, written down before any data is read.

Inside your own environment

Your IT team deploys it in your own cloud tenant or infrastructure. Your data never leaves.

Reads what already exists

No desktop agents, no screen capture and no keystroke logging. It works from data your systems already hold.

WHO IT IS FOR

For the people about to change how a business runs.

COOs, operations leaders, transformation directors and private equity operating partners in mid-sized businesses.

Relationship-run businesses

Owner-led firms, professional services and much of the mid-market. The question is: show us the unwritten process.

Regulated businesses

Banks, insurers and healthcare. The question is: show us where practice departs from the prescribed process, by step and role.

The best time for a Baseline is just before

  • An automation or AI programme
  • A new COO's first plan
  • Integration after a merger
  • A key person moving on
  • A 100-day plan

WAITLIST

Be one of the first Baselines.

We are working with a small number of design partners first. Tell us what you are about to change and we will write to you when a place opens.

Design partners get the first Baselines at a reduced fee, in return for a case study and a reference.

We will use your details only to contact you about Alescentrix. Read the privacy notice.