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.
RE: Pricing a project without access to the software
Subject:RE: Pricing a project without access to the software From:"Hemstreet, Deborah" <DHemstreet -at- kaydon -dot- com> To:<techwr-l -at- lists -dot- techwr-l -dot- com> Date:Fri, 19 Sep 2008 07:40:13 -0400
Black boxes are Fun! <not>
I had to do that for a company I worked for though once, tell them how
long I thought it would take to document an uncompleted project based on
the story board.
I completely agree with Bonnie. But if you cannot get an answer, you can
do what I did for one project:
1. Sit and think about what they did and did not tell you.
(For the project I worked on, they mentioned translations, but
not how many languages, nor if they wanted me to prepare graphics as
well)
2. What are the loop-holes? What are you missing? Can you estimate a
dollar cost? For example - if they want an installation manual (which
they forgot to tell me about), that would cost xxx, as opposed to a
functional SW manual, etc...
3. Base your estimate on 5 hours per page. Based on the complexity of
the screen captures, you should be able to determine how many pages will
be needed to explain one capture.
4. What about error messages and troubleshooting? Again, given them a
guesstimate for that as well.
5. Finally, give them a +/- 25% buffer and advise that while they could
benefit (you will do it faster), the lack of info indicates that they
will probably fall into the +%25 range...
I think others can give good tips as well. The main thing is to make an
estimate based on what you DO know, and then add a section that says:
IF you need X - it will cost xxx.
And don't forget to give a list of what YOU require from them (like a
computer with the SW installed, that they pay you to come to their site
to learn how it is installed, etc. and etc.)
Maybe I'm too demanding, but that is what I would do...
ComponentOne Doc-To-Help gives you everything you need to author and
publish quality Help, Web, and print content. Perfect for technical
authors, developers, and policy writers. Download a FREE trial. http://www.componentone.com/DocToHelp/
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-