Skip to content

Instantly share code, notes, and snippets.

@spjpgrd

spjpgrd/Keys to Testimonials.md

Last active June 21, 2017 17:19
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save spjpgrd/3d76ddf1b0382cacfd362bd33f7077bb to your computer and use it in GitHub Desktop.
Save spjpgrd/3d76ddf1b0382cacfd362bd33f7077bb to your computer and use it in GitHub Desktop.
Download ZIP
Raw
Keys to Testimonials.md

Testimonials

Ask these 6 questions to get a powerful testimonial

  1. What was the obstacle that would have prevented you from buying this product?
  2. What did you find as a result of buying this product?
  3. What specific feature did you like most about this product?
  4. What are three other benefits of this product?
  5. Would you recommend this product? If so, why?
  6. Is there anything you’d like to add?

  • 1st: Ask if they'll give one at the end. And why they picked you. The first instance where you can bring up the testimonial is at the starting point when you're sitting down with the client when they're buying into your consulting or your training, and you can ask them whether they would give a testimonial at the end. This agreement makes a big difference.

  • 2nd: In-progress testimonial

  • 3rd: The testimonial you get at the end, not after, but at the end. This is where you tag on a little assignment that the customer can do or should do as part of their whole exercise. Most customers agree to this. There's no problem getting this. It's the waiting after the project that's a problem.

  • 4th: After the Fact

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment