The operations audit
Know what
to fix first.
One working session to review how your business runs, followed by a ranked plan for what to change.
See sample findings belowWhat you leave with.
Written findings, ranked recommendations, and a practical first step. Your team can use the plan with us or take it elsewhere.
Findings
Where the work gets stuck.
A record of the recurring jobs, handovers, and tools we reviewed. What is slowing things down, with the evidence and gaps made clear.
Priorities
What is worth changing first.
An ordered set of recommendations weighed by likely benefit, effort, readiness, and risk. Including what should stay with a person.
A first move
How to act on the plan.
One priority workflow in more detail: the proposed change, approval points, dependencies, and a small pilot to test before building further.
Delivered within two business days after your session.
What to work on first.
Four findings, in priority order.Invoice follow-upsStart here
- What’s happening
- A team member checks outstanding invoices, sends reminders, and matches payments by hand.
- What to try first
- Check payment data and agree the reminder rules.
- What needs a person
- The owner approves reminder wording and timing. Disputed invoices always go to a person.
- Proposed change
- Connect the approved invoice list to a reminder schedule. Stop reminders as soon as a payment is recorded. Route disputes and unclear payments to the owner.
- Expected benefit
- Less routine chasing; a clear view of exceptions.
- Build effort
- Low–medium
- Risk to check
- Outdated payment records could trigger an incorrect reminder.
- How to test it
- Trial on a small, approved invoice set. Check that paid and disputed invoices never receive a reminder.
Customer enquiriesNext
- What’s happening
- New requests arrive through several channels. Details are missing and follow-ups depend on someone remembering.
- What to try first
- Agree one queue, an owner, and what needs approval.
- What needs a person
- Your team sets the price and approves the quote. Unusual requests are flagged for review.
- Proposed change
- Bring requests into a shared queue, collect the missing details, and assign the next action. Give the team a clear view of unanswered enquiries.
- Expected benefit
- Fewer missed handovers and unanswered requests.
- Build effort
- Medium
- Risk to check
- An unapproved price or quote could reach a customer.
- How to test it
- Run sample enquiries through every entry point. Confirm each gets an owner and that no quote is sent without approval.
Weekly reportingAfter source checks
- What’s happening
- The owner copies figures from different tools into a weekly spreadsheet.
- What to try first
- Agree the measures and verify each source.
- What needs a person
- The owner agrees the definitions and reviews exceptions before relying on the report.
- Proposed change
- Agree the useful measures, pull them into one report, and show the source and date for each number. Flag missing or stale data.
- Expected benefit
- Less copying and a consistent weekly view.
- Build effort
- Medium
- Risk to check
- Missing or stale figures could look like reliable results.
- How to test it
- Compare the first reports with a manual calculation. A missing source must be visible rather than silently treated as zero.
Hiring and supplier disputesKeep human
- What’s happening
- These conversations depend on relationships, context, and judgment.
- What to try first
- Keep decisions with the team; review admin separately.
- What needs a person
- People retain responsibility for hiring decisions, negotiation, and disputed terms.
- Proposed change
- Keep decisions and conversations with the team. Simplify scheduling and make supporting information easier to find.
- Expected benefit
- Keep judgment with the people who know the context.
- Build effort
- Not a build priority
- Risk to check
- A decision could be made without the relationship or context it needs.
- How to test it
- Confirm that the workflow only assists with administration and cannot make or communicate a decision on its own.
First step
Check payment data and agree the reminder rules.Sample findings. Select a row to expand it here.
How it works.
One session with your team, then analysis on our side. The next step is clear throughout.
- 01Start here
Tell us what’s getting stuck
Tell us about the problem. We’ll confirm whether the audit fits and agree the details before you commit.
- 0290 minutes
Walk through the work
Bring a decision-maker, someone close to the work, and recent examples. We trace recurring jobs together.
- 03Our side
Review and rank
We review the findings, check assumptions, and weigh the changes by benefit, effort, readiness, and risk.
- 04Within 2 business days
Receive your plan
Get the findings, priorities, and first workflow plan. You decide what to act on; any build is a separate choice.
A clear scope.
The fixed fee covers the audit and your plan. Implementation is a separate project, agreed only if you choose to continue.
Included in the $1,500 fee
- One 90-minute working session
- Review of recurring work across the business
- A closer look at one priority workflow
- Written findings and ranked recommendations
- Risk, readiness, and human-approval points
- Your plan within two business days after the session
Quoted separately
- Building workflows and integrations
- Tool migrations and software subscriptions
- Ongoing operation, maintenance, and support
- Website design and development
No obligation to continue. Your plan is yours to keep, share with your team, or use with another provider.
A good fit when the same work keeps coming back.
Information is chased, copied, or checked across people and tools. You can see the effort, but need help choosing what to change first. A decision-maker and someone who knows the work should attend.