Regulatory compliance
Reference buildFourteen jurisdictions watched, no deadline missed
An agent that monitors regulator websites across fourteen jurisdictions, extracts deadlines from the current source text rather than hardcoded rules, and escalates until a human confirms.
At a glance
- Duration
- 17 weeks
- Team size
- 1 person
- Engagement
- New build
- Project type
- AI & automation
- Industry
- Fintech
Built with
The situation
The challenge
Regulatory requirements change unpredictably and with little notice. The prior approach was a compliance team member checking websites by hand — which works right up until the week it does not, and the consequences of that week are legal and financial.
What we did
Monitor continuously, extract deadlines from the live source rather than a rules file, and design the whole thing to never go quiet.
The calls that mattered
Deadlines read from the source, not a rules table
Extraction from current regulatory text, so a changed deadline is picked up rather than silently contradicted by a hardcoded rule someone wrote last year.
Never silent, rather than always right
An escalating alert cadence as a deadline approaches, and drafted checklists that a human confirms before submission. The agent's job is to make sure nothing falls through, not to make the final call.
What changed
- missed filing deadlines
- 0missed filing deadlines
- less checklist preparation time
- 65%less checklist preparation time
- jurisdictions monitored
- 14jurisdictions monitored
- to flag a relevant regulation change
- <24hto flag a relevant regulation change
- 0 — since launch
- 65% — per filing
No missed deadlines since launch across fourteen jurisdictions, relevant changes flagged inside 24 hours, and 65% less time preparing each filing checklist.
Services used
- Scheduled regulator monitoring with relevance filtering
- Deadline extraction from live regulatory text
- Escalating alert cadence and drafted filing checklists
What we would do differently
Every project has one of these. Publishing it is the point — a case study with no regrets in it is marketing, not evidence.
For compliance-adjacent systems, designing for 'never silent' rather than 'always right' is the correct objective. Humans keep decision authority; the system's obligation is that nothing reaches a deadline unseen.
More work
- Internet Money · Crypto financial services$10M+monthly transaction volume
One wallet interface across five blockchains
A multi-chain crypto platform where every chain hides behind one interface, with a tamper-evident audit trail underneath it. $10M+ moves through it monthly.
Read case study - MagicTask · Project management SaaS100K+concurrent users
From latency spikes at 5,000 users to 100,000 concurrent
A gamified project management platform re-architected from a single Node server into an event-driven system that holds 100,000+ concurrent connections without the reward engine touching the critical path.
Read case study