Skip to content
MAVERICK Labs Contact

Workflow Audit · The usual first step

Start with one workflow. Keep the capability.

A scoped Workflow Audit maps one recurring process, from meeting actions and email follow-ups to forms, quotes and reports, and recommends a first automation with its review points made explicit. Building it is a separate decision.

Describe one workflow Try the 2-minute Opportunity Finder

Price

A fixed fee, quoted after a short call and agreed in writing before any work starts. You keep the report whether or not you build anything.

Who it is for

Teams with one process that keeps eating time.

Good candidates are recurring, rule-heavy and annoying: enquiry intake, quoting, job paperwork, status reporting, meeting follow-up, document checking. If you can describe what comes in and what should come out, it is probably a good fit.

A good fitThe process repeats weekly or more, follows rules most of the time, and the people doing it would rather spend that time on judgement or customers.
Probably not yetThe process changes from one case to the next, or the main problem is a missing decision rather than repetitive work. We will say so on the first call.

What you receive

A decision-ready first scope, in plain language.

Every finding is labelled by how well it is known, so you can see what was observed, what was concluded and what is still an open question.

Current-state mapInputs, hand-offs, systems, decisions, exceptions and outputs, as the people doing the work describe them.
Ranked opportunitiesEach one compared on likely value, effort, source quality and operational risk.
Recommended first automationScope, boundaries, approval points and acceptance checks for the first build.
What not to automateThe steps that should stay with people, and why.
Information requirementsWhat a build would need access to, and the boundary around it.
Open questionsWhat could not be confirmed during the audit, listed rather than guessed.
See what a report looks like

How it runs

Four steps, with you involved at each one.

The audit fits around your team. We do the analysis and the writing; your part is mainly the mapping conversation with the people who do the process.

  1. 1 · Short call
    Confirm the fit and the fee

    We talk through the process you have in mind, say plainly whether an audit is the right step, and quote a fixed fee.

  2. 2 · Mapping
    Walk through the process with the people who do it

    Inputs, hand-offs, decisions and exceptions. Sample documents only if you choose to share them, under an information boundary agreed first.

  3. 3 · Analysis
    Compare the opportunities

    We rank what could be automated, what should stay with people, and what a first build would need.

  4. 4 · Walkthrough
    Present the report. You keep it.

    You decide what happens next: build with us, build with someone else, or do nothing yet.

What it is not

Clear limits, stated up front.

The audit does not assume every step should be automated or that you need a new platform. It is not a compliance assessment or a security audit, and it does not commit you to a build.

Questions

Before you get in touch.

More answers on how we work.

What does it cost?

A fixed fee, set by the size of the process and quoted after the first call. It is agreed in writing before work starts, so there is no hourly meter running.

Do we need to share sensitive information?

No. Most of an audit is a conversation about how the work is done. If examples would help, we agree what can be shared and how it is handled first, and you can use redacted or made-up examples instead.

What happens after the audit?

You decide. The report is written so that any capable team could build from it. If you want us to build it, that is a separate, fixed-scope engagement.

How is this different from the Reality Audit?

The Workflow Audit looks forward: what to automate first. The Reality Audit is a specialist review of an existing system or set of claims: what it can actually show versus what is assumed.

Start with the process

Describe one recurring workflow.

What comes in, what should come out, and where it gets stuck. A few lines is enough.

Describe one workflow
Signal 01 / If the tool adds friction, it is not finished.