1
0 Comments

We said “no” to a client with a big budget. I’m still thinking about it.

A few months ago, we had a potential client that seemed perfect. Good budget, clear idea, nice people. Everything looked fine.

But the more we dug, the more it felt like there was no real core. No clear first value moment. Too many directions. Too many “we’ll see” features.

We could’ve taken the project, made the money, and shipped something. But it didn’t feel right. So we said no. Suggested simplifying the idea first.

It wasn’t easy. I kept second-guessing myself for weeks. But experience tells me building something that shouldn’t be built yet usually ends badly — for both the client and us.

Has anyone else here ever stopped themselves from building something, even though they technically could?

on April 15, 2026
Trending on Indie Hackers
I built a tool that shows what a contract could cost you before signing User Avatar 111 comments The coordination tax: six years watching a one-day feature take four months User Avatar 73 comments My users are making my product better without knowing it. Here's how I designed that. User Avatar 63 comments A simple LinkedIn prospecting trick that improved our lead quality User Avatar 50 comments I changed AIagent2 from dashboard-first to chat-first. Does this feel clearer? User Avatar 39 comments Why I built a SaaS for online front-end projects that need more than a playground User Avatar 15 comments