First, what's actually happening

Most decisions about software get made before anyone has looked closely at the work. A Diagnostic is three days of looking, and a straight answer about what's worth changing. Including, sometimes, nothing.

Show us where it breaks

Thirty minutes, free. We'll tell you whether you need one.

One repeating task, you can just have removed. These are different.

  • You've hired to keep up with the admin

    The last two people weren't to grow the business. They were to keep it tidy.

  • Someone important is away

    The work still has to go out. The bit that made it work was in their head.

  • It depends who's on shift

    Two people do the same job two ways. Both fine, until a customer compares them.

  • Simple questions take a tour of the team

    Where's that up to? Three messages and a phone call later, you know.

  • One spreadsheet, two people who understand it

    It works. It has worked for years. And you'd rather not think about what happens to it.

  • You can't prove what happened

    The work was done properly. Six weeks later, showing that is a different matter.

If any of those sound familiar, removing one task might not fix the underlying problem. It could just make the symptom quieter for a while.

Not a quotation dressed up as a report.

A focused look at one operational area.

We talk with the people who run the process.

We look at the spreadsheets, the job sheets, the inboxes, the handovers.

Then we pressure-test the work against absence, volume, exceptions and incomplete information.

One operational area. About three working days.

Yor working at a laptop, a Modulinc screen on the wall behind him

What you receive

  • A map of how the work actually runs today, workarounds included
  • The friction points, and the places that depend on one person
  • What happens under pressure: someone off, a busy week, a last-minute change, missing information
  • Prioritised recommendations, each marked as one of: leave as it is · change the process · use an existing tool better · automate or connect · build something new
  • A walkthrough call to go through it together

A Diagnostic tells you what to change. It doesn't change it.

That's deliberate. Every recommendation comes with a clear next step. Sometimes that's changing a process. Sometimes it's making better use of software you already have. Sometimes it means building something new. And sometimes the right answer is to leave things exactly as they are.

If you want us to build what we recommended, that's Implementation, scoped and priced separately, one module at a time.

£750

one operational area · about three working days

If you go ahead with Implementation within thirty days, the full £750 comes off the first module. It doesn't come off One Task Off Your Plate, which is priced to stand on its own.

Show us where it breaks

We write up what we see, without naming anyone.

Five sets of notes, one per sector. Each one lists the five places that sector quietly loses hours, two things we'd leave alone, and what good looks like instead. Two pages, free, no form, nothing to fill in.

Pick the one that looks like your business.

These aren't a sample of your Diagnostic. Your Diagnostic is about your work. These are about the shapes the work tends to take.

Start with a call, not a Diagnostic

Thirty minutes. We'll work out whether what you're describing needs one at all. Quite often it's a single task, and that's cheaper and faster. If it is a Diagnostic, you'll know what we'd look at and what it costs before you commit to anything.

Show us where it breaks

If it isn't a fit, we'll tell you, and it costs you nothing.