When does an audit make sense?
When there are several possible workflows, uncertainty about data availability, quality or access, or a need to align management, the process owner and IT around one initial use case.
What we examine
- Current workflow, roles and bottlenecks
- Inputs, data sources and system boundaries
- Actions and human approvals
- Technical complexity and operational risks
- Expected type of value and measurement method
- Dependencies, scope and next decision
What you receive
Deliverable
Workflow map
Current steps, responsibilities, handovers and points of failure.
Deliverable
Prioritised list of use cases
Use cases ranked by value, complexity, data readiness and risk.
Deliverable
Solution outline
A proposal for an app, agent, integration, conventional automation or a combination.
Deliverable
Basis for a pilot
Scope, testing, acceptance criteria, approvals and open questions.
From audit to pilot
An audit is not an automatic order for implementation. After the review, the client decides whether a use case should be stopped, clarified further or advanced to a proof of concept.
Participants and inputs
An audit does not require a large project, but it does require the right people: a process owner who knows the workflow in practice, a decision-maker who can prioritise, and, for workflows involving several or business-critical systems, someone with knowledge of IT and access rights.
The inputs are equally practical: examples of the task (preferably anonymised), the systems and documents involved, known failure scenarios and an overview of where time is currently spent. If no documentation exists, we map the process together in the workshop.
How a use case is prioritised
Candidates are assessed across four dimensions: expected value (time, quality, risk or throughput), complexity (rules versus interpretation), data readiness (whether the necessary data exists and may be used) and operational risk (what happens when the solution is wrong).
The best first use case is rarely the largest. It is the one where value is measurable, the data is available, and the consequences of errors can be managed through drafts or approvals.
What the audit is not
The audit is not implementation, and it does not change your systems. Nor is it a generic AI strategy report: the outcome is specific enough to support the next decision, but it does not promise results that have not been tested.
Factors that may stop or change a use case are documented openly: insufficient data quality, lack of access to sources, unresolved GDPR matters, a process that is genuinely unclear, or a benefit that does not justify the operating cost. It is less expensive to identify these issues during an audit than during implementation.
Price
Indicative price levels, also shown on the home page: Automation Audit Mini DKK 12,500–20,000 (1–2 workshops, process map, 3 prioritised use cases and a high-level ROI estimate) and Automation Audit Pro DKK 25,000–45,000 (roadmap, business case and technical solution outline as a basis for a PoC or implementation). All amounts exclude VAT. The final scope and quotation are agreed separately.
Common questions
Does the audit change our systems?+
No. The audit provides analysis and a basis for decisions. Any system changes require a separately approved scope.
Is AI always the outcome?+
No. The right solution may be conventional automation, integration, process change, AI or a combination.
How much does an audit cost?+
Indicative price levels are shown on the home page. The final scope and quotation are agreed separately.