Building things for yourself first

The best products I’ve ever worked on started as tools I desperately needed but couldn’t find.

There’s something fundamentally different about building for yourself. You have perfect product-market fit from day one — you are the market. You know exactly what success looks like because you feel it when you use it.

Why scratching your own itch works

When you’re the user, you can’t fake satisfaction. You know immediately if something is slow, confusing, or missing the point. Most products built for hypothetical users end up optimizing for metrics that don’t actually map to value.

Personal projects have another underrated advantage: they remove the activation energy problem. When I built a tool for my own workflow, I didn’t need to convince anyone it was worth doing. The ROI was obvious to me immediately.

The flip side

Building for yourself has one trap: you might be an edge case. Your problem might be unique to your workflow, your background, your tools. The real skill is knowing when your problem is universal versus when you’re just solving for one very specific person (you).

The way I think about it: if the idea makes you excited enough to build it for free, for yourself, with no promise of return — that excitement is data. It means you’ve found something real.

Start there.