Why Your Web App and Your Website Are Two Different Things | Hillcraft
Your app and your marketing site serve different audiences with different technical needs. Here's how to think about both — and why mission-driven leaders should scope them separately.
If you're building a software product, at some point someone will ask about the website. The honest answer is that the website and the app are two different things that happen to live on the internet under the same brand.
Two Products, Two Audiences
A web app is a tool. Users log in, accomplish something, and log out. The interface exists to serve someone already inside the relationship. A marketing site serves someone who has never heard of you, isn't sure they need what you offer, and hasn't decided whether to trust you. Building one well doesn't mean you've built the other.
Real Examples
Notion (notion.com vs notion.so), Stripe (stripe.com vs dashboard.stripe.com), Mailchimp (mailchimp.com vs login.mailchimp.com), and Intercom (intercom.com vs app.intercom.com) all separate the marketing site from the app. The marketing site converts prospects. The app serves customers. They share a brand but not a codebase.
Why They're Built Differently
Most web apps are Single Page Applications optimized for logged-in users — fast and responsive, but invisible to search engines. Marketing sites need server-side rendering so crawlers can read them, fast load times for strangers on mobile, and content tooling so a communications team can update pages without a developer.
Three Ways to Approach This
Fully separate properties (yourdomain.com and app.yourdomain.com), a hybrid framework like Next.js that serves both layers from one codebase, or a headless CMS paired with the app. The right answer depends on your stage and team. The wrong answer is treating them as the same project.