How do you decide what to build next?

For a long time, one question controlled my roadmap:

“What should I build next?”

I’d check competitors.

Read feature requests.

Browse Product Hunt.

See what other founders were building.

Then add another feature to the list.

It felt like progress.

But honestly, I was often just looking for something to build instead of something to solve.

Then I started asking a different question:

“What is stopping someone from getting value from my product?”

That changed everything.

Maybe they don't understand the product.

Maybe onboarding is confusing.

Maybe the export is too slow.

Maybe they don't trust the results.

Maybe they don't see why they should pay.

Maybe the bigger problem is that nobody is finding the product.

None of these problems need another shiny feature.

Sometimes the next thing you need to build is:

A better landing page.

A simpler onboarding.

A clearer explanation.

A better sales process.

Or just 5 conversations with real customers.

I’m slowly changing how I build now.

Customer problem first.
Feature second.
Because building something nobody needs feels productive...

until you realize you've spent another week moving in the wrong direction.

♥ 4 · the post on X

Your best feature requests come from users. 💡

Your roadmap is a guess. Your users are the signal.

I use Upvoty for this.

♥ 19 · the post on X

Building Babya in public, day whatever.
The first version only does one job. Log a feed fast, see the last one, do not make me think.

I almost added sleep, diapers, pumping, growth charts, the whole lot. Then I remembered I would be using this with one hand in the dark.

So I cut it.

If you have used a baby tracker, what is the one screen you actually open at night, and what is the stuff you never touch?

♥ 3 · the post on X

One underrated way to find business ideas:

Search Flippa.
Not necessarily to buy anything.

To look for sites with:
- traffic but weak monetisation
- ugly UX
- stale technology
- abandoned communities
- manual processes
- valuable niches

the post on X

One thing I've learned from building products:
A smaller product that solves one problem really well is usually easier to sell than a huge product with 20 features.

Don't build the dashboard first.

Build the reason someone would pay.

♥ 5 · the post on X

I’ve noticed something while building Hilead.

The features that get the most “thank you” messages are almost never the complex ones.

It’s the boring, practical stuff:
- Readable text
- Language-based conditions
- Simple sequence logic

The flashy features get attention.

The small ones get retention.

♥ 6 · the post on X

adding a feature feels like progress. but if users aren't coming back, another feature probably won't fix it.

watch where users get stuck, what they repeat, and where they drop off.

fix that before adding more.

♥ 1 · the post on X