>
Voice of Volge is a series of books, and the firm's thought leadership on the solutions and the domains Volge specialises in. Each edition takes one of them and sets out what the technology makes possible, what it makes mandatory, and what an operator has to put in place before either is true of them.
Automate the work, not the flowchart. Most organisations automate processes they have never truly seen. Map the designed process, mine the real one, and the gap between them is the finding.
Figures carry their basis and their date. Where published estimates disagree, the range is given and the basis named rather than averaged away, and where a widely quoted number does not survive checking it is corrected here rather than repeated. Every chart plots a figure stated in the text, and nothing is projected beyond what a named source projects.
Every automation programme begins with the same optimism and ends with the same surprise. The optimism is that software, and now AI, will take work off people’s hands. The surprise is how little the organisation actually knew about the work it was automating. A process is not what the policy document describes, nor what the process owner remembers; it is what the event logs record, and the three rarely agree.
The cost of that gap is not abstract. Automate a broken process and you industrialise the breakage, faster and at scale, with an audit trail that now proves you did it on purpose. A large share of digitisation budgets goes exactly this way, encoding the current mess rather than the intended design. The least glamorous step in the whole programme, seeing the real process before touching it, is also the one that decides whether the rest pays back.
This report is not a tools catalogue. It is an argument about sequence. Understand the work, then build on it. We set out why process visibility is the precondition for everything that follows, what ‘high definition’ means when the evidence is event logs rather than opinion, and how to read the distance between the process you designed and the one you actually run. The figures are sourced and dated; the examples are the ordinary kind, not the demo kind.
Where a specific platform earns a mention, here, Nintex’s process tooling, it is to make the argument concrete, not because the argument depends on it. Volge is a Nintex delivery partner, and says so plainly. The claim stands on its own. See the work in high definition, then automate.
The Voice of Volge desk
Nintex is a process-and-automation software company. What began as SharePoint-era workflow is now a single platform that documents how work runs and automates it, and, since 2025, orchestrates AI agents against it. It was built out over two decades and a handful of pointed acquisitions.
The recent chapters matter most to a buyer today: Agentic Business Orchestration (September 2025), locally-hosted AI in
Automation K2 5.9.1 (April 2026), Agent Designer and Nintex Orchestration now shipping inside the Nintex CE Platform, and Nintex Processes, launched on 26 October 2026. Nintex Process Discovery was placed end-of-life on 4 May 2026.
2025–26
Source: Nintex corporate and product materials, 2006–2026. Nintex is majority-held by TPG Capital (2021), with Thoma Bravo a minority holder. Ratings are G2 4.2/5 and TrustRadius 8/10, read November 2026.
This report covers the Understand layer, where Nintex documents how work is meant to run and supplies the evidence to test that against how it actually runs.
| Understand Focus of this report | Process Manager · Nintex Processes · Process Capture |
|---|---|
| Build & run | Automation CE · Automation K2 (on-prem) · RPA · DocGen · Forms · eSign |
| Orchestrate | Agentic Business Orchestration · Agent Designer · Nintex Orchestration |
Source: Nintex company page, September 2026; G2 and TrustRadius, read November 2026; Forrester Wave, Q3 2026.
This is not a young product. It is a two-decade platform that has just added governed AI and a locally-hosted engine, mature where it must be, current where it counts, and now built to orchestrate agents at scale.
Every large organisation runs two versions of every process, and only one of them is written down. There is the process as
designed, the flowchart in the quality manual, the swimlane in the onboarding deck, the story the head of operations tells the board. And there is the process as performed, with its reworked approvals and its shadow spreadsheet, and the exception that quietly became the rule. Automation and AI both act on the first. Value hides in the second.
Before the platform, before the agent, before the budget: an honest account of how the work actually runs. Seeing it is the first deliverable, and everything else depends on it.
The process in the manual and the process that actually happens are rarely the same document. The distance between them is the subject of this book.
This matters now because the tools have outrun the understanding. An organisation can buy an AI agent, a robotic process automation licence, and a workflow engine in an afternoon. What it cannot buy in an afternoon is an honest account of how its own work actually moves, which step waits three days for a signature, which invoice route the finance team abandoned in 2021, which "standard" procedure has eleven live variants across four regions.
Point automation at the designed map and you automate a fiction. The bot handles the happy path and falls over on the exceptions that make up most of the real volume. Point an AI agent at the same fiction and the failure is quieter and more expensive. The agent acts confidently on a process that no longer exists, and no one notices until the numbers drift.
The intelligent-process-automation market is priced as if this problem were already solved. Market.us estimates the category at roughly 16.81 billion US dollars in 2024, with a projected 61.23 billion by 2034 at a compound annual growth rate of 13.8 per cent (Market.us estimate, September 2025 edition). Firms are spending. The question this book asks is narrower and more useful. Are they spending against reality, or against the map?
Volge is a Nintex delivery partner and benefits if a client buys, and that commercial interest is marked wherever it appears in this book. The argument itself does not depend on it. You
need the map, you need the mine, and you need the discipline to work the difference between them.
Nintex answers half of that question directly, and the other half has just changed shape. Nintex Process Manager holds the process as designed, the map, and since 26 October 2026 it surfaces as Nintex Processes inside the Nintex CE Platform. The mine, the process as performed, was Nintex Process Discovery, which Nintex placed end-of-life on 4 May 2026, with support ending in May 2028 and customers migrated to Process Manager. The gap between intention and reality is still the worklist. What has changed is who holds the instrument that measures it.
Read on for the problem, then the surviving instrument, then the bridge Nintex shipped in its December 2025 release that turns a technical process model into a map a business person can read, and the MCP server that now hands that map to an AI assistant.
Volge: the working premise of this book
Automation and AI fail without process truth, and the money already committed says many firms are about to learn this the expensive way.
Automation is a multiplier, and a multiplier is indifferent to the sign of the number it multiplies. Applied to a clean process, documented and stable, it removes cost and delay. Applied to one that is none of those things, it industrialises the confusion. The technology is neutral; the understanding is not.
Consider the ordinary shape of a failed automation programme. A team picks a process that is painful and visible, say supplier onboarding. They document it by asking the people who run it what they do, and those people describe the map, the official steps in the official order. The team automates the map. Then live volume arrives, carrying the forty per cent of cases the map never mentioned, and the automation either breaks or, worse, processes them wrongly and silently.
The pattern repeats because the diagnosis is skipped. Interviews capture what people believe they do, which is a poor guide to what they actually do. Memory smooths over the reruns, the workarounds, and the informal escalations that keep the business moving. The designed process is a sincere account. It is also, routinely, wrong in the specific places that cost the most money.
AI raises the stakes. A rule-based bot fails loudly, it stops, throws an error, waits for a human. An AI agent is built to keep going. Give it an incomplete picture of a process and it will improvise a plausible completion, acting on steps that were retired, approvers who have left, and thresholds that changed two budgets ago. The failure mode is not a crash. It is confident, well-formatted, and wrong.
This is why process understanding has become the entry point for AI rather than an afterthought to it. Niranjan Vijayaragavan, then Nintex's chief product and technology officer, made the case under that heading in Forbes on 3 February 2026: “The AI entry point no one is talking about: Process intelligence”. He has since left; Five9 appointed him chief technology officer effective 29 June 2026. An agent is only as good as its model of the work. Give it the designed map and it inherits the map's blind spots; measure the work as performed and it inherits reality.
None of this argues against automation. It argues against automating in the dark. The sequence that works is dull and reliable. See the process as designed, measure it as performed, resolve the difference, and only then decide what to automate, what to simplify, and what to leave alone.
| Dimension | Process as designed: the map | Process as performed: the mine |
|---|---|---|
| Source | Interviews, manuals, workshops, policy | Event logs from ERP, CRM, and line systems |
| Shows | How work is meant to run | How work actually ran, case by case |
| Bias | Optimistic, tidy, singular | Complete, messy, many-variant |
| Nintex instrument | Process Manager, now Nintex Processes | Process Capture at the desktop; mining no longer sold |
| Fails when | You automate it as if it were true | You never look at it at all |
Source: Volge analysis, 2026. Nintex instruments per Nintex product pages and release notes, read 8 November 2026.
Spending on intelligent process automation is projected to nearly quadruple in a decade, which means the demand for tools has already been decided and the demand for process truth is the constraint that remains. Market.us estimates the category at 16.81 billion US dollars in 2024, with a projected 61.23 billion by 2034, a compound annual growth rate of 13.8 per cent (Market.us estimate, September 2025 edition). Treat
the exact figure as a directional estimate. Treat the direction as settled.
Interpolated years assume the stated 13.8% CAGR and are illustrative only.
Source: Market.us estimate, September 2025 edition. Endpoints reported; intermediate years interpolated by Volge at the stated CAGR.
Rising spend on automation does not, by itself, buy results. It buys capacity. Whether that capacity lands on real bottlenecks or imaginary ones depends entirely on the quality of the process picture feeding it. A firm can be a heavy, sophisticated buyer of automation and still be automating the wrong forty per cent, because the picture it is working from is the tidy map rather than the messy mine.
The corrective is cheap relative to the spend it governs. Process mining and process mapping are small line items next to an enterprise automation programme, and they determine whether that programme's budget is aimed at the steps that actually cost time and money. Skipping the diagnosis to save on the diagnosis is the expensive economy.
There is a second reason the understanding lags. Mapping felt, for years, like an administrative chore, a compliance artefact produced once and left to rot. That framing is now obsolete. A living process picture is the substrate every automation and every agent reads from. It has moved from filing cabinet to operating dependency.
Nintex sits on the understanding side of this market rather than only the execution side, which is the argument of the next three parts. First the map. Then the mine. Then the bridge between them.
Automation programmes fail in a small number of predictable ways, and each is invisible to anyone working from the
designed process alone. Name the three and you have a checklist for why an initiative underdelivered; see them in your own data and you have a worklist.
01 Undocumented variants
A process described as one path is usually many. Regions adapt, teams improvise, and a single "standard" purchase-to-pay quietly grows a dozen live variants no manual records. Automate the documented path and every undocumented variant either breaks the bot or bypasses it, which is how a shiny programme ends up covering a minority of real volume.
02 Hidden bottlenecks
Delay concentrates. In most processes a few steps hold most of the waiting, an approval that queues for days, a handoff between two systems no one owns, a rework loop triggered by bad upstream data. These do not show up on a swimlane diagram, which has no axis for time. They show up in event logs.
03 Silent deviations
The costly deviations are the ones nobody flags. A control skipped "just this once" that became routine. An approval threshold everyone treats as advisory. A step performed out of order because the official order was inconvenient. Each is defensible alone and dangerous in aggregate, and each is invisible until you compare the mine against the map.
| Failure mode | What the board sees | What actually happened | Surfaced by |
|---|---|---|---|
| Undocumented variants | Automation covers less than promised | Real work runs on paths the map omits | Event-log analysis |
| Hidden bottlenecks | Cycle time refuses to fall | A few steps hold most of the wait | Event-log analysis |
| Silent deviations | An audit finding, eventually | Controls quietly skipped at scale | Map vs mine comparison |
Source: Volge analysis, 2026.
If the documented path carries 60 per cent of volume and your automation covers only the documented path, your ceiling is 60 per cent before you have written a line of configuration. The other 40 per cent is not an edge case. It is the case you did not measure.
The distinction that matters is between failing loudly and failing quietly. Traditional automation is brittle. It stops when reality departs from its script, and a human notices. That brittleness is annoying and also protective. It is a smoke alarm. An
agent, by design, does not stop. It reasons its way past the gap and produces an answer, which may be right, may be wrong, and will in either case look equally polished.
An AI agent inherits every blind spot in the process picture you hand it, and then acts on those blind spots with confidence a rule-based system never had. This is the central shift of 2026. The organisations rushing agents into operations are, in many cases, pointing them at the designed map, the one document guaranteed to be incomplete, and calling the result transformation.
So the value of a complete process picture rises exactly as agents arrive. The agent needs to know the variants and the exceptions, the controls that apply and the true sequence of events. That knowledge does not live in the manual. It lives in the event logs, waiting to be read. Measuring the work as performed is therefore the thing to do before the agent, not after it.
This reframes the mining category. Finding savings in existing processes is part of it, but the larger role is as a readiness layer for anything you plan to hand to a machine, the difference between deploying an agent against your operations as they are and deploying it against a flattering description of how they used to be.
Nintex's own framing places process intelligence at the front of the AI question rather than the back. We agree, with one caveat we will keep repeating. Mining tells you what happened, not why, and the "why" still needs people. The instrument sharpens the judgement. It does not replace it.
Title of an article by Niranjan Vijayaragavan, then Nintex chief product and technology officer, Forbes, 3 February 2026
Process mining reconstructs the sequence and timing of work from data. It does not explain intent. A step that looks like a deviation may be a sensible local fix, and a bottleneck may be a deliberate quality gate. The instrument tells you where to look. Deciding what it means is still a human job.
The sequence below is deliberately unglamorous, and its whole value is that it refuses to automate before it understands. Each step narrows the field of what is worth automating, so that the expensive execution budget lands on the few steps that actually move cycle time and cost.
Reverse any two steps and the economics collapse. Automate before you mine and you scale the current mess. Mine before you map and you have reality with nothing to compare it against. Act before you compare and you are back to guessing, which is where most programmes started. The order is the product.
Automation multiplies whatever it is pointed at. Most firms point it at the map. The map is incomplete in the exact places that cost money, among them variants and bottlenecks as well as outright deviations, and agents make that worse. The fix is to see the process as performed before you change it. Part II supplies the map. Part III supplies the mine.
Process Manager attacks that failure by moving ownership to the front line. Maps are written in readable steps, not arcane symbols, so the person who runs the process can read it, challenge it, and own it. Feedback and change requests sit inside the process itself. Ownership is assigned, so every process has a named human accountable for keeping it honest. The result is a map that stays close to the truth because the people closest to the truth maintain it.
Traditional process mapping fails for a human reason, not a technical one. The maps are drawn by specialists in a notation only specialists read, stored somewhere the doers never
look, and updated on a cycle measured in years. So they drift from reality the moment they are signed off, and everyone reverts to tribal knowledge. The diagram becomes a compliance artefact, produced and filed and then ignored.
Nintex Process Manager, formerly Promapp, turns the process as designed into a living, business-readable document your whole organisation can own, in three verbs: identify, map, and model.
Nintex Process Manager exists to make the process as designed a living asset rather than a dead diagram, written in plain business language, owned by the people who run the work, and kept current because keeping it current is easy. Formerly Promapp, rebranded to Process Manager in 2022, it carries a deliberately modest tagline, which is to identify, map and model your processes. The modesty is the point.
That readability has a second payoff. A map anyone can read is a map anyone can improve, which turns process documentation from a project into a habit. New joiners learn the real procedure instead of shadowing a colleague, and auditors read the same document the operators use. Change becomes visible and versioned rather than whispered.
"Model", the third verb in the tagline, matters as much as the first two. A map records the steps; a model captures the logic and the decisions, the branches and the roles and the handoffs, in a form precise enough to reason about and to hand downstream. That precision is what makes the later moves possible. The model can be compared against mined reality, and the artefacts that drive automation generated from it.
| Attribute | Detail |
|---|---|
| What it is | Business process mapping and modelling: the process as designed |
| Former name | Promapp (rebranded to Nintex Process Manager, 2022) |
| Now surfacing as | Nintex Processes, launched 26 October 2026, native to the Nintex CE Platform |
| Tagline | Identify, map, and model your processes |
| Owned by | Front-line process owners, in business language |
| Core value | A living, current, readable map rather than a filed diagram |
Source: Nintex product pages, read 8 November 2026; rebrand confirmed 2022; Nintex Processes launch reported 26 October 2026.
The tagline hides three distinct jobs, and it is worth separating them because organisations tend to be good at one and poor at the others. Identifying, mapping, and modelling are not the same task, and a process programme that skips any of them leaves a predictable gap.
01 Identify: knowing which processes you actually have
Most organisations cannot name their own processes. Work is described by department or by system or by project, and the process, the end-to-end thing the customer experiences, falls between those categories. Identifying means building the register, the list of processes that exist, who owns each, and how they connect. Dull, foundational, and usually missing.
02 Map: writing down how it is meant to run
Mapping records the designed sequence in readable steps, naming what happens, in what order, by whom, with what inputs and outputs. Done in business language, the map becomes usable by the front line rather than filed by the quality team. This is the artefact new joiners learn from and auditors read.
03 Model, capturing the logic, not just the steps
Modelling adds the decisions and branches, the roles and conditions and handoffs, in a structured form. A model can be reasoned about, compared against mined reality, and handed to downstream tools. It is the difference between a picture of a process and a specification of one.
| Verb | Produces | Primary reader | Failure if skipped |
|---|---|---|---|
| Identify | A process register with owners | Operations leadership | You improve processes you cannot name |
| Map | A readable procedure | Front-line staff, auditors | Knowledge stays tribal |
| Model | Structured process logic | Automation and analysis | Nothing downstream to build on |
Source: Volge analysis of Nintex Process Manager, 2026.
Every process in Process Manager has a named owner. This single discipline does more for accuracy than any feature. A document with an accountable human attached stays
honest; an ownerless diagram rots. Volge configures ownership before it configures anything else.
Three AI features shipped inside ten months have changed the economics of getting a map on the page, because each attacks the single most expensive part of process documentation, the human effort of writing it down. The old objection to mapping was always cost, since it took specialists weeks. That objection is now much weaker. Exhibit 6 dates the releases; the paragraphs below explain what each one does.
01 AI Process Generator: from blank page to draft
The AI Process Generator entered beta in the March 2025 release and reached general availability in June 2025, for Professional tier and above. It drafts a process map from a description, turning the terrifying blank page into an editable first draft. The draft is not the deliverable, a human owner still refines it, but starting from eighty per cent complete rather than zero changes who can participate and how fast.
02 Process Capture: documentation that records itself
Process Capture reached general availability in the September 2025 release, included in Expert and Enterprise tiers, an add-on elsewhere, and not offered in the AEN region. It records the actual activity of a task as it is performed and auto-documents it, so the map is drawn from what someone did rather than from what they later remembered doing. This closes part of the memory gap that makes interview-based mapping unreliable, the map inherits the doer's real clicks, not their tidied recollection.
03 AI Model to Map: technical logic made business-readable
AI Model to Map, named AI Model to Map Converter in the product, reached general availability in the December 2025 release, Process Manager 4.12.27.0, having entered beta that September. It converts technical BPMN, the notation analysts and mining tools speak, into business-readable procedures that a process owner can actually use. This is the feature that bridges the mine back to the map, and it earns a full treatment in Part IV because it is the mechanism that closes the loop.
Source: Nintex Process Manager release notes, 4.12.10.0 to 4.12.27.0, read 8 November 2026.
Chris Ellis, Director of Solution Engineering, Nintex, on the general availability of AI Model to Map; reported by PEX Network, 6 January 2026
The practical effect of readable maps plus AI drafting is that process documentation stops being a project and becomes a habit, which is the only state in which it stays accurate. A project ends; a habit persists. Exhibit 7 contrasts the old mode with the new one, and the difference is less about technology than about who is allowed to participate.
| Dimension | Traditional mapping | Nintex Process Manager |
|---|---|---|
| Author | Process specialists | Front-line owners, AI-assisted |
| Language | Formal notation | Plain business steps |
| Starting point | Blank page | AI-generated draft |
| Update cadence | Every few years | Continuous, in-flow |
| Where it lives | A shared drive, unread | The tool people work in |
| Accuracy over time | Decays | Maintained by owners |
Source: Volge analysis, 2026.
The map is necessary and, on its own, insufficient. However current and readable, it remains a record of intention. It tells you how the work is meant to run, and, because owners keep it honest, it tells you that better than most organisations manage today. What it cannot tell you is whether the work actually runs that way in the millions of cases nobody watched.
That is not a criticism of Process Manager; it is a description of what a map is. A map of a city does not show you the traffic. For the traffic you need a different instrument, one that reads the record of what actually moved. A map with no mine is a plan with no feedback, and the mine is the subject of Part III.
Process Manager makes the designed process a living, owned, business-readable document, and recent AI features have cut the cost of producing it. That is the map. The next part reconstructs the territory.
Mining reconstructs how work actually runs from the event logs your systems already keep, and the gap it exposes against the map is where the money is. Nintex has retired its own mining product, which changes who supplies the instrument but not the argument.
Process mining reconstructs how work actually runs, case by case, deviation by deviation, from the event logs your ERP and CRM systems already produce as a by-product of doing business. Nothing new needs to be recorded. Every time an order is raised, an approval clicked, or a record updated, the system stamps it with an identifier and a time. Mining reads those stamps back into the story of the process, told by the process itself.
The method is worth understanding because its credibility rests on it. Enterprise systems log events, each with a case identifier, an activity, a timestamp and sometimes an actor. Process mining takes millions of those events and reassembles them into the paths cases actually followed, which steps, in which order, with what waits between them. The output is not an opinion about the process. It is the process, as recorded by the machines that ran it.
This is why mining beats interviews for factual questions. Nobody has to remember, estimate, or defend anything. The log does not round its cycle times, forget its reruns, or omit the awkward variant. It shows every path every case took, including the ones no one would have described in a workshop.
The honesty cuts both ways, which is the caveat this book keeps returning to. The log records what happened, not why, and it records only what the systems captured. Work done in email, on paper or in a spreadsheet leaves no event to mine,
so a process picture built only from system logs has its own blind spots. Good mining pairs the data with the people who can explain it, and that pairing is part of the method rather than an optional extra.
Nintex's own position has changed, and that change is the most important fact in this part. On 4 May 2026 Nintex announced end-of-life for Nintex Process Discovery, the product that delivered process mining and task mining: end-of-life on 1 May 2027, end of support in May 2028, with existing customers moved to Process Manager. Exhibit 8 sets out what Nintex retired and what survives.
| Capability | Status at November 2026 |
|---|---|
| Process mining | Delivered by Nintex Process Discovery. End-of-life 1 May 2027; support ends May 2028 |
| Task mining | Same product, same dates. No current Nintex page positions it as shipping |
| Process Capture | Shipping. Desktop activity recording inside Process Manager, GA September 2025 |
| Process mapping and modelling | Shipping. Process Manager, now surfacing as Nintex Processes |
Source: Nintex community, Process Discovery end-of-life announcement, 4 May 2026, updated 17 August 2026; Nintex Process Manager release notes, read 8 November 2026.
The analytical case is unaffected, because the process as performed is still the only honest baseline. What has changed is who supplies the instrument. Nintex no longer sells a mining product, so the mine now comes from a third-party mining tool, from Process Capture at the desktop, or from a sampled log analysis run by hand. The map, and the comparison that gives it value, stay inside Nintex.
Process mining is easier to trust once you can see the mechanism. There is no black box worth being nervous about; there is a pipeline that reads timestamps and rebuilds sequences. The four moves below are what happens between your systems and the picture on the screen.
| Move | Question it answers | Typical finding |
|---|---|---|
| Extract | What did the systems record? | Millions of timestamped events per process |
| Reconstruct | What paths did cases follow? | Many more variants than anyone expected |
| Analyse | Where is time and money lost? | A few steps hold most of the delay |
| Compare | Where does reality break from design? | Deviations no one had flagged |
Source: Volge analysis, 2026. Findings are typical patterns, not guaranteed outcomes.
System logs miss work done between systems, the copy-paste, the manual reconciliation, the swivel-chair step where someone reads one screen and types into another. Process Capture records that desktop activity directly, so the picture includes the work that never touched a logged transaction. It reached general availability in the September 2025 release. Together with log analysis it leaves fewer blind spots than either alone.
In most processes a handful of steps hold the large majority of the elapsed time, and the whole value of mining is that it names those steps instead of leaving you to guess. Waiting, not working, is usually the villain. A case spends far longer sitting in a queue than being actively handled, and the queues are invisible to a swimlane diagram that has no axis for time.
Source: illustrative composite by Volge, 2026, of patterns commonly surfaced by process mining. Not drawn from a specific named client; figures are indicative of the shape mining typically reveals, not a benchmark.
The pattern in Exhibit 10 is illustrative, and we have labelled it as such, but its shape is familiar to anyone who has mined a transactional process. The value-add work, the part a person is genuinely paid to do, is a thin slice. The rest is waiting, reworking, and shuffling data between systems. That composition is invisible in interviews, because people describe the work, not the waiting between it.
This changes where automation should point. Faced with a process like this, the instinct is to automate the value-add step, because that is the part everyone can see. The data says otherwise. The return is in the approval queue and the rework loop, where automation and process redesign remove waiting rather than speeding up work that was never the bottleneck.
It also disciplines the AI conversation. An agent set loose on the seven per cent of value-add work leaves ninety-three per cent of the elapsed time untouched. An agent, or a redesign, aimed at the approval wait and the rework loop attacks the actual cost. Mining is what tells you which is which, before you commit the budget.
Stop asking "which task can we automate?" and start asking "where does a case wait, and why?" The first question flatters the tools you already bought. The second finds the money. Mining answers the second.
The mine is only as complete as your digital exhaust. Work done on paper, over a call, or in a system the logs never reach stays invisible to it, which makes the mine a truer picture than the map, not the whole truth.
The single most valuable artefact Nintex can produce is not the map and not the mine but the difference between them, the gap where the designed process and the performed process disagree. That gap is not a failure to be tidied away. It is a costed, prioritised list of everything worth improving, automating, or deliberately leaving alone, and it is the reason to buy both instruments rather than either.
Neither instrument delivers this alone, which is the commercial heart of the argument. The map without the mine is a plan you cannot check. The mine without the map is a pile of reality with no baseline to judge it against, you can see that cases took eleven paths, but not which of the eleven you
intended. Only the comparison produces a worklist, and only a worklist justifies a budget.
| The map says | The mine shows | The gap is worth |
|---|---|---|
| One approval path | Eleven live variants | Standardisation, then automation |
| Approval takes hours | Approval waits days | The largest cycle-time prize |
| Controls always applied | Controls skipped at scale | Audit and compliance exposure |
| Handoffs are clean | Cases loop back repeatedly | Rework elimination |
| Process is stable | Behaviour drifts by quarter | Continuous monitoring |
Source: Volge analysis, 2026. Rows are representative gap types, not a single client's findings.
Volge: on the map-versus-mine gap
The gap is also self-prioritising, which C-level readers will appreciate. Each entry carries a size, the cycle time it wastes, the volume it touches, the control it bypasses. That turns process improvement from a matter of taste and politics into a matter of arithmetic. You work the gap in order of value, and you can say why each item sits where it does.
One direction of the gap remained awkward until recently. Mining speaks BPMN, the technical notation analysts read and process owners do not. So the mined reality, however valuable, tended to stay trapped in the analyst's tool, unread by the people who owned the work. The feature that unblocked this reached general availability in the December 2025 release, and it is the subject of Part IV.
The first mined result that unsettles a leadership team is almost always the variant count, the discovery that a process everyone described as one path was, in the logs, dozens. This is not chaos, or not only chaos. Some variants are sensible local adaptations; some are quality gates; some are genuine mess. The point of mining is that you can finally tell which is which.
The "long tail" here bundles dozens of rare paths that individually carry little volume but collectively resist automation and hide risk.
Source: illustrative composite by Volge, 2026. Shape is representative of mined transactional processes; not a specific benchmark.
Read Exhibit 12 the way an operator would. The designed path carries a comfortable-looking majority, which is why interview-based mapping feels adequate, most of the time, most cases really do follow it. The trouble is the rest. The top handful of variants carry real volume, and the long tail, though thin per path, collectively defeats any automation built for the main path alone.
The strategic move is not to eliminate variants on sight. Some earn their place. The move is to sort them. Standardise the ones that are needless divergence, protect the ones that are deliberate, and automate the main path only once it is stable enough to be worth the build. Mining supplies the sort; judgement supplies the decision.
This is where the map earns its keep a second time. Compared against the mine, it tells you which variants were intended and which crept in, separating a designed branch from an undocumented workaround. Without the map, every variant looks the same. With it, the mess sorts itself into signal.
A high variant count is not proof of a broken organisation. It is proof that you can now see the organisation. The count was always that high; you simply could not measure it. Measurement is the first improvement.
At the end of mining you hold something most organisations have never had, which is a factual, complete, case-level account of how the work truly runs. The remaining obstacle is one of translation. That account is expressed in BPMN, and BPMN is a language of analysts, not of the process owners who must act on what it says.
This is a real barrier, not a cosmetic one. A finding that only the analytics team can read is a finding that stalls. The process owner in finance or procurement, the person with the authority and the context to change the process, cannot act on a diagram they cannot interpret. So the mined truth sits in a specialist tool, admired and unused, while the map in Process Manager stays comfortably out of date.
The whole system Nintex has assembled only pays off when the two directions connect, with design flowing into reality for comparison, and reality flowing back into design for action. For years the second direction was the weak link. Mining could expose the truth, but returning that truth to the business in a form it could use required manual translation that rarely happened.
That link closed in the December 2025 release, when AI Model to Map reached general availability and turned technical BPMN into business-readable procedures automatically. A second link opened in the October 2026 release, when the Process Manager MCP server gained authentication for eleven AI clients, among them ChatGPT, Claude, Gemini and Microsoft 365 Copilot. Part IV begins there.
Mining reconstructs the real process from data you already keep, exposes where time is lost and how many variants exist, and, set against the map, produces the costed gap that is the actual product. Nintex no longer sells the mining half, which is a sourcing question rather than an argument against it. The one missing piece was translation. Part IV supplies it.
This is why we held the feature back from Part II despite it being a Process Manager capability. Its significance is not that it drafts a map; the AI Process Generator already does that. Its significance is directional. It runs mine-to-map, closing the return path that turns a diagnostic exercise into an operating loop. Chris Ellis, Nintex's director of solution engineering, called the release “a major step forward in making process intelligence accessible, actionable, and scalable across the organization”, as reported by PEX Network on 6 January 2026, and the accessibility he names is exactly that, reality rendered readable.
Recall the impasse from Part III. Mining produces truth in a technical dialect. The people empowered to act on that truth
do not speak the dialect. The translation between them was, until this year, a manual job that competed with everything else on an analyst's desk and usually lost. So insight accumulated faster than anyone could convert it into action.
AI Model to Map bridges the mined reality back to the business-readable map. From there, insight becomes action: DocGen and Forms carry the improved process into daily work, and the proof justifies the spend.
AI Model to Map is the feature that makes the whole map-and-mine system work in practice, because it carries the mined reality across the one barrier that used to stop it. That barrier is language. Generally available since the December 2025 release, it converts technical BPMN, the notation mining produces, into business-readable procedures that a process owner can read and question and change. The mine flows back into the map, automatically, and the loop closes.
Model to Map removes the translation cost. The mined process, expressed in BPMN, becomes a procedure in plain business steps inside Process Manager, the same tool the front line already uses to own its maps. What was locked in the analyst's screen becomes a document the process owner can read on Monday and change by Friday. The bottleneck between knowing and doing is the one being automated.
With the loop closed, the sequence from Part I finally runs end to end without a manual gap in the middle. Discover and map, then mine and compare, then act and map again, because acting changes the process and the cycle repeats. Exhibit 13 draws the closed loop.
AI Model to Map has been generally available only since the December 2025 release. We describe it on Nintex's framing and our own reading, not on a track record across dozens of enterprises. Automated translation also smooths, a mislabelled step reads as cleanly as a correct one, so treat the output as a strong draft an owner still checks, not an oracle.
The output of "owners act" becomes the next designed map, and the loop runs again, process understanding as a habit, not a project.
Source: Volge analysis of Nintex capabilities, 2026. AI Model to Map GA, Process Manager 4.12.27.0, December 2025; MCP authentication, release 4.26.23, October 2026.
Understanding a process pays nothing until it changes what happens on the ground, and two Nintex enhancers carry the improved process from the diagram into the day-to-day work. Nintex DocGen generates documents from process data. Nintex Forms captures data into the process. Named here as enhancers rather than headline products, they are what stop an improved map from staying a map.
01 Nintex Forms: clean data in
Forms captures the data a process needs at the point the process needs it, in a structured shape rather than a free-text email. Clean structured input is what makes downstream automation possible; garbage entering a well-designed process still produces garbage. Forms is the front door that keeps the process fed with data it can actually use.
02 Nintex DocGen: finished documents out
DocGen generates the documents a process produces, among them contracts and quotes, statements and letters, directly from process data, without the copy-paste step that introduces errors and delay. The process becomes the source of the document rather than a prelude to someone assembling it by hand. That removes a whole class of the manual data entry Exhibit 10 flagged as pure waste.
Neither enhancer is the reason to buy. We are deliberately not over-featuring them, because the argument of this book is about seeing the process, not about any single tool for running it. But they matter to the C-level reader for a specific reason. They are how the improvement you identified in the gap actually reaches the people doing the work. Insight that never touches the daily task is a report, not a result.
This is the honest end of the "insight to action" promise. There is no single button marked "act". There is a readable process, a clean way to feed it, and an automatic way to produce what it
owes the customer. Above all, there is the diagnosis that told you which part was worth the effort.
Placed in the loop, Forms sits at the process entrance and DocGen at its exit, with the improved, mined-and-mapped process in between. Data enters clean, moves through a process you can now see and have deliberately shaped, and leaves as a finished document. The understanding from Parts II and III becomes operational rather than analytical.
DocGen and Forms are enhancers, not the headline. They turn an improved process into improved work. Forms feeds it clean data, and DocGen produces its documents. Buy them for what they do to a process you already understand, not as substitutes for understanding it.
Nintex is a widely deployed, independently rated platform rather than an emerging bet, and the numbers say so on scale and on satisfaction. Nintex's company page reported more than 7,000 organisations in over 100 countries when it was last modified in September 2026, though the newsroom boilerplate of 22 October 2026 drops the count. Forrester named Nintex a Strong Performer in The Forrester Wave: Agentic Process Orchestration Platforms, Q3 2026. This is the part of the argument that de-risks the purchase.
| Proof point | Figure | Source · date |
|---|---|---|
| Deployed scale | 7,000+ organisations, 100+ countries | Nintex company page, Sep 2026 |
| G2 rating | 4.2 / 5 across 1,326 reviews | G2, Nov 2026 |
| TrustRadius rating | 8 / 10 across 530 reviews | TrustRadius, Nov 2026 |
| Recognition | Top Rated, seventh consecutive year | TrustRadius, 2025 award |
| Analyst placement | Strong Performer, not a Leader | Forrester Wave, Q3 2026 |
| Logo-wall names | L'Oréal, Panasonic, Sonos, CARFAX | Nintex solutions pages, Jul 2026 |
Source: as stated per row. Forrester placed Nintex as a Strong Performer, not a Leader; no Gartner Magic Quadrant placement is asserted here.
Read the ratings for what they are, which is durable third-party signal from large review bases. A 4.2 out of 5 across 1,326 G2 reviews and an 8 out of 10 across 530 on TrustRadius are not the scores of a product that frustrates its users, and a TrustRadius Top Rated award in 2025 for a seventh consecutive year, repeated in 2026, is a statement about consistency rather than a single good quarter. These are noisy measures, but the sample sizes make the direction reliable.
The logo-wall names matter for a different reason, and they carry a smaller claim than they appear to. L'Oréal, Panasonic, Sonos and CARFAX appear as customer logos on Nintex's solutions pages, with no published case study, metric or quotation behind any of them. Read them as evidence that the platform is bought by large, demanding organisations, not as evidence of what it achieved inside them. Nintex's published airline story is Virgin Australia, a different company from the Virgin Atlantic an earlier edition of this report named.
We should be equally clear about what we are not claiming. Nintex is not a Gartner Magic Quadrant leader on any designation we have sourced, and Forrester placed it as a Strong Performer rather than a Leader in the Agentic Process Orchestration Platforms Wave of the third quarter of 2026. The proof above stands on its own terms, which is the only kind of proof worth putting in front of a board.
The financial case rests on one documented study, attributed and dated so you can weigh it yourself. Forrester's Total Economic Impact study of Nintex Workflow found a 213 per cent return on investment with a nine-month payback. Nintex states that the study was conducted in late 2022, which makes the vintage old, and it covers Nintex Workflow rather than the mapping capability that is this book's subject. No newer Forrester study of Nintex exists.
ROI bar shown to scale against a 100% reference; payback bar shown against a 24-month reference. The Forrester study was conducted in late 2022 and describes Nintex Workflow specifically.
Source: Forrester Total Economic Impact of Nintex Workflow, study conducted late 2022 per Nintex. Payback and ROI as reported.
Treat the Forrester figures with the care their age deserves. A 213 per cent ROI and a nine-month payback are strong numbers, but the study was conducted in late 2022 and concerns Nintex Workflow rather than the mapping and mining capabilities that are this book's subject. We include it as directional evidence that Nintex automation pays back quickly, not as a forecast of your specific result. The vintage is on the label for a reason.
Against that single dated study, the useful number is your own. A mapping programme's return shows up as hours not spent rewriting procedures and as approvals that stop queueing, and both are measurable in the logs before and after. Nintex publishes customer stories in local government and elsewhere, but none we could source carries both a dated total and an independent audit, so we quote none of them. The calculation is cheap to run and the answer is specific to you.
The honest summary is that the returns are real and the exact number is yours to discover. What the map-and-mine approach changes is the confidence with which you pursue it. Instead of automating on faith and hoping for a Forrester-shaped outcome, you mine the gap, size each opportunity, and spend against evidence. The ROI stops being a promise and becomes a calculation.
The 213 per cent return and nine-month payback are real but dated, from a study Nintex says was conducted in late 2022, and specific to Nintex Workflow rather than to mapping. It is not a guarantee for your organisation. It is a reason to run the calculation on your own processes, which is what Volge does first.
The Process Manager MCP server turns the approved map into something an AI assistant can read, and that is a smaller and more consequential change than it sounds. Nintex opened it in beta on 13 August 2026 and shipped authentication for eleven clients in the October 2026 release, 4.26.23, among them ChatGPT, Claude, Gemini and Microsoft 365 Copilot. The server is read-only.
Read-only is the reassuring part and also the part that misleads. An assistant that can read the process library cannot
change a process, but it can repeat what the library says to anyone who asks, including a process that is out of date, a draft that was never approved, or a procedure that exists only for one region. The exposure is not write access. It is the authority a stale answer acquires when a machine delivers it fluently.
Three decisions follow, and all three belong to the process function rather than to the platform team. Which processes are exposed, meaning whether draft and retired maps are reachable or only published ones. Which audiences are exposed, because a procedure that is correct for one jurisdiction and wrong for another should not be answered the same way for both. And what the currency floor is, because a map last edited three years ago should not be served as the answer at all.
The third is measurable, which makes it the useful one. Set a currency threshold, exclude anything past it from the server, and the exclusion list becomes the backlog for the owners. A library that cannot be served to an assistant because most of it is stale is a library that was already failing its human readers. The machine simply asked more often.
Nintex runs a United Arab Emirates instance, and it is for exactly this subject. The status register lists the UAE for Process Manager production and Nintex Analytics, and for nothing else, which makes it the only in-region capability any non-Microsoft vendor in this series operates in the Gulf. Against that, Bahrain requires prior written authorisation for the kind of cross-system automated processing that process discovery is, and India requires logs to be maintained within its own jurisdiction. Classification comes before discovery, and discovery before any export.
The Gulf has one in-region home for process intelligence, and it belongs to this half of the portfolio rather than the other. Nintex's own services status register, read on 8 November 2026, lists a United Arab Emirates instance for Nintex Process Manager production and for Nintex Analytics. It lists the UAE for no other service. Nintex Automation Cloud, the workflow platform, runs in seven regions and none of them is in the Middle East or India.
That asymmetry is the right way into the regional picture, because it cuts in this subject's favour. The map can sit in the Gulf. The workflow that acts on the map cannot. For a programme whose first deliverable is an honest account of how the work runs, the instrument that holds that account has an in-region home and the instrument that automates against it does not. Sequence the programme accordingly.
It is also the only such capability either half of the research behind this chapter found. Flexera has no Gulf or Indian hosting region. Nintex Automation Cloud has none. Against that background a live United Arab Emirates instance for the mapping and analytics services is a genuinely distinguishing fact, and it rests on an operational register rather than on a brochure.
Nintex Services status register, read 8 November 2026
One distinction has to be kept, and it is the kind a procurement team will test. The regional footprint is operational fact, not a contractual commitment. Nintex's trust centre is a gated portal that returned no text, and no data residency article could be located in its product documentation. No contractual residency commitment by Nintex is asserted here. Where residency is a binding obligation, obtain the commitment in the contract, by name, and do not infer it from a status page.
Bahrain is the jurisdiction that reaches process discovery directly, and almost nobody reads it that way. Article 15 of the Personal Data Protection Law, Law No. 30 of 2018, requires prior written authorisation from the Authority for processing consisting of visual recording used for monitoring, and for automated processing of personal data files held by two or more controllers processing for different purposes. Read the second limb against what cross-system process mining does. It assembles personal data from the records of several systems, held for several purposes, and processes it automatically to reconstruct a sequence.
Ministerial Order No. 43 of 2022 adds a second gate. Article 3 requires a data protection impact assessment for systematic monitoring of a publicly accessible area on a large scale. Desktop activity capture is not that, but the drafting is a reminder that Bahraini law treats observation of behaviour as a category requiring assessment rather than as ordinary processing.
The practical consequence is a sequencing one rather than a prohibition. In Bahrain, establish whether the discovery design requires prior authorisation before the first extract is taken, not after the findings are circulated. An authorisation sought in advance is a precondition. The same question
raised by a supervisor after the fact is a finding, and the finding attaches to processing that has already happened.
Event-log mining and desktop capture sit differently in law, and a programme that treats them as one activity will misstate its own position. Log mining reads records the systems already keep as a by-product of doing business. Desktop capture observes a named person working. The second is monitoring, and every jurisdiction in this chapter treats monitoring more carefully than it treats record-keeping.
Four decisions settle it, and all four belong in writing before deployment. Which populations are in scope, and whether consultation with them is required or merely advisable. What is captured, meaning whether keystrokes, screen content or only application and window metadata. How long the capture is retained, which is where the Indian retention floor discussed below collides with a privacy instinct to delete quickly. And who may read the raw capture, as against the aggregated map derived from it.
The fourth is the one that most often goes wrong. A map built from capture is an operational artefact. The raw capture is a record of an individual's working day, and the two should not carry the same access list.
India is the jurisdiction where the raw material of process intelligence is mandated and its location regulated, which makes it unusually favourable ground and unusually exacting. CERT-In's Directions of 28 April 2022, No. 20(3)/2022-CERT-In, are in force and unamended. Direction (iv) requires every service provider, intermediary, data centre, body corporate and government organisation to enable logs of all their information and communications technology systems and maintain them securely for a rolling period of 180 days, "maintained within the Indian jurisdiction". Direction (ii) requires reporting of listed incidents within six hours of noticing them, which is what the log location is ultimately for.
The Digital Personal Data Protection Rules, 2025, notified on 13 November 2025 as G.S.R. 846(E), add a retention floor from the other direction. They commence in tranches, with rule 4 on consent managers from 13 November 2026 and rules 3, 5 to 16, 22 and 23 from 13 May 2027. Rule 6(1) then requires encryption, obfuscation, masking or virtual tokens, appropriate access control, and "visibility of access through logs,
monitoring and review". Rules 6(1)(e) and 8(3) impose a minimum one-year retention of personal data, associated traffic data and processing logs, binding on a processor as well as on the fiduciary.
CERT-In's own frequently asked questions of May 2022 soften the location rule. Question 35 states that logs "may be stored outside India also as long as the obligation to produce logs to CERT-In is adhered to by the entities in a reasonable time". Question 37 enumerates the log types in scope, including firewall, security monitoring, web, database, mail, proxy, application and virtual private network logs, together with event logs of critical systems. The binding text says India. The clarification says anywhere, provided production is timely. Cite both, decide deliberately, and record the decision.
For a process-mining engagement with its nearest Nintex region in Singapore, that is the operative tension. An event-log extract taken for discovery is derived from the logs direction (iv) covers, and the extract crosses a border. Settle whether the extract is itself a log for these purposes, settle the production time, and put both answers in the design record.
So Indian law requires the visibility that process intelligence consumes, and then requires it to be kept for a year. A discovery programme in India has more raw material than one anywhere else in this chapter, and less freedom to discard it. Rule 7 completes the picture with breach intimation to each affected data principal without delay, to the Data Protection Board without delay, and again in detail within seventy-two hours. There is no de minimis threshold.
India offers no residual balancing test, which constrains what a process intelligence programme may do with what it finds. Section 4 of the Digital Personal Data Protection Act, 2023 permits processing only with consent or for a legitimate use under section 7, and section 7 is exhaustive. There is no equivalent of a legitimate-interests basis, so a business cannot self-certify a new processing purpose as legitimate once discovery has suggested one.
The research and statistical exemption is narrower than it looks. Section 17(2)(b) is available only where the data is not used to take any decision specific to a data principal, which excludes most commercial deployment of a finding. A mined insight that changes how a particular customer's case is routed is a decision specific to a data principal.
Nor is there an automated-decision-making right in Indian law to constrain what mining may infer, which cuts the other way. The absence of such a right is not permission. It means the constraint sits on the lawful basis for the processing rather than on the output, and the lawful basis has to be established before the extract, not after the insight.
| Jurisdiction | Nintex process mapping in region | The gate on discovery itself | The supplier gate |
|---|---|---|---|
| United Arab Emirates | Yes, Process Manager production and Nintex Analytics | Federal PDPL in force with no Executive Regulations as at 8 November 2026; health data may not leave the State | DESC Cloud Service Provider Security Standard for Dubai government and semi-government |
| Bahrain | No | PDPL Article 15: prior written authorisation for automated processing of files held by two or more controllers for different purposes | No national accreditation scheme; international certifications specified instead |
| Oman | No | Classification before cloud processing, and a record of processing covering any movement of personal data outside Oman | TRA authorisation before contracting |
| Saudi Arabia | No | Prohibition on transferring content comprising government agency data outside the Kingdom | CST registration at Class A, B or C by data classification |
| Kuwait | No | Level 3 and Level 4 data and government-held personal data may not be hosted outside Kuwait | CITRA cloud licence, requiring a data centre inside Kuwait |
| India | No; nearest region is Singapore | CERT-In direction (iv): logs maintained within the Indian jurisdiction for 180 days, with FAQ 35 to the contrary | MeitY empanelment and STQC audit status for SEBI regulated entities under the 2023 cloud circular |
Sources: Nintex Services status register, read 8 November 2026, for regional availability. Legal instruments as cited in the text, each with its issuing body and date. Compilation by Volge, 2026. Qatar is omitted because the Qatari cloud and classification instruments could not be verified from a primary source.
Three further Omani obligations shape a discovery design. The Executive Regulations require a record of processing
activities from both controller and processor, and that record must cover any movement or processing of personal data outside Oman. A data protection officer is mandatory for controllers, with the officer's name and contact details published. And the Cloud Computing First Circular, Ministry of Transport, Communications and Information Technology Summary 10/2026 of 28 June 2026, requires government entities to classify data before storing or processing it in a cloud environment.
Oman has no instrument reaching process discovery directly, and it has the region's most severe penalty for moving the resulting data out. The Personal Data Protection Law, Royal Decree No. 6/2022, has been fully enforceable since 5 February 2026, when the transition period under the Executive Regulations closed. Criminal fines are imposed by the competent court, and most contraventions sit between 500 and 20,000 Rial Omani. Article 23, unlawful cross-border transfer, sits at 100,000 to 500,000.
So in Oman, classification is a precondition of discovery rather than an output of it. That inverts the instinct of most process programmes, which is to discover first and classify what they find. For a government unit the inversion is explicit. Circular Summary 6/2024 of 31 March 2024 emphasises processing within Oman and requires prior approval of the Cyber Defence Centre before government-held personal data moves out.
Saudi Arabia's constraint falls on the extract rather than on the analysis. Article 3-3-5 of the Cloud Computing Services Provisioning Regulations version 4 prohibits a provider or a subscriber from transferring content comprising data of Saudi government agencies outside the Kingdom, for any purpose and in any form, permanently or temporarily, including temporary storage and backup, unless another Saudi instrument expressly permits it. The Regulations were issued by the Communications, Space and Technology Commission under Decision No. 506/1445 and took effect on 10 October 2023. The article number and wording rest on named law-firm commentary, Aldhabaan Law Firm writing in the Chambers Cloud Computing 2026 guide, because the Commission's own file could not be read.
One repeated Saudi claim should be dropped rather than passed on. The National Data Management Office's Data
Management and Personal Data Protection Standards, version 1.5 of January 2021, contain no data residency, localisation or in-Kingdom hosting requirement, which was established by searching the whole instrument. The National Cybersecurity Authority's Cloud Cybersecurity Controls, CCC-2:2024, deleted the sub-controls of the 2020 edition that had required cloud services to be provided from inside the Kingdom, recording that localisation controls had moved to the National Data Management Office. The receiving instrument has not been identified. Quote the instrument being relied on, and name it.
An event-log extract from a Saudi government agency's systems is content comprising that agency's data. There is no Nintex region in the Kingdom, so a discovery engagement for a Saudi government customer is run against data that cannot leave. That points to a sampled analysis conducted inside the Kingdom rather than a hosted mining platform, which is a method decision rather than a limitation.
For a Saudi financial institution the gate is an approval rather than a geography. The Saudi Central Bank's Cyber Security Framework, No. 381000091275 of 24 May 2017 and in force, states at 3.4.3 that in principle only cloud services located in Saudi Arabia should be used, with explicit approval where they are not, and requires approval before cloud services are used at all. The Rules on Outsourcing, No. 41027017 of 15 December 2019, add a written no-objection for overseas outsourcing with a rationale for why the work cannot be done within the Kingdom.
Four accreditation gates in the region bind the supplier rather than the workload, and a discovery programme for a public body stalls at procurement without them. Saudi Arabia requires registration with the Communications, Space and Technology Commission, at Class A for public government data, Class B for confidential and Class C for secret or top secret. In Dubai, the Dubai Electronic Security Center's Cloud Service Provider Security Standard is mandatory, in the Center's own words, for all providers wishing to offer cloud services to Dubai government and semi-government entities, with annual surveillance audits and recertification every three years. Kuwait requires a licence from the Communication and Information Technology Regulatory Authority, and clause 2.1 of its Cloud Computing Regulatory Framework version 2.4 permits only a licensed party with a data centre and infrastructure inside Kuwait to contract with the public sector.
Oman requires a Telecommunications Regulatory Authority authorisation.
Bahrain is the exception, and the contrast is instructive. Its Cloud First Policy version 1.0, dated 24 April 2017 on its title page, names no national accreditation scheme and specifies international certifications instead. It also takes an explicit position against localisation, stating under Data Sovereignty that residency restrictions "undermine the economies of scale and security benefits to be gained from shared computing infrastructure". So Bahrain is relaxed about where the mining platform sits and exacting about the authorisation to run the processing at all. Those are two different questions, and a single regional policy that merges them will get both wrong.
The regional ground changes the order of the five steps in chapter one rather than the steps themselves. Classify before you discover, because in Oman and Saudi Arabia the classification decides whether the extract may leave at all. Establish the lawful basis and any prior authorisation before the first extract, because in Bahrain the authorisation attaches to the act of processing and cannot be obtained retrospectively. Separate the event-log position from the desktop-capture position in every document, because the two are different activities in law. And treat the Indian retention floor as a design input rather than a compliance afterthought, because it runs against the instinct to delete discovery data once the map is drawn.
One line belongs in every regional position and is usually missing. Name what is not in region. The mapping instrument has a United Arab Emirates home and the workflow engine does not, and any mining tool a client already owns has a footprint of its own that has to be established separately. A constraint disclosed in advance is a design decision. The same fact found by a supervisor is a finding.
If the answer is a hunch rather than a number, start with mining instead of automation. You are about to spend against a guess.
Ownerless processes rot. If you cannot name the owner, you cannot hold the accuracy, and no tool fixes an accountability gap.
If the process lives in a notation only analysts read, insight will stall at the analyst's desk. Business-readable is not a nicety; it is the difference between knowing and doing.
Software bought and left unoperated is shelfware. Decide up front whether you will run this capability yourself or have it delivered by a partner.
The questions to ask before buying, the objections a board raises and the honest replies, and then the operating detail: what must be in place before discovery, the order the work runs in, the controls and how each is tested, the ways a discovery programme fails, and what to measure once the loop is running.
Before committing to any process-understanding programme, a C-level buyer should be able to answer six questions, and if the answers are vague the programme is not ready. The questions are deliberately blunt. They separate a real diagnostic exercise from a tooling purchase dressed up as one, and any honest buyer should ask them before committing spend.
01 Which processes actually cost us the most?
02 How far is our documented process from the real one?
If nobody has compared the map to the mine, the honest answer is "we do not know", and that is the first thing to fix.
03 Who owns each process, by name?
04 What would we point an AI agent at, and is that picture true?
An agent inherits your process picture. If the picture is the designed map, the agent inherits its blind spots. Mine first.
05 Can the people who run the work read the process?
06 Who holds the licence, and who operates it?
A programme that can answer these six with numbers and names is ready to spend. One that answers with intentions and hopes should start with a diagnostic, which costs little and prevents the expensive mistake of automating the map.
A well-run board does not buy on enthusiasm. The four objections below are the ones we meet most often, each reasonable and each answerable, and none dismissed with a slogan. We set them out because an analysis that ducks the hard questions is not worth reading, and because the answers are, in every case, stronger than the objection.
01 “We already have process maps.”
You almost certainly do, and they are almost certainly out of date in the places that cost money. The question is not whether you have maps but whether you have measured them against reality. Most maps are sincere and wrong;
mining tells you by how much. If the comparison shows a small gap, you have spent little to confirm good news. It rarely does.
02 “Mining sounds invasive: new agents on every machine.”
Process mining reads event logs your systems already keep; it records nothing new. Desktop capture does observe how someone works, and it is optional, scoped, and deployed only where the logged systems leave a gap. We are candid that it touches how people work, which is exactly why we scope it narrowly and explain it plainly rather than switching it on everywhere by default.
03 “The ROI numbers are old.”
The Forrester figure is, and we flagged it as a late-2022 study specific to Nintex Workflow rather than to mapping and mining. We do not lean on it as a forecast. Nor do we substitute a customer story. The ones we checked are undated or self-reported, and they would not survive the scrutiny we are asking you to apply. Your own diagnostic produces a figure specific to you, and that is the number worth arguing about.
04 “Why not buy the software direct?”
You can, and the licence is the easy part. The value leaks in the work around it, which is connecting event logs, sorting real deviations from sensible adaptations, keeping owners engaged, and turning a one-off diagnostic into an operating habit. That is judgement and persistence rather than a login, and it is where programmes bought as software alone tend to stall.
Each objection assumes the purchase is the software. It is not. The purchase is a truthful, maintained understanding of how your work runs, and the discipline to act on it. The software is a means; the understanding is the thing you are paying for.
A single worked example shows the whole method more clearly than any amount of description, so here is supplier onboarding, a process every large organisation runs, and one that reliably hides money. The figures below are illustrative, drawn to match the shape mining commonly reveals rather than any one client. This is a walkthrough, not a benchmark.
The documented process is tidy. A request leads to a credit check and a compliance review, then to approval and activation. Interviewed, the team confirms it. On the map, a supplier is live in about fifteen working days, and everyone believes it.
Mined from the procurement and finance logs, the picture changes. The median case takes twenty-six days, not fifteen. Compliance review carries most of the extra. Cases sit in a review queue for days before anyone opens them. And there are not five steps but nine distinct paths, because two regions added their own checks that never reached the manual.
| Measure | Map (as designed) | Mine (as performed) |
|---|---|---|
| Median cycle time | ≈ 15 working days | ≈ 26 working days |
| Distinct paths | 1 | 9 |
| Largest delay | None assumed | Compliance review queue |
| Control adherence | Assumed 100% | Credit check skipped in ~1 case in 12 |
Source: illustrative composite by Volge, 2026, of patterns commonly seen in supplier-onboarding mining. Not a specific client benchmark.
The gap sorts itself. The compliance queue is the cycle-time prize, and the fix is a redesign plus a reminder, not a bot. The skipped credit check is a control exposure to close before it becomes an audit finding. Two of the nine paths are sensible regional checks worth keeping; the rest are drift to standardise. Only then, on the standardised main path, does automation earn its build.
AI Model to Map returns the mined, standardised process to Process Manager as a readable procedure the onboarding owner maintains. Forms captures the supplier's data cleanly at the front; DocGen produces the onboarding pack at the end. The next mining run checks whether the fixes held. They usually do, until the process drifts again, which is why the loop runs continuously rather than once.
A map-and-mine engagement fails on access and authority far more often than on method, and the gating item is never the licence. Six conditions have to hold before the first extract.
The second condition is where the weeks go. Event logs are owned by the teams that run the systems, and an extract is a
request to those teams rather than a configuration change. Make the request in week one.
The order of the five steps is fixed by dependency, as chapter one argued. What chapter one did not supply is the test that says each step is finished, and without those tests a programme drifts from stage to stage on the calendar.
| Step | What it produces | The exit test |
|---|---|---|
| 01 Discover | A process register with an owner against every entry | Every process in scope has a named owner who accepts the description. An entry nobody will own is a finding in itself |
| 02 Map | The designed process, in business language | A person who runs the process reads the map and makes no correction. Until they do, the map is a draft |
| 03 Mine | The performed process, reconstructed from logs and capture | Case counts reconcile against the source system's own totals for the period, within a stated tolerance |
| 04 Compare | A costed gap: variants, waits and deviations, ranked | Every item carries a volume, an elapsed-time cost and an owner. An unranked gap is a report |
| 05 Act | Simplification, automation or a deliberate decision to leave alone | A re-mine of the same process shows the change held. Nothing is closed on the strength of the fix alone |
Source: Volge analysis, 2026. The five steps restate chapter one; the exit tests are the part worth copying.
Step three carries the test most often skipped. If the mined case count does not reconcile against the source system's own totals, the extract is incomplete, and every variant count and cycle time derived from it is wrong by an unknown amount. Reconcile first, analyse second.
Discovery touches personal data, operational systems and the way people work, so its controls are as much about restraint as about coverage. Each of the controls below can be tested in an afternoon.
| Control | What it is | How you test it |
|---|---|---|
| Extract scope | Only the agreed fields leave the source system. | Compare the extract schema against the agreed field list. Surplus fields are the ones a supervisor asks about. |
| Identifier handling | Person-level identifiers are pseudonymised unless the analysis genuinely requires them. | Ask which findings depend on knowing who performed a step. Usually two or three, and the rest do not need the field. |
| Extract reconciliation | Mined case counts agree with source-system totals. | Re-run the comparison for one closed month and state the variance. |
| Retention and deletion | Discovery data expires on a stated schedule, subject to any statutory floor. | Ask for the deletion date of the oldest extract still held, and whether it passed. |
| Capture consent and scope | Desktop capture runs only on agreed populations, with agreed content. | Check the deployed configuration against the agreed scope. They diverge as the pilot expands. |
| Raw-capture access | The raw record of an individual's working day has a narrower access list than the map derived from it. | List who can read the raw capture today. If it is the same list as for the map, the control does not exist. |
| Process ownership | Every mapped process has an owner who maintains it. | Count maps with no edit in twelve months. That count is the decay rate. |
| Finding attribution | Each gap item carries a volume and an owner before it is prioritised. | Take the top five items and name the owner of each without consulting the build team. |
| Model-to-map review | Automatically converted maps are reviewed by an owner before they are published. | Sample converted maps and check for an owner's edit. Automated translation smooths, so a mislabelled step reads as cleanly as a correct one. |
Source: Volge analysis, 2026. Control names are generic, so the set applies whichever mining tool supplies the mine.
The raw-capture test is the one that separates a careful programme from a confident one. Everything else on the list protects the analysis. That control protects the people being analysed, and it is the reason a discovery programme retains its mandate.
Discovery programmes fail in five recognisable ways, and the first four produce a document rather than a change.
01 The unreconciled extract
An extract misses a subset of cases, usually a region or a channel, and the analysis proceeds. In production this looks like a confident variant count and a cycle time that operations does not recognise. The control is the reconciliation at step three, and the symptom is an operator saying the numbers feel wrong.
02 The finding with no owner
The gap is produced, ranked and circulated, and nothing happens because no entry has a name against it. In production this looks like a well-received report that is cited for a year and acted on never. The control is attribution before prioritisation.
03 Map decay
Maps are created during the engagement and never edited again, so within eighteen months the designed process is once more a fiction. In production this looks like a healthy map library with no edit history. The control is the decay rate, counted and reported, because ownership that is not measured is ownership in name.
04 Capture scope creep
Desktop capture is agreed for one team and expands quietly to several, because it is useful. In production this looks like a successful pilot and a growing consent problem. The control is the configuration comparison, run on a schedule rather than at the end.
05 Automating the standardised main path too early
The main path is standardised, declared stable and automated, while the variants it displaced are still being worked out by hand. In production this looks like an automation covering a shrinking share of volume. The control is to re-mine before building, and to require the variant distribution to have settled across two consecutive periods.
Gap closure is the only one of the four that is hard to fake. A closed item requires a re-mine showing the change held, which is why programmes that report closure honestly report lower numbers than programmes that report intent.
Four measures tell you whether process understanding has become a habit rather than a project, and none of them is a count of maps.
| Measure | Definition | Direction | Cadence |
|---|---|---|---|
| Map currency | Share of mapped processes edited within the last twelve months | Rising to a stated floor | Quarterly |
| Variant concentration | Share of cases on the designed path, per process | Rising where standardisation was the decision | Per mining run |
| Waiting share | Elapsed time spent in queues, as a share of total cycle time | Falling | Per mining run |
| Gap closure | Items from the ranked gap closed, with the re-mine confirming the change held | Rising, and evidenced | Quarterly |
Source: Volge analysis, 2026. Definitions are stated so that a figure means the same thing in two consecutive quarters.
A process intelligence programme is finished, in the only sense that matters, when four things are true on the day they are asked about. Every process in scope has an owner who has edited its map this year. A mined picture exists for the processes that carry the most volume, reconciled against source-system totals. The gap between the two is ranked, with an owner and a size against every item. And at least one closed item has been re-mined and shown to have held.
Three of those four can only be demonstrated after a second mining run. That is the honest reason a discovery engagement should not be scoped as a single pass, and it is also why the first pass should be small enough to repeat.
The argument of this book, see the process before you automate it, is not Volge's alone. Independent analysts, working from their own samples, report the same pattern. Programmes that skip process truth stall, and the ones that scale are the exception.
| Finding | Figure | Source |
|---|---|---|
| Firms that had scaled RPA to 50 or more robots | 3% | Deloitte Global RPA Survey, fieldwork Sep 2017 (n=424) |
| Digital transformations that fall short of objectives | 70% | BCG, Flipping the Odds, 29 Oct 2020 |
| GenAI projects forecast to be abandoned after proof of concept by end-2025 | At least 30% | Gartner, 29 Jul 2024 |
| Organisations getting zero return from enterprise GenAI | ~95% | MIT NANDA, The GenAI Divide, Jul 2025 |
| US C-suite respondents calling their GenAI rollouts “mature” | 1% | McKinsey, Superagency in the workplace, 28 Jan 2025 |
Sources independent of Nintex and Volge; full citations in the Sources annex.
Read down the column and one story repeats. The tooling scales faster than the understanding beneath it, and the gap is where the money leaks. Deloitte's 3 per cent, from fieldwork in September 2017, is the share of firms that had scaled RPA to fifty or more robots; the rest stalled, and Deloitte's November 2018 survey put the figure at 4 per cent. The most common reason, across these studies, is that the process the software was pointed at was not the process the business actually ran.
The 2025 figures sharpen the point, with two qualifications. Gartner forecast on 29 July 2024 that at least 30 per cent of GenAI projects would be abandoned after proof of concept by the end of 2025, and has published no outturn, so that remains a lapsed forecast rather than a result. The NANDA paper of July 2025 found that 95 per cent of organisations, not of pilots, were getting zero return. Both point the same way. Agents are being aimed at operations no one has measured against reality, which is the readiness layer this book is about.
A serious argument should survive contact with sources that have no stake in it. Every figure above comes from a body independent of both the vendor and its partner. One needs a caveat. The GenAI Divide carries the MIT NANDA masthead
but is the work of its four named authors, who disclaim institutional attribution, and it has not been peer-reviewed.
This book follows a small set of rules designed to keep a disclosed-interest analysis honest, and we state them so you can hold us to them. Every external figure is attributed and dated. Vendor positioning is labelled as positioning. Market sizing is labelled as estimate. Illustrative figures are labelled as illustrative. Our commercial interest is disclosed wherever it bears on the argument.
Where a number comes from Nintex, we say so and give the date. Where it comes from a third party, Market.us, Forrester, G2, TrustRadius, we name the source. The Forrester ROI figure is flagged as a study conducted in late 2022 and specific to Nintex Workflow, not to the mapping capability that is this book's subject. The market-size figure is a Market.us estimate of September 2025, and the interpolated years in Exhibit 2 are our own arithmetic at the stated growth rate, marked as such.
Exhibits 10 and 12, where time is lost and how variants distribute, are illustrative composites rather than measurements of a named client. They show the shape mining typically reveals, and they are labelled so no reader mistakes a representative pattern for a benchmark. Your own numbers are the only ones that matter, and finding them is the first piece of work.
We make no claim that Nintex is a Gartner Magic Quadrant leader. Forrester placed Nintex as a Strong Performer, not a Leader, in The Forrester Wave: Agentic Process Orchestration Platforms, Q3 2026, and we name the placement rather than imply more than it says. We do note that process mining is an analyst-recognised category, and Gartner has published a Magic Quadrant for Process Mining Platforms (April 2025). We describe Process Intelligence as Nintex positioning rather than a product, and we record that the mining half of it is now end-of-life.
Volge is a Nintex delivery partner and benefits if you buy. We have handled that conflict by sourcing every external claim independently, including the analyst figures on page 31, which come from Deloitte, BCG, Gartner, the MIT NANDA authors and McKinsey, none of whom have a stake in this book, labelling our estimates, and keeping the first step small.
If any figure here has aged or any attribution is wrong, we would rather know. A field guide is only useful while it is accurate, and this is a first edition.
Deloitte Global RPA Survey (fieldwork September 2017, n=424) found that 3% had scaled RPA to fifty or more robots; its November 2018 survey put the figure at 4%. BCG, Flipping the Odds of Digital Transformation Success (29 October 2020), found 70% of digital transformations fall short of objectives. Gartner (29 July 2024) forecast that at least 30% of GenAI projects would be abandoned after proof of concept by end-2025, and has published no outturn. MIT NANDA, The GenAI Divide (July 2025), found ~95% of organisations getting zero return from enterprise GenAI; the paper is not peer-reviewed and its authors disclaim institutional attribution. McKinsey, Superagency in the workplace (28 January 2025), found 1% of US C-suite respondents calling GenAI rollouts “mature”. Gartner Magic Quadrant for Process Mining Platforms (April 2025). None have a stake in this book.
Volge-analysis exhibits and the illustrative composites (labelled inline) are our own; interpolated market years are Volge arithmetic at the stated CAGR.
Tear-out version. Six questions from the operator's read (page 27), on a single page you can take into a meeting.
| Ask | If the answer is vague |
|---|---|
| Which processes cost us most? | Mine before you automate |
| How far is the map from reality? | Run the comparison first |
| Who owns each process, by name? | Assign ownership before tooling |
| Is our AI target picture true? | The agent inherits your blind spots |
| Can operators read the process? | Insight will stall at the analyst's desk |
| Who holds and operates the licence? | Decide, or it becomes shelfware |
Source: Volge analysis, 2026. See page 27.
Process intelligence is the lightest of the three layers to buy, but not free of prerequisites. Two lists follow. The first names the Nintex elements to licence, the second the non-Nintex pieces that must already be in place for a map-and-mine
engagement to produce anything. Process mining is not among the Nintex elements, because Nintex Process Discovery is end-of-life, so a mining tool, where one is needed, comes from elsewhere. Tiers are indicative for 2026; confirm current SKUs with Nintex.
| Nintex Process Manager (Promapp) | The mapping and operating-procedure library. Platform subscription, priced by user. |
|---|---|
| Nintex Processes | Process management native to the CE Platform, launched 26 October 2026. Nintex calls it the next evolution of Process Manager. |
| Process Capture | Desktop activity capture into draft maps. Included in Expert and Enterprise tiers; an add-on elsewhere; not offered in the AEN region. |
| AI Model to Map Converter | Converts BPMN models into readable procedures. GA December 2025. Expert and Enterprise tiers; an add-on on Professional. |
| Process Manager MCP | Read-only process knowledge for AI assistants. Open beta; no charge published. |
| Source-system event logs | ERP, CRM, or ITSM logs, or their exports. You cannot mine what you cannot extract. |
|---|---|
| Identity / single sign-on | Microsoft Entra ID or a SAML provider, for user access. |
| Data-governance clearance | Sign-off to pull operational logs, with privacy and retention rules agreed. |
| Process owners' time | Named owners to validate the mined maps against how work really runs. |
Nothing here needs a server or a data-centre. The gating item is not a licence, it is access to the logs, and the owners' time to read what the mine finds.
Plain definitions of the terms used in this book, in the sense we have used them.
| Term | Definition |
|---|---|
| Process as designed (the map) | How a process is meant to run, as documented. Held in Nintex Process Manager. |
| Process as performed (the mine) | How a process actually ran, reconstructed from event logs and desktop capture. |
| Nintex Process Manager | Business process mapping and modelling. Formerly Promapp; rebranded 2022. Tagline: identify, map, and model your processes. |
| Nintex Processes | Process management native to the Nintex CE Platform, launched 26 October 2026. Nintex calls it the next evolution of Process Manager, not a replacement. |
| Nintex Process Intelligence | Nintex's positioning term for mining, task mining, modelling and mapping, never a confirmed standalone SKU. The mining half was delivered by Nintex Process Discovery. |
| Nintex Process Discovery | The retired mining and task-mining product. End-of-life announced 4 May 2026: end-of-life 1 May 2027, support ends May 2028, customers migrated to Process Manager. |
| Process mining | Reconstructing the real sequence and timing of a process from event logs. |
| Event log | The timestamped record enterprise systems keep of what happened: the raw material of mining. |
| BPMN | Business Process Model and Notation, the technical notation mining produces, which AI Model to Map renders business-readable. |
| AI Process Generator | Drafts a process map from a description. Beta March 2025; GA June 2025, Professional tier and above. |
| Process Capture | Activity recording that auto-documents a task as performed. GA September 2025, release 4.12.22.0. |
| AI Model to Map | AI Model to Map Converter in the product. Converts technical BPMN into business-readable procedures. Beta September 2025; GA December 2025, release 4.12.27.0. Bridges mine to map. |
| Process Manager MCP | A Model Context Protocol server exposing approved process knowledge to AI assistants, read-only. Open beta from 13 August 2026; authentication for eleven clients in release 4.26.23, October 2026. |
| Nintex DocGen | Generates documents from process data. An enhancer. |
| Nintex Forms | Captures structured data into a process. An enhancer. |
| The gap | The difference between the designed map and the mined reality, variants, bottlenecks, deviations, and the costed worklist it forms. |
| Variant | A distinct path cases actually take through a process, often undocumented. |
| IPA | Intelligent process automation: the market category sized in Exhibit 2. |
Every external claim in this book, with source and date. Listed in order of first appearance.
Volge produces an honest account of how a client's work actually runs, and then works the distance between that and the designed process. The practice sits where this book locates the money, in the gap between the map and the mine, which is to say in the undocumented variants, the queues that hold most of the elapsed time, and the controls quietly skipped at scale. Delivery is by senior process and data practitioners who run the extract and the analysis themselves, inside the client's own environment.
The work has a usual shape, and it follows the five steps of chapter one with the exit tests of chapter six attached. Discovery builds the register and names an owner against every entry. Mapping produces a document a person who runs the process reads without correcting. Mining reconstructs the performed process and reconciles its case counts against the source system's own totals before any finding is drawn from it. The comparison then produces a ranked gap in which every item carries a volume, an elapsed-time cost and an owner. Acting on it closes with a re-mine, because a fix nobody has re-measured is a hope.
Nintex no longer sells a mining product, and that changes the sourcing rather than the method. Nintex Process Discovery was placed end-of-life on 4 May 2026, with end-of-life on 1 May 2027 and support ending in May 2028. So the mine comes from Process Capture at the desktop, from a sampled log analysis run by hand, or from a third-party mining tool a client already owns. The map and the comparison stay inside Nintex Process Manager, now surfacing as Nintex Processes.
Who does the work. A deployment strategist holds the business outcome and the governance cadence with the client's operations leadership. A transformation architect owns the method, the extract scope and the reconciliation, and signs the findings. Process analysts work alongside the client's own process owners rather than in place of them, because a map maintained by a consultant decays on the day the engagement ends. The same people stay from the first extract through the re-mine, which is what makes the control tests in chapter six drills the team has run.
The regional position is often what a Gulf or Indian client needs first. Volge is headquartered in the Gulf, and the sequencing set out in chapter five is applied rather than described. The lawful basis and any prior authorisation are settled before the first extract, which in Bahrain means establishing whether Article 15 of the Personal Data Protection Law reaches the design. Classification comes before discovery in Oman and Saudi Arabia, because there the classification decides whether the extract may leave at all. And the event-log position is documented separately from the desktop-capture position, because the two are different activities in law.
An engagement starts with a scoped diagnostic on one process, usually three to five weeks. It produces a map the process owner accepts, a mined picture reconciled against source-system totals, a ranked gap with an owner and a size against each item, a stated position on the lawful basis and the residency of the extract, and a re-mine date. Volge is a Nintex delivery partner and benefits commercially if a client buys, which a reader should weigh against the recommendations in this book. The conversation begins wherever the landscape stands today.
Volge is an engineering firm providing enterprise technology transformation services to clients across the Middle East, India, APAC, Europe, and North America.
Delivery stands on two pillars: Forward Deployed Engineering, with senior specialists embedded in the client’s own team, and Intelligent Command Centre Operations, run from our Global Delivery Centres, which keeps what they build running. Senior engineers stay with an engagement from the first diagnosis through to production.
Our services span Strategy, Data, Platforms, AI and Automation, Cyber Trust, Technology Operations, and Applied Functional Engineering. Engagements begin with a diagnosis. The firm is built on working autonomy: engineers decide, innovate, co-create, and own their work. Motivated engineers build the systems that sustain our clients’ growth.
This edition may be shared with organisations evaluating a Volge engagement. It may not be altered or republished without Volge’s permission, and figures carry their stated basis and date. Volge, Intelligent Command Centre, and Intelligent Command Centre Operations are marks of Volge; other names are the trademarks of their respective owners.