
Userdoc
The source of truth for your software project requirements
I'm not a fan of big launches...
With product development, when you're ready to show the world, you're essentially continuously launching over and over again.
But this was our first launch, v0.1 of our launch.
We contacted
- Our professional networks
- Our personal networks
- Our social networks
- My mailing list
And we got 5 customers signed up.
That doesn't sound like much, but it's what I expected for a niche product.
Now the fun part comes, as we get to really understand and evolve based on real user feedback.
After selling our business, my wife and I took off in an RV around Australia for 12 months.
This gave us a lot of time to think, and we decided we really wanted to build (and complete!) a product, and Userdoc was it.
We built a lot on the road, but the majority was when we finished travelling and settled back down in Melbourne.
We spoke with many potential customers. Agencies, freelancers, product businesses.
We knew Userdoc would have been handy for out agency, but did other people think the same?
1 Like
Comment
I was 110% busy running my agency, but on the weekends I would hack on the concept of a tool to "Capture user stories", which I knew would be beneficial for both my agency staff, and also our clients.
Hobby projects are meant to be fun, but this led to re-writing it a bunch of times in different technologies... so it never really got finished.
Oh the joys of being a programmer! 😆
1 Like
Comment
After running a software agency for 5 years, I realised that once you have a great team, and a great bunch of clients - the biggest problem in delivering high-quality software projects - is capturing the right requirements.
The initial seed has been planted 🌱
1 Like
Comment
About
My wife and I have ran a software consultancy for 8 years, and we found that after sales and staff - our biggest challenge was capturing requirements, confirming requirements, and getting everyone on the same page.


Comment