I shipped 3 features this weekend based entirely on community feedback. Here's what I built and why.

Thanks for sharing this mate. Build features based on customers feedback is the perfect things to do, because you build a product users want. Congrats on that!

This is a great example of why shipping based on real user feedback beats building in isolation. The verified MRR via Stripe is a smart differentiator — proof over claims always wins with other builders. Keep iterating!

that build log feature is the right call. I always struggled with showing progress on my side projects in a way that felt alive rather than just a landing page collecting dust. shipped something similar for NoHumans where the agent logs its own actions publicly and found that transparency loop actually brought more feedback than any launch post. the community feedback -> build -> ship cycle you describe is real, took me a while to not be defensive about what people said was missing

Build log + verified MRR is a killer combo for trust. When someone lands on your page and sees real proof of shipping velocity alongside revenue, it removes all the "is this legit?" friction instantly.

We took a similar feedback-driven approach with AnveVoice — our users kept asking for voice-based navigation on their websites, so we built an AI assistant that actually takes DOM actions (clicks, fills forms, navigates) instead of just chatting. Community feedback shaped the entire product direction.

The "Distribution > Validation" mindset resonates hard. Ship fast, listen, iterate. That's how you build something people actually want. Bookmarking IndieDeck — love the concept of turning a static portfolio into a living builder story.

This feels like one of those subtle but important shifts — you’re not just adding features, you’re making the page more credible.

Build log + verified MRR means someone landing there doesn’t have to guess anymore, they can just see what’s real. That usually changes the kind of conversations you get.

Would be interesting to see which one people react to more in practice.

I’ve been following since your launch post (the one that hit #1), and honestly this update makes way more sense than just adding random features.

The build log especially feels underrated, most ‘build in public’ stuff is scattered across Twitter, but this kind of centralizes it into something permanent.

The verified MRR is interesting though, feels like a strong trust signal, and Build log is also lowkey powerful. If people actually use it consistently, it becomes like a live resume.

Overall though, good stuff man this is getting interesting. You’re clearly listening to feedback instead of just shipping blindly

Wait you’re the same guy who hit #1 on Build Board right? Crazy how fast you’re iterating, didn’t expect you to ship this much this quickly.
Looked at the updates you made are really good, love the build log concept. worth following you bro !!

Love seeing feature decisions come straight from the community — that’s how truly useful products get built. The Build Log and Verified MRR ideas are great examples of turning user voice into real positioning rather than just cosmetic updates.

One thing I’d be curious to hear from others here: how do you balance feature requests from vocal users vs. latent needs you observe from user behavior (like analytics or session data)? Because sometimes the loudest voices aren’t the most widely representative of your audience.

In my experience, the creators who systematize feedback — tell users what they built because of their suggestions and then track actual usage — tend to build features that stick instead of features that just feel good to ship.

The Verified MRR via Stripe is smart positioning. Anyone can put '£2k MRR' in a bio. Cryptographic verification makes it real. That one feature shifts IndieDeck from portfolio tool to credibility tool, which is a much stronger hook for the audience you're building for.

I'd push back slightly on 'distribution > validation' though. What you actually did was validation done right. You shipped, community told you what was missing, you listened and built it. That's not distribution first. It's listening first, done publicly. The distribution was a consequence of doing that listening out in the open. Most people get this backwards — they validate in private then wonder why nobody cares when they ship.

Congrats on the #1 spots. How are people finding IndieDeck now that the launch boost has settled?

The real trap with feedback-driven shipping is building what people say they want instead of watching what they actually do in your product. Three features in a weekend sounds productive but you can end up with a cluttered product that satisfies vocal users while confusing the quiet majority who churn. Would love to hear which of the three got actual usage after you shipped it.

How are you verifying MRR exactly? Stripe API or something custom?