TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
>Hello all,
>can anyone recommend for me sources of information on freelance
>technical writing, especially what the going hourly rates are for
>tech writers? I might be moving from salaried work to freelance,
>by-the-hour, contracting work, and I'm not sure where to begin. Any
>suggestions?
>
>Thanks,
>Lori Brannigan
>lbranniga -at- lanshark -dot- com
My reply:
Hi Lori,
Assuming you are not a shill for Peter Kent <wicked grin>:
Run, do not walk, to pick up a copy of "Making Money in
Technical Writing" ISBN 0-02-861883-1 by Peter Kent. The new
edition is just out. This book will answer all of your questions
and more. At $16.95 US (list price) you just cannot afford to be
without it.
DISCLAIMER:
I am in receipt of a review copy of the book. As such I am
concerned with the integrity of the review process:
1.) My copy came to me free in exchange for my obligation to
write a review and get it published. I want you to know that.
When I do it will be my 33rd published book review.
2.) I have not finished reading it. I want you to know that
also.
That said, Peter Kent's new book will not tell you what rates
are in your area. It will tell you how you can determine those
rates for yourself. Kent's book is balanced in that he sets
forth the downside aspects of freelancing as well as the upside
potential. Freelancing is not for everyone. Before you jump into
the field, you owe it to yourself to look at both sides of the
question. I've read enough of the book (roughly 2/3) to believe
that some people can (and will) make $100,000 a year in
freelance technical writing but not everyone will.
Kent sets forth the success criteria in a mature, reasonable
way. Ability to write is not highest on the list.
Nea mentioned that roughly 1/3 of your gross receipts will go
for taxes. Kent's book speaks to that issue and he points you to
information sources and strategies you can use to reduce
somewhat the tax bite. I'm surprised at the attention he devotes
to aspects such as medical insurance, disability insurance,
retirement planning, working capital needs, etc. This is a 'how
to' book with real information - not cheerleading.
You are already ahead of the game by reading TECHWR-L and asking
a question of the group. Our little corner of the world figures
prominently (spelling?) in his book. As I said I haven't
finished reading it, but I know by now that "Making Money in
Technical Writing" is a keeper. That's why I would be so upset
if I found out you are a shill. <grin>
BTW the book doesn't have too much to say about technical
writing itself.
It is believed that writers should avoid use of passive voice,
for example,
but how do we know for sure? <grin>
BTW not all technical writing concerns computer program
documentation.
I'm surprised and pleased to find the breadth of his sources on
other aspects of the business.
Best luck to you,
Shorter Rankin, MBA
Sacramento, CA mailto:srank -at- pacbell -dot- net http://home.pacbell.net/srank/index.html
hosting the west coast edition of Kathy Frost's
style guide outline for technical communications
