[adambenayoun]

Joseph - thanks a lot for the feedback. We're at the stage that we're looking for feedback from other individuals and see how they are experiencing the pain we've experienced in the past.

We intend on reading every single feedback left on our form and here and discuss how we can better serve our potential users.

By the way - I loved the "github for specs" :)

[josephfung]

No problem. Good luck with the new service.

Oh yeah - thinking back to consulting work - something that let me "make a beautiful spec and share it" would have felt like a one-time-use service. Subscribe for a month, make a spec, take the learnings and add it to my own Word template.

The problem I mentioned (collaborative spec maintenance) is something that I know I'd pay for as a subscription - specifically because it helps me manage something for the ongoing health of our products. It becomes more core.

The only downside is that a solution more aligned to infrastructure costs (as I have suggested) can't command as high a price premium as something that is aligned to revenue (i.e. help me rationalize/explain higher estimates to customers).

[adambenayoun]

We're not planning on stopping at "make a beautiful spec and share it" - we are building a tool that ease the pain of writing and collaborating on specs - with your clients and/or team.

Your feedback however is very valuable - since the product is still in its infancy (heck we haven't launched yet) and knowing we love to iterate a lot and based on real world findings - this is this kind of feedback that will help us shape the product.

So again - thanks a lot!