Skip to main content

Services / CraftDuka

Business automation audit with a prioritised scorecard

Compare automation opportunities by effort, data readiness and consequence of failure. The audit produces a scoped shortlist rather than a list of tools to buy.

Who this suits

Business owners deciding which manual process to improve first.

When a simpler option is a better fit

An audit adds little if one well-defined bottleneck already has clean data and an agreed solution; scope that pilot directly.

Implementation approach

  1. Observe the current process with its operators

  2. Score candidate tasks using evidence from actual work

  3. Prepare a ranked report with dependencies and a recommended pilot

Illustrative operating rules

An original audit scorecard and a prioritised opportunity report example

Illustrative design example. Adapt these rules with the responsible team before implementation.

Business automation audit with a prioritised scorecard: decisions and ownership
Record or decisionIllustrative ruleAccountable owner
RepetitionScore 0–3 from observed frequency, not assumed time savingsProcess owner
ReadinessScore 0–3 for accessible structured inputs and clear rulesTechnical reviewer
Failure impactDescribe reversible errors versus consequential decisionsBusiness sponsor

Dependencies and access

  • Access to process operators
  • Redacted examples and observed handling times
  • Named owners of the systems involved

Limits and exceptions

Illustrative report: route website enquiries first because inputs are already structured; defer invoice matching until references are cleaned; keep discount approval manual. Scores inform discussion and are not financial forecasts.

Scope and cost drivers

Audit effort depends on process count, stakeholder access and system visibility. Implementation and subscriptions are quoted separately from discovery.

Acceptance and measurement

An accepted audit identifies a baseline, pilot boundary, owner, risk and testable outcome for each recommended opportunity.

Questions before starting

What must be ready before implementation?

Access to process operators; Redacted examples and observed handling times; Named owners of the systems involved.

Discuss the scope and availability

Tell CraftDuka about the task, your current systems and the people who will use it. Our team is based in Nairobi and serves Kenya and East Africa. We will assess the fit and availability before agreeing a project.

Privacy policy