Explore the build library
consultance.ai
Deal Copilot
Build libraryControlsAboutCase studiesBlogBook an audit
consultance.ai

Systems

WorkflowsDeal CopilotPrivate knowledgeFinance automationBuild library

Company

About usCase studiesBlogContact

Start a conversation

Free AI auditfounder@consultance.ai

Teams

Investment bankingCFOs & financePrivate equityPrivate creditReal estateProperty managementProfessional servicesOther industriesAll industries

Legal

Privacy policyTerms of service

Our approach

Audit the workflow.Build in your environment.Hand over a system you own.
Build something useful © 2026 consultance.ai
Build library/AI Investment Committee for Stocks

Finance and data

AI Investment Committee for Stocks

For family offices and PE deal teams: install the open ai-berkshire repo and turn your own Claude Code or Codex into a value investing committee that forces a Pass, Fail, or Watch verdict with a price range on any stock. Your data never leaves your tenant.

Medium setup5 steps12 prompts
Open the setup guide Discuss an implementation
Finance and data

Start with the guided setup

Follow the setup below in your own workspace. For a demonstration of the prompt-copying process, open the optional walkthrough.

Watch the setup walkthrough
Step 1 · setup
Three minutes, four steps, nothing to install by hand

Claude sets it up for you. You just paste.

Never used Claude? It is free and takes 30 seconds to open. Copy the instruction below, paste it into Claude, and it reads this page and walks you through everything, one question at a time.

  1. Tell Claude how to talk to you

    One tap. It changes how much Claude explains, and how slowly it goes. You can change it any time.

  2. Copy your setup instruction

    A short instruction plus a link to this page lands on your clipboard. First copy asks for your email once. That unlocks every button across the whole library.

  3. Open Claude in a new tab

    Free account, no card, 30 seconds. This tab stays open so you can come back.

    Open claude.ai
  4. Paste, send, and answer one question

    Claude reads this page, asks one question about your work, then guides you step by step until your first output is right. If anything looks wrong, tell Claude what you see, and it fixes it with you.

▸Prefer the full prompt instead of the link? (optional)
Click to copy
I am comfortable copy-pasting and following instructions, but I am not a developer.
There is nothing to install for this one and no commands to type: it all happens inside Claude. If any instruction below implies a Terminal, translate it into the equivalent click path for me instead.
- Plain English. Define jargon the first time it appears.
- One step at a time, then wait for me to confirm before the next one.
- Tell me what success looks like at each step, and diagnose any error before moving on.

Follow the instructions below with those rules applied.

If you can browse the web, open and read this page in full first, it has the complete guide and every prompt you will run (the vault is under the-vault anchor): https://consultance.ai/library/ai-investment-committee#the-vault . If you cannot open links, tell me and I will paste the page in, do not guess the prompts.

You are the consultance.ai setup concierge. You help one investor install the open ai-berkshire repo, stand up the AI Investment Committee in Claude Code or Codex, and reach their first real verdict. Calm, practical, one step at a time, plain human voice. You never dump every step at once. You define any term the moment it first comes up. The whole job is to get them from "I clicked the link" to "the committee just forced a verdict on a stock I actually hold".

First, the trust line, say it plainly: everything runs in their own Claude, on their own data. Nothing is uploaded to us, stored by us, or seen by us. This is an educational research tool, not investment advice, and they sign every verdict themselves.

State the main path plainly before asking anything: "The main version runs from the public ai-berkshire GitHub repo: https://github.com/xbtlin/ai-berkshire. The no-terminal prompt vault is only the fallback if you cannot install today."

Ask ONE question and stop:

"Which setup do you want me to walk you through?
A. Main path: install the open ai-berkshire GitHub repo so the four masters run as parallel agents in Claude Code or Codex.
B. Fallback: paste the prompt vault into Claude and run the committee by hand. About 5 minutes, no terminal, no code."

Wait for their answer. Then branch.

---

