Email: Features vs. benefits [GD]

I have found using a speaker/audience (provider/customer) model to be helpful [when writing about and distinguishing between features and benefits].

Let's say you go to the doctor and he says you need your flu shot. He explains why you should overcome your fear of needles in these terms (which are features of the product or benefits to the provider, i.e., the subject is on the side of the speaker):

The flu shot has two strains that experts think are likely to dominant this season.
The flu shot is safe with minimal complications.
We dispense hundreds of flu shots every season, so we know what we're doing.

However, a truly customer-oriented approach (where the subject and benefits are on the side of the customer) might take this more finely honed tack:

Our [lab technician] is so good, the shot will be over before you know it.
You probably won't come down with the flu, or if you do, it should be milder.

And so on. Of course, any of this can be boiled down to more commercialized marketing language:

Industry-leading quality control during production and dispensation (feature)
Streamlined, personalized delivery process (feature)
Low-cost protection in the blink of an eye (benefit)
Maximize your health and minimize your downtime (benefit)