Landing-page system + print collateral for a luxury-vehicle dealership

The problem

Every paid campaign was burning budget on a destination that was barely relevant. The dealer-network template they were stuck with showed a generic inventory grid, not the specific vehicle, financing, or event the ad was selling. Print collateral — showroom one-sheets, event invitations, financing summaries — was being rebuilt from scratch by an outside design shop every time, then never quite matching the digital campaign.

The combination meant they were paying for traffic and paying for design, and getting inconsistency from both.

The approach

Web first, but with print as a first-class output. We built the page system around content modules — hero, vehicle spec, financing block, event block, CTA. Each module is a React component on the web side, and also has a paired print template that renders to PDF.

Page-per-campaign, not template-per-campaign. Every campaign gets its own URL with its own focused message, its own social-share image, and its own print-ready PDF generated from the same source content. Marketing launches a page in under a day; print collateral comes free with every launch.

Stack: Next.js / Tailwind / Vercel for the web surface, a server-side PDF generator (running in a Vercel function) for the print outputs, and a small content schema in TypeScript so non-developer team members can edit campaign copy without touching React.

The outcome

The dealership now ships a landing page (and matching showroom collateral) in the time it used to take to brief the design shop. Mobile load is sub-second on a real-world network because each page only loads its own modules — not a generic template's full payload. The web and print outputs match because they share the same source.

The follow-on effect is the one we cared about most: the team finally has a brand system that survives in the wild instead of getting reinterpreted on every campaign.