Technical writing/Online help for web application


We have developed a web application. Now I am looking for freelancers who can write the online help and technical manuals for parts of it. However, I am not aware of the way these services are charged( num of pages ? / type of application ? / hours of work ? / etc ). Can anyone help me understand how these services are charged for and what are the market rates ?

Contract Documentation

asked Nov 11 '09 at 00:01
96 points

2 Answers


If your application is intuitive, it should be no more than $25 / hourly, usually less. This is how I based that:

Typically, documentation is done by testers, people who use each daily build and become almost as familiar with the application as the developers themselves. The average salary for them starts at about $41,600.00 / yearly, or approximately $20 / hour based on a 40 hour week.

I think, you'll end up paying that (roughly) even if hiring a freelancer charging $10/hourly , as there is a bit of a learning curve involved.

I would not go with a per page quote unless the person is already at least familiar with what they are documenting. What you'll get is a best effort to do what they can while still making some money out of the deal, wherein you'll end up spending close to the higher hourly rate I described while getting their output presentable and accurate.

I could be off a few bucks in either direction. Basically its the same bottom cost as far as a single project goes, what remains is how you go about getting to it. Pick the path of least frustration.

answered Nov 11 '09 at 00:40
Tim Post
633 points


You sure you need the help? I feel the same about writing documentation as I do about doing customer support.

You as a maker should be doing this yourself.

Especially early on in the life of what you made. You'll learn an incredible amount by doing this exercise yourself. If you find you need to write a ton to explain parts of your application, now you and your customer are going to be sharing the same pain. If you don't like writing about it, the chances your customer likes reading about it is slim.

Writing your own help and documentation will provide tons of good hints of where your application actually needs to become simpler or more intuitive.

answered Nov 11 '09 at 02:42
Nathan Kontny
1,865 points
  • If the guy can't write well, specially for a layperson to understand, he might be killing his product by writing the docs himself. Better to use outside people for testing your product before your potential clients drop it or you get bad press/word of mouth. – Gabriel Magana 14 years ago
  • I think Nathan's got a good point about what you can learn from writing your own technical documentation, but probably, when it comes down to it, Gabriel is probably right here. It's not about what you as a developer can learn from it, it is about providing something helpful and meaningful to the user. Only write your own technical documentation if you are as good at spelling, grammar, graphic design, and "explaining things to Grandma" as you are at writing code. – rbwhitaker 12 years ago

Your Answer

  • Bold
  • Italic
  • • Bullets
  • 1. Numbers
  • Quote
Not the answer you're looking for? Ask your own question or browse other questions in these topics:

Contract Documentation