Systems and process build
For when you already know what is broken and nobody has had a clear week to go and rebuild it.
When the diagnosis is not the problem
Sometimes a review is unnecessary. You know exactly what is wrong, you have known for months, and the reason nothing has changed is that fixing it properly means taking somebody off the work that pays for everything else. So it stays on the list, and every week it costs a little more than it did the week before.
The usual candidates are quoting, scheduling, onboarding, reporting, and the handover between two teams that have never quite agreed on who does what. None of them are glamorous. All of them are where growing businesses lose hours and margin without ever putting a number on it.
How the work runs
We agree what good looks like, then I design the process, build it, and test it with the people who will actually be using it, because a process that works only when I am in the room is not worth having.
If software is involved, it is configured and running before I leave, and your team has been trained on it rather than sent a document about it. Where something off the shelf does the job, I will say so and set it up properly. Where nothing quite fits, I build a custom solution around how your business actually works, which is the part most consultants hand back to you as a requirement document.
The test I hold it to is simple: it has to still be working a month after I have gone, without me.
What you get
A process in use rather than documented, the people who use it trained on it, and the documentation written so a new starter can follow it. Where the work removes admin rather than reorganising it, the time comes back to the team immediately, which is usually what makes the case for doing it.
If the fix turns out to be less about process and more about the tooling, that shades into automation and practical AI. If you are not yet sure which part of the business is costing you most, start with an operations review.
Common questions
How long does a process build take?
It depends entirely on the process. Something contained, like quoting, is a short piece of work. Rebuilding the flow between two teams takes longer because it needs both of them involved.
Do you work with our existing software?
Wherever it does the job, yes. Replacing working software is expensive and disruptive, and most of the time the problem is how it has been set up rather than the tool itself.
Can you build custom software if nothing fits?
Yes. Where nothing off the shelf fits properly, I build what you need and hand it over running, with your team trained on it.
What happens after handover?
The process is yours and it should not depend on me. If you want somebody keeping the improvements moving afterwards, that is what fractional operations support is for.
How is it priced?
A fixed fee per project, agreed once we both know the scope, rather than an open ended day rate.
Start with a conversation
Half an hour on the phone is usually enough for us both to work out whether there is something worth doing here.