Erebor
Building a bank's revenue system before it had one — and teaching it to answer in plain English
Industry
Banking
Engagement
Greenfield build
Stack
Salesforce + Claude
Started
Day one
The challenge
What they came to us with
Most banks come to us with a decade of accumulated workarounds. Erebor came to us with a blank page — which is harder than it sounds. There was no CRM, no pipeline view outside the core banking system, and no shared definition of what a deal even looked like as it moved.
Credit term sheets, vendor agreements, and NDAs moved by hand and by memory. Partner-sourced business was real and growing, but attribution lived in whoever happened to remember the introduction. Calls and commitments sat in individual inboxes.
In a regulated bank, that isn't just inefficient — it's exposure. Every process we built had to be auditable on the day it launched, not retrofitted for compliance a year later.
Our approach
How the work was sequenced
01
Design before configure
We mapped how a banker actually works a deal — first conversation to funded relationship — and built the object model around that, not around a template. Live sync with the bank core keeps opportunity stages and compliance status honest against the source of truth.
02
Put the paper in the system
Ironclad drives term sheets, vendor agreements, and NDAs, with Slack and Salesforce triggers moving each document forward. Gong captures the conversation so coaching and audit trails come from the same record.
03
Automation nobody has to maintain
Partner and channel attribution is captured at the source. Stale opportunities close themselves. Status changes land in Slack where the team already lives — so the pipeline stays accurate without anyone being asked to update it.
04
Teach it to answer
We configured Claude MCP against Erebor's systems and built custom Cowork skills on top. A banker asks where a deal stands, which agreements are outstanding, or how the partner channel is tracking — and gets a grounded answer, in the tool they already have open.
The results
What changed
From core to close
Pipeline, compliance status, contracts, and conversations resolve to a single system instead of four.
Claude in the workflow
Deal status, contract state, and channel performance answered in natural language — grounded in live bank data.
Built in, not bolted on
Every workflow shipped with the controls a regulated bank needs on day one, not after the first exam.
What's next
Growing the Claude skill library as more of the bank's operations move into the platform — the goal being that the system explains itself before anyone has to go looking.
Want results like this?
Tell us what's broken. We'll tell you how to fix it.
Book a free strategy call