ediately start collecting structured feedback — bug reports, feature requests, star reviews, open comments — all in one place, with a clean dashboard and a voting board so the loudest requests would naturally rise to the top.

Everything out there was either too complex, too expensive, or required my users to create an account just to leave a comment. So I built NoteBoard.

The product evolved a lot during the build. I originally planned for a simple feedback form. Then I added feature voting because I realized the most painful thing isn't collecting feedback — it's deciding what to actually build next. The voting board solved that. Then I added team collaboration because solo products don't stay solo forever. Then analytics, because patterns matter more than individual comments.

The pricing model also evolved. I started thinking subscription, then realized: why? This is a tool, not a service. You set it up once, it runs forever. A one-time $39 felt right — honest, simple, and the kind of pricing that builds trust instead of anxiety.

NoteBoard is what I wished existed when I started. Now it does.

20:T6a4,

I built NoteBoard because I was drowning in my own feedback.

When I launched my first products, user feedback came from everywhere — WhatsApp messages, Discord threads, random emails, comments in places I'd forget to check. By the time I'd collected it all, half of it was lost or I couldn't remember the context. I wasn't ignoring my users. I just had no system.

I wanted something I could drop onto any website with a single script tag and immediately start collecting structured feedback — bug reports, feature requests, star reviews, open comments — all in one place, with a clean dashboard and a voting board so the loudest requests would naturally rise to the top.

Everything out there was either too complex, too expensive, or required my users to create

NoteBoard

About