Hi HN,

I built Jangoro because I noticed a recurring pattern in the startups I worked for: we would spend months building features based on a single loud customer or a "gut feeling," only to forget a year later why we made that choice or if it actually moved the needle.

Jangoro is a "Decision Accountability System." It essentially acts as a git log for your product strategy.

The Tech Stack:

ReactJS/Remix NodeJS/Express DynamoDB SQLite

I’m using Gemini-2.5 to handle the sentiment analysis of the survey data, but I’ve focused heavily on the "Revenue Weighting" logic to ensure the data is grounded in financial reality, not just word clouds.

What I’d love feedback on:

The Logic: Does the "Customer Truth Graph" make sense to you from a data perspective?

Privacy: Right now, I handle data by manual CSV uploads to an SQLite DB. Is this a dealbreaker for your team?

Use Case: Does your team actually record why you don't build things?

It’s early days and there are definitely some rough edges. I’ll be here to answer any technical questions about the implementation or the data model.