PROPOSALS: attaching docs -Reply

Subject: PROPOSALS: attaching docs -Reply
From: Judith Leetham <JUDITHL -at- WORDPERFECT -dot- COM>
Date: Mon, 6 Mar 1995 10:09:44 -0700

It is usually sufficient to include a Table of Contents for each deliverable.
If you attach sample text, the potential customer may look at the content
of the text, not the organization.

judith leetham, WordPerfect, the Novell application group
jleetham -at- wordperfect -dot- com

>>> Christopher Shade <christopher -dot- shade -at- PSCMAIL -dot- PS -dot- NET> 03/03/95
11:59am >>>
In writing proposals, is it a good idea to attach sample documents, or
sample document templates, to give the customer a feel for the
documents to be delivered?

For example, for an implementation effort, would a proposal that
contained a sample Operations Guide, as an attachment, impress the
customer more than a proposal without the sample Guide? Assuming it's
a produced well. This Operations Guide obviously would not contain all
operational instructions and information (since software customizations
have yet to be implemented, since even requirements have not been
defined, since details about the transitioned business processes have
not been realized, etc.--essentially, since the entire project has yet to
happen) but this sample would present the framework for the final
version.

--Christopher Shade in Denver, who's not sure that the last sentence in
the last paragraph, with that parenthetical interruption, makes any sense.


Previous by Author: TECHWR-L Digest - 26 Mar 1995 to 27 Mar 1995
Next by Author: Re: Verbal, Oral -Reply
Previous by Thread: PROPOSALS: attaching docs
Next by Thread: Subjects You Missed in School


What this post helpful? Share it with friends and colleagues:


Sponsored Ads