Community financial institution
≈ $2.4B in assets (approx.) · 30 branches · ~400 employees
Governed core-banking assistant
Staff ask questions of the core banking system through governed MCP tools. Anything consequential is composed and paused for a human, so the assistant is useful without being able to act alone.
- Organization
- Community financial institution
- System
- Core banking platform with a well-defined request surface
- Runs on
- The institution's own cloud tenancy
- Scope
- Governed assistant with approval-gated actions
Where they started.
Staff wanted to ask the core system questions in plain language: account status, transaction history, exception queues. The institution's IT security team, reasonably, would not allow an assistant that could act on the core system on its own, and would not allow the core's data to leave the tenancy.
What was built.
- MCP connectors that mirror the core platform's real request shapes rather than inventing an abstraction over them.
- Read paths open to the roles that need them, with per-user credentials so an answer never exceeds what that person could see themselves.
- Write paths composed by the agent and paused in the approval queue; on approve, the request replays with the approver's own credentials.
- Every decision and every replayed request recorded in the audit log.
What changed.
- A useful assistant that cannot act alone.
- Security review passed on the strength of the approval engine and the audit trail.
- Consistent answers for staff who previously escalated to a specialist.
- A pattern the institution can extend to other systems.
Account data does not leave a bank's boundary, full stop. The agent's usefulness had to be earned without any of that data reaching a third party.
The institution's own cloud tenancy
Components involved.
More like this.
Multi-brand industrial manufacturer
≈ $200M revenue across five brands (approx.) · 5 brands · 4 ERPs · 1 CRM
- Use Case:
- Consolidation, forecast and pricing intelligence across four ERPs
- Results:
- One governed lakehouse behind an AI agent: audit-grade consolidated financials that trace to the source transaction, forecast and pipeline by business unit, large-job margin watch, and plain-English inquiry over all of it, inside the company's own Azure tenant.
Healthcare receivables agency
≈ $10M revenue (approx.) · ~60 employees · national client base
- Use Case:
- Placement-file intake automation
- Results:
- Placement files arriving in any layout are normalized into the agency's existing upload format, with a human approval queue before anything reaches the system of record. A one-and-a-half-person manual job becomes a review step.
Healthcare receivables agency
≈ $10M revenue (approx.) · ~60 employees · regulated healthcare receivables
- Use Case:
- Protected-health-information send gate
- Results:
- Every outbound file that carries protected health information is checked against the placement it belongs to and held for human approval, with an audit trail of who released what, and when.
Have one like it?
Every spotlight started as a conversation about a process nobody liked doing, under a data-locality constraint.