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:"Bonnie Granat" <bgranat -at- granatedit -dot- com> To:"'Pippa Cohen'" <cohenpippa -at- googlemail -dot- com>, <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Fri, 19 Sep 2008 07:36:22 -0400
Maybe an hourly rate would be better than trying to price the work itself?
You could tell them that after you determine your pace you could provide a
total project cost *estimate.*
Will you have the information you need to do your work from what they say
they'll provide you?
> -----Original Message-----
> From: Pippa Cohen [mailto:cohenpippa -at- googlemail -dot- com]
> Sent: Friday, September 19, 2008 7:31 AM
> To: techwr-l -at- lists -dot- techwr-l -dot- com; Bonnie Granat
> Subject: Re: Pricing a project without access to the software
>
> Thanks Bonnie
>
> Just to clarify, the application seemed intuitive to *me*,
> but there is a need for it to be documented because the
> client is seeking to reduce training and support time for
> their users. There is zero documentation at the moment and
> they are being asked for it most days.
>
> The client will be telling me what they want documented, by
> providing a list of screens with complexity indicators, so
> this will form the scope of the project.
>
> I guess my main concern is that it is the client who is
> deciding the level of complexity for each area to be
> documented, not me.
>
> P.
>
>
>
> On Fri, Sep 19, 2008 at 12:00 PM, Bonnie Granat
> <bgranat -at- granatedit -dot- com> wrote:
>
>
> If (1) you didn't see anything that you think needs
> documenting, and (2) the
> client hasn't explicitly told you what it wants
> documented, I think the
> thing you simply must do immediately is *ask the
> client* what it wants to be
> documented. Then go from there. I mean, how can you bid
> on something that's
> in a black box? Makes no sense to me.
>
>
> Bonnie Granat
>http://www.GranatEdit.com
>
>
>
>
>
>
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-