Config-driven per-vertical use-case landing pages (draft template)

[NetanelBaruch]

What this is (draft)

A config-driven, per-vertical use-case landing page system. One reusable template component renders a full, long landing page for any vertical from a config, served at /for/<vertical>.

Four verticals are included as a working proof:

• /for/fintech — for regulated fintech and payments
• /for/dev-tools — for developer platforms
• /for/security — for security and cybersecurity
• /for/ecommerce — for e-commerce and marketplaces

The ask for the marketing squad / Pixel Point

This is a starting point, not a finished design. We want one source-of-truth landing page template that fits any vertical, where the content swaps per vertical according to the client visiting. This PR proves the mechanism (one component, one config per vertical); please craft it into the production, polished, reusable template.

How it works

• src/components/pages/connect-usecase/index.tsx — the single template. It renders a hero, a final CTA, and an ordered list of typed section blocks: prose, features, badges, split, demos, proof.
• src/components/pages/connect-usecase/config.ts — one entry per vertical: hero, an ordered sections array, and a final CTA. Adding a vertical is a config edit, no new component code.
• src/app/(website)/(connect-footer)/for/[usecase]/page.tsx — the dynamic route with generateStaticParams and generateMetadata; unknown slugs 404.

How the content was built

Every vertical's copy is grounded in real Attio (CRM) + Grain (call) research: the actual pains buyers voice, the use-cases they run, the product elements they value, and the objections to preempt. This is why each vertical leads differently (fintech leads with compliance, dev-tools with build-vs-buy and the embeddable Inbox, security with critical alerting, e-commerce with order lifecycle).

Guardrails already applied

• Customer names: only already-public/approved logos appear (Ebury, MongoDB, Whoppah, Hemnet, TatilBudur). Every other real account is anonymized to its industry (for example "a global FX and payments provider"). Nothing ships named without sign-off.
• Demos: the Connect video cards are illustrative samples, labeled as such, never real customers. Fintech's two demo videos (Tallywave) are added here; the other verticals reuse channel-demo videos already on main.
• Brand: no em dashes, channels limited to Slack, Microsoft Teams, WhatsApp, Telegram, Email, iMessage, communication-layer framing, no "runs your brain".

Notes

• Reuses channel-demo videos in public/videos/channels/ and customer logos already on main.
• Per-visitor personalization (showing the right vertical to the right client) is a separate layer: deterministic campaign/UTM routing to /for/<vertical> now, optional on-site detection later.
• Google Ads drafts (keywords + RSA copy per vertical) live in the marketing workspace, ready to import.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
website-new	Ready	Preview	Aug 11, 2026 1:08pm