Case study · Paid client work

Callixa: Voice-AI Landing Page

A conversion-focused landing page for an AI receptionist, taken from scope document to a live, client-approved production site through seven review rounds.

Cinematic 3D render of a glass voice waveform lit in purple, fuchsia, and orange
RoleDesign, build, deploy
ClientCallixa.ai
StackHTML/CSS/JS + Vercel
StatusLive in production

Every missed call is lost revenue

Callixa is an AI receptionist for service businesses: it answers calls around the clock, qualifies callers, books appointments, and routes to the right person. Its buyers are non-technical owners in trades, dental, legal, and medical who are comparing it against a human receptionist and competitors like Smith.ai.

The landing page had one job: make a skeptical visitor hear the product answer their kind of call, then book a demo. The page had to demonstrate the product rather than describe it, and it had to earn trust with specifics, not hype.

Demonstrate, don't describe

The hero is the differentiator: a per-industry video player with an 11-vertical switcher, grouped into Trades & Services and Health & Professional. A plumber lands on the page and watches a plumbing call get answered, booked, and logged.

Under it sits a rotating 23-phrase headline, a static two-column FAQ grid with every answer visible, and plain-language pricing. Accessibility is treated as a feature: the brand indigo is decorative only, while all readable text and focus rings use an AA-safe lighter tint, and every animation honors reduced-motion preferences.

From scope document to live site

  1. 01

    Scope to design tokens

    The client's scope document became a dark token-driven design system and a ten-section page structure, from nav to intake form. Reference sites were mined for patterns, never palettes: the layout ideas stayed, the colors became Callixa's own.

    scope v1.0 · token CSS
  2. 02

    Concept rounds

    Four preview versions explored the hero. An audio-waveform experiment was built, tested, and deliberately reverted once the client confirmed video carries the proof better. Palette explorations settled the electric-vs-indigo question with side-by-side variant pages.

    v1–v4 previews · palette variants
  3. 03

    Client review rounds R1 to R7

    Seven numbered revision rounds, each deployed to its own URL so the client could compare live builds instead of screenshots: an accent split separating decorative indigo from AA-safe text, a one-screen hero variant, and two full typography passes across the page.

    7 rounds · live variant URLs
  4. 04

    The delivery pivot

    The original plan was a GoHighLevel page build, but GHL's builder couldn't reproduce the fonts, token CSS, or custom components. I proposed shipping the page as a standalone static build instead, with GHL supplying only the form, calendar, CRM, and tracking through marked slots. The client approved, and no quality was lost to the platform.

    static HTML · GHL integration slots
  5. 05

    Deploy loop

    Production deploys run through Vercel in seconds, so cosmetic changes ship while the client is still on the call. Edit, deploy, verify on the live URL: the whole loop takes minutes, and the client always reviews the real thing. Since September 2026 production runs at callixa.ai on the client's own Vercel team, in 45 languages with an IP-based default language and right-to-left support.

    vercel --prod · minutes to live

A page the client iterates on live

7 Review rounds shipped

Every round deployed as a live URL for real side-by-side client review.

11 Industry verticals

The hero switcher shows each visitor their own industry's call being answered.

Minutes From edit to live

A fast deploy pipeline means feedback lands in production the same conversation.

Paid ClientHTML/CSS/JSDesign TokensVercelGoHighLevel

Available for remote work

Need a page like this for your product?

Tell me what you're launching and I'll walk you through exactly how I'd build it, round by round.