First we find where your team loses time. Then we fix it.

Four steps, always in this order

1. Diagnosis

We look at how the work really happens, with the people who do it: short interviews and observing a real working day. When we audit a system, we go in with read-only access and change no records. At the end you get a document with what exists, what is missing and where to start.

At an engineering firm, the audit showed that 1 in every 7 hours of work was not counted in the cost of any project. The firm knew this before investing in the ERP.

2. Tidy up

We simplify the process with the people who run it and get more out of the tools you already pay for and your team already knows. We only suggest a new tool when the current one isn’t enough, and we explain why.

At an IT services company, the first big change was moving all the work into the management tool they already had, with filters, tasks and alerts.

3. Build

We build what is missing: automations, dashboards, AI agents, an ERP or a sales system. Testing is done with real work, such as a proposal or an actual bill of materials, so the testing time also counts as work done.

In a small PR team, invoices started to process themselves. In one month, 86% of bank statement lines were resolved without anyone touching them.

4. Train

There are one-to-one sessions every week, training built on your team’s real cases, and one-page guides for each process instead of manuals. In one of our proposals we wrote “tools are 30%, people are 70%”. Time with your people is in the plan from day one.

AI isn’t always the answer

We use AI when it pays off, and a person always makes the decision. In an expense system, fixed rules handle most lines and AI only sees what is left. In public tenders, the numbers are calculated by code and every total is checked. AI writes the conclusions from them.

We have also proposed automations that the client turned down for good reasons, and we left them out.

Ways to work with us

Diagnosis

Putting time into the wrong place costs money and brings no growth. When the case is simple, the review takes a few hours and is part of preparing the proposal. When it is more complex, we audit your systems, which can take from two days to a month.

Project

When you already know what needs doing, we build it with scope and price fixed up front. It can be an automation, a dashboard, an AI agent or an ERP implementation. A small automation can be running the same day. An ERP goes in in phases and takes months. We agree up front how the result will be measured, and any work outside the scope is quoted separately.

Ongoing support

For teams that want someone close by after delivery. We agree what each month covers: sessions, adjustments and system maintenance, consulting hours or training.

Training

Hands-on workshops, with your team working on its own cases. We teach people how to think through the problem. No PowerPoint. It can be a single workshop or a programme: at an IT consultancy with over 400 people it was 12 two-hour workshops, built on each person’s real contacts.

After every delivery we always recommend a period of testing and adjustments, so that what we built works in your team’s day-to-day. The price depends on the project and is put in writing before we start. We talk about it in the first conversation.

What always stays on your side

The non-disclosure agreement is signed before we receive any document. Licences, AI accounts and databases are in your company’s name from the start, and access keys never sit in the code. Each process is written up in a one-page guide.

The more complex systems may need us for maintenance or to add what comes up later. Even so, if we stop working together, whoever comes next can pick up what is there.