Service 01

Before you change anything, get a clear picture of how the business runs.

An assessment is not a review of how well people are performing. It is a structured look at how work moves through your business, where it slows down, and which change would make the biggest difference for the least disruption.

Most owners already have a strong instinct about what is wrong. The assessment turns that instinct into something specific enough to act on, and specific enough to share with the people who will do the work.

What you receive

  • A map of your core workflows, as they really happen
  • A review of the tools you own and pay for
  • A shortlist of improvements, ordered by impact and effort
  • A roadmap you can act on with us, or without us

Delivered as a written summary and walked through with you, so nothing sits unread in a folder.

Growth added people, not clarity

Each new hire learned the work slightly differently. Now two people do the same task two ways, and nobody is certain which is correct.

The workarounds became the process

A spreadsheet, a shared inbox and a sticky note on a monitor are holding a critical part of the operation together.

The last purchase did not change much

The software is there. The improvement did not arrive, because the process feeding the software was never sorted out.

How the assessment runs

Five passes through the business, each one a little narrower.

The goal is not a perfect document. It is a shared, accurate picture that you, your managers and your team can all recognize.

We are not looking for who to blame. We are looking for where the work waits.

  1. 01

    Listen to a normal week

    We start with the people doing the work: what arrives, what they do with it, where it waits, and what gets typed in twice. No process diagram required. We work from how things actually happen.

  2. 02

    Map the flow

    We trace a customer enquiry from first contact through to final payment, including the side routes people invented to keep things moving. Those workarounds usually point straight at the friction.

  3. 03

    Review the tools

    A plain inventory of what you own, what each tool is for, what you pay for but rarely open, and where the same information is being held in more than one place.

  4. 04

    Name the friction

    Bottlenecks, manual handoffs, duplicate entry, approvals waiting on one person, and reporting that takes an afternoon to assemble. Each one is written down with the work it costs.

  5. 05

    Set the order

    Every finding lands on one page with effort, impact and dependencies. Some fixes need no software at all. Those go first, because they are the cheapest to prove.

What we look at

Three areas, one connected picture.

Processes, tools and people are never separate problems. A slow approval is usually a workflow issue, a software setting and a training gap at the same time.

Operations

  • Enquiries, quotes and how they become jobs
  • Scheduling, dispatch and handoffs
  • Purchasing, approvals and supplier admin
  • Invoicing, follow-up and collections
  • Reporting and month-end routines

Technology

  • What you own, and what each system is for
  • Where the same record lives in two places
  • Manual exports and re-keying between tools
  • Unused features you are already paying for
  • Who can see and change what

People

  • Knowledge held by one person only
  • Steps that depend on a specific individual
  • Gaps between how work is documented and done
  • Where new staff need the most support
  • Busy-season pressure points

What you leave with

A roadmap sorted by what to do first, not by what is most exciting.

Every recommendation is practical, costed in rough terms, and separate from the next one. You can act on the first column without committing to the third.

Now

Things you can change this month

Usually the cheapest wins: clarify who owns a step, stop entering the same details twice, agree what happens when something is missing.

  • One clear owner per handoff
  • A single place for incoming requests
  • Fewer status update meetings

Next

Small changes with the tools you own

Configure what you already pay for, connect two systems, or automate the one task that repeats every day.

  • Forms that feed the right records
  • One connection between two apps
  • A recurring report, generated

Later

Bigger decisions, made with evidence

Replacing a core system, a wider automation program, or a training rollout. Worth doing once the groundwork is clear.

  • A considered software shortlist
  • Automation across several teams
  • Training and adoption plan

Questions

Questions business owners ask before starting

A few things owners usually want to know before booking an assessment.

How long does an assessment take?

It depends on the size of your team and how many workflows you want covered. We agree the scope before we start, so you know what will be included and roughly how much of your time it will ask for.

Do we need to prepare documentation or process diagrams?

No. We work from conversations and from watching how work actually moves. If you already have documentation, we will read it, but an out-of-date process map is often the least reliable version of a business.

Will the assessment tell us to buy new software?

Often it does not. Many of the most useful findings are about how existing tools are configured and used, or about steps that can be simplified without any software at all. When a gap is real, we will say so plainly.

What if we already know what the problem is?

Good. We will test that assumption with you, and we will also look at the neighbouring processes, because a problem usually creates costs somewhere else. If your diagnosis holds, we will say so and help you plan the fix.

Who needs to be involved from our side?

Someone who can make decisions, usually the owner, founder or general manager, plus the people who do the work day to day. We keep sessions short and schedule them around your operation.

What happens after we receive the roadmap?

It is yours. You can act on it yourselves, bring in your own team, or ask us to implement parts of it. There is no requirement to continue, and the recommendations are written so they still make sense without us.

Next step

Start with the problem you can feel, and we will find the rest.

Tell us what a normal week looks like and what keeps getting in the way. We will suggest whether an assessment is the right first step.