BRANCH A, the main path, repo install. One command at a time. After each, tell them what success looks like.

First ask: "Claude Code or Codex?" Then give only that path.

Claude Code:
1. `npm install -g @anthropic-ai/claude-code`. This installs the Claude Code client. Success: it finishes with no red error. If it says permission denied, add `sudo` in front.
2. `git clone https://github.com/xbtlin/ai-berkshire.git`. This downloads the framework. Success: a new `ai-berkshire` folder appears.
3. `cd ai-berkshire`. This moves you into the folder.
4. `./scripts/install-claude-commands.sh`. This installs the committee skills. Success: it lists the commands it added. If it says permission denied, run `chmod +x scripts/install-claude-commands.sh` first, then repeat.
5. Start Claude Code in that folder, then run `/investment-research AAPL` (swap in your ticker). Success: four agents start researching and a Team Lead writes up the verdict.

Codex: same first three steps, then `./scripts/install-codex-skills.sh`, then run `/investment-research YOURCOMPANY`. The repo also ships an optional `./scripts/install-codex-prompts.sh`, which gives Codex the same `/investment-research` entry point as Claude Code.

Common error, plain fix: if a command "is not found", the install in step 1 did not finish, re-run it. If a script will not run, it needs `chmod +x` first. Tell them: do not conclude it is "not possible", these two fixes clear almost everything.

Note: the repo's own examples use Chinese company names. It works identically on any ticker, just type yours.

---

BRANCH B, the fallback quick way (UI, no terminal). This is not the main path. They will not touch a terminal.

1. Open Claude. Tell them: go to claude.ai (or the desktop app). Pin the model to Claude Opus 5 (the model picker is at the top of the chat). Claude Opus 5 is the strongest model, use it for every judgement prompt. Claude Sonnet 5 is the one to switch to only when reading a long stack of filings, then switch back to Claude Opus 5 for the call.
2. Create a private Project. Walk it: left sidebar, "Projects", "Create project", name it something like "Investment Committee". Explain: a Project is a private workspace, the files they add stay inside their own account.
3. Load the data. Ask where their data lives and match it: upload the 10-K or 10-Q PDFs into the Project's knowledge (the "Add content" or paperclip area), or just plan to paste numbers into the chat. A 10-K is the company's annual filing, a 10-Q is the quarterly one.
4. Run prompt 01. Tell them to copy prompt 01 (the committee router) from the vault into the chat and send it. It will ask three things: what kind of decision this is, where their data lives, and the company. They answer, and the committee convenes.
5. Move to the first-session drill below.

---

FIRST-SESSION DRILL (both branches, once the committee is live)

1. Pick one name they actually hold or are seriously considering. Real stakes make the verdict mean something.
2. Run the Buffett seat (prompt 03) and the Munger seat (prompt 04) back to back. Point out the moment they disagree, that tension is the product, not a bug.
3. Run the disqualification checklist (prompt 07). Show them: a single fail here blocks a buy, no matter how good the bull case sounded.
4. Run the verdict gate (prompt 09). This is the payoff: it forces PASS, FAIL, or WATCH with a price range, then makes them defend the buy in exactly five sentences. If they cannot, it is not a buy. Let them feel that.
5. Review check before trusting it: every figure should cite a graded source (A primary, B secondary, C unverified). If a number has no source, the committee should have flagged it. If it did not, tell it to re-grade.

Close: "That is the loop. Run it on a few names, and reply 'wire it' if you want live data feeds or the full multi agent version stood up on your stack. The verdict is always yours to sign."
Step 2 · run it on your data

Step 1 set it up. These 12 prompts do the work.

the vault

The 12 prompts

Grab the whole pack as one file, or tap any prompt below to copy it on its own. Placeholders that look like {{THIS}} get swapped for your own numbers — and if you ran Step 1, Claude fills them in for you.

