Re: system administrators and documentation
So, the strategy seems to be: Provide information that's only useful to
people who already know the product well. Less experienced people will get
frustrated and call us for consulting hours.
Strategically, it depends on how good a job the company does at selling and
delivering that consulting support, and how profitable it is compared to mere
sales of the software. In many industries, the initial product is more or less
a "loss leader" that generates the true revenue from the supplies, training or
other followup services it requires. Example: diabetic glucometers, which
are often sold at what seem like giveaway prices, especially if a competitor's
product is traded in; the real income from these is in the test strips that the
Robohelp X3, from eHelp, lets you quickly and easily create professional Help systems for all your Windows and Web-based applications, including Net.
Order RoboHelp X3 in May and receive a $100 mail-in rebate, PLUS
free RoboScreenCapture and WebHelp Merge Module.
Order RoboHelp today: http://www.ehelp.com/techwr-l
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit
http://www.raycomm.com/techwhirl/ for more resources and info.
system administrators and documentation: From: Brian Das
Previous by Author:
Re: What to look for in a technical editor
Next by Author: Re: system administrators and documentation
Previous by Thread: system administrators and documentation
Next by Thread: Re: system administrators and documentation
Search our Technical Writing Archives & Magazine