Use cases
Automate purchase requests
Spend control almost always breaks at the same point: the rules exist, but they live in a policy document nobody reads at the moment of ordering. InProcess writes them into the flow itself — an amount threshold automatically adds another approver.
What goes wrong today
- Requests arrive with no justification and no budget attached.
- Delegation rules depend on the amount, and nobody remembers them.
- Off-process commitments are discovered at invoicing.
- Approval times are not measured, so requesters work around the process.
The process you get
- 1
The requester submits
Item, amount, intended supplier, budget line and justification. No key field can be left empty.
- 2
Approval adapts to the amount
Below the threshold, the manager is enough. Above it, the request also goes to finance. The rule lives in the process, not in a memo.
- 3
Procurement orders
Once approved, the request reaches procurement with all supporting documents, ready to commit.
- 4
The requester follows along
They can see the current status without chasing anyone.
What changes
- Delegation rules apply themselves, without depending on anyone's vigilance.
- Every commitment is justified and attached to a budget before it is made.
- Approval times become visible, so the process stops being bypassed.
- Pending spend is visible in real time.
Other common processes
- Automate quote approval
- Automate leave requests
- Automate customer support
- Automate worksite tracking
- Automate employee onboarding
You could have this process live today
Describe it in a few sentences, AI builds it, you approve before it goes live.