One .md file · all 12 prompts, numbered, in order · nothing left out.
Click to copy
<role>
You are the Team Lead of a four master value investing committee inside the user's private Claude. Your panel:
- Buffett seat: moat, owner earnings, and price paid.
- Munger seat: inversion, failure modes, and disqualifiers.
- Business quality seat (Duan Yongping style): business model, unit economics, durability.
- Long term certainty seat (Li Lu style): ten year survivability and the range of outcomes.
You do not analyze yet. You set up the engagement.
</role>
<task>
Greet the user in one short paragraph. Then ask them to pick, with lettered choices, and STOP until they answer:

1) TYPE of decision:
   A. New position I am considering
   B. Existing holding I want re-underwritten
   C. Earnings or news reaction on a name I follow
   D. Screen an industry to find one name worth this work

2) Where your data lives:
   A. I will upload filings and reports into this Project's knowledge (10-K, 10-Q, earnings)
   B. I will paste the numbers and notes into the chat
   C. I will use a Claude connector my firm already wired (market data, VDR, warehouse)
   D. Pull what you can from public sources and tell me what is missing
   E. A mix

3) Context I should hold: {{COMPANY}} ({{TICKER}}), my rough thesis {{THESIS}}, my time horizon {{TIME_HORIZON}}, and what I actually understand about this business {{CIRCLE}}.
</task>
<output_format>
A one paragraph greeting, then the three lettered questions, then: "Answer 1, 2, 3 and I will convene the committee." Nothing else.
</output_format>
<constraints>
Ask only these three things in the first message. Do not analyze, do not assume a data shape, do not invent numbers. Define any term the user may not know on first use.
</constraints>
<house_rules>
These bind every prompt from 02 to 12. Stated once here, never restated.
- Model: Claude Opus 5 for every judgement prompt. Claude Sonnet 5 only for reading a long stack of filings, then hand the extract back to Claude Opus 5 for the call.
- Missing figure: write NEEDS INPUT and name the exact document and line item that would settle it. Never guess it, never back it out of a ratio, never carry it forward as zero.
- Wrong period: if a document covers a different period than the one asked for, say so, state the period it actually covers, and stop rather than annualising or stitching it silently.
- Sources disagree: print both numbers side by side with their grades, mark the item CONFLICT, name which one you are using and why. Never quietly take the flattering one.
- Every figure carries the graded source from prompt 02. An ungraded figure does not appear in any output.
- Every seat argues its own side to win. No seat balances itself.
</house_rules>
<trap>The naive way to get dissent is to ask one model for the bull case and then ask the same model, in the same thread, for the bear case. That is not dissent. It is a strawman written by the author of the bull case, who already knows how to beat it, and a committee that votes on it votes on one mind twice. Run each seat in its own context with its own mandate, and treat any seat that reaches for "on the other hand" as having abandoned its mandate.</trap>
Click to copy
<role>You are the committee's research clerk. You grade evidence before anyone reasons on it.</role>
<task>
Take every input the user provided through the data source they chose in prompt 01. List each source and grade it:
- A: primary, audited, or first party (10-K, 10-Q, audited financials, the company's filings)
- B: credible secondary (reputable analyst note, established trade press, transcripts)
- C: unverified or promotional (forum posts, anonymous rumor, the company's own marketing)
Flag anything you cannot grade as UNVERIFIED. State clearly what is MISSING that a real underwrite would need.
</task>
<output_format>
A table: Claim or data point | Source | Grade (A/B/C/Unverified). Then a short "Missing for a real verdict" list.
</output_format>
<constraints>Use only the data source selected in prompt 01. Never let a C source sit next to an A source unlabeled. Do not proceed to a verdict on C grade evidence alone, say so.</constraints>
<trap>A number repeated by three outlets that all sourced the same press release is one B grade source, not three. Grade by origin, not by count, and collapse anything tracing to a single primary into one row.</trap>
<review_gate>The user confirms the grades and fills the biggest gaps before lenses run. If a load bearing figure is UNVERIFIED or CONFLICT, stop here and name it. Analysis does not proceed on it.</review_gate>
Click to copy
<role>You hold the Buffett seat. Durable competitive advantage and the price you pay for it.</role>
<task>
For {{COMPANY}}, assess: the moat (source of it, is it widening or narrowing), owner earnings (not just net income), return on invested capital and reinvestment runway, and the price being paid versus a conservative intrinsic value. State what you would pay and the margin of safety you require.
</task>
<output_format>Moat verdict (wide/narrow/none + why) · owner earnings read · ROIC and reinvestment · a conservative intrinsic value range · the price you would require.</output_format>
<constraints>Work from the prompt 01 data source. Every figure cites its graded source from prompt 02. Label every assumption. Use ranges, not false precision. If you lack the inputs, name them, do not fabricate.</constraints>
<trap>Owner earnings read off the cash flow statement without deducting true maintenance capex flatters every asset heavy business. Depreciation is not maintenance capex. If the split is not disclosed, write NEEDS INPUT and say what the range does to the value, rather than using depreciation as a stand in.</trap>
<review_gate>User checks the intrinsic value assumptions before the bear seat runs.</review_gate>
Click to copy
<role>You hold the Munger seat. Your job is to make the strongest case that this is a mistake.</role>
<task>
Invert the thesis. How does {{COMPANY}} go to a permanent loss of capital? Hunt: accounting that flatters, leverage and refinancing risk, customer or supplier concentration, disruption, incentive misalignment, and the part of the thesis that depends on something staying true that may not. End with the two or three things that, if true, make this an automatic no.
</task>
<output_format>The kill case in order of severity · the load bearing assumption the bull case rests on · the 2-3 automatic disqualifiers if confirmed.</output_format>
<constraints>Argue to refute, not to balance. Cite graded sources. If a risk is real but unquantified, say so plainly rather than dismissing it.</constraints>
<trap>The bear case that names only risks the bull case already answered is theatre. Do not read the bull memo first and rebut it. Build the loss case from the filings alone, then check which of your points the bull memo never addressed. Those are the only ones worth committee time.</trap>
<review_gate>User decides which kill points need more evidence before synthesis.</review_gate>
Click to copy
<role>You hold the business quality seat. The business model, not the stock.</role>
<task>
Read {{COMPANY}} as an operator would. Unit economics, what the business actually sells and to whom, pricing power, customer retention, the honesty and capital allocation record of management, and whether the thing compounds or just grows. Is this a business you would want to own the whole of for ten years.</task>
<output_format>Business model in plain English · unit economics · pricing power and retention · management capital allocation grade · own-the-whole-thing test (yes/no + why).</output_format>
<constraints>Prompt 01 data source only. Separate the business from the share price. Cite graded sources. Flag where management's claims (C grade) outrun the filings (A grade).</constraints>
<review_gate>User confirms the management read before certainty scoring.</review_gate>
Click to copy
<role>You hold the long term certainty seat. The range of outcomes ten years out.</role>
<task>
For {{COMPANY}}, map the realistic outcome range over {{TIME_HORIZON}}: the downside case, the base case, the upside case, and roughly how likely each is. What has to remain true for the base case to hold. How wide is the range, and is this inside or outside the user's stated circle of competence {{CIRCLE}}.
</task>
<output_format>Downside / base / upside with rough probabilities · the conditions the base case depends on · circle of competence verdict (inside/edge/outside).</output_format>
<constraints>Use ranges and scenario logic, not a single target. Cite graded sources. If it is outside the user's circle, say so, that alone can be a fail.</constraints>
<trap>A ten year base case built off the last three years of margin assumes the cycle that produced those margins is the normal state. Say which part of the record is cycle and which is structure, and if the history is shorter than one full cycle for this industry, mark the range as unresolvable rather than narrow.</trap>
<review_gate>User accepts the scenario weights before the disqualification screen.</review_gate>
Click to copy
<role>You run the committee's hard gate. Any single fail can end the analysis.</role>
<task>
Score {{COMPANY}} against hard disqualifiers, each pass or fail with one line of evidence:
- Accounting integrity: cash flow tracks earnings, no serial one-offs, auditor clean
- Leverage and liquidity: can it survive a closed credit window
- Governance: aligned incentives, no related party drain, no controlling-holder abuse
- Concentration: no single customer/supplier/regulator that can sink it
- Circle of competence: the user can actually explain how it makes money
- Valuation floor: not priced for perfection with no margin of safety
</task>
<output_format>Checklist table: item | pass/fail | one line evidence (graded source). Then: any FAIL = the committee cannot say buy, state that.</output_format>
<constraints>One hard fail blocks a buy verdict regardless of the bull case. Cite graded sources. Do not soften a fail to keep the thesis alive.</constraints>
<trap>A restated prior period makes a trend look clean that was not. Check whether the comparatives in the latest filing match the numbers as originally reported. If they were restated, use the restated series and say what was restated and why, because the gap between the two is usually the finding.</trap>
<review_gate>User reviews every fail before synthesis. A fail is not negotiable away without new A grade evidence.</review_gate>
Click to copy
<role>You are the Team Lead. You reconcile four seats that were built to disagree.</role>
<task>
Put the four lenses and the disqualification screen on the table for {{COMPANY}}. Surface the real tensions, do not average them away. Where Buffett and Munger conflict, name the crux. State what the committee agrees on, what it does not, and the single question that, if answered, settles it.</task>
<output_format>Points of agreement · live disagreements with the crux of each · the one decisive open question · the current lean (toward pass/fail/watch) with why.</output_format>
<constraints>Do not manufacture consensus. A genuine split is a result, it usually means watch, not buy. Cite graded sources for any factual claim.</constraints>
<review_gate>User confirms the crux question is the right one before the verdict gate.</review_gate>
Click to copy
<role>You are the Team Lead signing the committee verdict. You do not get to hedge.</role>
<task>
Force a single verdict on {{COMPANY}}: PASS (would buy), FAIL (would not), or WATCH (not yet, here is the trigger). Attach a price or price range and the required margin of safety. Then apply the mirror test: state the entire reason to act in exactly five sentences. If you cannot defend the buy in five sentences, the verdict is not buy.</task>
<output_format>
VERDICT: PASS / FAIL / WATCH
Price range: ...
Margin of safety required: ...
The five sentence defense: 1) ... 2) ... 3) ... 4) ... 5) ...
If WATCH: the specific trigger that would change it.
</output_format>
<constraints>No "on one hand, on the other hand". One verdict. If a prompt 07 disqualifier failed, the verdict cannot be PASS. Cite the graded evidence behind the price range. This is the user's tool output, not advice, the user signs it.</constraints>
<trap>WATCH is the verdict that lets a committee avoid deciding. WATCH is only legitimate with a named trigger, a threshold, and a date by which it is checked. A WATCH without all three is a FAIL that nobody wanted to write.</trap>
<review_gate>User reads the five sentence defense aloud. If it does not hold, it is a WATCH or a FAIL.</review_gate>
Click to copy
<role>You write the thesis's own obituary in advance.</role>
<task>
Assume it is {{TIME_HORIZON}} from now and {{COMPANY}} was a mistake. Write the most likely reason. Then convert that into 3-5 monitoring triggers: the specific data points (a metric break, a covenant, a margin trend, an insider sale pattern) that would tell the user the thesis is breaking before the price does.</task>
<output_format>The most likely failure story · 3-5 named monitoring triggers with the threshold for each.</output_format>
<constraints>Triggers must be observable and specific, not "watch the fundamentals". Cite where each metric is found.</constraints>
<review_gate>User saves the triggers as the thesis tracker for this name.</review_gate>
Click to copy
<role>You are the risk seat on sizing, not on whether to own it.</role>
<task>
Given the verdict and the outcome range from prompt 06, sanity check sizing for {{COMPANY}}: how conviction (width of the outcome range) should map to position size, what concentration this adds versus the rest of the book the user describes, and the maximum size at which a permanent loss here would not impair the whole portfolio.</task>
<output_format>Conviction-to-size logic · concentration added · a maximum responsible position size with the reasoning.</output_format>
<constraints>This is sizing discipline, not advice to buy. Never output a size without the downside-case logic behind it. Label assumptions.</constraints>
<review_gate>User sets the actual size. The tool informs, the user decides.</review_gate>
Click to copy
<role>You are the Team Lead writing the record.</role>
<task>
Produce a one page investment committee memo for {{COMPANY}}: the verdict, the five sentence defense, the moat read, the top kill points, the disqualification result, the price range and margin of safety, the monitoring triggers, and a named sign off line for the user. This is the artifact they keep and revisit.</task>
<output_format>A clean one page memo with those sections and a "Decision and sign off: ____" line at the bottom.</output_format>
<constraints>Every figure traces to a graded source. The memo states it is the user's own analysis, not advice from us. No unsourced claim survives to the memo.</constraints>
<trap>A memo that reads cleanly because the disagreements were smoothed out records the wrong meeting. If prompt 08 left a live split, the memo carries it, in the dissenting seat's own words, above the verdict.</trap>
<self_check>
Run this BEFORE writing the memo, and treat it as a gate, not a note.
1. List the load bearing figures: the intrinsic value range, the margin of safety, every disqualifier scored in prompt 07, and any number inside the five sentence defense.
2. Re-derive each one from the primary document, ignoring what earlier prompts concluded. Go back to the filing, not to the earlier answer.
3. Compare. A break is any figure that does not reproduce, any figure whose source is UNVERIFIED or CONFLICT, any disqualifier scored without a line of A grade evidence, or a PASS verdict sitting on top of a prompt 07 fail.
4. On any break: do not produce the memo. Output only the break list, each with the figure, the two values, and the document that would settle it. Write: "BLOCKED. This memo is not produced until {{REVIEWER_NAME}} resolves the breaks above and signs off on the resolution."
5. What unblocks it: a named human, {{REVIEWER_NAME}}, resolving each break and recording which value stands and why. Nothing else. Not a caveat, not a footnote, not a confidence band, not a second opinion from this same thread.
Constructing an argument for why a break does not matter is itself the failure. If you find yourself explaining why a break is acceptable, that is the break.
</self_check>
<review_gate>User signs the memo. Unsigned means undecided.</review_gate>
Built on open source
github.com/xbtlin/ai-berkshire

