Walkthrough · Claude for Business
Build your own deal-review analyst.
We built this walkthrough for a friend who splits his time between investing and commercial real estate. The idea: turn the frameworks of investors you respect — plus your own track record — into an analyst that scores every deal the same rigorous way, then learns your taste one deal at a time.
What you'll end up with
Not a chatbot that has opinions about your deals — a small team with jobs. By the end of this walkthrough you'll have:
A deal reviewer with a fixed rubric
Every deck and every deal gets scored the same way, every time — verdict, signal, noise, red flags, and the questions that actually decide it.
A diligence team that fans out
Parallel agents on market size, competitors, the people behind the deal, and the financial model — while you do something else.
Your diligence spreadsheets, completed
Your checklist workbook and comparison matrix filled in per deal — same format every time, sourced numbers only, ready for your review.
A calibration loop that learns your taste
A short interview after every review, logged and promoted into standing filters — so review #30 knows you in a way review #1 couldn't.
A portfolio tracker
One place where every position, update letter, and mark lives — so "what's happening across my portfolio?" is a question your analyst can actually answer.
Build the corpus — from two sources
An analyst is only as good as what it has read. Yours gets two libraries.
a) Public: the investors whose judgment you trust
Pick a thinker whose framework you'd actually want applied to your deals — a well-known SaaS investor's public essays, a value investor's shareholder letters, a real-estate operator's talks. Have Claude gather what they've published — essays, conference talks, podcast transcripts — and then distill it: strip the banter and the politics, keep only the investing content, and compress it into paraphrased "framework cards" the agent reasons from.
Two rules make this work:
- →Set a source-precedence hierarchy. The primary thinker's own writing is the spine; supporting voices defer to it. Without this, the agent blends five people into a mushy average — or worse, fabricates a position nobody holds.
- →Spend where it matters. Bulk transcript-crunching can run on cheap or local models; save the strong model for judgment and synthesis. Hours of audio costs almost nothing to distill this way.
One line on IP: your private corpus is for your use. If you ever share your setup with a friend, ship the method and your scripts — not other people's verbatim content.
b) Private: your own deal history
Past decks, your old deal memos, term sheets, the deals you did and — just as valuable — the ones you passed on and why. Drop them in a folder. This is the part of the corpus that makes the analyst yours instead of a generic one.
# a corpus is just folders — no database, no magic deal-review/ corpus/ essays/ # the thinker's own writing (the spine) talks/ # transcripts, distilled to framework cards my-deals/ # your decks, memos, term sheets, passes kb/ rubric.md # how every deal gets scored filters.md # your standing preferences (grows over time) calibration-log.md # dated record of what you taught it
The forward-building interview
Here's the honest problem: most investors don't have a written pass/reject history. Your taste lives in your head. So instead of trying to write it all down up front — you won't — the agent builds it forward, one reviewed deal at a time.
After every review, the agent asks you two to four one-tap questions:
- →“Lean in, pass, or watch?”
- →“What single thing most attracts or repels you here?”
- →“Did my review miss your actual concern?”
Thirty seconds of your time per deal. The leverage is in the promotion ladder: a one-off answer stays in the calibration log; a pattern that recurs two or three times gets promoted into an active filter the agent applies to every future deal; and when you teach it a threshold — the point where a metric goes from acceptable to alarming for you — the rubric itself gets updated, with a dated note. Review #30 knows your taste in a way review #1 couldn't.
Build the team
The center of the team is the deal reviewer: a thin agent persona pointing at the rubric and corpus you just built. The design rule that makes it dependable is a fixed output contract — every review, no matter the deal, comes back in the same shape:
- →Verdict — lean in, pass, or watch, stated up front
- →The real signal — what actually matters in this deal
- →The noise — what's dressed up to impress you and should be ignored
- →Red flags — including what's conspicuously absent from the deck
- →Metrics to demand — the numbers you should ask for before going further
- →The three questions that decide it — and a fit-with-your-strategy read, with a weighted score
Around the reviewer, a diligence team fans out in parallel when a deal clears the first read: one agent sizes the market from primary sources, one runs the competitive scan, one backgrounds the founders or the sponsor, one stress-tests the financial model's assumptions, one compares the term sheet's terms against what's market. Each comes back with a sourced brief; the reviewer synthesizes. What used to be an afternoon of tabs is twenty minutes of reading their reports.
If your deals are buildings rather than companies: the same pattern powers property work — lease abstraction across a rent roll, acquisition diligence checklists, LOI drafting. We wrote a full walkthrough for that world: Claude Code for commercial real estate.
▶Watch: Claude Code Masterclass for People Who Don't CodeWire up your work products
This is the step most people skip, and it's where the compounding lives. Don't let the agent invent its own report format — hand it the actual spreadsheets you already use: your diligence checklist workbook, your deal-comparison matrix, your portfolio tracker. Claude learns each one's structure and fills it in per deal, for your review — same format every time, so deals stay comparable across months and memory.
Four rules keep this honest:
- →A fixed output contract beats freeform "thoughts." The same structure every run is comparable and reviewable; prose impressions are neither.
- →Every number needs a source — or it doesn't go in the sheet.
- →The agent drafts, you decide. No AI makes an investment decision.
- →Corrections persist to disk — a dated calibration log — or they never happened.
Start from our kit
You don't have to build the skeleton from scratch. We open-sourced the structure we use ourselves — the agents, the rubric and interview-protocol templates, the safety rails — with zero data inside. Bring your own credentials, add your own corpus.
claude-finance-team
A five-agent finance team as a Claude Code plugin: a group CFO with a multi-entity registry and routing, a deal reviewer with the full rubric + interview protocol + calibration templates from this walkthrough, a tax advisor, and QuickBooks + Count bookkeeping specialists with real safety rails — auto / approval / refuse write tiers, so nothing touches your books without a yes.
github.com/uwskiguy/claude-finance-team# inside Claude Code — two commands, then say hello to your CFO /plugin marketplace add uwskiguy/claude-finance-team /plugin install
Tools we like
The AI-forward stack we run our businesses on
A short list of tools that pair well with an AI team — the ones we actually use day to day. A couple are our referral links (tagged below); they cost you nothing and sometimes get you a perk.
Claude
The AI this whole guide is built around — Claude Code for real multi-step work, claude.ai for everyday questions.
Mercury
referralBusiness banking built for modern companies — clean API, virtual cards, and the account structure that keeps your books easy to reconcile.
Ramp
referralCorporate cards with AI-driven expense automation — receipts, approvals, and categorization that a finance agent can read and reconcile.
Count
A modern cloud ledger built for automation — your books as clean, queryable data an AI finance agent can read and reconcile, with your approval before anything posts.
Notion
Docs and a knowledge base your team — human and AI — can share. A natural home for the calibration notes and playbooks your agents build.
Google Workspace
Drive, Gmail, and Sheets — the documents and data you connect Claude to. A dedicated Drive folder is the easiest way to hand your AI a corpus.
Claude for Business
Set up safely first. Then build your analyst.
The setup guide covers installing Claude Code, the permission model, and connecting your files the safe way — start there if you haven't. Then come back and give your deal flow a team.
Questions? Grab office hours