When should you use it?
- You research individual companies
- You want a repeatable folder structure
- You prefer Excel models you can audit
Not for: Treating the output as advice; Placing trades from it
What do you need, and what do you get?
You need
- Annual reports and press releases
- Earnings call transcripts
- The same directory layout for every ticker
You get
- Financials CSV and Excel model
- Scenario valuation
- Memo files and one-pager
- Weekly update task
How does it work, step by step?
- Create the scaffoldMake subfolders for filings, transcripts, charts, model and memo.
- Load the sourcesDrop in reports and transcripts.
- Build the modelHave it extract figures and write a spreadsheet with formulas, not pasted values.
- Run scenariosAsk for bear, base and bull cases with stated assumptions.
- Write and scheduleProduce the written thesis and short PDF, and schedule a refresh every week.
The prompt
The original prompt by Kevin, word for word, with a link to where it was published. Below it is our adapted version with fill-in blanks, if you want it. Works in Claude Cowork and Claude Code. Values in lime are placeholders.
Original prompt by Kevin
Read all PDFs in filings/. Write a one-page business overview of Adyen in memo/01_business_overview.md covering: what they do, how they make money (take rate, processed volume, net revenue), main segments and geographies, top customers and customer concentration, competitive position vs. Stripe / PayPal / Block / Worldline, and the three biggest structural risks. Use plain English, no jargon.
Exactly as published by Kevin in 9 steps in Claude Cowork to automate your investment analysis.
Our adapted version (optional)
In the [ticker] folder you will find filings and transcripts. Extract five years of revenue, margins, cash flow and share count into model/financials.csv with the source page for each figure. Build an Excel model with live formulas and a three-scenario discounted cash flow, listing assumptions on their own tab. Write a business overview, a thesis with risks, and a one-page summary in memo/. Mark any figure you could not find.
What can go wrong?
- Check every extracted figure against the filing before trusting the model.
- Scenario outputs depend entirely on the assumptions; review them first.
Our take
The folder scaffold is the real asset; once every company lives in the same structure, the workflow becomes a repeatable checklist. Asking for formulas instead of static numbers keeps the model auditable. Kevin's run worked because the inputs were organized before any analysis started: filings, transcripts and charts each in their own subfolder, with the model and memo kept apart. Copy that layout for every ticker and the second company takes a fraction of the time. The extraction step is where errors creep in, so check each figure the agent pulls against the filing page before trusting anything built on it. Bear, base and bull cases are only as good as their stated assumptions; read those first and change them where you disagree, rather than arguing with the output. A weekly refresh is handy once filings start arriving. Keep the memo as your own research. It is not advice, and nothing in this workflow should place a trade or move money.
Where the time goes back: Hours of setup per company, from data entry to formatting, become a repeatable run.
FAQ
Why a fixed folder?
Is the memo a recommendation?
Source and credit
The original prompt on this page is by Kevin, shown word for word with a link to where it was published. The summary, notes and adapted version are ours.
- Original
- 9 steps in Claude Cowork to automate your investment analysis
- Creator
- Kevin
- Published on
- investwithai.substack.com (Substack)
- Original date
- Apr 15, 2026
- License
- Not openly licensed; the original prompt is shown word for word with credit and a link to the original
- Originally for
- Claude Cowork
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.