1
5 Comments

Landing page updates, thoughts welcome

I recently updated the landing page for a SaaS I build Packetriot. Not going to explain it's purpose or background so I can see if that comes through :)

I've been working on this business for almost two years and haven't really asked for any feedback on my landing page. It's gone through many iterations. Each update is my attempt to communicate better to visitors but I've also used these changes to affirm the direction and changes I make in the business.

Toward the end of last year my business began to pick up and grow in a direction I didn't expect. Growth was more B2B than B2C, so I decided to change focus and priorities and felt a change in my landing page was required too.

I'm interested if the service, problem domain, and value proposition comes through clearly. I'm open to any other feedback as well :)

Thanks in advance for your thoughts and would be glad to help if you'd like some feedback on your project too.

  1. 2

    Hey John, I'm an ngrok user and when I get to the site, my first reaction is "I'm gonna stick with ngrok".

    Unless there's a pain that Packetriot (you know, I think I've seen your app mentioned somewhere now that I think of it) is suited to solve (pesky NATs?)... in which case, I don't know, maybe that's something to put up front.

    Overall though, I think how your page focuses on communicate what Packetriot allows you to do is good enough.

    I think I'd just get the second section to be straight up "a lot of people come to us for (THIS), we solve that problem really well." That kind of working would do two things: it'd match the conversational, accessible tone of your video, and maybe help people see why they'd consider you over something else.

    Hope that helps.

    1. 1

      Hi Pascal, thanks for your inputs! I appreciate the thoughtfulness of your comments and the time you took to review my site and share them with me.

      You're right, I provide an alternative to ngrok. Since it's a utility, it's difficult to communicate the differences of why you should switch. Off the top of my head, the pains we do solve is 1) a stable URL, 2) no rate/request limiting, 3) custom domains are available on all tiers, 4) our client automatically manages Let's Encrypt for you, so less tooling and 5) we provide Linux and Mac repos making software updates simple and transparent.

      This makes me think I should put a section near the top to explain these differences (or advantages).

      One unique feature Packetriot does provide that attracts my business customers is the ability to self-host our tunneling server on-prem or in their own cloud instance. For companies working with sensitive customer data they feel better having control and not passing their customer data through a SaaS.

      Your feedback helps a lot and I really appreciate it. I'm a programmer (lots of Go) and pretty experienced with lots of systems and network programming, so if you ever think I can help please reach out. Cheers!

      1. 2

        I think that ultimately, communicating those differences would help, but it would cement your product as a derivative to ngrok, as a commodity. That's what I'm worrying about a little bit, but it won't hurt.

        And so I think one section (one full-width block) on your home page could be dedicated to "Companies like that we have an on-prem option" and the describe that in full. Again, I'd use that kind of soft-spoken language to communicate that you're a company that's trusted, that has Skin-in-the-game, that people rely on your dependability. You're exposed.

        "Our on-prem option is called Spokes. It's offers the same tunnelling as Packetriot, but all the traffic goes through your company's own infrastructure."

        "Maybe your developers need to test APIs that don't work with a localhost URL"
        "Maybe some of your devices need a stable URL without a stable IP address"

        Having that kind of "Maybe" language here will attract attention of the readers who scan the page. They might not notice that they're in the On-prem block, and it won't matter. That list will flow for both on-prem readers who read in the micro, and for those who scan in the macro. It still connects with the product's Job-to-be-done. See what I mean?

        1. 1

          Thanks for this advice. I feel like you hit a very good point which is to avoid being considered a commodity or a clone. I'm beginning to learn what corporate or enterprise customers value and trying to focus on that message more.

          I see what you mean with the use of language. It does prompt some thought and possible connection to the value proposition being presented.

          I'm going to spend some time reading through the links you shared with me and reflect. Really appreciate the thoughts you shared Pascal, please reach out if you ever think I can be of help.

      2. 2

        Ah, the stable URL thing is appealing. I've got a couple more thoughts for you. I'll right back soon.

Trending on Indie Hackers
I quit. 52 startups in 52 weeks 59 comments Launching new product today, hope to get your support and feedback ❤️ 15 comments Twitter accounts directory 11 comments 🐚 I Need Your Help! Landing Page Feedback 6 comments My first product with GPT-3: Get backlinks to improve your SEO 6 comments My Process For Building Fast 5 comments