Approval workflows that route themselves and stop waiting on you

Why approvals are the bottleneck nobody owns

Most approval processes were never designed. They accreted. Someone decided purchases over a certain amount need a manager's yes, so now finance forwards emails and hopes. Someone added a second signer for anything touching a customer contract, so now deals stall in an inbox for four days. The rules live in people's heads, the routing happens by memory, and the status of any given request is a mystery until you go ask.

The cost is not the approval itself, it is the waiting and the chasing around it. A vacation request that takes thirty seconds to approve sits for a week because it landed while the manager was traveling and nobody escalated. A discount that needs a director's sign-off holds up a signature the customer was ready to give. Multiply that across procurement, hiring, expenses, content, and contracts, and you have a team spending real hours being a human router instead of doing the work only they can do.

Approvals are also where things slip through. When routing is manual, the request that should have gone to two signers goes to one, or the out-of-policy expense gets waved through because the approver was busy and trusted the sender. A built approval flow does not get tired, does not skip the second signer, and does not forget the rule you wrote down.

• Purchase and procurement requests that need budget or manager sign-off
• Discounts, quotes, and contract terms that exceed a rep's authority
• Expense reports, reimbursements, and travel that need a policy check
• Time off, hiring requisitions, and offer approvals in people ops
• Content, campaigns, and legal reviews before anything ships or publishes

What we automate and how it works

We start by mapping the real path a request takes today, not the one in the policy doc: who actually signs off, in what order, what the thresholds are, and what happens when someone is out. Then we rebuild it as a single automation on a platform like n8n, Make, or Zapier that runs the moment a request is submitted. The trigger can be a form, a new row in a sheet, a Slack message, a deal reaching a stage in your CRM, or a record created in your ERP. From there the flow does the routing your people used to do by hand.

The automation reads the request, applies your rules to decide who needs to approve it, and routes it to them in the right order. A purchase under 500 euros might auto-approve and just get logged. Between 500 and 5,000 it goes to the team lead. Above that it needs finance too, in sequence, so the second approver only sees it once the first says yes. Approvers act right where they already work, an Approve or Reject button in Slack or Teams, a reply to an email, a click in a form, no new tool to learn and no portal to log into.

Once a decision comes back, the flow finishes the job. It writes the outcome to your system of record, updates the CRM or ERP, notifies whoever raised the request, and kicks off whatever comes next: cutting the PO, releasing the contract, provisioning the new hire. If a step needs judgment, reading a messy free-text request to figure out what is actually being asked for, flagging an expense that looks off, we drop an LLM into that step so the flow can classify and route intelligently instead of dumping everything on a human. This is the same connective tissue we build across the Workflow Automation pillar, pointed specifically at sign-off.

• Rule-based routing by amount, department, request type, or risk level
• Sequential and parallel approvers, with the right order enforced automatically
• Auto-approve for anything under a threshold you set, logged but not delayed
• Approve or reject in Slack, Teams, or email, no new portal to adopt
• Automatic reminders and escalation when an approver goes quiet
• Write-back to CRM, ERP, finance, and HR systems once a decision lands

Chasing, escalation, and the audit trail

The hardest part of any approval process is not the yes or no, it is getting a busy person to look at it at all. So the flow does the chasing. If an approver has not acted within the window you set, one business day, four hours, whatever fits, the automation reminds them automatically. If they still go quiet, it escalates: to their manager, to a backup approver, or up the chain, based on rules you define. Nothing sits in a dead inbox because the one person who could act was on holiday.

Every request also gets a clean, timestamped record without anyone maintaining it. Who submitted what, which rule routed it, who approved or rejected and when, what the amount was, and what happened next. That log is worth more than the time it saves. When finance runs a quarter-end review, when an auditor asks how a purchase got approved, or when someone disputes a decision, you have the whole chain in one place instead of reconstructing it from Slack threads and memory. For anything touching real money or customer commitments, that traceability is the difference between a process you can defend and one you just hope was followed.

• Timed reminders so approvers never need a human to nudge them
• Automatic escalation to a backup or manager when a request stalls
• Out-of-office aware routing that skips to the next approver
• A complete, timestamped record of every request and decision
• Exportable logs for finance reviews, audits, and dispute resolution

What it takes to build and what you own

A focused approval flow for one process, say purchase requests or discount sign-off, is usually a two to three week build. We spend the first few days getting your rules and thresholds exactly right, because a routing rule that is almost correct is worse than none. Then we build it, test it against your real requests, and run it in parallel with your current process until you trust it. Nothing gets ripped out and replaced. We connect to the tools you already run, Slack, your CRM, your finance or HR system, through their APIs, and the automation becomes the layer that moves a request between them.

When it is done, it is yours. The flow runs in your accounts, on your tools, with documentation your team can actually read and edit. If your threshold changes from 5,000 to 10,000, or you add a new approver, that is a change your ops person can make without calling us. We build so you can own it, not so you are stuck with us. And because Roiwerk works outcome-first, if the flow does not actually take the chasing and routing off your team's plate, you are not paying for it.

Where an approval flow touches several systems or several other automations, we compose it cleanly rather than cramming everything into one brittle mega-workflow, the same integration discipline we apply across our tools and integrations work. An expense approval that ends by posting to your accounting system, or a hiring sign-off that provisions accounts on approval, connects to those downstream builds instead of duplicating them.

Results, ROI, and when not to automate a sign-off

The payoff shows up in two numbers: cycle time and hours saved. Approvals that used to take days routinely drop to hours or minutes, because the request stops waiting for a human to notice it and start routing. On the labor side, the people who were manually forwarding, chasing, and updating systems get those hours back, and that alone usually pays for the build inside a month or two on any process with real volume. There is a second, quieter return too: fewer out-of-policy approvals slipping through, and faster sign-off on the deals and hires where speed actually wins.

We will also tell you when not to automate. If a decision genuinely needs a conversation every time, a nuanced legal judgment, a sensitive people decision, a one-off with no repeatable pattern, then automating the routing is fine but automating the decision is not, and we will keep the human firmly in the loop. If a process runs a handful of times a month, the build may cost more than it saves, and a lightweight shared form beats a full automation. Auto-approval is powerful and also the thing to be careful with: we only turn it on for low-risk, clearly-bounded cases, and we keep hard human sign-off on anything consequential. The goal is to remove the waiting, not the judgment.

• Cycle times that drop from days to hours or minutes on routed requests
• Hours returned to the people who were manually forwarding and chasing
• Fewer out-of-policy sign-offs because the rules are enforced every time
• Auto-approval only for low-risk, clearly-bounded cases you define