CentrIQ

What it becomes

Three businesses. One foundation. Three systems that look nothing alike.

CentrIQ is not a product with a fixed feature list. Every business gets its own environment: what comes in, what it is called, what the rules are and what the screens show are all shaped to how that business runs. Below is what that actually produced for three of them.

No customers are named. Each is described by business type and situation, with anonymised data in every screen.

Ports & maritime · four ports

A ports authority managing vessel scheduling, berths and billing across four ports

What was broken

Vessel windows were agreed by email and held in a scheduling spreadsheet one person maintained. Berth clashes were found by someone noticing. Billing was assembled after the fact from three sources, so revenue leaked quietly and disputes were unwinnable.

What their system does now

Every vessel movement, berth window and service sits in one view across all four ports. Clashes surface as they are created, not the day before. Charges accrue against the movement as it happens, so billing on departure is a check rather than a reconstruction.

Their word for a booked window is a “nomination”. That is what the system calls it.

Berth schedule · four ports
BERTH 1
BERTH 2
BERTH 3
BERTH 4
vessel windowclashbilled on departure
Revenue by port

98%

142

6

Vessel record + history
activeserviced
Run sheet · both depots
NTHon time
STHloading
INTlate
RTNbooked
Exceptions

Scheduled

In progress

Needs a human

Customer update, drafted
drafted for youSend

Freight & logistics · 85 staff, two depots

A freight operator coordinating movements across two depots

What was broken

Bookings arrived by email and phone, were written on a whiteboard, then copied into a spreadsheet at the end of the day. Two depots kept two versions. When a load ran late, whoever answered the phone had to work out the story from scratch.

What their system does now

One run sheet covers both depots. Anything running late lands on an exceptions board before a customer calls, and the update to that customer is drafted for the operator to send. Pricing and invoicing pull from the movement, so nothing is re-entered.

The whiteboard is still on the wall. It has a footy tipping ladder on it now.

Professional services · migration practice

A migration practice where each consultant was handling three hundred emails a day

What was broken

Everything happened in individual inboxes. Client files were folders on a drive, deadlines lived in people’s heads, and if a consultant was away nobody could answer where a matter was up to. Volume, not complexity, was breaking the business.

What their system does now

Everything arriving is triaged against the right client file automatically, with replies drafted for approval. Every matter has one view: what stage it is at, what is outstanding, what has been lodged. Any consultant can pick up any file and see the whole history.

They call each piece of work a “matter” and its deadline a “lodgement”. So does the system.

Shared inbox · triaged
Triaged · consultant A
Triaged · consultant B
Needs a human
312 today
reply drafted
Matters by stage
shipped
in progress
due Fri
at risk
Lodgements, ageing
0–2d
3–7d
7d+
nothing ages quietly

Three systems. Same platform underneath. That is the whole idea.

None of them adopted CentrIQ’s way of working. Each got a system shaped around theirs, in their language, with their rules and their reporting. Because the foundation already exists and is maintained, all three were live in weeks rather than after a year-long build.

What would yours look like?

Describe how the business actually runs and we will tell you what we would pull in, what the screens would show, and what it would take.

Talk to us See the ecosystem