What does an operations audit cost?
Short answer: anywhere from four figures to six, depending on scope and who you ask, and the price tag tells you less than what is behind it. This guide covers what drives the cost, what a real audit must include, and the questions that separate a diagnostic from a dressed-up sales pitch. Our own number is on the page, because hiding it would fail our own test.
What drives the price
- Scope. One workflow (say, inquiry-to-booked-work) costs a fraction of an end-to-end assessment of a whole operation. Narrow scope is not a weakness; it is usually where the money is.
- Depth of access. An audit built from interviews alone is cheaper and weaker than one that watches the real workflow run: the inbox, the phone logs, the handoffs, the queue times.
- Who does the work. Large consultancies carry large overhead. Boutique operators price lower and are often closer to the work. Neither is automatically better; the deliverable is what matters.
- What happens after. Some audits exist to sell the next engagement. That inflates scope and softens findings. An audit priced to stand alone can afford to be honest.
What a real audit must include
Whatever you pay, the deliverable should contain three things. A map of the workflow as it actually runs, not the org-chart version: where inquiries enter, where they wait, who touches them, where they die. A prioritized leak list: the specific failures, each weighed against your revenue numbers, ordered by what they cost you. And a concrete first fix: what to change, in what order, and what should stay manual.
If the deliverable is a maturity scorecard, a benchmark deck, or a list of software to buy, you did not get an audit. You got a brochure with your logo on it.
Our pricing, for reference
Stahl Automation audits start at $1,500 for one revenue-critical workflow, with a fixed quote in writing after a short scoping call. Larger, multi-site, or compliance-bound scopes are quoted individually. The fee is fully credited toward your first implementation sprint when booked within 30 days, and it is backed by a straight-answer guarantee: if we do not find leaks worth multiples of the fee, we tell you that in writing and you keep the roadmap.
Full engagement mechanics are on the pricing page.
Questions to ask anyone selling you an audit
- "What exactly do I hold in my hands at the end?" Vague answers here predict vague deliverables.
- "What happens if you find nothing worth fixing?" The only good answer is a written one.
- "Is the fee credited if we continue?" Crediting the audit against implementation aligns the incentives.
- "Will you tell me if the fix is process, not software?" Anyone who always recommends their own tool is selling the tool.
- "Who actually does the work?" The person who scopes it should be the person who shows up.
Common questions
What does an operations audit typically cost?
It varies enormously with scope and firm size, from four figures for a focused single-workflow diagnostic at a boutique firm to six figures for enterprise-wide assessments at large consultancies. Our own audits start at $1,500 for one revenue-critical workflow, with a fixed quote before anything begins.
What should an operations audit include?
At minimum: a map of the actual workflow as it runs today, a prioritized list of the failures with their estimated business impact, and a concrete recommendation for what to fix first. If the deliverable is a generic maturity scorecard with no specific fixes, you bought a sales document.
How do I know an audit will not just be a sales pitch for a bigger project?
Ask what happens if the audit finds nothing worth a bigger project, and get the answer in writing. Any credible auditor should be willing to tell you your operation is fine, point you to a cheaper path, and let the roadmap stand on its own.
Want your number instead of a range?
The scoping call is short and free, and it ends with a fixed quote in writing. Whether you take it is up to you.