● TJ / 001Index
Case Study / 032026
§ Case Study / 03 — AI Builder

AI Builder

Production AI inside a venture firm I can't name.

Role
Embedded · Solo build
Year
2026 — Present
Stack
Anthropic API · Claude Code
Firm
Undisclosed
§ 01The Situation
A venture firm runs on judgment applied to too much information: thousands of companies, years of meeting records, signal arriving faster than anyone can read it. The partners didn't need a demo. They needed systems they could trust on a Tuesday morning, built by someone close enough to see how decisions actually get made.
§ 02The Bet
An embedded builder who understands the investment motion ships things an outside vendor can't, because the feedback loop is internal. When the builder sits inside the workflow the system serves, iteration happens at the speed of a hallway conversation instead of a quarterly roadmap. That loop is the moat.
§ 03The Work
Four production systems, each built inside the workflow it serves:
  1. A sourcing and scoring engine.Pulls from the firm's internal systems (CRM, email, meeting records, and similar) and scores opportunities against a taxonomy of 4,000+ companies. Surfaces what matters before anyone thinks to go look.
  2. A tear-sheet engine for meeting prep.Walks into every partner meeting first. Compresses thousands of historical meeting notes into the two minutes of context that change how the conversation goes.
  3. A traction monitor on a weekly cadence.Scans hundreds of companies every week for movement: hiring, shipping, raising. The partners stopped asking what's new and started asking what changed.
  4. A verification layer.Catches hallucinated quotes and misattributed citations before anyone relies on them. Venture runs on trust, so the system that checks the system is the product.
§ 04The Outcome
Four production systems, live, in the partners' hands every week. Infrastructure the investment team runs on, built solo, inside the firm's walls.
Companies in the taxonomy
0+
Classified and scored. The map the sourcing engine runs on.
Companies monitored weekly
0+
Traction signals on a standing cadence, not on demand.
Production systems in weekly use
0
Sourcing, tear sheets, traction, verification. All four in the partners' weekly rotation.
§ 05 — Over Coffee

I can't name the firm, the sector, or anyone in the room. The systems run anyway. That's the proof I get to keep.

— Ask me about it anyway. I've gotten good at talking around the details.