All solutions/Vertical·Banking & Capital Markets

Loan origination

Document extraction + policy reasoning + draft credit memo with every covenant explained.

Shipped against
  • Top-10 commercial bank
  • Specialty commercial lender
  • Regional business bank
  • Equipment finance lender
  • Asset-based lender

Anonymised — clients under NDA

+47%
underwriting throughput
10 wks
to production MVP
6-person
squad with credit officer embedded

The context

Commercial and specialty loan origination is 60% assembly: pulling financials, spreading, reconciling against credit policy, drafting the memo. The credit officer's actual judgement applies to maybe 20% of the file.

Why it doesn't scale today

The bank has tried this. Vendor underwriting platforms automate the easy structured pieces and leave the messy ones — partnership financials, side letters, unusual covenants — to the underwriter, who now also has to fight the platform. Net cycle time barely moves.

What we ask in week one

  • iWhich of your loan categories have enough structural consistency to draft autonomously, and which need underwriter touch from the start?
  • iiWhere does your underwriter need full edit control vs. accept the recommended draft as-is?
  • iiiHow do we ensure every recommended term is grounded in your policy clause and the closest comparable in your book?
  • ivWhat does the audit trail look like for your credit committee and your regulator?

What we build

We build the underwriting surface as a working draft: document extraction, spreads, policy mapping, and a credit memo the underwriter edits. Every recommended term is annotated with its policy basis and the closest comparable. The underwriter owns the file; the assembly disappears. Throughput goes up without dropping the bar.

Why we're the right squad

Our practice leads have run credit operations at top-tier banks — they know which corners credit committees will not let you cut. We size the engagement around a single loan category first; throughput compounds from there.

What you keepA system, not a prototype
  • Documentation

    Architecture, data contracts, deployment runbooks, eval criteria — written for the team that owns it next.

  • Infrastructure

    IaC, monitoring, rollback, on-call playbooks. Standard tooling, not bespoke.

  • Evals

    Eval harness + prompts + labelled fixtures + regression suite. Extends with your team.

  • Architect anchor

    A lead architect from our side stays in your Slack for at least 90 days post-handoff.

Want to scope this for your team?

We'll come back with a pod composition, a 2-week discovery sprint plan, and a price — measured against the KPI you care about, not against activity.

RelatedAdjacent solutions