find the signal before you scale

A founder I spoke to last month had 12 salespeople, a $4M pipeline, and no answer to a basic question: which deals are real?

She'd done what every advisor, board member, and SaaS playbook tells you to do. Build the sales team and fill the funnel. Measure activity, report to the board. Her CRM was full, her team was busy, and her board deck looked healthy.

But when I asked her which customer profile actually converts, why her best deals close, and what makes the stuck ones stuck, she didn't have answers. Not because she hadn't thought about it. Because the data she was collecting didn't tell her.

She was scaling a process she hadn't mapped.

This is the problem I keep seeing. Founders build revenue teams before they understand what drives revenue. They add headcount, tools, and spend on top of a system they haven't validated. Then, when growth stalls or costs spike, they can't diagnose why, because they never established what "working" looked like in the first place.

I call it the mapping problem. And it turns out there's now academic research that confirms it.

Earlier this year, researchers at INSEAD and Harvard Business School published a randomised controlled trial across 515 startups. The study split founders into two groups. One received structured frameworks to map where value is actually created in their business, where process changes and new tools would have the most impact. The other group had access to the same technology but no structured mapping process.

The results weren't marginal. The founders who mapped first produced 1.9x more revenue. They identified 44% more use cases and acquired 18% more customers, while using 39.5% less capital.

The study's conclusion was striking: access to technology isn't the constraint. Most founders already have the tools they need. What they lack is a structured way to figure out where those tools create value. The researchers called this "the mapping problem," the gap between having capabilities and knowing where to point them.

That finding mirrors what I've seen over fifteen years on both sides of the table. I spent a decade at Accenture leading delivery, writing proposals, and answering RFPs. I understood how work got built and shipped, but I'd never sat inside a dedicated sales function. Moving to Apptio put me there for the first time. The companies that scale well aren't the ones with the best tools or the biggest teams. They're the ones that paused long enough to understand what was actually working before they invested in doing more of it.

At Apptio, I saw what a disciplined sales process actually looks like. Our sales director ran MEDDPICC with real rigour. Every opportunity had to answer specific qualification questions before it moved to the next stage. He knew which deals were committed and which were noise, because the process forced that clarity. It was the first time I'd been inside a sales function where pipeline inspection was a discipline, not a guessing game. That contrast with everything I'd seen before is what made the mapping problem visible to me.

The pattern is always the same. A founder builds a product people want. Early customers arrive through relationships, referrals, and the founder's own hustle. Revenue grows. The board says hire. So they hire. And suddenly, the thing that was working, founder-led selling, intuition about which prospects are real, gets handed to people who don't have that context. The new hires follow a process that was never documented because it lived in the founder's head. Pipeline goes up, and conversion goes down. Nobody can explain why.

That's the moment where mapping would have made the difference. Before adding people and spend, the founder needed to answer a handful of questions. What does our actual buyer look like, beyond the ICP slide deck? Why do our best deals close, and what happens in the conversations that stall? What's repeatable here, and what was a one-off?

These aren't sophisticated questions. They're obvious ones. But most founders skip them because the pressure to scale feels more urgent than the work of understanding what to scale.

signalrev exists to fix this. Not by adding a pipeline or automating outreach. By helping founders map what's actually working before they invest in scaling it. The work is slower than most founders want. It's also cheaper than they expect, because it prevents the expensive mistakes that come from scaling too early.

The INSEAD study put numbers on something practitioners have known for a long time: the founders who slow down to find the signal first don't just avoid waste. They grow faster. 1.9x faster, with 39.5% less capital.

If you're a founder with 5 to 50 people in the company and you're honest about whether your pipeline numbers are real or hopeful, that's where the conversation starts.