Most enterprise leaders now accept that AI needs better processes underneath it. Camunda's research found that 72% of decision-makers have watched process-related problems derail an AI initiative. Another 82% expect their AI investments to fizzle without more investment in process design.
Many organizations struggle with where to begin. The same research found that 73% of enterprises lack a structured approach to process redesign. Teams buy tools, launch pilots, and roll out agents one department at a time, with no shared method holding the work together.
This following guide takes a practical view of that first move. It covers how to choose your first process, how to prepare your team, and which of three paths into a ProcessOS engagement fits where your organization stands today.
Pick one process to start
A typical enterprise runs more than 500 core processes. At roughly 12 months to re-engineer each one the traditional way, the backlog stretches across centuries. Trying to tackle everything at once only recreates that problem, so the teams that move fastest pick one process, re-engineer it from end to end with ProcessOS, and let it set the pattern for the next.
Camunda's re-engineering teams, including forward deployed engineers, looks for six traits in a strong process to start with:
- It crosses many hands: Several systems, teams, and agents touch it, and work is inefficient at the handoffs between them.
- It runs often or is important: Each case carries enough volume or value for the gains to compound.
- It already has stalled pilots: Existing AI work becomes a building block instead of a sunk cost.
- It carries regulatory exposure: An audit trail and enforced human oversight pay back immediately.
- It has a baseline you can see: You already measure KPIs like cycle time, cost per case, or customer drop-off.
- It has one accountable owner: A business leader owns the outcome from start to finish.
Few processes check every box, but the strongest candidate usually checks most of them. Treat your first process as a lighthouse that earns attention from the C-suite. A visible first win builds the momentum that every later process depends on.
Prepare with three questions
You can make progress before any engagement begins. A small cross-functional team from IT and the business can kick off the work in less than a day by answering three questions.
- What should improve? Choose two or three numbers that will define success, such as end-to-end cycle time, manual effort, or cost per case. Count token spend and human review time inside cost per case so the hidden costs of AI stay visible.
- How does the process run today, roughly? You do not need a perfect model of the current state. The outcome you want, the use cases the process must cover, and the rules that cannot change give you enough to start. Camunda began redesigning its own quote-to-cash process with very little documented knowledge.
- Would this step exist if we could use AI on day one? Hold every process step to that standard. Fixed rules and required approvals stay in place, and every other step either earns its place or goes.
The second question often feels like the biggest hurdle, and ProcessOS takes much of that weight off your team. As the discovery installment of this series explained, ProcessOS reconstructs the current process from your systems, logs, and documentation, then brings its findings to your subject matter experts for review. That way, your team spends its time validating the picture instead of drawing it from scratch.
Three ways to engage with Camunda
Every path to process re-engineering follows the samefour lifecycle stages: Discover, design build and deploy, and continuously improve. Teams that already know Camunda can run more of that lifecycle themselves, while teams new to the platform lean more heavily on Camunda's experts. In every case, your Camunda account team helps you choose the right next step.
Where you stand
How to start
What you get
Not yet a Camunda customer
A proof of concept, or process discovery and remodeling
Evidence on one process to inform your decision on implementation
Already a Camunda customer
Headless ProcessOS access plus a joint workshop
A re-engineered process and a team that knows the method
Ready for a larger engagement
A 12-week engagement with re-engineering experts and/or a certified partner
A production-ready, re-engineered process
If you are not yet a Camunda customer: start with a proof of concept or discovery
Organizations new to Camunda can start small and decide with evidence in hand. A proof of concept takes one concrete process and delivers a hands-on result within a few weeks. A discovery and remodeling engagement maps how a process runs today and designs its re-engineered future state, which gives leadership a clear view of the opportunity before anyone commits to a build.
Both options end at a decision point. If the results justify it, you continue into implementation. Discovery alone tends to reset expectations about speed. With ProcessOS, discovery that traditionally required two to three months of workshops takes only a few weeks. In one engagement, the team analyzed the process in two and a half weeks and transformed it in four.
Starting later carries an advantage of its own. Organizations that have not yet scaled AI have no siloed tools to untangle, so they can design their most important process for AI from the first day.
If you already run Camunda: get headless access and re-engineer a process yourself
Camunda Enterprise customers already have the platform and the skills, so they can move fastest. ProcessOS Harness is available in early access with Camunda 8.10 as a headless experience. Engineers who know Camunda work with ProcessOS through an AI coding agent such as Claude Code or GitHub Copilot CLI, and subject matter experts review and approve the output at defined gates. Your organizational knowledge stays in your own Git repository, and Camunda never uses it to train shared models.
Pair that access with a workshop. Camunda's team works alongside yours to choose the right first process and re-engineer it, so your engineers learn the method on a real problem with real stakes. As the ProcessOS early access blogdescribed, a strong run brings a technical operator and a business process owner to the table together.
This path also suits teams planning a move from Camunda 7 to Camunda 8. One bank is migrating 60 Camunda 7 processes to Camunda 8 and improving each one for AI along the way, so a version upgrade becomes a re-engineering opportunity.
If you are ready for a larger engagement: re-engineer a process from beginning to end
Organizations ready to commit to a critical process can work with Camunda's forward-deployed engineers in a 12-week engagement. You bring your team and one process. Camunda brings a re-engineering pod and ProcessOS. By week 12, you have a re-engineered process ready for production.
Certified Camunda partners deliver ProcessOS engagements as well. Camunda scopes larger engagements where team capacity and business value line up, which keeps each one focused on a process that matters to the business.
Measure from the first run
Next, capture your process’ baseline metrics before you build, because you can only prove value against a starting point. Four categories of metrics are present in nearly every engagement, regardless of the industry:
- Speed: end-to-end cycle time, and the time it takes to ship a process change when the market or a regulator moves.
- Efficiency: cost per case with tokens and human review included, plus the share of cases that run straight through.
- Trust and risk: the share of decisions with a complete audit trail, and the time it takes to answer a regulator's question.
- Experience: customer drop-off and the decision time customers actually feel.
You do not need a separate measurement program to track them. Once the process runs on Camunda, the orchestration layer records every run, and the audit trail becomes your data. Report the gains after each iteration, and track how the re-engineering work itself speeds up. Each process you re-engineer adds reusable patterns, integrations, and policies to your catalog, so process number 20 costs far less than process number one.
Start with one process
Every path into ProcessOS begins with the same decision. Pick the process that costs your organization the most time, risk, or customer frustration, check it against the six criteria, and answer the three framing questions with your team. Then talk with your Camunda account team about the path that fits.












