Book a call
Case study · Financial services Compliance workflow Singapore

Approval chains, replaced.
Errors 13% → near zero.

A 22-person Singapore finance firm was running compliance approvals through email threads and spreadsheets. Version errors. Missed steps. Every escalation traced manually. We rebuilt the workflow in 6 weeks with rule-based routing, timestamped steps, and a full audit trail that writes itself.

−60%
Coordination work
~0%
Error rate (was 13%)
6w
Built in
F+2
Foundation + 2 cycles
Compliance Workflow · Live Audit log on
Request · 12:14 PM SGT
Trade authorisation, Hartwell Partners portfolio
SGD 2,400,000 · Equity rebalance
Submitted
Analyst · auto-routed
12:14 PM
Compliance review
Cleared · 6 checks passed
12:31 PM
3
Senior partner sign-off
Awaiting · escalates 2:00 PM
In progress
4
Audit log entry
Auto-generated on completion
Queued
Before

Approval chains lived in inboxes.

The firm's compliance team processed 30 to 50 trade authorisation requests a week. Each request started as a forwarded email, picked up a spreadsheet attachment somewhere along the chain, and bounced through compliance review, partner sign-off, and audit-log entry — manually, person by person, in whichever email thread someone happened to start.

Roughly 13% of submissions had a version-control error: a stale spreadsheet attached, an out-of-date compliance note copied in, or a missed sign-off step that surfaced only when an auditor flagged it weeks later. Every one of those errors meant a re-do. Every re-do meant the analyst, the compliance officer, and the senior partner all touched the request again.

The firm wasn't short on talent. They were short on a system that knew what step came next without anyone having to remember.

"We didn't have a process problem. We had an inbox problem pretending to be a process."

— The compliance lead, paraphrased from scoping
What we built

Routing by rule. Timestamps by default. Audit log by construction.

Six weeks. Foundation Build plus two Function Cycles. The workflow stopped living in email and started living in a system that wrote its own audit trail.

01
Structured intake form
Analysts file requests through a single form. Required fields enforce what used to be a memo's worth of context. No more attaching last week's spreadsheet by mistake.
02
Rule-based routing
Each request routes to the right reviewer based on type, threshold, and portfolio. The system knows the rules; people stop re-deciding them every time.
03
Automatic escalation
Sign-off pending past the SLA escalates to a backup. No one sits on a request because they're on leave or out of office.
04
Audit log, written automatically
Every submission, review, sign-off, and escalation timestamps itself. The audit trail is a byproduct of the work, not a manual reconstruction afterward.
05
Compliance dashboard
Live view of every request in flight. Stuck approvals, breached SLAs, and audit anomalies surface without anyone running a query.
Timeline

Six weeks, four committed milestones.

48 hours
Scope document delivered. Routing rules captured, escalation thresholds confirmed, data sources mapped, audit-log format agreed.
Day 7
Working MVP. Intake form live, three of five routing rules wired, dashboard reading from real submissions. Compliance lead testing in parallel with the old email flow.
Week 6
Full build deployed. All routing rules live. Escalation active. Audit log generating automatically. Old email-and-spreadsheet flow retired.
Ongoing
Function Cycles. Two further cycles added: a quarterly compliance report generator and an external-auditor portal that reads the audit log directly.
What this means

Process errors are usually system absences.

Most "process problems" in service businesses are actually missing systems. The work itself is fine. The way the work is captured, routed, and recorded is held together by people remembering things.

For this firm, that meant six weeks of build, a 60% drop in coordination work, and an audit trail that's never going to be the reason an audit fails. The team didn't get smaller. The work that didn't need a person stopped needing a person.

Yours could be the next one

Build a workflow that writes its own audit trail.

No pitch. No proposal. We talk about your business, identify the leverage, and tell you honestly whether we can help.