Process maps end up as documentation rather than systems.
For business analysts
Your process map, running.
Branches, thresholds, checks against live records and a designed rejection path. If you can map it, we author it with you as configuration, and Koldheim runs it without a development project in between.
Today
What it looks like now
01
02
Workflow tools flatten real branching into a straight line.
03
Every change to a rule joins a change-request queue.
What changes
What you get, and where it shows up
Configuration, not code
Records, steps, stages and rules are defined as configuration. A new process is authored, not built, and runs on the same engine as every other.
More on thisReal branching
Route on anything the process knows: cost, stock position, department. Both outcomes of every decision are designed, including rejection.
More on thisMeasured, not estimated
Every run keeps its steps and decisions, so approval counts and decision times come from the process itself.
More on thisWhich services
3 of 9Where you work in it
Asset RequisitionsOperations
A worked example of real branching: stock position, value and budget in one process.
Spend RequestsOperationsApproval limits by cost centre, amount band, person or role, set by your administrators.
Field TrialsAgricultureIncidents raised by rule the moment a recorded result breaks it.
Keep exploring
Where to next
Try the Asset Requisitions rule
The rule the service runs, in your browser. No form, no call.
Stop chasing approvals. Start running the process.You own a process that lives in inboxes, spreadsheets and corridor reminders. Koldheim gives it a shape everyone follows, and shows you where every request is.
Approve it without having to own it.One platform, isolated per customer in the database, signed in through your identity provider. No custom code for your team to maintain, and a record of every change.