Process Mapping Consultant for the Current State You Haven’t Written Down
Fixed-scope current-state mapping of order-to-cash, procure-to-pay or record-to-report, staffed with contract business analysts and process consultants.
A process mapping consultant documents how your work actually runs today, step by step, before you change the system that runs it. KORE1 staffs contract business analysts and process consultants for fixed-scope current-state mapping of order-to-cash, procure-to-pay and record-to-report.
Last updated: October 7, 2026
- This page
- Writing down the current state, counting the hand-offs and the waiting, and staffing the people who do it.
- Covered elsewhere
- Choosing the platform is mid-market ERP selection advisory. Grading the proposals is vendor selection and RFP advisory. Moving the records is ERP data migration staffing. Building the automation is Power Automate consultant staffing.
Nearly every ERP project we staff has the same gap at the start. Somebody can describe the process in a meeting. Nobody can hand you the document. So the requirements list gets written from memory, the demo gets scored against that list, and the gaps turn up in week six of the build as change orders. Every time.
A map is cheap. The thing it prevents is not. Ask anyone two quarters into a bad build.
Our project staffing desk, part of KORE1’s IT staffing services, puts contract analysts on this work for the four to six weeks it runs. They’re on our W-2 through contract staffing, they sit with your people, and what they leave behind belongs to you. All of it.
What a Current-State Map Actually Records
A flowchart of boxes is not a current-state map. Anyone can draw boxes in an afternoon. Pretty, too. The findings live in the five things most people skip.
- Who touches it, and in what orderNot departments. Named roles. A requisition that crosses from operations to purchasing to finance and back again has crossed three boundaries. Every boundary is a place where it can stop.
- Touch time against elapsed timeHow many minutes of actual work, against how many calendar days from first keystroke to posted entry. These two numbers are almost never close. Not once, in our experience. The gap between them is the whole reason anyone funds the project.
- Every exception pathThe happy path is the easy half. What happens on a partial shipment, a price variance, a credit hold, a rejected approval. Ask five people and you will get five answers. That is the finding.
- The spreadsheets nobody mentionsWorkbooks that sit between two systems and reconcile them by hand. They almost never appear in a requirements document. They almost always appear in week six of a build, because somebody finally asks where a number came from.
- What the controls areWho can approve what, to what limit, and whether the system enforces it or a person remembers to. Auditors ask. The map answers. Nothing else does.
Notation matters less than people think. Most of our analysts draw in BPMN, the Object Management Group notation whose current version, 2.0.2, was adopted in January 2014 and has not changed since. A swimlane diagram in Visio or Lucid is fine. A photographed wall of paper is fine too, as long as somebody transcribes it the same week. Nobody ever does.
What is not fine is a map with no numbers on it. A picture of a process tells you the order of operations. That part is cheap. It does not tell you where the fourteen days went.
One Requisition, Five Desks, Nineteen Days
This is what a current-state map of procure-to-pay looks like once the clock goes on it. A solid mark is someone actually working. A hollow one is the requisition sitting in a queue. The garnet edge is a hand-off, the moment work changes owner.
- Solid, someone is working on it
- Hollow, it is sitting in a queue
- Garnet edge, work changed owner
- Orange, the longest single wait
- 7
- hand-offs, each one a place the requisition can stop
- 2 hr 23 min
- touch time, every keystroke by every person added up
- 19 days
- elapsed time, from first keystroke to posted entry
- 6.3 days
- the longest single wait, and it is one approval
Two hours and twenty-three minutes of work. Nineteen days. Read that twice.
Read it once and the requirements list mostly writes itself. The expensive problems have stopped being opinions and turned into quantities you can rank. One approval is sitting on a third of the elapsed time. And a missing general ledger code sent the whole thing backwards, over a boundary it had already crossed once. Nobody describes that loop in a meeting. To the people living it, that is just Tuesday.
Now price the two fixes. Default the GL code at the point of entry and the rejection loop disappears, which is a configuration setting. Put a dollar threshold and a delegate on the approval and the 6.3 days collapses, which is also a configuration setting. Neither one needs a new ERP. Not one.
That is the uncomfortable half of this work. Some of what a map finds does not justify the platform you were about to buy, and the rest of it finally tells you what to ask the platform for. Both answers are worth more than the fee. Easily. And the second one is what feeds a selection advisory something firmer than a wish list.
A Consulting Firm, Your Own People, or a Staffed Mapping Crew
The deliverable is roughly the same document. What differs is who owns it afterwards, and who is available to answer questions about it in month nine.
Consulting firm
Your own team
KORE1 contract crew
Who does the interviews
FirmA team the firm assigns and can rotate mid-engagement.
In-housePeople who already know the process, and already have a day job.
KORE1 crewNamed analysts you interviewed, for the weeks it runs.
What it costs
FirmA fixed fee per phase, usually with a change order clause.
In-houseNothing on the invoice. Whatever those people were going to do instead.
KORE1 crewHourly per analyst, on a KORE1 W-2.
Candour of the answers
FirmHigh. An outsider gets told things a manager never hears.
In-houseLower. Nobody describes their own workaround to their own director.
KORE1 crewHigh, for the same reason, and the analyst has no software to sell you.
When the scope grows
FirmA change order, priced by the firm.
In-houseIt stops. The quarter close always wins.
KORE1 crewAdd an analyst for the heavy weeks, drop the seat after.
Who owns the document
FirmYou do, in whatever format and tool the firm uses.
In-houseYou do, and the knowledge stays in the building.
KORE1 crewYou do, in your tools, built to your template.
Afterwards
FirmGone, unless you buy the implementation too.
In-houseStill here, back on the day job.
KORE1 crewKeep one analyst on the build, or hire them outright.
The in-house column is better than it looks. Much better. A controller who has run the close for nine years knows things no analyst will surface in three interviews.
What in-house mapping almost never survives is the calendar. Two of the last four mid-market mapping efforts we were brought into had already been attempted internally, stalled at a quarter close, and restarted from nothing eight months later, which is how a document that should have cost a few weeks of contract hours ends up costing two internal attempts and the ERP change orders it was supposed to prevent. If you want the knowledge to stay in the building, the cheapest version is usually a contract analyst holding the pen and your own people in the room, which is also roughly how ERP staff augmentation gets bought for every other phase.
$44,110
a real fixed-fee discovery phase, 182 hours, on a mid-market ERP integration
14%
of that program’s cost, spent before a line was built
$101,860
median salary for management analysts, May 2025
17 days
KORE1’s average time to hire for IT roles
Discovery figures are Foretopia delivery benchmarks from a 2026 integration proposal for a regulated manufacturer, shared with KORE1 by Colin Boothe, CIO at Foretopia. Full program midpoint was $312,530 at a $215 blended hourly rate. Salary from the BLS Occupational Outlook Handbook, which also projects 10 percent growth for the occupation from 2025 to 2035. Hiring figure from Why KORE1.
Who Actually Holds the Pen
Two seats cover most mid-market engagements. A third shows up when the scope crosses more than one ledger. Sometimes a fourth.
- Business analystRuns the interviews, draws the swimlanes, chases the exception paths and writes the thing down. The best ones are unbearably literal. Relentless. They will ask what happens on a partial receipt until somebody admits nobody knows.
- Process consultantBrings the shape of a working process to compare yours against, and knows which findings are worth fixing before a migration and which are noise. Usually the one who sets the touch-time measurement so the numbers mean something.
- A functional specialist, sometimesA revenue or AP subject expert when the scope is one deep process rather than several shallow ones. On regulated work, somebody who has written a validation plan before.
- A facilitator, on the hard onesTwo departments that disagree about who owns a step will not resolve it in a workshop run by one of them. Rare. Worth it when you need it. Ask us.
Screening for this is less about tools than it sounds. Visio, Lucid and BPMN notation are a week of ramp for anyone competent. What we push on in the interview is whether the analyst can describe an exception path they found that nobody had told them about, and what it cost to find it. The ones who can tell that story have done the work. The ones who talk about templates have delivered somebody else’s. We pass on those.
The title drifts, too. Business analyst staffing and process consulting overlap almost completely at this scale, and we fill the seat from the same bench either way. If the engagement grows into running the project, that is a different search, covered on ERP implementation project manager staffing.
How a Fixed-Scope Mapping Engagement Runs
Four to six weeks for one process family. The order is not negotiable, because step five is worthless without step three.
- Agree the boundary in writingWhere does it start, where does it stop. One sentence each, written down. Order-to-cash runs customer order to cash applied, procure-to-pay runs requisition to a payment clearing the bank. Sounds obvious. It stops being obvious the moment somebody wants quoting folded into the first one and vendor onboarding into the second, and that is an argument worth having now rather than in week three with three interviews already booked.
- Interview the people who do the workNot the managers describing it. The clerk who keys it. Her, specifically. Two or three people per step, separately, because the disagreements between them are data.
- Draw it, then put the clock on itSwimlanes by role, every hand-off marked, and a duration against every step and every wait. A map with no durations cannot be prioritised. It will not get funded either.
- Walk it back to the roomRead the draft out to the same people and let them correct it. Something will be wrong. Always is. Better now than in a requirements document.
- Mark what is broken and what is just undocumentedSeparate the steps that are genuinely defects from the steps that work fine and simply were never written down, because conflating those two is how a mapping exercise turns into a forty-item wish list that no CFO will fund and no project manager can sequence.
- Hand over a document and a short listThe maps, the measurements, the exception paths, the spreadsheet inventory, and a ranked list of findings with a named owner and a rough effort against each one, so the list can go straight into a requirements document or a project plan without being rewritten first. In your file store, in your format, not in a consultant’s portal. That matters in month nine.
Nobody should be mapping everything. Ever. A full process inventory is a different and much larger exercise, and the APQC Process Classification Framework gives a sense of the scale: version 7.4 of the cross-industry model sorts a company into 13 enterprise-level categories and more than a thousand processes and activities. Pick one family. Finish it. Then pick the next.
If the findings turn into build work, that is capacity bought by the month or a full ERP program team, and the handover matters enough that we treat it as its own step, the same way our knowledge transfer and exit planning does when any contractor rolls off.
Order-to-Cash, Procure-to-Pay, Record-to-Report
These three carry most of what an ERP touches, and most of what goes wrong when it lands. Scope one per engagement. Just one.
Order-to-cash. Customer order through fulfilment, invoice, collection and cash application. The common finding is pricing. Quotes approved in one system, orders keyed in another, and a discount that somebody honours by hand because a customer called about it in 2023. It is also where a data migration hurts most, because open orders, partial shipments and unapplied cash all have to cross the cutover intact, and the current-state map is what tells the migration team which of those states actually exist in your data rather than which ones the manual says should.
Procure-to-pay. Requisition through purchase order, receipt, invoice, three-way match and payment. Five systems, usually. Approvals and receiving are where the days go, as the diagram above shows. Usually the shortest engagement of the three, and usually the one with the quickest configuration wins sitting in it, because approval thresholds, delegate rules and default coding are settings in every platform we staff rather than development work, which means the findings can often be actioned before the mapping engagement has even closed out.
Record-to-report. Transactions through reconciliation, consolidation, close and reporting. Map this one if the close takes longer than it should. Expect the spreadsheet inventory to be the headline. On multi-entity closes the finding is often intercompany, which is its own conversation and one our accounting and finance desk has regularly.
Mapping more than one at a time is possible and rarely a good idea. The interviews compete for the same controller. She has a day job. Several, probably.
One Analyst, a Small Crew, a Fixed Scope, or Keep Them
Same recruiters, different paperwork. Pick by how firm the boundary is, because a fixed price on a scope nobody has drawn yet is a guess you end up paying for twice. Whichever route you take, 92% of the people we place are still in the seat twelve months later.
One seat
A single analyst
One contract business analyst holds the pen for four to six weeks on one process family.
Contract staffingSmall crew
An analyst and a consultant
Two or three people when the scope spans several departments or more than one ledger.
Project staffingFixed scope
Deliverables on a SOW
Once the boundary is written down, pay against named documents instead of hours.
SOW staffingKeep them
Contract, then hire
The analyst who mapped your close is often the best internal hire you will make that year.
Contract-to-hire
Common Questions
What does a process mapping consultant actually do?
A process mapping consultant interviews the people who do the work, draws how a process really runs today as swimlanes by role, and puts a duration against every step and every wait. The drawing is the easy half. Finding the exception paths nobody mentions is the job.
How long does current-state process mapping take?
Four to six weeks for one process family, with a contract analyst on it most days. For comparison, a 2026 fixed-fee discovery phase on a mid-market ERP integration ran 182 hours over four to five weeks. Scope creeps when the boundary was never written down. Write it down.
Do we really need this before an ERP selection?
You need it before the requirements list, which comes before the selection. Without a current-state document, requirements get written from memory and the gaps surface as change orders in the build. That discovery phase was 14 percent of the program cost and it protected the other 86. Cheap insurance.
Can our own team map our own processes?
They can, and they know things an outsider never will. Two obstacles are reliable. Internal efforts stall at the first quarter close. And nobody describes their own workaround honestly to their own director. Nobody.
What does process mapping cost?
Price it as weeks of a contract analyst, not as a product. One analyst for four to six weeks is the usual shape, and the BLS puts the median salary for management analysts at $101,860 as of May 2025, which is the right anchor for an hourly contract rate once you add the employer burden we carry on a W-2 and the fact that a mapping analyst is billing against a fixed, short scope rather than an open-ended seat. A crew of two or three costs proportionally more and finishes sooner. Your call.
Which notation should the maps use?
Whichever one your people will reopen in a year. BPMN 2.0.2 is the formal standard and has not changed since January 2014, so analysts are easy to find for it, but a clean Visio or Lucid swimlane is fine. The non-negotiable is durations on the map, not the notation. Never the notation.
Should we map the future state at the same time?
Not in the same engagement, and not with the same hours. Future-state design run alongside current-state mapping turns into a wish list, because the room starts solving problems before it has agreed what they are. Finish the current state, then design against findings. In that order.
Name the First Step and the Last
Tell us which process family you want mapped, where it starts, where it ends, and roughly how many people touch it. Say what the map is for, a selection, a migration or an automation build. You’ll hear back from a KORE1 recruiter with seats, rates and analysts to interview.
Scope a Mapping Engagement →Or call 949-706-6990
