Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Business Process Automation 5 min read

Business process mapping: what it costs to do properly

Build a process mapping budget from the decision, the process scope, workshop hours, validation and the documentation you need at handover.

E
EncryptTechBD · 0 comments
Laptop and office supplies on a clean desk
Photo: Olu Eletu / StockSnap

Process mapping is one of the few purchases where the deliverable can look impressive and still be useless. A wall of coloured boxes may win the workshop and answer nothing. The cost is driven less by the number of diagrams than by the decision the map must support, the number of people who have to agree, and how much of the real exception handling you are willing to expose.

This guide is for a Bangladeshi business owner or operations manager who has been quoted a per-day or per-diagram rate and wants to know what the number should include. It builds the budget from work and outputs, not from a market price. It is the costing companion to the comparison of process mapping methods.

Name the decision before you buy the map

Maps are commissioned for different reasons, and each requires a different level of precision. An automation decision needs systems, data, rules and exceptions. An audit or quality decision needs controls, owners and evidence. A training decision needs a clear sequence and a usable SOP. A software purchase needs requirements and integration points. A reorganisation needs handoffs and decision rights.

Write the decision in one sentence and the person who will make it. If the sentence is “we need to document everything”, the scope is unbounded and the quote will be either inflated or incomplete.

What drives the effort

  • Number of processes and locations. One order-to-cash process in one office is different from the same process across three branches with local workarounds.
  • Cross-functional handoffs. Every handoff adds an owner, a queue and a failure mode to validate.
  • Exception density. Returns, partial payments, credit terms and manual approvals take longer to map than the happy path.
  • Participant seniority and availability. Workshops with six busy people cost more in calendar time than in facilitation hours.
  • Evidence quality. Existing SOPs, system exports and a sample transaction reduce discovery time. Missing records increase interviews.
  • Notation and tooling. A SIPOC is faster than BPMN with error events and message flows. The tool should follow the decision, not lead it.
  • Language and review rounds. Bangla workshops with English documentation add translation and terminology review.

Six cost lines to price separately

1. Process inventory and scoping. A list of processes, owners, start and end triggers, and the decision each map supports. This line prevents the workshop from mapping the wrong boundary.

2. Facilitation and workshops. Preparation, room or call logistics, facilitation and a decision log. Ask how many sessions are included and what happens when a key person is absent.

3. Current-state mapping. The steps, roles, systems, inputs, outputs, exceptions and controls. This is where most of the interviewing happens.

4. Validation with the people who do the work. A map signed off only by managers is a management theory. Validation catches the workaround that the process owner did not know about.

5. Future-state design and requirements. Only where the decision requires change. Include rules, data, integration points and acceptance criteria, not just prettier boxes.

6. Documentation, training and handover. SOPs, RACI, measures, version control and a session with the team that will maintain the map.

A formula for the estimate

Estimate hours in four buckets, then multiply by the role rates you already pay. Use a sample process to calibrate rather than guessing from a template.

workshop hours = processes × sessions per process × session length

participant hours = workshop hours × average attendees

validation hours = interviews × interview length

mapping hours = processes × complexity factor × hours per process

Use a complexity factor you can explain: one for a simple single-team process, two for a cross-functional process with exceptions, three for a regulated or multi-branch process with controls. The factor is a planning convention, not a benchmark. Then add documentation, project management and a contingency for additional validation rounds.

Budget worksheet

Use one row per line with unit, quantity, rate source, one-off cost, monthly cost (for tooling), owner and evidence. Keep internal time visible: workshop attendance, interviews, document review and sign-off are real costs even when no invoice arrives.

Add a stop rule to the worksheet. For example: “If the process inventory exceeds twelve processes, the remaining processes move to a second phase.” A stop rule protects both sides from a scope that grows every time someone remembers another exception.

How to keep scope under control

Define the start and end trigger in operational language. “Order received” and “cash reconciled” are boundaries; “sales” and “finance” are departments. Map five to seven steps at the first level, then go deeper only where the decision needs detail. Put unrelated issues in a parking lot with an owner, and keep a decision log that records what was agreed and what was deferred.

Walk one real transaction through the map with the person who processed it. This is the cheapest validation available and it exposes missing systems, approvals and rework faster than another workshop.

What good handover looks like

At the end, you should hold a process owner, a trigger, inputs and outputs, systems touched, exceptions, controls, measures and a version history. For automation, add data fields, rules, integration points and acceptance criteria. For training, add an SOP that a new employee can follow without calling the consultant. The map is not the asset; the shared understanding and the maintained document are.

Our business automation team maps processes only as far as the next decision requires, then builds the workflow or requirements from that evidence. The pricing page explains how discovery, design and implementation are separated, so you can stop after the map if that is the right call.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes