Sorry but what about this is "Show HN"? You're not <i>showing</i> anything!<p>This seems to be a fairly common thing on HN - have half an idea, do a bit of webdesign and create a email-submission form.
This is an ok home page.<p>Your idea could be very good or very bad, depending on how your service works. But right now, there is no way to tell because it shows nothing at all.<p>You basically asked for some feedback on the content of some <title> tags.
Like the title, but was disappointed.<p>Coming up with a spec format that clients will like has always been a fairly easy problem to solve - as well the spec is usually worked on once the project has been awarded, so isn't even part of the sales process. As well it's hard to improve the writing + sharing experience of Word + Email or Google Docs + Sharing.<p>The attention to estimating is nice, and will save freelancers or less experienced teams time, but is only really useful to teams that do contract and custom work.<p>I was hoping for more of a focus on the collaborative work that comes out of writing specs: more around the commenting/editing/workflow. When working on a spec (either internal or external) change requests or modifications are important, as are interdependencies and change tracking.<p>Your product title made me think "GitHub for Specs" and it doesn't seam you're going that way. Shame.
Something to help format and present specifications to a client would likely be something I would be interested in trying.<p>However basing estimates on "industry averages" is probably about as bad an idea as letting your manager estimate your work for you.<p>As Joel Spolsky has said in at least one article[1]: <i>Only the programmer who is going to do the work can figure out what steps they will need to take to implement that feature. And only the programmer can estimate how long each one will take.</i><p>Industry averages might be usable at some level as a sanity check, but honestly most software that is more complex than very basic CRUD is not going to conform to any "averages" for purposes of estimating.<p>[1] <a href="http://www.joelonsoftware.com/articles/fog0000000245.html" rel="nofollow">http://www.joelonsoftware.com/articles/fog0000000245.html</a>
Nothing to see here but I am curious to see what this team has come up with. As a UX Architect/Product Manager it's a tough game staying on top of client requests, clarifying them and then handing them off for development. I think the challenge is having something that meets the needs of everyone but is flexible enough to adjust for unforeseen work, new requirements and shifting priorities.
Like the project idea, but like others have said, there's nothing much to show for right now.<p>I understand what you're trying to do -- outsourcing requirements for your MVP before invest more time -- but seriously, call a spade a spade... (This is probably more Ask HN than Show HN.)