2

Phantom Checker — Drop Monitoring Conversion Site

A conversion-focused site for a retail product-drop monitoring service, centred on a two-axis pricing configurator that resolves monthly event volume against seat count — with the entire scroll and header animation layer built directly on platform primitives rather than a motion library.

Technology Stack

React 18, TypeScript, Vite 7, Tailwind CSS 3.4, tailwindcss-animate, React Router, HugeIcons, Fontsource, Vercel

Overview

Duration: 3/2026

Phantom Checker is a monitoring service for resellers: it watches retailers for product drops and restocks and pushes alerts the moment something goes live. Its buyers live in Discord, Telegram and Whop, which is where the product is distributed and where this page has to send them.

That audience shapes everything. They are technical, sceptical, and comparing several monitors at once, so the page leads with coverage and detection speed rather than brand language, and it puts real pricing on the page instead of hiding it behind a sales call — in this category, a "contact us" pricing section is read as a disqualification.

Page Structure

Each section is an isolated module composed into a single conversion flow:

Interactive Pricing

The pricing section is the most engineered part of the page, because the product does not price on one axis. Cost depends on monthly event volume and on how many people need a seat, and the two interact — the seat tiers available differ per volume bucket.

It is modelled as a matrix rather than a set of plan cards:

Encoding it this way makes the price grid data, so adding a tier is an edit to a table rather than another hand-built card, and marketing can change pricing without an engineer rebuilding the section.

Scroll Choreography

Animation is built on IntersectionObserver directly rather than pulling in a motion library, keeping the bundle small on a page whose audience is often on mobile data:

Header Behaviour

The header animator is a plain function with no framework dependency — it takes an element and a sentinel, toggles classes, and returns its own teardown:

Build Details

The theme running through this build is doing the interactive work directly on platform primitives — observers, frame scheduling, a data table — and spending the complexity budget on the pricing model instead, which is the part a visitor actually has to understand before they will buy.