Contents
Pilots impress. Production pays.
The Voice of Volge is Volge’s thought-leadership series, unsigned and institutional, every figure sourced, quantified and year-stamped. Volge is a Nintex delivery partner; interest disclosed.
volge.com/voice
About Nintex
Nintex is a process-and-automation software company. What began as SharePoint-era workflow is now a single platform that maps, mines, automates and, since 2025, orchestrates AI agents against work, built out over two decades and a handful of pointed acquisitions.
The recent chapters matter most to a buyer today: Agentic Business Orchestration (Sept 2025), a rebuilt global partner programme, locally-hosted AI in Automation K2 5.9.1 (Apr 2026), and Agent Designer + Nintex Orchestration entering beta.
The platform today: one landscape
This report covers Workflow Automation, the Build & run layer, where the work is built and run at scale across the business.
| Understand | Process Manager · Process Intelligence |
| Build & run Focus of this report | Automation CE · Automation K2 (on-prem) · RPA · DocGen · Forms · eSign |
| Orchestrate | Agentic Business Orchestration · Agent Designer (beta) · Nintex Orchestration (beta) |
In the field: independent proof
Source: Nintex customer stories and G2/TrustRadius, 2022–26. Customer outcomes as reported by Nintex.
What this means for a buyer in 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.
The pilot is cheap. The production system is expensive.
The demo is quick, impressive, and inexpensive. The production system is governed, integrated, and paid back. This book is about crossing from the first to the second.
Why most automation stalls, and what makes the survivors scale
Begin with the uncomfortable number. More than 40% of agentic-AI projects will be cancelled by the end of 2027, Gartner said on 25 June 2025, on escalating cost, unclear value, and weak risk controls. That is not a forecast about bad models. It is a forecast about bad plumbing. The models arrived; the governance, the integration, and the deterministic substrate did not.
The pattern repeats across every serious study of the past eighteen months. MIT's Project NANDA found that roughly 95% of generative-AI pilots produce no measurable profit-and-loss impact, and only about 5% reach rapid revenue acceleration (The GenAI Divide, 18 August 2025). S&P Global reported that 42% of companies had abandoned most of their AI initiatives, up from 17% a year earlier, and that around 46% of proofs of concept were scrapped before production (14 March 2025). Deloitte, taking the more generous view, still found only a quarter of enterprises had moved at least 40% of their pilots into production (State of AI in the Enterprise 2026, 21 January 2026).
Read together, these are not four opinions. They are one finding, measured four ways: the pilot is easy and the production system is hard, and almost everyone is stuck on the wrong side of that gap.
The next era of automation isn't just about automating what's in front of us; it's about orchestrating across people, systems and AI agents to deliver outcomes at scale.
, Amit Mathradas, then Nintex CEO, September 2025The reason the survivors ship is unglamorous. They stop treating the agent as the whole system and start treating it as one component inside a governed workflow. Judgement goes to the AI where judgement adds value. Precision goes to a deterministic workflow where compliance and repeatability are non-negotiable. A human sits at the control points that matter. That is the shape of the systems that reach production, and it has a name.
The one-sentence thesis
Agent pilots fail as pilots and succeed as orchestration: a deterministic-workflow substrate carrying probabilistic AI, under one governed framework, with a human in the loop where it counts.
Nintex calls the answer Agentic Business Orchestration, or ABO: structured workflow executions, AI-driven decision-making, and human control, held together in a single framework. Unveiled on 24 September 2025, it is a deliberate refusal of the binary that has wrecked so many programmes: the belief that a system must be either fully agentic or fully hard-coded.
AI for modern business cannot be purely agentic, nor purely deterministic; it must support both.
, Niranjan Vijayaragavan, Chief Product & Technology Officer, NintexThe rest of this report is the case for that sentence, built out for a reader who signs cheques. Part I sets the failure data on the table, because a board that has not seen the numbers will underrate the risk of doing nothing well. Part II explains the hybrid and draws it, so the mechanism is legible rather than asserted. Part III walks the ladder from pilot to enterprise and names the substrate that carries the weight. Part IV does the economics, return, proof, and the buy-versus-build question that quietly decides most of these programmes. Part V is the operator's read: a checklist, our role, and the annex.
Two of those figures deserve a moment. Buying from a specialist succeeds about twice as often as building in-house: a two-to-one advantage that survives most attempts to argue it away. And of the crowd of vendors selling the word "agentic", Gartner counts only around 130 that mean it. The market is loud; the signal is thin. Choosing well is most of the work.
How to read the exhibits
Every chart and table in this report carries its own data and its own source line. The prose makes the argument; the exhibits carry the evidence. Where a number is an estimate rather than a measured result, we say so on the exhibit itself.
The failure data, without the flattery
The case against doing nothing well is quantitative, and it is grimly consistent. Four independent bodies measured the same thing, the share of AI ambition that never reaches production, and arrived at figures that rhyme. We put them on one axis below, and note where each is measuring pilots, projects, or companies, because the denominators differ.
The Gartner line is the sharpest, because it is about agentic projects specifically and it is a commitment about the near future, not a description of the past. More than 40% of agentic-AI projects will be cancelled by the end of 2027, the firm said, and the causes it named, escalating cost, unclear value, weak risk controls, are governance failures, not model failures.
A single bad year could be a blip. A worsening trend is a signal. S&P Global's finding is not merely that 42% of companies abandoned most of their AI initiatives; it is that the figure rose from 17% the year before. Enthusiasm collided with delivery, and delivery won.
(14 Mar 2025)
Deloitte's State of AI in the Enterprise 2026 (21 January 2026) offers the most flattering framing available, and it still lands hard. Only a quarter of enterprises have moved at least 40% of their pilots into production. Put the other way, three-quarters have not, which means most organisations are running a lab, not a business line, and paying for both.
None of this argues against agents. It argues against a particular way of buying and building them: as isolated pilots, without governance, without integration into the systems that run the company, and without a deterministic floor to stand on. We turn to that diagnosis next.
A note on one number we will not use
A widely circulated claim that "89% of AI projects never scale" appears in several vendor decks. We cannot trace it to a primary source we trust, so we leave it out. The figures above are enough, and they are attributable.
Why pilots stall
Pilots stall for four reasons, and none of them is model quality. They stall on hype, on poor integration, on the absence of governance, and on the missing deterministic substrate. The first is a marketing problem; the other three are engineering and operating problems, and they are the ones that cost money.
Hype sets the trap. A demo that works on a curated example creates the impression that the hard part is done, when in fact the hard part has not started. The demo runs once, cleanly, in a sandbox. Production runs ten thousand times, messily, against live systems, with auditors watching. The gap between those two conditions is exactly where the 95% of pilots with no P&L impact go to expire.
An agent that cannot reach the ERP, the CRM, the document store, and the approval chain is an expensive chatbot with API access. Most pilots are built against mock data or a single system, then fail when asked to reach across the six systems a real process touches. Integration is not a feature you add later; it is the substance of the work, and pilots that defer it are deferring the moment of failure, not avoiding it.
A probabilistic system makes different choices on different runs. That is tolerable in a brainstorming tool and intolerable in a payments run, a claims decision, or a regulatory filing. Without controls, who approved this, on what data, under which policy, with what audit trail, a promising agent becomes an unmanageable liability the moment it touches anything that matters. Gartner's "weak risk controls" is this, precisely.
The deepest reason is architectural. Teams reach for a purely agentic design because it demos well, then discover that the parts of the process which must be exact, the compliance checks, the sequencing, the mandatory steps, cannot be left to a model that improvises. Lacking a deterministic floor to stand on, the whole system inherits the variance of its least reliable component. This is the failure the hybrid is built to prevent, and it is the subject of Part II.
The four stall points, in order of cost
Hype creates the false start. Poor integration breaks the demo against live systems. Missing governance makes the result unusable where it matters. And the absent deterministic substrate makes the whole thing unreliable by construction. Only the first is cosmetic.
Every stall point has a corresponding fix, and the fixes are not exotic. They are the ordinary disciplines of running production software, applied to a new kind of component. The table maps the diagnosis to the remedy that Agentic Business Orchestration supplies.
| Stall point | Why the pilot dies | What production actually needs |
|---|---|---|
| Hype | A curated demo implies the hard work is finished when it has barely begun. | An honest maturity model that treats the demo as rung one of several. |
| Poor integration | Built against mock data or one system; breaks across the six a real process touches. | Native connectors and a workflow engine that reaches live systems of record. |
| No governance | Non-deterministic choices with no audit trail, unusable where compliance bites. | A governed, low-code environment with approvals, policy, and traceability. |
| No deterministic floor | The exact steps are left to a model that improvises, so variance spreads. | Conditional workflow control where precision and compliance are required. |
Notice that three of the four remedies have nothing to do with the model and everything to do with the system around it. This is why the buy-versus-build gap is so wide: the model is the commodity, and the governed substrate that makes it safe to run is the scarce, expensive, specialist part. Building that substrate in-house is where most internal programmes lose the two-to-one bet against them.
The through-line to Part II
If the failures are governance and architecture failures, the fix is a governance and architecture fix: a deterministic workflow substrate carrying AI decisioning, under one framework, with a human at the controls. That is Agentic Business Orchestration, and it is where we go next.
Five ways an automation stalls, and what each one needs
The stall points from the last section resolve into five recurring failure modes. Each is a way a pilot dies, and each has a single answer inside Agentic Business Orchestration. The card set names the failure, states the stall in a line, then gives the answer.
The stall. The exact steps, sequencing, mandatory checks, compliance gates, are left to a model that improvises, so variance leaks into work that has to be exact.
The answer. Structured workflow executions run the mandatory steps the same way every time; the model is asked to judge, never to improvise the floor.
The stall. Built against mock data or a single system, the agent breaks when a real process reaches across the six systems of record it actually touches.
The answer. Nintex Automation CE reaches the ERP, the CRM, and the document store through native connectors, so the orchestration runs against live systems rather than a sandbox.
The stall. An agent allowed to act without approval gates, policy, or an audit trail turns into a liability the moment it touches a payment or a filing.
The answer. Agent Designer builds inside a governed, low-code environment, so approvals, policy, and lineage are inherited by default rather than added after the fact.
The stall. A pilot with no measured profit-and-loss line cannot defend itself when the budget is reviewed: which is where Gartner says the money is pulled.
The answer. The orchestration is scoped to one named process and measured against it, cycle time, exception rate, cost per case, so value is reported, not asserted.
The stall. An agent asked to reason over inconsistent, unlabelled, or unreachable data inherits the mess and repeats it at speed.
The answer. Nintex Forms captures structured input at intake, and the deterministic workflow validates and logs it before the AI lane reads anything.
Why five, not fifty
Every autopsy we have read reduces to one of these five. A programme that can place its own failure on this card set can also find its remedy on it, which is the point of naming them.
When Gartner said more than 40% of agentic-AI projects would be cancelled by the end of 2027, it named three reasons: escalating cost, unclear value, and inadequate risk controls (25 June 2025). Those three are the five failure modes, grouped. The table maps each stated reason to the failure beneath it and the ABO control that retires it.
| Gartner's stated reason | The failure beneath it | The ABO control that answers it |
|---|---|---|
| Escalating cost | Integration rebuilt for every pilot; sprawl compounding the cost to run. | Connectors built once on Nintex Automation CE and reused; one framework consolidates the sprawl. |
| Unclear value | Pilots with no measured P&L line, unable to survive a budget review. | Process-scoped measurement against a named baseline, cycle time, exception rate, cost per case. |
| Inadequate risk controls | Ungoverned autonomy over a non-deterministic floor, with no audit trail. | Agent Designer governance, a deterministic workflow floor, human control points, end-to-end audit. |
The mapping carries a quiet implication. None of the three reasons is a complaint about model quality, and none is answered by a better model. Each is answered by the system built around the model, the substrate, the governance, the measurement. This is why buying a proven platform beats building one, a point Part IV puts a number against.
The test a board can apply
Ask which of Gartner's three reasons your programme is most exposed to, then ask which control retires it. If the answer is "a better prompt", the programme is still on rung one.
Agentic Business Orchestration, explained
Agentic Business Orchestration is a hybrid, and the hybrid is the point. Nintex unveiled ABO on 24 September 2025 as the combination of structured workflow executions, AI-driven decision-making, and human control inside a single governed framework. The design principle is stated plainly: AI where judgement adds value, conditional workflow control where precision and compliance are critical.
The wager behind that principle is a refusal. Most failed programmes bet on one pole, either a fully agentic system that improvises everything, or a fully deterministic one that cannot adapt. ABO bets on neither, and puts a governed seam between them so that each does the work it is suited to.
AI for modern business cannot be purely agentic, nor purely deterministic; it must support both.
, Niranjan Vijayaragavan, Chief Product & Technology Officer, NintexStructured workflow executions are the deterministic floor. They run the exact, repeatable, auditable steps, the sequencing, the mandatory checks, the compliance gates, the same way every time. This is the part a model must never be allowed to improvise.
AI-driven decision-making is where judgement lives. When a step requires reading unstructured input, weighing ambiguous evidence, or choosing among options, the AI decides, and hands its decision back to the workflow to execute. Judgement is used deliberately, not everywhere.
Human control is the third leg, not an afterthought. People sit at the control points, approvals, exceptions, escalations, where accountability must rest with a person. The human is in the loop by design, at the places the design chooses.
Why "orchestration" is the right word
An orchestra is many instruments under one score and one conductor. ABO is deterministic workflow, probabilistic AI, and human judgement under one governed framework. The value is not in any one player; it is in the coordination: which is exactly the capability isolated pilots lack.
The choice is usually framed as agentic versus deterministic, as if those were the only options. They are the two ways to fail. The table sets both against the hybrid, on the dimensions a production owner actually cares about.
| Dimension | Pure agentic | Pure deterministic | ABO hybrid |
|---|---|---|---|
| Handles ambiguity | Yes | No | Yes, via AI decisioning |
| Repeatable & exact | No: improvises | Yes | Yes, on the workflow floor |
| Auditable trail | Weak | Strong | Strong, governed end to end |
| Adapts to change | Yes | No: brittle | Yes, where change is expected |
| Compliance-safe | Risky | Yes | Yes, precision where it counts |
| Human accountability | Unclear | Rigid | Designed-in control points |
| Reaches production | Rarely | Often, but limited | Built for it |
The pure-agentic column is where the demos come from and where the 95% go to die. The pure-deterministic column is safe but cannot cope with the ambiguity that real processes throw at it. The hybrid column is the only one that answers "yes" down the whole list, and answering yes down the whole list is what shipping to production requires.
ABO also does something a board will value directly: it consolidates. Instead of a drawer of disconnected AI pilots, each with its own risk profile and its own integration debt, one framework carries them all. We return to that consolidation argument in Part III; here it is enough to note that the hybrid is the thing that makes consolidation possible.
One process, three kinds of work, one governed framework
A claims-style process, drawn as ABO runs it. The deterministic workflow carries the sequence; AI decisioning handles judgement; a human holds the control point. Governance wraps the whole run.
One governed framework wraps every lane: identity, policy, approvals, data lineage, and a full audit trail across the whole run, so a probabilistic decision inside a deterministic process is always accountable to a person and a policy.
The diagram makes the earlier abstraction concrete. Judgement sits in the AI lane and nowhere else; precision is guaranteed in the workflow lane; the human lane carries accountability. Nothing is left to improvisation that should not be, and nothing is hard-coded that needs to flex.
One invoice exception, walked end to end
An invoice arrives quoting a price the purchase order does not. A pure deterministic system kicks it to a human queue; a pure agentic system guesses. ABO does neither: it reads the mismatch, judges whether it sits inside tolerance, clears what it can, and pulls a person in only for what it should.
Every clearance, by the AI within tolerance or by the approver above it, is written to the same audit trail, against the policy and the person accountable for it.
Where control holds. The three-way match is deterministic and stays that way. An invoice clears only when the purchase order, the goods receipt, and the invoice agree within a policy the workflow enforces identically on every run. The posting to the ERP and the audit record are equally fixed. None of this is a matter of judgement, so none of it is handed to the model.
Where AI decides. Judgement begins where the numbers disagree. The AI lane reads the invoice, classifies the mismatch as price, quantity, or tax, and weighs it against the tolerance and the supplier's history. A £40 overcharge from a supplier with a clean record and a standing tolerance is a different object from the same overcharge on a first invoice from an unknown vendor. The AI proposes a decision and a confidence, then hands both back to the workflow.
Where a person is pulled in. The approver sees only what should reach a person: the out-of-tolerance cases, the novel suppliers, the recommendations the AI itself flags as low-confidence. The approver approves, adjusts, or rejects, and the reason is logged. Everything the AI cleared within tolerance never troubles a human at all, which is the entire economic point.
| Step | Who acts | Kind of work | Control |
|---|---|---|---|
| Receive & match | Workflow | Deterministic | Same rule every run |
| Read & classify mismatch | AI lane | Judgement | Confidence returned |
| Assess against tolerance | AI lane | Judgement | Policy-bounded |
| Clear within tolerance | Workflow | Deterministic | Logged, auditable |
| Out-of-tolerance case | AP approver | Human control | Reason recorded |
| Post & close | Workflow | Deterministic | Written to ERP + audit |
The reading that generalises
Swap invoice-exception for claims triage, customer onboarding, or contract intake and the lanes do not move. The deterministic floor carries the mandatory steps, the AI lane carries the ambiguous ones, and the person carries the accountable ones. The process changes; the division of labour does not.
Agent Designer and Nintex Orchestration
A framework is only as good as the environment in which people build on it. Two capabilities carry ABO from principle to practice, and both entered open beta on 17 March 2026, with a further update on 3 June 2026.
Agent Designer is the governed, low-code environment required for mission-critical operations. "Governed" and "low-code" are doing equal work in that phrase. Low-code means the people who understand the process can build the agent without a platform team as a bottleneck. Governed means what they build inherits policy, approvals, and audit by default, rather than bolting them on later, which, as Part I showed, is where pilots fail.
Nintex Orchestration provides modular, phase-based workflows. A process is broken into phases that can move forward, jump back, or repeat, the control flow that real operations need, rather than the straight line that only demos require. It is in open beta as of July 2026, with general availability expected later in 2026; we describe it as in beta because it is.
Together, Agent Designer and Orchestration are the reason ABO is a platform rather than a slogan. One gives builders a governed place to work; the other gives processes a shape that matches how they actually run. Neither is exotic. Both are the ordinary machinery of production software, which is exactly what pilots were missing.
Answering “inadequate risk controls”
Of the three reasons Gartner gave for cancelled agentic projects, the one an operator can do least about after the fact is inadequate risk controls (25 June 2025). Cost can be renegotiated and value can be re-measured, but a system built without controls cannot have them retrofitted once it is touching money. Controls are an architecture decision, taken at the start or not at all.
ABO takes that decision at the start through Nintex Agent Designer, the governed, low-code environment required for mission-critical operations. Three controls do most of the work, and each maps to a question an auditor will actually ask.
Every decision in a run is recorded: what was decided, on what data, under which policy, by the AI or by a person. A probabilistic choice inside a deterministic process is only acceptable if it leaves a trail, and the trail is written by default rather than reconstructed later. The question it answers: show me why this happened.
Defined points in the flow require a sign-off before execution continues. A gate is not a suggestion the workflow may skip under load; it is a stop the deterministic floor enforces. Gates sit where policy or value demands a person, and nowhere else, so they add friction only where friction is the point. The question it answers: who agreed to this before it ran.
Accountability rests with a named person at the control points, approvals, exceptions, escalations. The human is placed by the design, not summoned by a failure, and the action is logged as the accountable act. The question it answers: who owns the outcome.
Governed and low-code, doing equal work
Low-code lets the people who understand the process build the agent. Governed means what they build inherits audit, gates, and human control by default. Take either word away and Agent Designer becomes the thing that failed in Part I.
Controls are worth listing precisely, because a board signs against a list, not a principle. The table sets each control beside what it does and the evidence it leaves, the record an auditor, a regulator, or a post-incident review will ask to see.
| Control | What it does | The evidence it leaves |
|---|---|---|
| Identity & policy | Binds every action to an authenticated actor and the policy in force. | Who acted, under which rule. |
| Approval gate | Halts execution until a required sign-off is given. | The approver, the timestamp, the decision. |
| Human control point | Routes exceptions and escalations to a named owner. | The person, the override, the reason. |
| Data lineage | Traces the inputs a decision was made on. | The source records, versioned. |
| Audit trail | Writes the whole run, AI and human alike, to one record. | The end-to-end account of what happened. |
A probabilistic decision inside a deterministic process is acceptable only when it is accountable to a person and a policy.
: The governance principle behind ABOThe controls are deliberately ordinary. They are the disciplines any regulated operation already applies to its people, extended to a new kind of actor. That is the reassuring part: making an agent auditable does not require a new theory of control, only that the control be built in rather than promised.
Three claims carry into Part III. First, the production-grade architecture is a hybrid, not a pure design. Second, the hybrid needs a governed, low-code build environment, Agent Designer, or it recreates the governance gap that killed the pilots. Third, real processes need phase-based control flow, which Nintex Orchestration supplies, in beta.
AI where judgment adds value, conditional workflow control where precision and compliance are critical.
, The ABO design principle, Nintex, 24 September 2025The architecture is settled. The remaining question is the one boards actually lose sleep over: can it scale from a single working process to the enterprise, without the whole thing turning back into a pile of pilots? That is Part III, and it depends on a substrate strong enough to build and run on.
The bridge to Part III
A governed hybrid solves the architecture problem. Scaling it solves the operating problem, and scaling needs a build-and-run substrate, a maturity path, and a way to consolidate rather than multiply the pilots. We turn to all three next.
Pilot to production, one rung at a time
Deloitte found only a quarter of enterprises have moved 40% or more of their pilots into production. The other three-quarters are stalled on a rung. The ladder makes the rungs explicit, so a programme knows where it is and what the next step costs.
One governed framework across the business
Multiple processes run under shared governance, monitoring, and control. Consolidation replaces sprawl. This is the state Deloitte's top quarter approaches.
Live, governed, measured against P&L
The process runs against systems of record with audit, approvals, and human control points. Value is measured, not asserted.
Connected to real systems, with governance
The agent reaches the ERP, CRM, and document store; controls and audit are in place. This is the rung most pilots never reach, and where most die.
Works on real data, in a sandbox
The process runs end to end on representative data, but not yet against live systems. Promising, and dangerous if mistaken for done.
Works once, on a curated example
Impressive, cheap, and misleading. The hype rung. Ninety-five per cent of the P&L-impact failures begin their life here.
The ladder is ours, not a standard
We built these five rungs as a planning heuristic, not a validated maturity model. Use them to locate a programme honestly, not as an industry benchmark, and not as a number to quote back to us. The Deloitte and Gartner figures around them are independent; the rungs themselves are Volge's framing.
Climbing is not automatic. Each rung adds a discipline the last one lacked, and each has an owner. The table is a planning aid: it tells a programme what to add next and who is accountable for adding it.
| Rung | State | What you add to climb | Owner |
|---|---|---|---|
| 1 | Demo | Real, representative data instead of a curated example. | Process team |
| 2 | Contained pilot | Live connectors to systems of record; the integration work. | Platform + Volge |
| 3 | Integrated pilot | Governance: approvals, policy, audit, human control points. | Risk + Volge |
| 4 | Production at scale | Monitoring and P&L measurement; run-book and support. | Operations |
| 5 | Orchestrated enterprise | Shared framework across processes; consolidation of pilots. | COO / CIO |
The ladder also reframes the buy-versus-build question. Every rung above the demo is substrate work, connectors, governance, monitoring, and substrate work is exactly what specialist platforms have already built and internal teams have to build from scratch. The 67% versus 33% success gap between buying and building, which we detail in Part IV, is this ladder measured in outcomes.
A blunt planning rule
If your programme cannot name which rung each process is on, it is on rung one. The value of an explicit ladder is that it makes "we have a pilot" a precise statement instead of a comforting one.
What the orchestration stands on
Every orchestration needs an engine to build on and run on, and for ABO that engine is Nintex Automation CE: the build-and-run substrate. It is the part that reaches the systems of record, executes the deterministic workflow, and gives the AI and human lanes somewhere to plug in. Pricing starts from $15,000 a year, which sets a concrete floor under a programme's economics.
The substrate matters because it is precisely what internal builds underestimate. A team can stand up an impressive agent in a fortnight; standing up the governed, integrated, always-on engine beneath it is the work of many quarters, and it is the work Nintex Automation CE removes.
On top of the substrate sit capabilities that agents invoke as building blocks, rather than features to be admired in isolation. An orchestration composes them into a process; it does not treat each as a separate product. Four are worth naming.
| Capability | What an agent uses it for |
|---|---|
| Nintex RPA | Task automation across applications. Two lines run today: Nintex RPA (formerly Kryon) is the strategic go-forward product; Nintex RPA LE (formerly Foxtrot) continues alongside it. |
| Nintex DocGen | Document generation from process data, including a DocGen Agentforce connector for Salesforce, so generation composes into a CRM-driven flow. |
| Nintex Forms | Structured data capture at the front of a process, feeding clean input into the workflow and the AI lane. |
| Nintex eSign | Electronic signature at the control points where a signature is the accountable act. |
One way to read the whole platform is as a stack. The substrate runs and reaches; the enhancers supply capability; Agent Designer governs the build; ABO orchestrates the three lanes into a process. The diagram stacks them in that order.
Then-Nintex CEO Amit Mathradas framed the ambition in September 2025 as orchestrating "across people, systems and AI agents to deliver outcomes at scale." (He left for Five9 effective 2 February 2026; we attribute the line to him as then-CEO and name no successor.) The stack is that sentence rendered as architecture.
The capabilities an agent composes
Nintex RPA (formerly Kryon) is the strategic go-forward line, current release v25.11. It gives an agent hands: attended and unattended automation across applications that expose no API, so screen-level work can be delegated rather than left undone.
Nintex RPA LE (formerly Foxtrot) is maintained alongside it. Existing desktop automations keep running and stay supported; new work belongs on the go-forward line, not here.
Turns process data into a finished document, a quote, a contract, a letter, without a person retyping what the system already holds. The DocGen Agentforce connector composes generation into a Salesforce-driven flow, so a decision taken in the CRM produces the paperwork that follows it.
Called, not opened
Each capability is something an orchestration invokes at the right step, not a destination a user visits. The value is in the composition, which the substrate runs and Agent Designer governs.
Captures structured, validated input at the front of a process, feeding clean data into both the workflow and the AI lane. This is where the “data not ready” failure is retired, at intake, before a decision is ever asked for.
Adds a signature at the control point where a signature is the accountable act. The human’s approval becomes a signed, logged record, closing the audit trail the governance layer keeps.
Read left to right, a customer-onboarding flow calls each in turn: Forms captures the application, RPA pulls a record from a system with no API, the AI lane judges the risk, DocGen produces the agreement, and eSign closes it: with the workflow sequencing the lot and a person approving where policy requires.
One framework, or a drawer of disconnected pilots
Sprawl is the tax that pilots levy after the fact. Each one arrives with its own tools, its own risk profile, its own integration debt, and its own quiet maintenance cost. Nintex positions ABO explicitly against "software sprawl and the risks of disconnected AI pilots", consolidation is a selling point, not a side effect.
| Dimension | A drawer of disconnected pilots | One governed framework |
|---|---|---|
| Governance | Per pilot, inconsistent, often absent | Shared, applied by default |
| Integration | Rebuilt each time; duplicated debt | Built once on the substrate, reused |
| Risk profile | Many, each unmanaged | One, monitored centrally |
| Vendor count | Many, overlapping | Consolidated on one platform |
| Cost to run | Compounds quietly with each pilot | Amortised across the framework |
| Path to scale | Each pilot restarts the climb | Rungs already built, reused |
The financial logic is simple. Ten pilots on ten stacks pay for governance ten times and still have less of it than one framework provides once. The consolidation argument is therefore also a cost argument, and a risk argument, and a speed argument: which is why it belongs in the board pack rather than the architecture review.
The consolidation dividend
Every rung of the ladder built inside one framework is a rung the next process inherits for free. Sprawl throws that reuse away. Consolidation banks it. That compounding is the difference between a programme that accelerates and one that merely repeats.
What shipping is worth
Return on a production orchestration is measurable, and it has been measured. The headline case is E.T. Browne, maker of Palmer's, which recorded a 5,005% return over five years and $29 million delivered, cutting approval cycles from two-to-three weeks to a week or less (Nintex customer story). The number is large because the base, manual, multi-week approval, was slow.
A single customer story, however striking, is an anecdote until an analyst models the average. Forrester's Total Economic Impact study of the Nintex platform put return at 213% with a nine-month payback (circa 2022: we label the vintage because these studies age). Read together, the two numbers bracket the case: the analyst average is healthy, and the standout customer shows the ceiling when the starting process is slow enough.
| Lens | Return | Payback / period | Vintage |
|---|---|---|---|
| E.T. Browne (Palmer's) | 5,005% over 5 years, $29M delivered | Approvals: 2–3 wks → ≤1 wk | Nintex customer story |
| Forrester TEI (modelled) | 213% ROI | 9-month payback | circa 2022 |
These are platform returns, established before ABO existed, which makes them a floor for the argument rather than a ceiling. The orchestration layer is meant to extend that record into processes that pure workflow could not previously reach: the ones needing judgement as well as precision.
MIT's Project NANDA measured the choice that quietly determines success: buying agentic capability from a specialist vendor succeeds about 67% of the time, while building it internally succeeds about 33%: roughly half. The gap is not marginal. It is a doubling of the odds, and it points at a proven platform.
specialist vendor
internally
The result is intuitive once the ladder from Part III is in view. Buying starts you several rungs up: the substrate exists, the governance exists, the connectors exist. Building starts you at the bottom, paying to construct the very machinery whose absence killed the pilots. The 67/33 split is the ladder, measured in outcomes.
Two caveats, because we prefer them to slogans. First, the 67/33 split is one study, MIT NANDA's, and it drew methodological criticism; read it as directional, not decisive. Second, we sell the "buy" side, so weigh our fondness for a figure that favours buying accordingly. And buying only wins if the platform is genuinely agentic: Gartner counts about 130 of those among the thousands claiming the label. The advantage is contingent on choosing well, which Part V describes.
The decision, compressed
Build, and you take a one-in-three bet while paying to construct the substrate. Buy a proven platform, and you take a two-in-three bet with the substrate already built. For a system that must run the business, the arithmetic is not close.
Proof of a platform is not only its return; it is its footprint and its reputation among the people who run it. Nintex serves more than 7,000 organisations across over 100 countries (24 September 2025). User ratings are solid rather than inflated: G2 puts it at 4.3 out of 5, TrustRadius at 8.0 out of 10. We report those without dressing them up.
The context is a market growing fast enough to make inaction its own risk. The agentic-AI market is estimated at about $5.2 billion in 2024, rising to roughly $196.6 billion by 2034: a compound annual growth rate of about 43.8%. That figure is a Market.us estimate, and we label it as an estimate rather than as a Gartner or Forrester number, because it is one.
We make no claim that Nintex holds a Gartner Magic Quadrant or Forrester Wave leadership position; those are specific designations and we will not assert them without the citation to match. The case here rests on the architecture, the customer proof, the buy-versus-build evidence, and the footprint: which is enough.
No board should buy on the customer headline alone. We frame the return as bear, base, and bull, anchored on the sourced figures, so the case survives scrutiny rather than flattering it.
Bear
Payback slips beyond Forrester's nine months as integration proves harder than scoped. Return still positive, but the programme lives or dies on rung 2-to-3 execution. Mitigant: partner-led integration.
Base
The modelled Forrester return, ~9-month payback, holds at platform level (circa 2022 vintage). ABO extends reach into judgement-heavy processes previously out of scope. The reasonable planning case.
Bull
A slow, high-volume approval process like E.T. Browne's compounds into outsized five-year return and $29M delivered. Available only where the manual base is genuinely slow.
The honest planning number is the base case. The bull case is real but conditional; the bear case is survivable because the return stays positive even when execution disappoints. A business case built on the base, aware of the bull, and hedged against the bear is one a board can sign without embarrassment.
Nintex introduces Agentic Business Orchestration, structured workflow, AI decisioning, human control, positioned against software sprawl and disconnected pilots.
Then-CEO Amit Mathradas departs for Five9. We name no successor.
Nintex Agent Designer and Nintex Orchestration enter open beta.
The quarter's product update lands, continuing the beta programme.
General availability expected; in beta as of July 2026.
Seven questions to ask before you scale
If a programme cannot answer these plainly, it is closer to rung one than it thinks. Each maps to a failure the data in Part I already documented.
The tell
A programme that answers all seven crisply is on the two-in-three side of the buy-versus-build bet. A programme that answers vaguely is, statistically, one of the 95% with no P&L impact, and does not yet know it.
Glossary
The terms used in this report, defined for a generalist reader.
- Agentic Business Orchestration (ABO)
- Nintex's framework combining structured workflow executions, AI-driven decision-making, and human control in one governed system. Unveiled 24 September 2025.
- Deterministic workflow
- A process that runs the same exact steps in the same order every time: the floor that guarantees precision and compliance.
- Probabilistic AI
- A model that may make different choices on different runs; suited to judgement, unsuited to mandatory exact steps.
- Human in the loop
- A designed control point where a named person approves, overrides, or escalates before execution resumes.
- Nintex Agent Designer
- The governed, low-code environment for building mission-critical agents. Open beta from 17 March 2026.
- Nintex Orchestration
- Modular, phase-based workflows that move forward, jump back, or repeat. In beta as of July 2026; GA expected later in 2026.
- Nintex Automation CE
- The build-and-run substrate for ABO. Pricing from $15,000/yr.
- Nintex RPA
- Task automation across applications. Nintex RPA (formerly Kryon; current release v25.11) is the strategic go-forward line; Nintex RPA LE (formerly Foxtrot) is maintained alongside.
- Nintex DocGen
- Document generation from process data, including a DocGen Agentforce connector for Salesforce.
- Nintex Forms / eSign
- Structured data capture at the front of a process; electronic signature at accountable control points.
- Maturity ladder
- The five rungs from demo to orchestrated enterprise used in Part III to locate a programme's true state.
- Total Economic Impact (TEI)
- Forrester's modelled cost-and-benefit methodology; here, 213% ROI, 9-month payback, circa 2022.
- Proof of concept (PoC)
- A limited build to test feasibility; ~46% are scrapped before production (S&P Global, 2025).
- Software sprawl
- The accumulation of disconnected tools and pilots, each with its own cost, risk, and integration debt.
Sources, dated
Every figure in the argument traces to one of the entries below; the About-Nintex page (folio 04) additionally draws on Nintex corporate and customer materials, 2022–26. Estimates are labelled as estimates. We deliberately omit the unverified "89% never scale" claim.
What you need in place to build and run
Workflow automation is the layer with the most moving parts to procure. Two lists follow, the Nintex elements to licence, and the non-Nintex pieces that must already be in place, so a build-and-run programme does not stall on a missing prerequisite. Tiers and figures are indicative for 2026; confirm current SKUs with Nintex.
| Nintex Automation Cloud (CE) | The cloud workflow platform. Subscription, Standard or Enterprise tier; priced by users or workflow-execution volume. |
| Nintex Forms | Digital intake forms. Included in the platform. |
| Nintex DocGen (Drawloop) | Document generation. Licensed as an add-on module. |
| Nintex eSign (AssureSign) | Compliant e-signature. Licensed separately. |
| Nintex RPA (Kryon) | Bridges legacy screens that have no API. Licensed separately. |
| Nintex Automation K2 | On-premises / hybrid engine for regulated, mission-critical builds. Separate on-prem licence. |
| Premium connectors | SAP, Oracle, Salesforce and similar. Licensed per connector. |
| Microsoft 365 and/or Salesforce | The systems the workflows act on, plus API access to any ERP/CRM in scope. |
| Identity / single sign-on | Microsoft Entra ID or an equivalent SSO provider. |
| On-prem infrastructure (for K2) | Windows Server and SQL Server, plus the hosting infrastructure and network. |
| Change & release governance | So scaled workflows do not fork per team as they spread. |
| Owners and a run team | Process owners and an admin or centre of excellence to run the platform after go-live. |
One accountable team, from strategy to shipped software
Volge delivers workflow automation on the Nintex platform through one team and one arc. Four roles hold the work from the first workshop to operational handover; nothing is handed off between phases.
One automation approach, from pilot to production
The architecture is settled, a deterministic floor, an AI lane where judgement pays, and a person at the control points. The five phases below are how Volge takes a Nintex programme from pilot to production.
The publication
Voice of Volge: Volge’s thought-leadership series. Each report states the firm’s position on one partner platform.
Editorial
Unsigned and institutional, in the house Morpheus voice. Every figure sourced, quantified, and year-stamped.
The publisher
Volge: an independent deep-tech enterprise service provider and a premier Nintex delivery partner.
Disclosure
Volge is a Nintex delivery partner and benefits if you buy. Evidence sourced independently; interest disclosed.
Set in Raleway and Inter · US Letter, portrait · No 02 · July 2026 · Workflow automation · Prepared for named-client distribution.