Customer story
How Storm Ventures answers partner questions with sourced numbers
With Taylor Hoefler, Operations & Investor Relations
- active portfolio companies
- ~80
- funds with active companies
- 5
- metrics tracked by hand before Cura
- 2
- Firm
- Storm Ventures, early-stage B2B, Palo Alto
- Portfolio
- ~80 active companies across five funds
- Before Cura
- Google Drive folders, filled by hand
- On Cura since
- August 2026
One morning in August, a partner at Storm Ventures emailed Taylor Hoefler with a request. The partner wanted one portfolio company’s ARR and revenue, back to late 2023.
Taylor works in operations and investor relations at Storm Ventures, an early-stage B2B venture firm in Palo Alto. Storm was founded in 2000 and has about 80 active portfolio companies. It has five partners and an operations team of two. For years, Taylor kept the firm’s record of those companies by hand.
This time, Taylor asked Claude, with Cura connected. The numbers came back fast, and each one had its source. Taylor called it the first real use of Cura in the moment, for a request.
“[A partner] asked me for [a portfolio company]’s ARR and revenue since late 2023, and it was able to pull that really fast and source everything, which is awesome.”
From saved files to a sourced record
Founders send their updates and board decks to Storm’s partners by email. The partners share them with the team in a Google Chat channel. Taylor saved all of it. Taylor even took screenshots of chat comments, so that no detail was lost.
“I would print to PDF all of the emails. I download every deck. I grab everything manually, and then I’d save it as a file on my computer.”
The files went into a shared Google Drive, with a folder for each company. The drive ran about one quarter behind. At the end of each quarter, Taylor gave the files to Claude to help write an update on each company for Storm’s investors.
Taylor also tracked two metrics by hand: ARR and cash on hand. More than two was hard to keep up.
Before Cura
- Each founder email printed to PDF and saved to a Google Drive folder.
- Two metrics tracked by hand: ARR and cash.
- Claude worked from files that Taylor saved for it each quarter.
- Portfolio news found by chance on LinkedIn.
A careful record, kept by hand.
With Cura
- Founder emails and decks land in Cura, filed by company.
- Cura pulls the metrics out of each update and deck.
- Claude reads portfolio data from Cura.
- Cura watches LinkedIn, X and the news for every company.
One record, with a source for each number.
Years of files, loaded once
Storm did not start from zero. Taylor zipped the shared drive and sent it to Cura, and Cura’s team loaded the files.
The rest of the setup was a conversation. Taylor pasted the list of portfolio companies into Cura’s chat and asked it to add them. Then Taylor uploaded a PDF from Storm’s quarterly LP report. Taylor asked the chat to create a label for each fund and to put the right label on each company.
“I love that that’s not something I’d have to manually put on everybody.”
Later, Taylor gave Claude the LP handout, Storm’s quarterly document of its positions. Taylor asked Claude to add those values to Cura as custom fields. Claude wrote the values for the companies it could match.
Every number with its source
Cura reads the decks and updates and pulls out the metrics. Each value links to the document it came from. That link matters at Storm. For the firm’s controller, the test of a number is accuracy and a source.
Taylor works with the data in Claude. Taylor made a Claude project named Cura and told it to always use the Cura connector. In an open chat, Claude had mixed several tools. In the project, Claude uses one.
When the partner’s request came, Taylor went back and forth with Claude on the layout of a spreadsheet. Taylor called the work easy.
Portfolio numbers for an LP meeting
Before Cura, Taylor built a Claude project called the Storm metrics agent. The idea is simple. A managing director opens it in the Claude app on a phone and asks a question.
“I wanted it to basically be optimized for mobile. [A managing director] could be in an LP meeting and pull up numbers on our companies, or just Storm overall performance, really fast on his phone.”
The agent holds Storm’s fund performance history. For portfolio companies, it could answer on two metrics only: the ARR and cash that Taylor tracked by hand.
Taylor’s next step is to connect the agent to Cura. Then it can answer with every metric that Cura holds on a company. The fund performance history stays in Taylor’s own source documents.
Portfolio news that reaches marketing
Taylor’s colleague on the operations team runs Storm’s marketing. Some portfolio announcements reached that colleague late, from a LinkedIn post seen by chance.
Cura watches LinkedIn, X and the news for every Storm company and puts the posts in one feed. In September, Taylor’s colleague filtered the feed to funding, customer traction and new hires, and to Storm’s more recent funds. Storm’s IT team had set up the Cura connector in Claude, so the connection took one click.
One rule goes with it. For a draft that will go public, Claude gets an instruction to use public data only. Some funding news reaches Storm by email before the company announces it.
Key takeaways
- Keep every file. Then load the archive once. Taylor’s saved decks and emails gave Storm a history in Cura from the start.
- Ask for the source with the number. A partner, a controller and an LP all ask where a number came from. Keep the link to the document next to the value.
- Give your AI assistant one source. Taylor’s Claude project uses only the Cura connector. With one source, Claude does not mix tools.
- Use public data only for public drafts. Private news arrives by email before a company announces it. Tell the assistant which data it can use.
Thank you to Taylor for sharing Storm’s story.
Read more customer stories
For small teams with a long history
See Cura running on your own portfolio.
Storm started with a drive of saved updates. Start with yours. Book a demo and we’ll load your portfolio into Cura.
Book a demo