Use case · Credit and underwriting
Agent Serve reads the borrower file, drafts the memo in your house format, checks it against credit policy, and waits for the credit officer.
A credit and underwriting use case for Agent Serve, the AI workspace where teams build, deploy, and manage AI agents: a workflow reads the borrower folder in the Library, drafts the credit memo, checks it against the credit policy and waits for the credit officer, while a dashboard and Chat prepare the committee pack.
At a glance
The problem it removes
A memo starts as a folder of statements, an application and emails. The analyst retypes figures into a template, rereads the credit policy for the right limits, and rebuilds the same committee pack every week. Decisions wait on paperwork, not on judgement.
Before and after
| Work | Before | With Agent Serve |
|---|---|---|
| The memo | BeforeFigures retyped from statements into a Word template. | With Agent ServeAgent Serve drafts the memo from the folder in your format. |
| Policy checks | BeforeThe analyst rereads the credit policy for limits and conditions. | With Agent ServeThe draft is checked against the policy before review. |
| Committee pack | BeforeRebuilt every week from exports and old slides. | With Agent ServeA dashboard arrives as a PDF before each committee. |
| Questions about a borrower | BeforeSomeone searches the folder and emails back an answer. | With Agent ServeChat answers from the folder and shows the source. |
How it runs
Agent Serve prepares the draft and checks it. The credit officer reads it and makes the decision.
The analyst starts the workflow on a borrower folder in the Library: statements, the application and the term sheet.
The File block reads each document, and an agent pulls out revenue, debt, covenants and the purpose of the loan.
The agent writes the memo in your house format, and Guardrails check its claims against the credit policy knowledge base.
A Human step sends the draft to the credit officer, who edits it and records the decision. The memo is saved back to the folder.
In depth
Agent Serve keeps the borrower file, the draft and the committee view in one workspace.
Agent Serve keeps statements, the application and the memo draft in one Library folder, and Chat can save a committee pack there as a Word document.
Agent Serve shares a memo with an email or domain allowlist, a password or SSO, and the link can be turned off when the committee is done.
An Agent Serve dashboard shows exposure, watch-list movements and new limits, and Subscribe sends it as a PDF before every committee.
Agent Serve workbench scenarios recalculate outcomes as you change assumptions such as size and term, without touching recorded results.
What does the work
The Library holds statements, applications and the memos written from them.
A workflow drafts the memo, checks it against policy and waits for sign-off.
The credit policy and underwriting guidelines sit in a knowledge base.
Analysts ask Chat about a borrower folder and keep the documents it writes.
A committee dashboard arrives as a PDF before each meeting.
Examples
Three credit and underwriting jobs teams run on Agent Serve, each ending with a person’s decision.
An Agent Serve workflow drafts the memo from the borrower folder and the credit officer signs it off.
An Agent Serve dashboard of exposure and watch-list moves is sent as a PDF before each committee, with notes saved to the Library.
An underwriter attaches the submission folder in Agent Serve Chat and asks for a brief checked against the underwriting guidelines.
Examples show what teams can build in Agent Serve. They describe patterns, not named customer deployments.
Governance
Agent Serve drafts and checks. Credit officers decide, and every draft and decision is traced.
Security and governanceAgent Serve applies team space roles to the Library, and access policies can turn off public file sharing for a group.
The Agent Serve Hallucination Check tests a draft against the credit policy knowledge base and flags what the policy does not support.
Relays never send email or book meetings without an approval, under any autonomy setting. An approval covers the exact payload the reviewer saw and expires if nobody decides.
Every workflow run records each block’s inputs, outputs and errors, so a reviewer can trace how a result was reached.
Proposals, approvals, declines and executed actions are written to the workspace audit log, which admins can export.
Admin, write and read roles per workspace, plus permission groups that limit which models, blocks and integrations a team can use.
Sign in through your identity provider with SAML 2.0 or OIDC, and provision people with SCIM.
Run Agent Serve in your own cloud or data centre, next to the systems it reads.
Zero data retention with supported model providers, backed by your own provider keys and agreements or self-hosted models. Some provider features keep data by design, such as Gemini Deep Research, so they are outside zero data retention.
Use your organisation’s own model provider keys at organisation or workspace level.
Further reading
The deep dive models the time a weekly committee pack takes and what changes, with every figure labelled.
Read the blogEvery week the committee secretary rebuilds the same pack from memos, spreadsheets and emails. Here is a setup where four workflows assemble it from the source systems and the secretary decides when it goes out.
Commercial lending · 12 min readA commercial credit memo takes days, and most of that time goes on copying numbers and restating policy. This playbook builds one workflow that does the drafting and leaves the credit judgement with the officer.
Commercial lending · 5 min readCommercial underwriters lose hours to an inbox of broker submissions before any risk is assessed. This long read argues for a Relay that reads, sorts and briefs, while underwriters keep every decision.
Commercial insurance · 5 min readQuestions
No. Agent Serve drafts memos and checks them against your policy. A credit officer reviews every memo at a Human step and makes the decision.
Yes. The Agent Serve workflow’s instructions and template set the structure, and Chat can save the result as a Word, PDF or Markdown file in the Library.
Not as .xlsx today. Agent Serve Chat saves Word, PDF, PowerPoint, Markdown, HTML and CSV files, and tables export as CSV.
Agent Serve applies the team space’s roles to the Library. Sharing outside the team uses an allowlist, a password or SSO, and admins choose which share modes are allowed.
A team can start with the Agent Serve memo workflow and a credit policy knowledge base, then add the committee dashboard and its scheduled PDF.
Last updated
Enterprise access
Agent Serve is available to teams by invitation. Tell us what you want to build and we will set up your workspace with you.