2
2 Comments

Use buyer pain points to improve your landing page

Hey gang,

I noticed that many landing pages don't talk about a buyer's problems or pain points (I use the term 'buyer' broadly to mean someone who may pay for your product or use it for free).

But adding buyer pain points to your landing page can help you stand out in at least 3 ways:

  • Buyers look for proof that you 'get it' before they buy ("why would I buy from someone if they don't understand my problems in the first place?")
  • Buyers want to know when to think about your product ("what event or thought in my daily life should remind me of your product?")
  • Buyers will engage with problems first, then ask for more ("you nailed it, now I need to know how you're going to help me!")

To help out, I wrote an article explaining how to use buyer pain points with 5 real-life landing page examples.

http://jehanlalkaka.com/talk-about-your-buyers-problems/

Was it helpful?

on March 4, 2020
  1. 2

    Great write up @pmmjehan,

    Deffo would have loved to see more examples of sites that do this well.

    Saving this advice.

    If I may ask, I put up a very simple landing page at https://boomadmin.com while I work on MVP. Do you think I am communicating the pain well ?

    I do like the idea about asking potential customers about their pain points first and probing them deeper. Will deffo do that more.

    1. 1

      @nojvek Thanks for taking a look! I have a few more examples I can add to the article, as you suggested. Maybe we can also make boomadmin an example :)

      Boomadmin seems like a cool app with a potentially huge market size. I think you're doing a good job of communicating the features and in many cases the benefits too.

      To help bring out the buyer pain points, let me ask you:

      • Why is admin UI usually ignored until it's too late?
      • How inconvenient is it for customer success without a fast and simple admin UI? Can you describe the inconvenience step-by-step?
      • How long would it usually customer success to support customers without an easy-to-use admin UI?
      • How much time can it cost the dev team if they're left without an admin UI or forced to make one from scratch?
      • What are the hardships of making an admin UI in-house?

      Answers to those questions (or questions like those) will help you clearly connect your product and features back to the real-life problems your customers are having. And I believe when they see that connection on a page, clearly spelled out, good things will happen.

      Let's keep the dialogue going. I love figuring out stuff like this.