Skip to content
Client
Frame
Role
Webflow development · Motion · AI demos
Year
2024
Stack
Webflow · GSAP · Lottie (Jitter) · OpenAI API · custom proxy

Frame.

A pre-seed productivity startup with a waitlist page that couldn't show what the product did. We built the site, the motion, and two working AI demos running on the page itself.

Frame had a waitlist site — no motion, no interaction, and no way to feel what the product actually was.A screenshot can't demo an agent.So the demos went on the page, live.

Two of them: a preview of the personal agent on the OpenAI API, and the AI-employee use cases wired to the product's real integrations. Webflow is frontend-only, so a proxy server sat between the site and the API, taking the requests, handling CORS and relaying them on.

  • Motion where it counts. Built in Webflow with GSAP, keeping movement on small interactions — hover states, a draw-on footer logo — rather than decorating every section.
  • Feature animation. Lottie sequences built in Jitter to show the product's main features moving, which static UI shots could never do.
  • The agent demo. A preview of the personal-agent feature running live on the OpenAI API — built when ChatGPT was still basic chat and 'agents' weren't a category yet.
  • The proxy. Webflow is frontend-only, so a proxy server sat between the site and OpenAI: it took the front-end requests, handled CORS, and relayed them to the API.
  1. Frame — home page, desktop
  2. Frame — AI use cases demo
    Frame — supporting screen
  3. Frame — AI agent demo
  4. Frame — section motion
  5. Frame — portrait screen 1
    Frame — portrait screen 2
    Frame — portrait screen 3
  6. Frame — product UI
    Frame — supporting detail
  7. Frame — footer and brand mark

Next case

Mihailove.

Development — 2025

More projects

View all

I need

I need