
www.Usenet.com
| <-- __Chronological__ --> | <-- __Thread__ --> |
> From: Adams-Blake Company <[EMAIL PROTECTED]> > > There is no substitute for "doing it yourself." That's wonderful if you happen to be a professional at everything. I find that few people are, though their bosses may want them to be (paying you to fill one position while you fill 3 others). If you happen to be a seasoned, veteran corporate traveler who uses executive cars then you can write from your own experience using whatever you can learn about copy writing. Otherwise it's going to take research, learning about newsletters, and gaining and polishing copy writing skills. Does the client have time for this? Can your employer send you to a course first? What level of professional service is the client paying for and what do they deserve? The newsletter has to cater to the wants and desires of executive and corporate travelers, especially those things that pertain to your client, though additional information is lagniappe (and can also be co-op advertising to offset costs). What will make their travels more enjoyable and convenient? What bothers them when they travel? You have to ask yourself or your client all the relevant questions you can think of, sort their importance, and go get the answers. Then you have to write it in an interesting and organized manner. It's all logical and all the resources are out there for you to learn, but don't expect to be a professional at it overnight. If they want and are paying for professional work, and fast, then they should be contracting a pro or buying content that has already been professionally written. If, on the other hand they just want it done, or they're paying chump change, then just gather up as much free junk as you can, rewrite it need be (and allowed by any agreements), visit the library, pick up some magazines and learn as you go along. Or, (here's the one I like), get your boss to use the client's services to send you on a business trip as an executive each time you write the newsletter. Then you can tap right into the relevant information from 1st hand experience:) They could write it off, huh? :)
| <-- __Chronological__ --> | <-- __Thread__ --> |