Show HN: Userdoc – My new startup after selling my development agency (userdoc.fyi)

9 points by chrisrickard ↗ HN
Hey HN, my wife and I ran a software development agency for 8 years, and sold it recently to work on some products related to our experience, and Userdoc is our first product :)

Userdoc is a requirements management tool with AI assistance, allowing you to easily create user stories, personas, and user journeys with AI assistance.

We found managing requirements (especially on large systems) was quite tricky, so Userdoc acts as the source of truth for your software requirements, and integrates with your project management tools to sync your stories, but keep them centrally in Userdoc as living documentation.

Would love any feedback, there's a quick video on the website!

8 comments

[ 4.4 ms ] story [ 29.7 ms ] thread
Congrats on the launch! How does Userdoc compare to project management tools like Jira, Asana etc?
Cheers! User does not replace project management tools like Jira, in fact they work together. Where Jira is about planning and implementation (who does what, when, hows it's progressing etc) - it's not a great place to keep requirements, especially as your source of truth.

So where Userdoc comes in is.. 1. The requirements gathering phase (e.g. work with your clients or team) 2. The requirements sign-off phase (get clients to approve the requirements) 3. Sync all requirements into Jira, Asana, Trello - 1000's of other platforms. 4. Testing - you can export documents of all the stories and AC's easily 5. Changes - instead of making new stories for changes, alter the existing AC, and sync 6. Long-term documentation - don't lost your requirements after the sprint ends

Looks awesome! Were there specific challenges you faced in your agency that sparked your idea to build Userdoc?
Much appreciated.

I ran my agency for 8 years, and we had a small clients, but worked on large complex projects.

I started with Google docs, then Confluence, then Notion - but I could never find a tool suitable (and opinionated) enough for capturing all this info.. as I really wanted to build a map of the system in docs, that was easy to reference when the next sprint comes up.

Userdoc has been designed to facilitate the initial collaboration with the client (user story mapping, personas, journeys etc), but also be a business asset, where requirement specs are iterated on, approved, and kept as long term documentation. As an initial test, we used Userdoc on a very large government project, and it significantly helped the whole team.

This looks great. Will definitely try it out. I run a dev shop and have been thinking along these lines also.
I wonder if the demo sound is generated from text? I think it's good enough, probably would pick more informal or fun profile not to sound so robotic.
Thanks for the feedback, and yeah the voiceover is generated using murf.ai. I picked the "funnest" voice I could find, but it was a trade off of me messing with re-recording myself 50 times, or using text to voice. Will definitely take this on board.