This phase is a defined piece of work with a fixed scope and a fixed fee:

the Operational Friction Assessment.

You own everything it produces, whether or not we ever build anything together.

Understand the business first.

What does the business do, and how does it make money?

What are the top three to five operational priorities right now?

Where is leadership feeling the most pain?

We don't touch a process map until we understand what the business is actually trying to do.

Walk the operation - with your people.

We go through each key operational area with the team members who live in it.

Every manual, repetitive or paper-based task.

Every handoff between people, departments or systems.

Every place errors, delays and duplication occur.

Your people know where the friction is; our job is to get it out of their heads and onto the table.

Quantify the friction.

Time per task × frequency × the cost of the person doing it.

Then the downstream costs: rework, errors, missed commitments, staff frustration. And where relevant, compliance and risk exposure.

Friction stops being a feeling and becomes a number.

Prioritise, honestly.

We rank every opportunity by value of the saving against effort to fix.

Quick wins get separated from strategic builds.

And we apply a filter most automation firms won't: we separate what should be automated from what should simply be eliminated.

Some processes don't need a system. They need to stop existing.

What you receive:

a prioritised roadmap; typically two to three recommended system deployments, each with estimated ROI, a phased sequence, and a clear next step.

If the numbers don't justify proceeding, the roadmap says so.

We think in 'micro-projects', always looking to break things down to smallest practical economic unit, so that you experience speed-to-vale.

One system at a time, generally starting where the return is highest and the complexity lowest.

Design the to-be state.

What triggers the process, what happens, what comes out the other end and, importantly, where human judgement must stay in the loop.

We design around your people, not instead of them.

Check the library before building anything.

Across dozens of deployments we've built field-proven system designs for the operations that leak the most: proposals, reconciliation, onboarding, knowledge, communications, vendor management.

If a proven design fits, we adapt it to how your business runs - which contributes to why delivery takes days and weeks, not quarters.

Where your situation is genuinely unique, we build. But we never make you pay for a blank page that didn't need to be blank.

Connect it to what you already use.

New systems plug into your existing tools. Your team shouldn't have to move house to get a better kitchen.

Test it with the people who'll use it.

Working - and proven - before we hand it over.

The ROI metrics were agreed in Phase 1, before anything was built. Now we measure against them - actual time saved, errors removed, risk reduced, margin recovered.

Then one of three things happens, and all three are fine:

>> We move to the next system on your roadmap.

>> We hand over and you run it yourself. Everything is documented; nothing is hostage.

>> You keep us on high or low support (optional) for a range of monitoring, maintaining, improving.

Then the loop repeats.

That's what operational transformation, one proven system at a time means: not a two-year programme, but a compounding sequence of measured fixes, with each one paying for the next.

Most of our clients prefer to move to a formal retainer at this point, receiving increasing value for a budgeted line item.

Every engagement is scoped against a defined, measurable commercial return, and our fees are accountable to it.

The Assessment tells you where the value is before you commit to anything larger.

If we can't see the return, we'll tell you at the cheapest possible moment: the start.

Our general terms:

50% of agreed fee to start work.

50% at delivery for user-testing.

Continued adjustments are included within 14 days from user-test handovers.

Start with the Assessment →