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.
I've been asked to prepare an estimate many times and usually they just want a general idea so they don't end up with a 50-page manual that costs $100k. They're likely doing their due diligence. I tell people that I am paid on a time and material basis at X per hour. I can estimate what a manual of that size usually takes, but that there are so many variables, like the number of edits, availability of SMEs, stability of the product, etc., that it takes however long it takes.
I also charge to drive there no matter what the state of the drive unless it is under 30 minutes.
I was doing a req for Amazon last week and I goofed on a number. I emailed my contact, worried they were already concerned that the price was too high, and you know what they said? "I wondered about the low price but I was just about ready to submit it so I'm so glad you caught me in time."
Moral: Sometimes the fear of being too costly is in our heads and not those of our clients.
Good luck!
Lin
-----Original Message-----
From: techwr-l-bounces+linlaurie1=hotmail -dot- com -at- lists -dot- techwr-l -dot- com [mailto:techwr-l-bounces+linlaurie1=hotmail -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf Of Peter Neilson
Sent: Thursday, October 5, 2017 2:35 PM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: Quoting a user manual
I'm hearing red flags going off, especially if you are bidding against others. You should be estimating based on your worth to them, rather than your own costs. "$5000 for turning just one valve?" "No, $5000 for knowing which valve to turn."
You ought to cover contingencies, if the deadline is that short. What if they review your work but deliver their review in a corrupt file that you cannot read, and that makes you miss deadline? What if you find out, at the last minute, that they omitted a crucial piece of information? Stuff like that should cause you to get paid more, rather than be found in default and perhaps not get paid at all.
Others will probably have better suggestions.
On Thu, 05 Oct 2017 17:20:25 -0400, Chris Morton <salt -dot- morton -at- gmail -dot- com>
wrote:
> Hi all,
>
> I charge an hourly rate. I've been wooing a client for many months and
> am finally close to getting what I hope to be my first of many assignments.
> Although I've created many user manuals, I have never had to provide a
> project estimate before.
>
> They project their motherboard user manual will be approximately 50
> pages, with me being handed an InDesign file as its basic structure.
> No problem.
>
> I may have hands on access to a physical unit while I create the
> manual innards. I may have to make one trip by car to the client's
> site, which is but a few hours away through the country (read: likely
> a pleasant road trip).
>
> The deadline for completion is Oct. 27.
>
> Beyond complete specs and ready access to a SME, what other info
> should I ask for before providing an overall project estimate? What
> would you guess that estimate to be?
>
> Chris Morton
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com
Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
