The Blame Game Won’t Fix Your Growth: Why Product Velocity Is the New Sales Lever

·Commentary on SaaStr

You’ve seen it happen. Growth decelerates. The board gets nervous. The CEO fires the VP of Sales, hires a new one, and waits six months. Rinse, repeat.

Jason Lemkin over at SaaStr calls this “the blame game” in a recent piece, and he’s right that the answer has changed. For most of B2B history, products were static. A great sales leader could walk in, upgrade the team, reroute leads, and double revenue in 90 days. That playbook worked because the product was a constant.

But in 2026, products evolve in months, not years. Lemkin argues that when growth slows, you should ask the product question first — because a mediocre product will stump even the best sales team. Our data backs this up, but it also reveals a layer he didn’t touch: the internal misalignment between sales and product teams is often the real bottleneck.

At PainSignal, we track over 13,000 real problems from workers and business owners across 64 industries. In the Product Management category alone, we track 12 distinct problems, and many of them revolve around product competitiveness and feature gaps. Across SaaS, problems like “product not competitive” and “features behind competitors” consistently rank high in severity — often above 3.5 out of 5. That means the product issue is real, not just a convenient excuse.

But here’s the twist: in the same dataset, we see an equally high number of problems related to sales execution, pipeline quality, and misalignment between what sales promises and what product delivers. The blame game isn’t about choosing sides; it’s about a broken feedback loop.

Lemkin’s diagnostic questions are solid: check if your competitive position has eroded, if win rates are declining against specific rivals, if your release velocity is too slow. But he stops short of addressing how to fix the underlying coordination problem. Many founders I talk to say their sales team and product team barely speak — or when they do, it’s to point fingers.

The best companies we’ve studied share a common pattern: they align on shared metrics. Instead of sales blaming product for lack of features and product blaming sales for overpromising, they both track a single north star — like net dollar retention or competitive win rate — and tie bonuses to it. When both teams own the same outcome, the blame fades.

Another insight from our data: the pace of product change isn’t uniform. Lemkin says products get stale in months, but we see many mature B2B companies still shipping major releases on a 6-12 month cadence and growing fine. They succeed not by chasing every AI trend, but by focusing on reliability and integration. Velocity matters, but so does coherence. A product that ships every week but breaks customer trust is worse than one that ships twice a year with polish.

So what should an indie hacker or seed-stage founder actually do when growth slows?

First, don’t fire anyone yet. Run Lemkin’s diagnostic. If your product is genuinely competitive and win rates are stable, then it’s a sales execution problem — and a new VP of Sales might help. But if your product is falling behind, no sales leader can save you.

Second, invest in the feedback loop. Make your sales team document every lost deal with competitive intel. Share that intel with product weekly. Ensure both teams have a shared dashboard of metrics they jointly own. This doesn’t require a big budget — just a spreadsheet and a recurring meeting.

Finally, be honest about your release cadence. If your competitors ship weekly and you ship quarterly, you need to accelerate or differentiate on something that can’t be replicated quickly — like domain expertise or data moats. Speed isn’t the only lever, but it’s become a table stake.

Lemkin’s piece is a necessary wake-up call for founders who default to sales as the scapegoat. But the deeper truth is that fixing growth requires fixing how product and sales talk to each other. The companies that thrive won’t have better sales teams or better products — they’ll have both, and they’ll align them on the same mission.

Want to explore the real problems your business faces? Check out the full dataset at PainSignal. The data might surprise you.

This article is commentary on the original article by Jason Lemkin at SaaStr. We encourage you to read the original.

Explore more problems and app ideas across SaaS, B2B Software.

Browse App Ideas

Join the beta — full access for the first 1,000 builders

Join Beta