North Stack reads the email your team already gets, runs the routine jobs against Acturis the way a person does, and escalates the calls that matter — every decision cited to your own rules and written to an audit ledger you can hand to the FCA.
A renewal lands, the agent classifies it, scores its confidence, and starts the run itself.
Runs inside the stack you already use
It clears the routine inbox work end-to-end: renewals compared, letters drafted, claims records found, risk re-keyed into Acturis. Your handlers stop doing the endless part and keep the judgement calls. In the demo that comes to 214 handler-hours a week, about 5.7 FTE of capacity handed back.
Nothing improvises near client records. Every action runs a mapped process, stops at a human gate when it matters, cites the rule it used, and lands in a tamper-evident ledger. Under FCA and Consumer Duty, that is a control you’re adding rather than a risk you’re taking on.
It runs a process you mapped, not a prompt it improvises. You know exactly what it will do before it ever runs, and every run is measured against the same map.
Every step is a tamper-evident, hash-chained ledger entry, and every decision cites the exact rule and row it used. Proof you can hand to a regulator, not a chat transcript you have to trust.
It drives Acturis, M365 and the portals through the same screens a person uses today. No API to wait for, no rip-and-replace, no year-long rollout.
Everything that hits the shared inbox lands in one place.
The agent works out what it is, which workflow it belongs to, and how sure it is.
Routine jobs run end-to-end through a process you mapped, and you can watch where each one is.
Pricing, rates, appetite and watchlists are versioned sheets it looks figures up in. It never invents them.
Anything sensitive or uncertain stops at a human checkpoint, with the proposed action laid out in full.
Every step, whether agent, human or system, is a tamper-evident ledger entry.
Every message is triaged for what it is, which workflow it belongs to, and how confident the agent is, with the key fields pulled out. Routine, high-confidence work runs; anything ambiguous is left for a person. It never improvises outside a mapped process.
Each job runs through a workflow you mapped: the exact steps, the systems each touches, where the human gates and exception lanes sit. That makes it knowable before it runs, which is the core difference from a general-purpose agent.
When a run decides, it cites the sheet, row and version it used, alongside a field-by-field read-back against the system of record. You can trace a decision back to the row behind it instead of believing a conversation.
RPA is brittle and can’t read an inbox. A generic AI agent improvises and leaves you a transcript, not a defensible record. North Stack is the regulated middle: the flexibility of an agent with the control of a mapped, audited process.
| Capability | North Stack | Generic AI agent | RPA (UiPath / Blue Prism) |
|---|---|---|---|
| Handles a free-text shared inbox | ✓ | Yes | No |
| Knowable before it runs | ✓ | No | Yes |
| Tamper-evident audit trail | ✓ | Transcript only | Logs actions |
| Cites the rule behind each decision | ✓ | No | No |
| Runs Acturis with no API | ✓ | Fragile | Brittle replay |
| Human approval gates on writes | ✓ | No | Limited |
Tell us a little about the work you’d want it to take off the desk, and we’ll set you up with the live North Stack demo environment and a founder-led walkthrough.
Already invited? Log in to the demo →
The request form is unavailable right now. Email i@choy.in and we'll get you in.