We built Quotavue because CRM forecasting is broken by design.
RevOps leaders deserve a forecast that comes from pipeline reality, not rep optimism.
Eight years of watching forecasts fail the same way.
Lisa Hartwell spent eight years in revenue operations: first at a logistics software company managing a 40-rep sales org, then as RevOps lead at a B2B fintech going through its first growth phase. In both roles, the quarterly close followed the same script. Week 10 pipeline looked healthy. Week 12: a CRO review exposed three deals that had gone dark in week 7. Nobody had updated Salesforce. Nobody wanted to be the one to cut the forecast. The number missed.
The data to catch those deals early was sitting in the CRM the whole time. It was in stage timestamps, in contact engagement gaps, in the close dates that had slipped twice without explanation. But extracting signal from a Salesforce org by hand is not a sustainable practice for a three-person RevOps team.
She built Quotavue in 2025 to read that signal automatically. Not to replace the RevOps team's judgment, but to give them a number that doesn't depend on rep self-report at all.
Lisa Hartwell, CEO and Founder, Quotavue
The team
Eight years managing forecasts in B2B sales orgs before founding Quotavue in 2025. Nashville native. Believes the forecast belongs to RevOps, not the rep who last touched the deal.
Built ML-based deal-scoring pipelines at two mid-market SaaS companies before joining Quotavue as the first engineering hire. Designed the signal-scoring architecture from the ground up.
Ten years running sales and RevOps engagements for B2B software companies. Has sat in more quarterly miss post-mortems than he cares to count. Joined Quotavue to fix the root cause instead of the symptoms.
How we think about this
We derive forecast probability from CRM activity patterns, not from what reps type into the forecast field. The score is the same whether the rep is optimistic or not.
A forecast without a confidence band is just a guess with extra steps. We show the range because that's what a board should be looking at anyway.
Historically the forecast is what sales tells RevOps, and RevOps passes it up. We think that's backwards. Signal-derived forecasting puts the accountability where the analytical rigor is.