Product-adjacent Marketing

What it is. Product-adjacent marketing is when your marketing site and your actual product drink from the same codebase. The marketing pages run on Next.js right next to the app. They import Button.tsx and Card.tsx from the same folder engineers use for the dashboard. Design tokens live in one source of truth. API calls hit the same endpoints. A visitor can log in on the marketing site and see their real account stats pulled live from the product database. This turns the website from a static brochure into an active extension of the product. In 2026 any B2B tool serious about growth uses this model once they have product market fit and at least one frontend engineer who owns both experiences. The site deploys with the same pipeline, updates with the same PRs, and never drifts because there is only one source of truth for how things look and work.

What it isn't. It is not a Framer launch page that looks perfect in the browser but feels like a different product once users click through to the app. It is not a Webflow CMS site where the team tries to mimic product interactions with custom code embeds and ends up maintaining two design systems that slowly diverge. It is not bolting Sanity onto a marketing site that still lives in a separate repo and requires constant sync work. Those setups look fine at launch and become expensive regrets when the product ships a design system update that the marketing site never receives. The hover states do not match. The loading animations feel different. The brand voice stays consistent only if someone manually checks every week. That tax compounds fast.

Concrete example. Linear shipped their 2025 marketing site as a pure product-adjacent build. The site at linear.app runs in the same monorepo as the issue tracker. Their famous command bar component gets imported directly into marketing hero sections. Roadmap embeds on feature pages pull live data from the same PostgreSQL tables the product uses. When Linear updated their entire color palette and typography scale in April 2025 the change went out in one deploy instead of two separate handoffs. Their content team edits pages through Sanity Presentation mode without ever leaving the React environment. This let them test three different pricing layouts in one sprint using real user data from the product. Conversions jumped because the CTAs matched the exact buttons users would see after they signed up. Vercel takes it further. Their marketing pages for v0 include live AI previews powered by the same infrastructure customers pay for. No mocked data. No separate demo environment. The pricing calculator uses the identical calculation functions as the dashboard billing engine. Perplexity follows the same pattern with search components that are byte-for-byte identical between marketing site and product.

When to use it. Use product-adjacent marketing when your growth depends on technical marketing that must showcase real product capabilities. Use it when your design system changes every two weeks and you refuse to update the same component twice. Use it when you need personalized landing pages that greet logged-in users with their actual usage numbers or when your SEO content scales past 500 pages and requires ISR to stay fast without crushing Vercel bills. The Framer versus Webflow versus Next.js breakdown puts this use case squarely in the Next.js column because shared code eliminates entire categories of alignment meetings and migration headaches. The engineering investment pays back once you make your third design system refresh or your first data-driven campaign.

When not to use it. Do not use it for your first landing page as a two-founder startup still hunting product market fit. The setup cost will murder your velocity. Skip it if your marketing team is larger than engineering or if writers need to publish case studies without opening pull requests. Avoid it for simple brand campaigns or portfolios under 40 pages where Framer ships faster and cheaper. Webflow wins hard for content-heavy sites between 50 and 400 pages where non-technical editors rule the day. Choosing product-adjacent marketing without the team or the actual need means you pay developer salaries to do work that a Webflow plan could handle in half the time. The migration table in the parent article is brutal for a reason. Moving from Webflow to a shared Next.js codebase at scale eats six to ten weeks and a lot of regret.

Build your marketing site like it ships with the product because in 2026 it basically does.