Skip to main content
Stacklane

Marketing sites, Next.js + Tailwind + Motion, same codebase as the product, no Webflow.

Marketing sites land in one of two places, a Webflow that becomes a maintenance project or a marketing CMS the engineering team built once and forgot. We build the second kind, in the same codebase as the product, with proper instrumentation and the typography vocabulary the brand actually owns.

What we build

  • One codebase with the product

    Shared components, shared tokens, shared design system. A feature update that changes the marketing claim doesn't require a platform handoff. Engineers ship marketing pages with the same workflow they ship product features.

  • Built for the page, not for a CMS

    Marketing copy lives in the codebase or in MDX, where engineers and writers can both edit it. No 'open the CMS dashboard' loop. PRs review the actual change, not 'someone updated something somewhere'.

  • Performance budget enforced in CI

    LCP under 1.5s, INP under 200ms, JS payload under the per-page budget. Lighthouse CI fails the build on regression. The marketing site doesn't accidentally bloat over time.

  • Multi-locale as a first-class shape

    Pages ship in EN + the team's secondary locale (NL for us) by default. The locale switch is structural, not bolted on. The translator overlay works on the same Next.js source.

  • PostHog event taxonomy from launch

    Every CTA fires a typed event. Funnel data is queryable from day one. We don't ship the site and bolt on tracking when the team wants to optimise.

  • Editorial pages that scale

    Long-form articles, case studies, changelogs, customer stories, all live in MDX next to the marketing routes. New article = new file. No CMS schema migration to add a new section to the editorial template.

Where this fits

  1. Your marketing site is in Webflow and every feature launch requires a platform-specialist on the team.

  2. Your marketing copy and product copy drift because they live in different platforms with different owners.

  3. Your team is shipping campaign-led landing pages on a regular cadence and the current platform bottlenecks iteration.

Tech stack

  • Figma
  • Next.js
  • Tailwind
  • Motion
  • PostHog

Want this for your team?

30 minutes with a founder or senior engineer. We'll scope what you need and tell you straight whether Stacklane fits.

Book a Free Call

Related capabilities

Other patterns in this area

Back to Brand & Marketing