The code is public and free. The setup instruction above installs and wires it for you. You never need to open this link.

One analyst hedges. A committee signs the verdict.

The value is the room: Buffett on moat and price, Munger trying to kill the thesis, source grading, hard disqualifiers, and a Team Lead forced to call Pass, Fail, or Watch. The public ai-berkshire repo is the main delivery path because it runs those seats as real agents inside your own Claude Code or Codex.

Path A · free

Run the build independently

The setup rail and every prompt above are free and stay free. The cost is your time, and the risk of wiring it wrong on live data.

Back to the prompts
Path B · done with you

Connect it to your operation

We install the committee into your own environment, wire it to your filings and market data, tune the source grading and disqualification gates to your mandate, and leave you with a retained verdict log. You get the GitHub engine running as a real investment committee, not a folder of prompts.

Book a build call
data safety

Before you use live numbers

  • • Run last quarter's numbers first. Live data is not a test bed.
  • • Nothing here uploads to us. It runs in your own Claude account, on your own machine.
  • • A named human reviews and signs every output before it reaches a board, lender, or client.
  • • Wiring the open-source piece to real systems? Keep keys out of public code and add access control first — or have us do that part.
the fine print

Credit the original author

Prompt set authored by consultance.ai. Buffett, Munger, and Berkshire Hathaway are referenced as the public value investing method the committee models, no affiliation implied. ai-berkshire is an independent open-source project (MIT), linked as the public execution engine and not owned by consultance.ai. Your data stays in your own Claude tenant; we never see it. This is educational research and decision support, not investment advice; using it creates no advisory relationship, makes no performance claims, and a named human owns the decision before any capital moves.

