Customer story
Exceptional Capital spent two years building a portfolio bot. Cura replaced it in 48 hours.
With Melissa Aurigemma, Chief of Staff
- to the whole team using Cura
- 48 hrs
- a week back for Melissa
- 5+ hrs
- portfolio companies, 4 team members
- ~30
- Firm
- Exceptional Capital, pre-seed and seed fund
- Portfolio
- ~30 companies, 4 team members
- Switched from
- A homegrown Slack bot
- On Cura since
- Early 2026
Melissa Aurigemma used to block calendar time for portfolio support. At least once a week. Sometimes daily.
Melissa is Chief of Staff at Exceptional Capital, a pre-seed and seed stage fund that supports ~30 companies with 4 team members. Before each block of support, there was always a lift. She first had to piece together what to execute.
For two years, the team tried to build its own Slack bot to hold that portfolio context. In early 2026, Exceptional adopted Cura. The whole team was using it within 48 hours, and Melissa now gets 5+ hours a week back.
From four places to dig to one place to ask
The lift had four parts. Melissa ran global Slack searches for things people had mentioned in passing. She checked emails that she had scraped into a Google Sheet. She read WhatsApp threads. She pinged team members to find where each task stood.
“By the time I’d actually pieced together all details of what to execute, I’d burned 30 to 60 minutes. Then the actual ‘work’ started.”
Now the same prep is a single @Cura query in Slack. Slack threads, forwarded emails, Granola transcripts and the metrics sheet all sit in one place.
Before Cura
- 30 to 60 minutes of digging before the work started.
- Context spread across Slack, email, WhatsApp and Google Sheets.
- Pings to team members to find where each task stood.
- Intros volunteered on calls, then forgotten.
- A homegrown Slack bot that needed 15 to 20 minutes most days.
The work started after the digging.
With Cura
- One @Cura query in Slack.
- Slack threads, emails, Granola transcripts and the metrics sheet in one place.
- Cura assigns the task and keeps the context.
- Intros and follow-ups from calls become tasks.
- The bot is retired. No daily upkeep.
5+ hours a week back for Melissa.
Two years on a homegrown Slack bot
For two years before Cura, Melissa tried to build an internal solution. With the help of engineering resources, the team developed a viable Slack bot.
Then the portfolio grew, and the in-house build had a hard time with context. The bot was Q&A, as opposed to a fully unified orchestration. Melissa saw that the firm needed something more sophisticated.
“It became time consuming to maintain and upgrade — 15 to 20 minutes most days fiddling with it to kinda work.”
So she stopped. Cura did out of the box what she had tried to build. The homegrown bot is retired, and the upkeep went with it.
Five steps to set up
As the portfolio grew, Melissa decided to give Cura a try, mostly to buy back the time lost on admin work.
Her expectations were low. Exceptional has a handful of email accounts, companies in all different stages, and a very active Slack channel that gets messy. She thought the data would take a while to register in a helpful way. “It was really like 24 to 48 hours,” she said.
Setup was five things. Tag @Cura into the relevant Slack channels. Add domain names in the web app. Forward a few emails. Connect Granola. Share a Google Sheet with current metrics.
Within hours, everything was in one spot.
One tag for the whole team
Exceptional asks its portfolio questions in Slack. A single @Cura tag queries the Slack threads, the forwarded emails, the Granola transcripts and the metrics sheet.
The team came along just as fast as the setup. Their first reactions were about the speed. Marell Evans, the firm’s founder, watched Melissa walk through it.
“Marell (General Partner and Founder) was watching me walk through it and said, this is like a hire. I replied — you’re not wrong.”
Intros that get done
A few days in, Melissa noticed a task that Cura had generated and assigned. An intro had come up on a call with a founder.
Melissa slacked Andrew Van Nest, the firm’s Managing Partner, about it. He didn’t remember the context. She didn’t remember either.

She tagged @Cura in Slack. Two seconds later she had the exact context: open-source licensing, why the intro had come up, and where in the call it was mentioned.
Andrew, looking back through it: “ohhh yea!!!”
“Great example of something smart said on a call and lost forever — until Cura haha.”
Key takeaways
- Count the minutes before the work. Melissa burned 30 to 60 minutes on digging before each block of portfolio support. Measure that time first.
- Price the upkeep of a homegrown tool. Exceptional’s Slack bot was viable. It also took 15 to 20 minutes most days to keep it working.
- Ask where the team already talks. Exceptional asks its questions in Slack, with one @Cura tag. The whole team used it within 48 hours.
- Turn what you offer on a call into a task. An intro offered on a call is easy to lose. Record the task, and keep the reason with it.
Thank you to Melissa for sharing Exceptional Capital’s story.
Read more customer stories
Portfolio management without the busywork
See Cura running on your own portfolio.
Book a demo and we’ll load your portfolio into Cura. Reviews, KPIs and the signals you can’t afford to miss, all in one place.
Book a demo