
Helping you solve your documentation issues
By Ellis Pratt and Carol Johnston. 11 December 2003
We asked some leading sales experts for tips on implementing writing sales proposals. You can get these tips free.
Just fill in your details here:
See also: Writing Sales Proposals: e-learning training course on writing sales proposals
Have you ever given a prospective customer sales literature that contained avoidable errors, or felt uncomfortable about the quality of the sales proposals you've sent out? This article explains how we built a solution to producing sales proposals and other sales literature for our own company using an affordable content management solution, one that costs from $400 to buy.
When we started our company, Cherryleaf Ltd, we wanted to have from the start a system that would ensure we'd be consistent across all our sales and marketing media. For us, that meant a Web site, sales proposals, training course outlines, datasheets and simple marketing brochures. We also wanted to be able to amend content quickly and reduce the amount of manpower needed to produce it. As we claim to be documentation specialists, we needed to take some of our own medicine.
There were a number of problems that we'd experienced at our previous employer that we were determined to avoid or solve:
We built our solution around a low cost single source content management system called AuthorIT. AuthorIT enables you to "single-source" your documentation - you produce your document in many different output media, but only store and work with it in one place.
Creating a document in AuthorIT is like making something out of a set of child's building bricks - you construct your document from many smaller pieces called "objects". AuthorIT stores the components that make up your document in a single database, so you can re-use chunks of information across documents.
You can re-use each object as many times as you like - in the same document or in many documents. When you make a change to the object, your changes happen instantly in all the places where that object is used. This capability has saved us a lot of time and has given us the consistency we want.
We embed topics within other topics, which makes it is possible for us to write core pieces of content once. By putting all the chunks of information into the system, we created a library of supporting materials that writers could choose to include in their proposals.
In some instances we want to include or exclude entire topics, depending on the output, and the solution enables us to do this very easily.
We combine the chunks of information, or topics, in different ways. For example:
You generate documents in Author IT using "Books". We can arrange the same topics into a different order within each Book, which means we can re-arrange the content in each sales proposal to suit each situation. We've created a series of Word and HTML templates for the different types of output we need, and AuthorIT uses the relevant template when each document is generated.
The illustrations below show how a topic from the library is used in different documents.
Example 1: The topic "About Cherryleaf" is used in a sales proposal put together for ABC Corp, with the proposal generated as a Word document.

Example 2: The topic "About Cherryleaf" is used as part of a page on our Web site, and generated automatically within the HTML code of the page
