Work you can try for yourself.

Working demonstrations on sample data, walkthroughs of how we would build it, and client work, described only as far as each client allows.

Client work

Described without naming the client, as our agreement allows. Nothing here is the client's data or their real system.

In progress: first release November 2026.

The problem: Customers write on WhatsApp, Instagram, Facebook and email. Each channel lives on a different phone or inbox, so replies are slow, enquiries get lost, and quotes are typed by hand.
What we're building: One staff application for all four channels, with an AI agent working inside it, connected to the company's ERP under strict control.
How it works: Every message lands in one queue. The agent answers routine questions and hands the rest to staff. Managers assign conversations, staff can take over at any time, and quotes are sent in the customer's own chat.
Status: First release in November 2026. Results will appear here once they are measured, and only with the client's written agreement.

Sample data, not the client's system.

Three small working systems with made-up data. Nothing you do is saved or sent anywhere.

Payments
Bank alerts matched to the right account
Payments that quote a reference are matched automatically; anything uncertain waits for a person to confirm.
Try payment matching
Stock
Stock across branches, with serial numbers
Sales and transfers update every branch at once, and reorder alerts appear before shelves run empty.
Try the stock system
Operations
A live board shared by two teams
A hotel front desk and housekeeping working from one room board, with a night report at the end.
Try the room board

Walkthroughs of the decisions behind a project, so you can judge our thinking before you talk to us.

Deciding
Keep, connect, improve or build
A four-way test for what to change in your current system, and what to leave alone.
Read the walkthrough
Moving
From spreadsheets to one connected system
The six steps that make a move from Excel smooth, shown on fees and results.
Read the walkthrough
Reviewing
What a Systems Review report looks like
The shape of the written report every engagement starts with, for a fictional organisation.
See the sample report

Every client story follows the same shape, and none is published without the client's written agreement.

The client
The kind of organisation, named only if they agree.
The problem
What was slipping through the gaps, in the client's terms.
What we built
What we kept, connected, improved or built, and why.
How it works
The steps the system now takes, and what stays with people.
What changed
Measured results only, with the client's permission. Until then, the status of the work.

Start with a free consultation. We'll look at how you run today and set out in writing what we would connect, fix or build.