We generated $100M in pipeline in six months for an analytics product. The way we did it violated almost every demand gen playbook I'd ever read.
A real $100M pipeline result from Salesforce/Tableau reveals what most enterprise demand gen gets wrong: it targets the technical buyer (data engineer, IT architect) when the business unit leader is the one who actually funds the deal. The key insight is dual persona messaging — positioning simultaneously for technical credibility and business outcome. The essay covers why most enterprise pipeline fails at top of funnel, the specific messaging shift that changed results, and what $100M in pipeline actually requires to build.
The number sounds impressive. $100 million in pipeline in six months. I've put it on my resume and my bio and every profile I've ever written. But the honest story behind that number is more useful than the number itself, because it came from recognising a mistake we'd been making for months before we fixed it.
We were selling to the wrong person.
Enterprise analytics software has always had a two-buyer problem. There's the technical buyer — the data engineer, the BI architect, the IT leader who evaluates capabilities, tests performance, and ultimately signs off on whether the tool can do what it claims. And there's the business buyer — the VP of Sales who wants their pipeline forecast in real time, the CMO who wants to understand which campaigns are actually closing deals, the CFO who wants one version of the truth for the board deck.
These two buyers want completely different things. The technical buyer wants to know about connectors, scalability, and governance. The business buyer wants to know what changes for them on Monday morning. Most enterprise software companies pick one audience and write everything for them. Usually they pick the technical buyer, because those are the people who show up to evaluations and ask detailed questions.
We had been doing exactly this. Our messaging was technically rigorous and genuinely accurate. It was also, for a VP of Sales trying to decide whether to fund a major analytics initiative, almost entirely opaque.
The shift came from a sales call where I was listening in. The field rep had walked through our standard deck — architecture, performance benchmarks, integration capabilities. The VP of Sales across the table was polite but clearly waiting for something that hadn't arrived. At the end he asked one question: "What specifically will be different for my team six months after we deploy this?"
The field rep answered it well, actually. He said: "Your reps will know which deals are at risk before you have to ask them. They'll be able to run their own forecast analysis without waiting for the analytics team. You'll stop losing deals because someone found out a customer had a problem three weeks after the customer knew about it."
The VP of Sales leaned forward for the first time in the meeting.
Everything the field rep had just said was true, and it had been true of our product for years. But it wasn't in our messaging. We were leading with the architectural story and hoping customers would draw the business outcome conclusions themselves. They weren't. They were evaluating us as an analytics infrastructure tool and making decisions based on infrastructure criteria — which meant we were winning the deals where the champion was a data engineer and losing the ones where the champion was a business leader.
We rebuilt the go-to-market positioning around what we came to call "insight democratisation" — the idea that every analyst in your organisation could have access to the insights that only your best analysts could find before. We didn't change the product. We changed the story about what the product was for.
The technical content didn't disappear. Technical buyers still needed to evaluate capabilities. But we restructured the sequence: business outcome first, technical proof second. The value proposition your CFO could understand had to come before the connector catalogue your data engineer needed to see.
The second change was in how we trained the field. We built a parallel set of discovery questions for business buyers — not "what data sources do you need to connect?" but "what business decisions are currently too slow because the data isn't available when people need it?" Different questions surfaced different champions. Different champions brought different urgency to deals.
I want to be honest about what this number represents, because I've seen it misused. Pipeline is not revenue. Enterprise pipeline is a collection of opportunities at varying stages with varying probabilities of closing. $100M in pipeline in six months is a real marketing achievement, but it's a leading indicator, not a lagging one. The only thing that validates pipeline is close rate and average deal size over time.
Our close rates on the pipeline we generated also improved — which is the more meaningful number, and the one that made the revenue organisation take the messaging work seriously. When your pipeline conversion improves alongside your pipeline volume, it's evidence that you're finding better-fit opportunities, not just more of them.
The structural lesson: most enterprise demand gen programs optimise for pipeline volume at the expense of pipeline quality. More leads, more opportunities, more top-of-funnel activity. The harder and more valuable work is ensuring that the pipeline you generate represents real business urgency at the right level of the organisation. A VP of Sales who understands exactly what changes for their team is a better opportunity than a data engineer who's excited about the architecture.
"The technical buyer evaluates whether the product can do what it claims. The business buyer decides whether anyone will actually fund it. You need both — but you need the business buyer first."
That's the demand gen lesson I still apply at UiPath. When I review enterprise marketing programs, the first question I ask isn't "how much pipeline are we generating?" It's "who is our pipeline champion?" The answer tells me almost everything about whether the pipeline is real.
Kuber Sharma leads platform product marketing at UiPath. He writes Positioned, a newsletter on AI-era product marketing strategy for enterprise PMMs.