3
17 Comments

Seeking feedback on first draft of landing page -- Basereport io

http://basereport.io
submitted this linkon November 6, 2020
  1. 3

    You lost me straight away. The main title "trust us with your data" tells me nothing about what you do, it just scares me away.

    Maybe you want to sell it more like. "Easily create custom reports from your data"..

    Good luck.

    1. 1

      Trust us with the keys to your house.

  2. 2

    NIce, i would put the email address floating at the bottom on all pages, perhaps scale it up on the last page.

    1. 1

      Good recommendation, thank you

  3. 2

    I liked the UX, where you're leaving the user with no other option but to click on the next button. I also like the clutter-free UI which prevents any kind of distraction. I feel just 3-4 paras of text is not enough to get someone to share their email. You need to provide more concrete information what your business is and it's benefits to the customer.

    1. 1

      I realize that now. Thank you. Several other comments echo'ed the same. I will need some time to think about this more.

  4. 2

    I can imagine where this might be going (and I think it is probably a useful product) but as a potential user I would prefer more specific concrete details before handing over my contact information

  5. 2

    The email sign-up is four clicks away, that'll hurt conversions. Make that consistently shown, available on the first landing page. Use bullets instead of paragraphs for the text and focus on what's in it for me and why I should care.

    Hope that helps a bit!

  6. 2

    Ok. Clicked on your landing page. Here's a play by play:

    Catchy title... tell me more...

    Ok, something about API. For "complex data flows" - no idea what that means.

    I'm a developer and I have built APIs. Is this for me? Or for end users? Not sure.

    Clicked next page...

    Ok, so my data will be secure and I have control over it. Good. Next page...

    Hmm, a lot of words here. So this looks like it will save some development time. On something. Still don't know what problem this is solving.

    Next page...

    Oh! I was hoping to see some examples but now it's asking me for an email address.

    Not sure if this is for me, so I'm out. Still don't understand what problem this is solving.

    =========

    Sorry if that seems harsh, but I think you need to be specific about a) who it's for, and b) what is the problem you're solving. And put this on the front page.

    The rest of the pages just need to support the above, with examples, maybe testimonials, and a demo (fi you have one).

    Hope that helps!

    Farez

    1. 1

      Harsh is the best feedback an early startup can get. Took me a while to realize. "Wow, nice!" gives you nothing.

      P.S. The landing page itself is nice indeed.

    2. 1

      It's not harsh. I needed harsh. I'm so new to trying to sell something. I'll get this figured out with the help of your comments. Awesome, thank you!

    3. 1

      Agree. Im a developer, i make apis, and eat them too, but i have no idea what your site is selling me. but maybe im stupid. However UX/Colors Good.

  7. 1

    The problem I see straight away is, too many clicks before even understanding what your service does and how it could help me.

    I stopped clicking after the second slide.

    Sorry to appear harsh, but if I stopped after the second slide someone else would stop at the first.

  8. 1

    Looks good - simple and confident. I'd add arrow key navigation and maybe speed up the animations.

  9. 1

    Sign up form is 3 clicks away. It should be front and center assuming you care about conversion.

  10. 1

    Although I am not a data engineer, I couldn't really understand what the product is for.

  11. 1

    The major issue:

    1. Data is a sensitive topic and you are asking for trust in the very first line without building any trust. Usually, a copy in a landing page starts with 'build', 'Create', 'learn', 'achieve' etc. As you can see, these are all about what is in it for the user.
    2. The messaging should be about what's the users problem that you are solving rather than what you do. Like "Get custom APIs built for complex data workflows". You can put it in a cooler way but messaging should be around this line.