Hey HN,

My wife and I have built Userdoc, a requirements management system to gather, collaborate on, and confirm your software project requirements.

We ran a software consultancy for 8 years and found that after sales and staff, our biggest challenge was capturing requirements, confirming requirements, and having a standard way for everyone to access these (both clients and staff).

We found important info was being kept solely on a JIRA ticket (and disappeared when the ticked moved to "Done").

Requirements were being confirmed in many places. E.g. verbally, in emails, in project management tools, etc. Which led to miscommunication and a lack of traceability.

And although I had always believed in working software over comprehensive documentation - I found with larger projects and complex business rules, keeping the functionality in your head was a full-time job.

So we developed Userdoc.

An opinionated requirements management system, leveraging standard agile concepts (user stories, user personas, and user journeys) to build a knowledge base for your software project.

There's a video demo on the website which runs through the core functionality.

Let me know if you have any questions or feedback, and thank you!