Process Audit

Know what to automate before you pay to build it.

For businesses that know they're losing time to admin, but not exactly where, or what to fix first.

Over one to two weeks we look at how the work actually gets done in your business. Then we give you a written plan: what to automate, in what order, what each is likely to save, and a fixed price for each one.

One job on its own is what we call a starter build (£300–£1,500). Starter builds do not need an audit. The audit is for businesses deciding which bigger system to build first.

The price

£1,500

A fixed fee. Credited in full against any custom build (£3,000+) if you proceed within 60 days. If you don't go ahead, you keep the plan.

  • ✓Takes one to two weeks
  • ✓On video calls, or in person if you're nearby
  • ✓A written plan you keep
  • ✓A fixed price for each thing worth doing
Start with a free 30-minute call
Free call or paid audit?

What a free call can tell you, and what it can't.

Take the free call first, from us or anyone else. It's genuinely useful. But half an hour on the phone is an informed guess. The audit works from your real figures.

A free 30-minute call gives you

  • A fair idea of whether the job you described can be automated.
  • A rough price, based on similar work.
  • A straight answer on anything that obviously won't work.
  • A feel for whether you'd want to work with Ben.

The audit adds

  • A clear picture of who actually does what, day to day.
  • Savings worked out from your own hours, staff costs and volumes.
  • The order to do things in, once each one has a price next to it.
  • A written plan you can hand to any developer, ours or not, and get a like-for-like quote.
What you get

One written plan, yours to keep.

  1. 1

    A map of how the work gets done

    Who does what, when, and in which software, written down and drawn out. Most clients find this useful on its own.

  2. 2

    A list of what is worth automating, in order

    Ranked by what each one saves against what it costs, so you start with whatever pays for itself fastest.

  3. 3

    What each one would save

    Hours a week, what those hours cost you in a year, and how long the build takes to pay for itself. Worked out from your own figures, not an industry average.

  4. 4

    How each one would work

    In plain English: what it does, step by step, and which of your systems it connects to. Clear enough for any developer to quote against.

  5. 5

    A fixed price for each

    A number you can plan and budget around, item by item.

  6. +

    Yours whatever you decide

    Take it to another developer, use it in-house, or file it for next year.

How it runs

Two weeks at most, from start to plan.

  1. Start of week one

    A two-hour first session

    On a video call or in person. We go through the business end to end: every process, every piece of software, every hand-over between people. We ask the questions your team stopped asking because “that's just how it's done”.

  2. Later in week one

    Watching the work

    We watch the key jobs being done, read whatever is already written down, and map it out. This is where the workarounds and the spreadsheets that “just work” turn up.

  3. Week two

    The written plan

    We work out what each change would save, how each would work and what each would cost, and write it up. You get it as a PDF, with a 30-minute call to go through it.

Is it right for you?

Right for some businesses, not all.

We'd rather tell you it isn't the right fit than take your money for something you won't get much from.

A good fit if

  • ✓ You have a team, roughly 5 to 200 people, and jobs that get done the same way every time
  • ✓ People spend hours a week moving information from one place to another
  • ✓ Your software doesn't talk to each other
  • ✓ You think something could be automated but don't know where to start
  • ✓ You want the case for it on paper before committing to a build
  • ✓ You've had quotes before that felt vague

Probably not right if

  • ✗ You work on your own and there's no team process yet
  • ✗ You already know exactly what you want built. Skip the audit and just tell us the job
  • ✗ You're looking for a recommendation for off-the-shelf software
  • ✗ The way you work changes every week
  • ✗ There's no budget to build anything afterwards
Questions

What people usually ask.

Do I have to use you to build it afterwards?+

No. The plan is yours to take anywhere. Credited in full against any custom build (£3,000+) if you proceed within 60 days. If you go elsewhere or decide not to go ahead, you keep the plan and owe nothing more.

What's the difference between the free call and the audit?+

The free call is a 30-minute conversation to understand your business and check there is something worth automating. The Process Audit takes one to two weeks: we look at how the work actually gets done, work out what each change would save from your own figures, and give you a written plan with a fixed price for each item.

Can you do it remotely?+

Yes. Most audits are done over video calls and screen sharing. If you're in Derbyshire, South Yorkshire, Nottinghamshire or nearby, we're happy to come in person for the first session at no extra charge.

How much of my team's time will it take?+

The first session is two hours. After that we may need 30 to 60 minutes with particular people. Usually three to five hours in total across two weeks, arranged around your diary.

What if we already know what we want built?+

Then skip the audit. Tell us the job and we'll quote for it directly. The audit is most useful when you're not sure where to start, or want the whole picture.

Is the £1,500 plus VAT?+

No. The Automation Agency is not currently VAT registered, so £1,500 is the whole fee.

Start here

Start with a free call.

Thirty minutes, no commitment. We'll talk through your business, and tell you honestly whether the audit is the right next step or whether you can skip it.

Prefer a conversation?

Call Ben, Monday to Friday, 9am–5.30pm. You'll get Ben, not a call centre.

01246 923041

Two quick questions, then pick your slot

So we can come to the call with something useful rather than spending the first ten minutes working out who you are.

Rather write it down? Tell us about the job.