What did you see when you first stepped into the role at DefenseStorm?
DefenseStorm had a solid tech stack already in place — clearly thought out to make life easier for AEs. But I wasn't familiar with Fluint. When I started diving in, I saw the potential right away. The challenge was adoption. A tool is only as good as how much the team actually uses it, so that became my first focus.
How did you drive adoption?
I made it close to mandatory. If a rep didn't have a mutual success plan or a consolidated deal review in Fluint, it was going to be hard for me or any SLT member to understand forecast confidence. Once the team understood the why — that this was about pipeline clarity, not busywork — adoption started moving.
What does Olli actually do for your deal reviews?
Because Fluint pulls in everything from Salesforce and Gong, Olli already has the full picture before we even sit down. It'll surface what problems we're solving, positive business outcomes, metrics — and then score the deal against MedPICC. It literally calls out your gaps. If you think you understand the process because you know who signs off, but you don't have a timeline, Olli flags that. It's real.
What's the outcome you've seen most clearly?
Forecasting. We increased our win rate to 33% by using Fluint to understand our gaps and pressure-test our pipeline. As a deal progresses, Olli's confidence score moves with it. The team started asking better questions — why is Olli scoring this at 20%? What are we missing? That shift in thinking has been huge.
Is there anything Olli does that you just couldn't replicate without it?
The just-in-time coaching. When my reps are prepping for a call, Olli tells them what discovery questions to ask and what gaps still exist in the deal. Without that, they'd be spending a lot of cycle time trying to figure out where they stand — and probably missing things. With Olli, it's like having a coach available any time, even when I'm not.
What have you started using more recently with Fluint?
The flows. We're using workflows now to send breakup emails on stalled deals — and some of those deals come back. Prospects respond and say they need a couple more weeks. Having that back-and-forth with Olli as part of the workflow has made a real difference in how we manage cycle time.
What would you tell another sales leader thinking about bringing Fluint on?
Think about the problem you're trying to solve. A tool is only as good as its adoption, and adoption only happens when the team understands the why. For us, the why was forecast accuracy and win rate. We've been able to measure exactly that. Know your success metrics before you launch, and hold the team to them.














