Frequently Asked Questions


Why should I use a tech writing consultant instead of a full-time employee?

There are many reasons for hiring tech writing consultants; for example:

  • You need extra staff for crunch times.
  • You need a particular project done fast, and your current writers are too busy to do it.
  • You have a project that requires an extra degree of attention because it is unusually large and important to your company.
  • You need a person with special skills, such as a template developer, API writer, communications manager, or a person with expertise in meeting presentation and facilitation.
  • You don’t have the head count for a permanent employee.
  • You want to start up a Tech Pubs department, but don’t have an established workflow or job description yet.
  • You find through an internal review that you are missing critical operational docs.

Can’t I get by with a junior writer?

Maybe, but our clients have found that experienced writers need little training and ramp-up time, work expertly and efficiently, and end up being much more cost-effective than junior writers. And after using Write Quick’s tech writing services, you may find that you’d like us to mentor your junior writers as you develop your Tech Pubs department.

I don’t know what kind of documentation I need. Can Write Quick help?

Absolutely! In fact, Write Quick’s new TechPubs In a Box® service was designed to provide you with everything you need to start a Tech Pubs group “out of the box.” After reviewing your products and services, Write Quick helps you plan your documentation and workflow. Write Quick can recommend the most appropriate tools and software, as well as hire, train, and mentor your technical writers. Write Quick can also manage your project, track user satisfaction, troubleshoot problems, and run usability studies.

Why can’t the engineers write the documentation?

Often, engineers can produce decent documentation, but in most cases, they don’t have time and it’s not what they want to be doing. Plus, they are often too close to the nuts and bolts of the product. Professional technical writers approach your product from the customer’s point of view, seeking to educate and guide in such a way that your users get the most value and best possible experience from your products.

What value do technical writers add besides writing the docs?

A technical writer’s role goes beyond just writing—technical writers are active participants in product development. Often, as a result of documenting products, technical writers discover defects or have ideas to improve usability. We can produce internal cheat sheets that will shave time and money off the cost of your projects. And, we produce a centralized repository of clearly written, organized information that can serve your internal staff as well as your customers.

Customers often believe that the quality of a company’s documentation represents the quality of its products. Many times, especially with early development software, the documentation is the first “product” a customer or potential customer will see. If it is professionally produced, it can serve as a powerful form of marketing and sales collateral.