03 The hard part
Why do approval systems get bypassed?
Because of one unanswered question. Every workflow project we have run has stalled at the same point, and it is never the technology.
- The question: what happens when the approver is unavailable? Not "unavailable in theory", but on the Friday before a long weekend with a dispatch waiting.
- The wrong answer: nothing happens, and the request waits. Two of those and the team goes back to WhatsApp, which is where the audit trail disappears.
- The other wrong answer: it auto-approves. That converts a delay problem into a control problem, and the first time it approves something it should not have, the whole system is switched off.
- What actually works: a named delegate per approver, set in advance, activated by the leave record or by the approver, with the delegation itself written into the trail. Plus escalation up the hierarchy after a stated time, so a request can wait but can never be forgotten.
The escalation was the part that changed behaviour. Once a pending approval started appearing on the director's Monday list, the queue emptied itself.
04 Delivery
How we build one
Five steps, and the first two are conversations rather than configuration. Most of the elapsed time goes into agreeing the rule, not implementing it.
Step 1: Time the current path
Request to action, measured rather than estimated, and where it waits. The waiting is almost always in one place and rarely the one people assume.
2 to 3 daysStep 2: Write the rule in a sentence
By value, category, cost centre, margin or vendor, with thresholds as numbers. A rule that cannot be written in a sentence should probably not be a rule.
2 to 3 daysStep 3: Answer the absence question
Delegates, escalation timings and what may never auto-approve. This is the decision that determines whether the system is used or bypassed.
1 to 2 daysStep 4: Build escalation and fallback first
Reminders, escalation, a manual path and an alert to a named owner, before the happy path is wired at all.
1 to 2 weeksStep 5: Hand over the rule editor
An administrator on your side is trained to change thresholds and approvers without us, because a workflow you cannot edit is one you will abandon.
1 day
05 Governance
The record it leaves behind
The routing saves time. The trail is what makes the saving defensible when somebody asks a question six months later.
- Every action carries the actor, the timestamp, the value, the rule that routed it and the channel it was actioned from, and none of it can be edited afterwards.
- Delegated approvals show both people: the delegate who acted and the approver whose authority was used. An audit that cannot distinguish the two is not an audit.
- Anything writing into the books is part of the accounting system, so it inherits the logging control an external audit already tests: an unalterable, timestamped record of each entry and each later change, which is control A.8.15 of ISO/IEC 27001. Retention is set per workflow rather than left indefinite.
06 The people
Who do you actually work with?
Four founders, named. An approval matrix is a political document as much as a technical one, so it is agreed with you before anything is built.
The rules are agreed with the people who will live inside them. That is the step most rollouts skip and then repeat.
-
Dhanush Prabha
Co-Founder, CTO and CMO
Connects the systems so the workflow is one path rather than four, and builds the escalation logic.
-
Sriram Ravichandran
Founder and CEO
Maps the workflow, negotiates the service levels, and gets the approval matrix signed.
-
-
07 Cross-border
How do we work with clients in another country?
None of this needs you to be in any particular country. The work is remote either way, so these are the answers a buyer asks for before signing, and they are the same on every engagement we run.
Working hours
Our day runs on UTC+5:30. The overlap window with your team is written into the scope rather than assumed, and everything outside it runs asynchronously.
How we communicate
One written update a day on the channel you already use, a standing weekly call inside the overlap window, and a named person to escalate to. Nothing important is agreed only on a call.
Who you contract with
Synerdyn Private Limited, the company behind IncorpX, named in the agreement with its registration number. The governing law and the forum are agreed before you sign, not after a dispute.
Currency and payment
Invoiced in your currency or in ours, your choice, and settled by bank transfer. Milestones are tied to deliverables you can see, never to elapsed time.
What you own
Copyright in everything built for you is assigned on final payment: source code, design files, prompts, configuration and documentation. Third-party licences are listed by name so nothing is a surprise later.
Where data sits
You choose the region your data is stored and processed in, and the answer is written down before the build starts, with who at IncorpX can reach it and for how long.
Offset from our working day standard time
- London-5:30
- Dubai-1:30
- Singapore+2:30
- Sydney+4:30
- New York-10:30
- San Francisco-13:30
IncorpX is a brand of Synerdyn Private Limited. The contracting entity, the governing law and the invoicing currency are all named in the proposal before you sign anything.
08 Reference
Terms used on this page
- Escalation matrix
- The rule for what happens when an approval is not actioned in time: who receives it next, after how long, and whether it may auto-approve.
- Delegation of authority
- Approval rights passing to another person during absence, recorded so the trail shows who actually approved.
- Maker-checker
- A control requiring that whoever creates a transaction is not whoever approves it.
- Straight-through processing
- Written STP: a request meeting every rule that is released with no human action at all.
- Service level
- Written SLA: the time within which an approval is expected to be actioned, and against which a breach is measured.
- Approval trail
- The unedited record of actor, timestamp, value and routing rule for every action taken on a request.
- GDPR
- The EU and UK data protection regime. Article 83 sets administrative fines of up to €20 million or 4% of worldwide annual turnover, whichever is higher, which is why consent, retention and access control are build decisions here rather than paperwork.
09 Questions
Workflow automation FAQs
Next step
Tell us the approval that holds things up most.
We will come back with the routing rules, the escalation matrix, the delegation design and a fixed quote. The first map is free and yours to keep.
Read by Dhanush Prabha, our CTO, not a form queue. Reply usually within one working day, in your time zone.
