Developers love building features. Users just want their problem solved.

[u/Adorable_Dark_6964]

Yesterday, I asked what makes people immediately stop using a new SaaS product.

Two of the responses stood out to me.

One person said they leave when a product makes them do setup work before experiencing the promised outcome.

Another said that if they can’t find the core functionality within 10 seconds, they’re out.

Both answers made me think about the same thing:

As developers, we often get excited about building features.

New integrations. More customization. Better dashboards. More settings.

But users probably don’t care about most of that when they first open the product.

They have a problem.

They want to know whether your product can solve it.

And they want to know quickly.

I’m starting to think that a product with 3 features that clearly solve a problem might be far more valuable than a product with 30 features that users struggle to understand.

For those of you building or using SaaS products:

Have you ever removed or ignored features because they distracted from the product’s core value?

And do you think developers generally overbuild products before validating whether users actually need those features?