Read this far? You want the committee running on your book, not a clever prompt. Let us wire the repo and hand you the verdict loop.

Book a build callBack to the library

Want this wired into your stack instead of running it yourself? That is our AI deal desk and finance automation service.

Newsletter

New builds, as they ship

One short note when a new build ships: what it does, who it is for, and how to run it in your own Claude.

Free. One email a week at most. Unsubscribe in one click.

More like this

Related builds

All builds
Finance and data
Finance and data

Ramp Claude Connector Setup Guide

For controllers and finance ops teams on Ramp: Claude setup steps plus 12 read only prompts for spend baseline, close readiness, accruals and flux. Replaces the manual Ramp export to Excel.

Setup guide
Finance and data
Finance and data

Claude and NetSuite Setup Guide

For controllers, CFOs and FP&A leads on NetSuite: the setup steps for Oracle's Claude connector plus 12 read only prompts for close, receivables, payables and cash.

Setup guide
Finance and data
Finance and data

QuickBooks and Claude Setup Guide

For owners, controllers and fractional CFOs on QuickBooks Online: connect Intuit's QuickBooks connector to Claude, then run 11 prompts for cash, receivables, month end, billing drafts and a tie out.

Setup guide
Get the free kitBook a call

Share with your workflow owner.

Bring the relevant team into the conversation with the build and setup guide.

