If you're a finance person, you've probably looked at Claude Code once and looked away.

How I Set Up Claude Code as My Investment Research Analyst

If you’re a finance person, you’ve probably looked at Claude Code once and looked away. A black terminal. Commands that mean nothing. Something for engineers, not for someone who spends their day in spreadsheets and annual reports.

I’ve now been running my entire investment research workflow on Claude Code for sixty days. Screening, scraping, modeling, drafting reports, monitoring portfolios.

Claude vs. Claude Code: The One Thing Nobody Explains

Claude and ChatGPT are chatbots. You ask, they answer. Claude Code is different. Claude Code is Claude with hands.

A chatbot can help with one step at a time. Claude Code can run the whole chain. You give it the end goal. It opens a browser if it needs to. It scrapes data if it needs to. It writes files, reads files, runs five things in parallel. It asks you for input only when it actually needs you.

“A smart, hardworking person does more by doing more. A wise person does more by eliminating more. Claude Code is the eliminator.”

Step One: Install Claude Code

Install from Claude Code page. Open terminal, paste install command. Type claude to start. Download Cursor — where the knowledge base, chat, and tools are all visible at once.

Step Two: Obsidian as Claude Code’s Memory

Claude Code on its own has no memory. Every session starts fresh. For research, it’s a problem. Research compounds.

Folder structure:

• raw/ — inbox: articles, transcripts, screenshots
• wiki/ — librarian’s domain: structured summaries, topic folders, master index
• output/ — drafts, reports, deliverables

CLAUDE.md — the rulebook Claude Code reads every time. Write rules once, followed forever.

Daily workflow (four verbs):

1. Clip — Obsidian Web Clipper extension, one click → lands in raw/
2. Compile — “Process everything in raw/” — Claude Code reads, files in wiki/, updates indexes
3. Query — Ask the library: synthesis, cross-reference, filing answers back as notes
4. Audit — Monthly: “Look for inconsistencies, broken links, gaps. Give me a report.”

“Every question you ask becomes a new note. Every note links to its sources. The library grows smarter every time you use it.”

Step Three: Playwright + Firecrawl

Playwright — browser automation (Microsoft). Claude Code can open a browser, navigate, click, fill forms, log in, read screen. Useful for: screeners requiring many filters, IR pages with dropdowns, regulator portals with disclaimers.

Firecrawl — fast programmatic web scraping. Converts web pages to clean markdown. Use case: pull insider trading data from Finviz, scrape annual report, search “latest news on Indian specialty chemicals” and pull top 10 articles.

Real prompt example: screen 5 names for portfolio deployment → Firecrawl to Finviz → parse → cross-check fundamentals → ranked list with thesis, insider purchases, key metrics. Manual equivalent: 90 minutes minimum with errors.

60 Days: What Surprised Me

1. The terminal stopped feeling like a coding tool by end of week one. Plain English input works.
2. Research used to leak — Notion, Apple Notes, bookmarks, PDFs in 5 folders. Obsidian system stopped the leak.
3. The system is the discipline. Anyone can install the tools. The rulebook forces consistency.

“Claude Code is for coding if you want to code. It’s for cooking if you want to cook. It’s for shopping if you want to shop. And if you’re really into finance, it’s the most powerful research tool I’ve ever used.”

원문: https://x.com/leopardracer/status/2058949350315667829?s=52