7
10 Comments

Architecture Question: How do you connect your landing page, pricing page and app?

Hey IH Squad πŸ‘‹

Typically when setting up a SaaS project I'll have my marketing pages live at www.mysaasapp.com and my application live at app.mysaasapp.com.

The glue between them is the pricing page. The UI lives on the marketing site but clicking pricing Option A will take you to the onboarding flow at app.mysaasapp.com/signup?plan=A.

I'm curious how everyone else here does this? Is there a better easier way?

on January 15, 2020
  1. 2

    Yes, same here.

    One of the main reasons is that I want the marketing side server-side rendered, or static html, to speed up loading for SEO. The app can then be SSR or a SPA, but either way doesn't have to bother about SEO.

    Another reason is that I want to be able to tweak / deploy the marketing site without having to bother app users (with potential downtime).

    1. 2

      I really feel you here. I find that having to put marketing changes through the dev pipeline cumbersome. Also I like the option of having a wysiwyg editor for marketing copy. Just so I can hand it off to a copywriter/marketer easier.

  2. 2

    I've done the same thing as you ;)

  3. 2

    I have the same identical setup. Though, now I'm trying to keep analytics for landing and app together so I can build a kind of funnel:

    Visit Landing > Visit Sign Up > Sign Up > Actually use the app/Pay/Invite ...

    I also have a SaaS where the landing page is both the marketing page and the app so I can showcase immediately the app to the user, but this makes sense as it is a small app (and I didn't want to develop another website :D)

  4. 2

    Sounds decent

  5. 1

    I think this is pretty difficult and so many people are working on some different platforms like jacobmartin you can visit here and use the easier way.

  6. 1

    I keep everything under one app and use Next.js (minimal React framework) for SSR, code-splitting, and other benefits. I guess having a separate marketing site might make sense for larger teams, but I really like just easily being able to share styles and components across all pages.

  7. 1

    I am deep into ssg (static site generators) and my approach would be different. Gatsby for example lets you build an spa inside your static site. You decide what the base route for your app will be and you create your spa like you would with a classic react app from there.
    Honestly, I don't know if it is better. You have only one code base so it may simplify tooling, code reuse, design, ... And it may simplify analytics as well but I see many services doing as you do, even in the 'ssg world'.

  8. 1

    Are these two separate applications? like I have my static marketing site www.mysaasapp.com build on Wordpress while my actual app app.mysaasapp.com is a JS based application running on Azure.
    In any case, your marketing site can host multiple hooks to your app. I have a "more info" button on various pages that link two sites.
    I have separate analytics for both sites so I can measure how the traffic is flowing between two sites.

    1. 1

      Ok so same as I've got going on really.

  9. 3

    This comment was deleted 4 years ago