Not before you check it. Sellers and buyers give different reasons for a lost deal 50 to 70 percent of the time, so the feature a customer names isn’t always what’s stopping them. How I check which blockers are real, and how to say no without losing the customer.

One missing feature, every time

Spend enough time with a B2B startup's customers and you'll hear the same sentence in different versions: "We'd sign (or roll it out everywhere) if it just did X." X is different for every customer.

At a company I worked with, almost every customer had one. Each could name the feature that stood between them and signing, or between using it in one place and using it properly.

Each request on its own was reasonable. Put together, they described a do-everything platform, which a small startup can't build, let alone maintain.

Is the blocker really the blocker?

Sometimes, yes. Klue analysed more than 3,400 interviews with buyers after a deal closed, and product issues were among the most common reasons they gave for choosing someone else, next to how the sales process went [1]. Missing features do lose deals.

But the reason a seller writes down and the reason the buyer gives are often different. Primary Intelligence, now part of Corporate Visions, compared the two in its win/loss interviews and found they differ 50 to 70 percent of the time [3]. The same research found that 53% of buyers said the losing vendor could have won.

A named feature is an easy reason to give. It's polite and specific, and nobody has to say "we're not sure it's worth the money" or "your demo didn't convince our team". So I treat a blocker as a claim to check. Two questions usually tell you a lot: what do they do today without it, and who else has asked for the same thing?

A named feature is an easy reason to give. It’s polite and specific, and nobody has to say “we’re not sure it’s worth the money”.

What happens if you build them all

Every request arrives with a customer's name on it, so every request looks like revenue. Usually one customer wants it. Once it ships, everyone else gets one more screen, setting or menu item to work around, and the team gets one more thing to maintain. Pendo's usage data from 615 products found 80% of features are rarely or never used [2].

Every request arrives with a customer's name on it, so every request looks like revenue.

The roadmap I set up there worked like an onion: fix the core first, and add layers only once the core is solid. So a request that touched the core (the part every customer used every day) got attention quickly. A new layer that one customer wanted waited, however loudly it was asked for.

Written down, that sounds harsh. I think it's the only way a small team keeps the core working, because every yes to one customer is time taken from the part all of them use.

One door for every request

Saying no is easier when there's a process behind it, so the decision doesn't depend on who asked or how upset they were. This is the one I wrote:

  1. All requests come in through one place. Whoever hears a request sends it to product through Slack, and it lands in Linear in a fixed format: the company, the user, their account status, the request with its business case, and how urgent it is.

  2. Product triages every request within one to three days. Each one gets one of four answers: not now, with the reason; added to a project as a customer request and looked at again each quarter; fast-tracked, if it blocks revenue; or already on the roadmap.

  3. Requests are scored on two things: how much revenue the customer brings, and how well the request fits where the product is going.

  4. Once a quarter, leadership reviews the priorities together.

And one rule sits over all of it: if it's not on the roadmap, it stays in the backlog, whoever asks.

The business case field does a lot of the filtering on its own. If nobody can write one sentence on why a request is worth money, that's already an answer.

If nobody can write one sentence on why a request is worth money, that's already an answer.

Saying no without losing the customer

Most of the damage from a no comes from how it lands. A customer who hears nothing for weeks, or a vague "we'll see", assumes they've been ignored. A clear answer with a reason is easier to accept, even when it's not the answer they wanted.

That's why "not now" in the process always comes with the reason attached, written down so sales can pass it on in the customer's terms. And why those requests come back every quarter: "not now" means "we'll look again in three months", and the customer can be told exactly that.

The fast track is just as important. If a request really is blocking revenue, it shouldn't sit in a queue behind everything else. Having a quick lane for those makes the slow lane easier to defend.

And before any of that, check the blocker. Ask what they do today without the feature, and whether anyone else has asked for it. If it's a real gap that several customers share, it probably belongs on the roadmap anyway. If it's one customer's way of saying they're not convinced yet, building it won't fix that.

Edita Dermontaité

Edita Dermontaité

Hands-on CPO and product leader who still builds (with AI)

I’ve often been the first: the first product hire at Leadcamp and Bizzy, where I led product as CPO for five years, and the first user researcher at Lighthouse, where I spent two years building the research function.


For the past year I’ve worked as a fractional CPO and hands-on product leader, helping B2B SaaS teams between traction and scale connect what engineering builds to what brings in revenue.


I started out as a graphic designer, so I still design and test things myself, these days mostly with AI: in Claude and Lovable, or straight in code with Cursor.


More about me →

Working through this at your company?

Book a free 30-minute call, or a coffee in Ghent. We’ll look at what’s slowing your product down and what to do about it. I work with teams fractionally or hands-on as an embedded product leader, 2–5 days a week, depending on your needs and my availability.

Product leadership for B2B SaaS between traction and scale, from a hands-on CPO and product leader who still builds (with AI). I take product decisions off the founder’s shoulders and get product, engineering and sales moving in one direction: revenue.

Edita Dermontaité speaking to an audience

Copyright © 2026 New North BV

Copyright © 2026 New North BV

Made in Belgium with ❤️

Made in Belgium with ❤️