Case study · Supporting work · Marketing and acquisition
A responsive public product experience designed to explain the offer, guide prospects through the launch story, capture leads, and connect acquisition activity to the operating platform.
A funded-trader evaluation is a complicated financial product: rules, tiers, payouts, and risk parameters that can bury a visitor in detail. The site had to make the offer understandable in one pass, earn enough trust for a financial commitment, keep the dense material available without leading with it, and feed acquisition activity into the platform the business ran on. All of it with analytics held behind consent.
The homepage is a five-act scroll narrative (hero, shift, reveal, advantage, call to action) choreographed to unfold at reading pace on any screen. Pricing and evaluation pathways were typed content, rules and FAQ were searchable rather than buried, and policy pages carried the trust load. Every path converged on two actions: start an evaluation or leave contact details.
Motion supports pacing rather than decoration: transitions carry the reader between acts, and heavy visuals load lazily, only on clients that can afford them.
The live homepage
Mobile
Visitors meet the product before the rulebook.
The narrative explains what the offer is and why it matters before pricing tables and rule detail appear. The dense material stays one click away, as typed pricing data and a searchable FAQ, instead of leading the page.
ResultA complicated offer reads simply without hiding its terms.
One motion system paces the story instead of decorating it.
GSAP ScrollTrigger drives the act transitions through a shared section-pinning component, with Lenis smoothing the scroll. The three.js background loads lazily with SSR disabled, third-party scripts are deferred, a background effect was reworked specifically to kill mobile scroll jank, and the product demo video was cut from 76 MB to 4 MB.
ResultCinematic on desktop, fast and calm on mobile.
The lead form is real infrastructure, not a mailbox.
A server-side route validates and rate-limits submissions, then forwards them to the platform CRM over a token-authenticated internal integration. The receiving side lives in the platform itself, so a lead on the marketing site becomes a record an operator can work.
ResultMarketing activity landed as operational records the business could act on.
Nothing tracks until the visitor decides: a first-party consent framework gates the Meta, Google, and X pixels, and a double-firing bug got its own fix. Real-user performance data comes from Vercel Analytics and Speed Insights.
The acquisition path
The site shipped, carried the product's public launch, and remains live at velocityfunds.io. Leads flowed directly into the operating platform, and the marketing surface held the same design language as the application, so the brand read as one system from first visit to funded account.
One honest caveat: the evaluation operation the site marketed was wound down in July 2026, and the live site still presents the launch-era offer. Updating the public story to match the company's pivot is on the list below.
Transition messaging first: the public story should track the operating reality after the pivot. Then sharper conversion event definitions, so consented analytics answer questions instead of collecting motion, a formal accessibility pass over the animated acts, and structured content experiments on the story itself.
Next.js App Router with Tailwind CSS v4 design tokens. The five acts are discrete components choreographed by GSAP ScrollTrigger through a shared section-pinning wrapper, with Lenis for scroll smoothing. Three.js scenes load through SSR-disabled dynamic imports on capable clients only. Content is typed data: pricing tables, rules, and a searchable FAQ. It replaced an earlier hand-written static HTML site the brand had outgrown.
A dedicated server route validates payloads, applies rate limiting, and forwards accepted leads to the operating platform's CRM through a token-authenticated internal integration, with explicit failure responses when the upstream is unavailable. No third-party form vendor sits in the path.
A first-party cookie-preferences framework gates Meta, Google, and X pixels behind explicit opt-in. The live responses carry hand-written security headers, including an enforcing Content-Security-Policy. Vercel Analytics and Speed Insights provide aggregate, real-user performance visibility.