--- title: What an Automation Audit Looks Like url: https://varstatt.com/jurij/p/what-an-automation-audit-looks-like author: Jurij Tokarski date: 2026-04-21 description: Workflow automation service review in one week. Map internal portals, admin panels, and n8n / Make workflows — what you have, what's broken, what to consolidate. section: Blog (https://varstatt.com/jurij/archive) tags: retainer-shapes (https://varstatt.com/jurij/c/retainer-shapes) --- An automation audit is one week, $997, fixed deliverable: review every internal tool and workflow, trace each end-to-end, hand back a prioritized plan. Fix, consolidate, automate, semi-automate, or remove. One week is all it takes to surface what's actually going on. The hard part isn't the audit — it's accepting what it finds. ## Most Automation Doesn't Pay Off Most businesses think about automation as a binary: this process is either automated or it isn't. The "automate everything" crowd pushes for the first state — every step end-to-end, no humans in the loop. The "we'll just keep doing it manually" crowd defends the second. Both are usually wrong. The honest answer most teams don't want to hear: a meaningful share of the automations I find should be deleted, not optimized. Workflows that fire correctly but produce output nobody reads. Sync jobs between systems that no longer need to be in sync. Notification triggers from a tool the team stopped using eight months ago. Automation isn't free — it has maintenance cost, surface area for breakage, and cognitive overhead for whoever inherits it. The other thing most teams underrate: the **semi-automated, human-in-the-loop** approach. Solve 80% of the problem with a workflow that does the boring parts — collect, normalise, format, draft. Leave the last 20% — the part that needs judgment or exception handling — to a human who reviews and approves. You get most of the speed gain, almost none of the failure modes, and a system that degrades gracefully when something upstream changes. People skip this option because it doesn't sound impressive. "Half-automated" feels like a half-measure. It isn't. Full automation is the right call when work is genuinely high-volume, low-judgment, and well-defined. Most internal processes don't qualify on all three. The audit doesn't optimize for "automate more." It optimizes for the right shape per workflow: full automation where it earns its keep, human-in-the-loop where judgment matters, manual where volume doesn't justify maintenance, and deletion where nothing of value would be lost. ## The Tool That Became Infrastructure Most businesses have one. An **admin panel built three years ago** as a stopgap that now runs half of operations. An internal portal nobody updates that still generates the reports the team relies on. A cron job added to paper over a data sync issue that never got properly fixed. These don't feel like technical debt when they're working. They feel like the job — until the person who knows them leaves, or a vendor changes an API, or you want to add a workflow and discover you can't without touching something fragile. The [cost of not addressing it](/principles/philosophy/business-cost) compounds quietly until it doesn't. ## What the Audit Covers Every internal portal and tool gets reviewed: maintenance burden, training overhead, data integrity, opportunity cost of consolidation. The **workflow automation layer** gets the same treatment. n8n workflows, Make scenarios, Zapier automations already in place, scheduled processes and cron jobs. Error rates, redundant triggers, data flow integrity. Most businesses running a workflow automation service for more than a year have accumulated sequences that overlap, fire in the wrong order, or silently fail without alerting anyone. This is the layer an n8n workflow review or Make.com consultant engagement usually starts with — mapping what actually exists before recommending what to change. Rebuild work, when the audit finds it's needed, happens in n8n or Make — not Zapier. The [crontab tool](/toolkit/crontab) is useful for sanity-checking schedule expressions during the review. ## What You Get A prioritized plan — each item tagged as fix, consolidate, automate, semi-automate, or remove. Every item includes effort estimate and expected impact. In most audits, "remove" and "semi-automate" together account for more items than "automate." That's what an honest review tends to find. [Consolidation](/principles/philosophy/consolidation) is the underlying principle — fewer, better tools instead of more layered on top of each other. The plan is ordered by impact. You leave with a clear picture of what to do now, what can wait, and what to stop paying for. The audit is the plan, not the implementation. Execution is a separate engagement, scoped based on what surfaces. The [simple request that uncovered something bigger](/jurij/p/simple-e-commerce-request-uncovered) is a common pattern the audit is designed to surface before it becomes an expensive surprise. ## Who Needs This Businesses with internal portals built by previous developers, where the original developer is gone and nobody's confident about what the system does. Operations teams where manual processes persist despite existing tooling. Companies considering new back-office investment but unsure what they already have. If your internal tooling feels harder to understand than it should, or automation has grown without anyone keeping track, [submit a project brief](/brief).