8
7 Comments

Landing page for a new SaaS

Hi all!

I just got a new landing page up last week as I have been hacking away at an MVP for the past two weeks or so. Probably has some rough edges, but here goes!

Inbound

  1. 3

    The landing page is not clear. Start by identifying your early target audience and communicate ONLY to them till you hit your first few milestones (wrt signups).

    I'm assuming the early target customer is a Sendgrid user who doesn't want to pay significantly higher just for inbound processing. Say that upfront. Use the same terms to describe the problem as your target audience is using. Include a savings chart compared with other providers.

  2. 2

    I might be a potential user that had this problem before (I am using zoho emails and they don't allow automatic forwarding from one address to another without paying, while GSuite allows easily creating account aliases).
    But I won't use your service because:

    • I don't want to route ALL my email to your servers. I don't know you and emails are sensitive information. At least when going to a bigger provider I know they have proven track record. What happens to all emails that are not routed? Are they still being delivered to the original address? What are your server's reputation? Are all my emails going directly to my spam folder? (Gmail, AWS, Zoho, Mailgun etc invest a lot in keeping their email servers with good reputation so the emails do not get delivered to spam). To not get into the DKIM, DMARC and SPF entries.
    • You list "Receive mail via HTTP" as a potential advantage/feature, but for me it's the other way around. I want to receive these emails in my current inbox so I can reply to them, auto organize the discussion threads, etc. Delivering them on HTTP adds the necessity to implement a service myself to handle these. And if I have the time/resources to do that, I can implement a "re-router" myself.
    • A more decent solution I would consider is to connect with a SMTP account (server, username, password) and the re-routed emails to be delivered to me through the same protocol. Basically the experience is to have emails from [email protected] delivered to [email protected] with as little configuration and confidential information exchanged as possible.

    And in the FAQ, the usage of "I" makes it not trusting your business. Email is pretty important for a business (especially for a young/small one that does not want to pay extra for the feature already provided behind a pay wall by their email providers).

    And about the pricing, I find it very expensive for what it offers. It has to do way more than that to pay $1 per 200-300 processed emails.

    1. 1

      A more decent solution I would consider is to connect with an SMTP account (server, username, password) and the re-routed emails to be delivered to me through the same protocol. Basically the experience is to have emails from [email protected] delivered to [email protected] with as little configuration and confidential information exchanged as possible.

      Yeah, it is not on the landing page yet, but there will be a rules engine to send to HTTP or send to storage(maybe S3) or forward to another email. The rule filters will be able to decide on the routing by "to", "from" and "headers". This work will be done soon.

      The pricing feedback is great, I literally threw that up there without thinking about it much and wanted feedback to guide me on pricing.

  3. 1

    Hi Rob,
    good job launching your landing page. Here are some things that I would think about while reviewing your landing page.

    Your H1 works for me, but your H2 is too jargony. It can be slimmed down to be more efficient and to captivate more of your USP.
    for example
    H2: Stop processing email with inefficient methods! Manage all your incoming email with a simple API.

    Then instead of How does it work:
    Dwelve into the use-cases of what people can do with your API, what is it better than Mailgun/Sendgrid, what can you and can't do with it.

    Ultimately tell me about why you're building this, show me some data that allows me to understand it's worth using your solution instead of something else, or building it myself

  4. 1

    I confirm what @saurabhnanda says : reduce drastically your target first.

    Maybe avoid bracket : if you have to add them, it means your first message is not cristal clear.

    Finaly, the word "inbound" appears 4 times on your landing page ! It could be great for SEO, but repetitions are an hassle for reading confort.

    I stay here for a second iteration :)

  5. -1

    This comment has been voted down. Click to show.

    1. 2

      how is this relevant to the thread? you're just self-promoting your app?

Trending on Indie Hackers
How I grew a side project to 100k Unique Visitors in 7 days with 0 audience 47 comments Competing with Product Hunt: a month later 33 comments Why do you hate marketing? 27 comments $15k revenues in <4 months as a solopreneur 14 comments Use Your Product 13 comments How I Launched FrontendEase 13 comments