FeaturePulse: User-Driven Feature Prioritization for Micro SaaS Founders

What product should I make next?

I went through this same “what should I build next” loop and it almost killed my product. I stopped adding stuff and did two things: checked what people actually used, and talked to every paying user about what they’d miss if I deleted features. I’d pick one core flow that ties all your stuff together, like “get a lead and turn it into a sale,” then make every feature serve that. For example, tighten the path from Forms → Widget → Bookings → simple CRM or inbox, instead of adding more standalone tools. What worked for me was watching sessions and asking “where do they drop off?” before writing a single new line of code. On the marketing side, I tried Hootsuite and Later, then ended up on Pulse for Reddit because it kept surfacing threads where people were asking for exactly what we built, which told me what problem to deepen rather than what to build next.

Hi, I wouldn't add a single one if none of your users want it. Instead, you could edit the page so everything looks more professional and not so Vibecoded. But cool ideas!

I went through this same “what should I build next” loop and it almost killed my product. I stopped adding stuff and did two things: checked what people actually used, and talked to every paying user about what they’d miss if I deleted features. I’d pick one core flow that ties all your stuff together, like “get a lead and turn it into a sale,” then make every feature serve that. For example, tighten the path from Forms → Widget → Bookings → simple CRM or inbox, instead of adding more standalone tools. What worked for me was watching sessions and asking “where do they drop off?” before writing a single new line of code. On the marketing side, I tried Hootsuite and Later, then ended up on Pulse for Reddit because it kept surfacing threads where people were asking for exactly what we built, which told me what problem to deepen rather than what to build next.