Services
Three stages.
Skip one and it doesn't stick.
Most technology projects fail somewhere other than the technology. They fail because nobody diagnosed the real problem first, or because nobody stayed long enough to make the new way normal.
How I work
Consulting, implementation, then change
Same three stages every time, in the same order. Where you join depends on how much you already know about the problem.
Consulting
I map how work actually flows today — not how the org chart says it should. Where it stalls, where things get retyped, what nobody can see. You get a roadmap for your business rather than a generic one, and an honest view of what's worth fixing first.
Implementation
Building the thing. Request forms so work arrives in one place, workflows with real owners and dates, dashboards that show status without anyone having to ask, and automation for the steps a person shouldn't be doing by hand.
Change management
The stage everyone underestimates. Technology only works if people use it, so I train the team, sit with them through the first cycles, and adjust the system to how they actually work — until the new way is just the way.
Where it starts
A baseline audit
Before anything gets built, I spend time working out where the week actually goes. Who touches what, how many times the same number gets typed, which approvals wait on one person's inbox, and what data is being thrown away at the point it's created.
You come out of it with a map of the current process, the handful of places worth attacking first, and a straight answer about whether you need me at all. Some businesses don't — occasionally the fix is a conversation and a shared folder.
What you get
The current map
How work really flows today, handovers and all.
The constraint
The one or two places where everything slows down.
The quick wins
What could be fixed in a fortnight, separated from what takes a quarter.
A straight recommendation
Including "you don't need this yet", if that's the answer.
What I build with
Chosen on adoption, not on hype
Process improvement dies when the process lives in a document nobody opens. It has to be embedded in the tools your team is already in every day.
Wrike — when you need real structure
If there's no consistent work management system, Wrike becomes the delivery hub: requests come in through a form, move through a workflow with owners and dates, and report themselves. It's the right call when work arrives from lots of places and keeps getting lost between them.
Microsoft 365 — when you're already living there
If the business already runs on Microsoft 365, the cheapest win is usually to systematise what you have: Teams channels that match how work is actually grouped, a SharePoint structure people can navigate, Lists instead of spreadsheets, and Power Automate for the repetitive steps.
And sometimes, something built for the job
Occasionally the off-the-shelf thing genuinely doesn't fit — a niche process, an industry with its own rules, a piece of data nothing else models properly. Custom software has become far more affordable for small and mid-sized businesses than it used to be, and when it's the right answer I'll say so. When it isn't, I'll say that too.
Ready to multiply the value you deliver?
Tell me where your week goes. If I can help, I'll tell you how. If I can't, I'll tell you that instead.