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.
A significant part of my income comes directly from my cheerful
willingness to scramble to pick up the ball after the client
has fumbled it. While one can complain that a client should have
excellent planning and execution, the fact is that many clients
simply cannot do their legwork very well, and are willing to
pay good money to people who can deliver the goods regardless.
Of the entire spectrum of disorganized clients, the ones to work
with are those who have a clear idea of what they want, know
quality when they see it, have money (and the authority to spend
it), but are so grossly overworked that they're not on top of things.
What I do is offer a soup-to-nuts package deal: "Give me money,
engineering data, all your presentations and collateral, and an
idea of what you're looking for, and I will deliver something
that is so close that we can print it after one pass of minor
corrections."
The problem with this approach is that the work is bursty rather
than steady-state, with mad dashes to get three clients' work
done on the same day interspersed with periods of silence. You
MUST charge a high rate if you do this kind of work, since projects
that require that you put documents together in almost no time
at all don't rack up the number of billable hours that plodding
away at an enormous manual does.
Personally, I have gotten away from billing by the hour, and am
now generally giving a per-project bid and asking for one-third
up front before I begin work. The arrival of a check proves that
the person I'm talking to has meaningful spending authority, and
greatly reduces my anxiety about how long the project will slip.
Also, clients generally like fixed dollar amounts, because they
are easier to budget for. All my clients have been reasonable about
recognizing the need to re-quote projects that have changed to
any great extent.
The flaw in this procedure is that you have to estimate projects
pretty well. So far I have been saved by Fate from a couple of
serious blunders (a grossly underbid project was redefined into
a much fancier form by a client, for instance, and I got to re-bid),
but maybe I have things figured out now.
-- Robert
--
Robert Plamondon, High-Tech Technical Writing, Inc.
36475 Norton Creek Road * Blodgett * Oregon * 97326
robert -at- plamondon -dot- com * (541) 453-5841 * Fax: (541) 453-4139 http://www.pioneer.net/~robertp
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html