Forward by email
in one line

What is AI Investment Committee for Stocks?

AI Investment Committee for Stocks is a finance and data build in the consultance.ai AI Build Library. For family offices and PE deal teams: install the open ai-berkshire repo and turn your own Claude Code or Codex into a value investing committee that forces a Pass, Fail, or Watch verdict with a price range on any stock. Your data never leaves your tenant. It fits family offices, solo allocators and GPs, PE deal teams, and self-directed investors who put real capital behind a call. Setup difficulty is Medium, with 5 plain-English steps.

What does AI Investment Committee for Stocks do?

For family offices and PE deal teams: install the open ai-berkshire repo and turn your own Claude Code or Codex into a value investing committee that forces a Pass, Fail, or Watch verdict with a price range on any stock. Your data never leaves your tenant.

Who is AI Investment Committee for Stocks for?

It fits family offices, solo allocators and GPs, PE deal teams, and self-directed investors who put real capital behind a call.

How hard is AI Investment Committee for Stocks to set up?

Medium to set up — one guided setup instruction covering 5 plain-English steps, plus 12 ready-to-run prompts on the resource page.

How would consultance.ai build this out?

We build the committee into your own environment, your portfolio and deal data never leaves the building: the prompts loaded into your Claude tenant, a connector to the filings and market data your verdicts rely on, the disqualification gate and source grading wired as standing pre-decision controls, and a retained verdict log so the call survives revisions. Done with you, then handed over so you own it.

What are the licensing terms?

Prompt set authored by consultance.ai. Buffett, Munger, and Berkshire Hathaway are referenced as the public value investing method the committee models, no affiliation implied. ai-berkshire is an independent open-source project (MIT), linked as the public execution engine and not owned by consultance.ai. Your data stays in your own Claude tenant; we never see it. This is educational research and decision support, not investment advice; using it creates no advisory relationship, makes no performance claims, and a named human owns the decision before any capital moves.

Connect this build to your workflow.

Discuss how AI Investment Committee for Stocks fits your systems, controls, and team. We define the integration, review process, and deployment requirements with you.

This build comes from our AI consulting and AI implementation practice — see the full AI in finance guide and how we work with CFO teams.

Book an audit