2
1 Comment

Building Is Easy. Deciding What to Build Is the Hard Part.

Writing code is the straightforward part.
Figuring out what’s worth building, that’s where most startups stumble.

We’ve seen founders with incredible tech end up stuck, not because their product didn’t work… but because it solved a problem nobody really cared about.

The best products don’t start with features, they start with pain.
Real pain. The kind users will pay to remove.

Before writing a single line of code, ask:
“Who is this for and what do they hate doing right now?”

If that answer isn’t painfully clear, the product might not be ready to exist yet.

How do you validate what to build next before investing serious time?

posted to Icon for group Startups
Startups
on October 10, 2025
  1. 1

    That's why they say you shouldn't build a perfect product. You need to start with an MVP and find product-market fit. You'll probably have to change direction a few times to create something people will actually want to pay for.

Trending on Indie Hackers
We just hit our first 35 users in week one of our beta User Avatar 51 comments From Ideas to a Content Factory: The Rise of SuperMaker AI User Avatar 27 comments Why Early-Stage Founders Should Consider Skipping Prior Art Searches for Their Patent Applications User Avatar 21 comments Codenhack Beta — Full Access + Referral User Avatar 17 comments I built eSIMKitStore — helping travelers stay online with instant QR-based eSIMs 🌍 User Avatar 15 comments As a founder we need ideas,insights and lessons, here are some take aways that I've got from HN last week User Avatar 14 comments