FreshworksWebAI ShippedCase study

Freshworks’ Demo Hub. A home for every demo, from an agency design to a live page.

Freshworks’ demo page came to me as an agency design. I owned the redesign through a brand change, built and tested ideas with Claude Code, and prepared the dev handover in Figma. It’s live at freshworks.com/demos.

Role
Product Designer
Company
Freshworks
Year
2026
Methods
Research, prototyping with Claude Code, Figma, dev handover
The live Explore demos page: a featured demos list, a video stage and the demo’s pitch
The same page on a phone
Live on freshworks.com
01 · Where it started

It started as an agency design.

I took the demo page over from an agency and redesigned it to the brand guidelines at the time.

Before that version launched, Freshworks updated its brand, so I went back to the page in the new look.

The agency design: a carousel with a headline over the product shot, and a video grid with placeholder copy
My first redesign: a large serif heading, a carousel of colour-blocked demo cards and a filterable library
The agency design, then my first redesign
02 · Research

Looking at how others do it.

I roughed out the page in the new brand, then looked at other demo pages and motion galleries to see how they get someone to the right demo.

GSAP’s demo gallery, with its stacked spotlight, shaped the hero.

My first pass in the new brand: a dark hero with a demo list beside a video stage, above a placeholder library
First pass in the new brand
03 · How I worked

Building ideas instead of describing them.

I used Claude Code to turn my ideas into working pages, so I could click through a layout, change it and try again the same day.

The strongest ones went into Figma, where I refined them for review.

  1. 01 · ExploreIdeas as working pagesI sketched ideas and built them in the browserClaude Code
  2. 02 · IterateQuick roundsClick through a layout, change it, try againClaude Code
  3. 03 · Into FigmaFigma framesThe strongest pages came into FigmaClaude Code
  4. 04 · RefineReady for reviewI refined the designs and ran the reviews
  5. 05 · SpecSpecs and a prototypeI wrote up every state, with a reference prototypeClaude Code
  6. 06 · HandoverDev handoverI built the handover in Figma
How the work moved
04 · Three directions

Three directions for review.

A carousel you page through, a list beside a video stage, and panels that open one at a time.

Each one was a working page, so reviewers could click through it.

Direction A: a carousel of demo cards you page through
Direction B: a list of featured demos beside a video stage and its description
Direction C: dark panels that open one demo at a time
The three directions
05 · Spotlight

Spotlight won.

The agency carousel put headlines on top of product shots. Spotlight gives the list, the video and the description their own columns.

The other featured demos sit stacked behind the one playing.

Live · choosing a featured demo
06 · One filter

One filter for the library.

An early version filtered the featured demos and the library separately. Two filters was one too many, so I kept one: experience.

Each card also says whether it’s a video or an interactive tour.

Live · filtering by experience
07 · The player

Watching a demo.

The video takes the full width, with the title and description below and Book a demo close by. On a phone, it opens as a bottom sheet.

When the first dev build of the phone version looked off, I updated the reference prototype to show how it should behave.

Live · desktop and phone
08 · The handover

The handover, in Figma.

Page mockups at each breakpoint, every player state from playing to locked to ended, and components with notes for developers.

The reference prototype covered motion and behavior. See the live page

Page mockups of the Spotlight page at desktop, laptop and tablet widths
The video player playing, handing off, locked and ended, at each width
Notes for developers on how the phone player scrolls when its content runs long
Dev handover in Figma