Figma says Harvey uses agents to produce hundreds of tailored demos

• Harvey is making hundreds of tailored demo videos with agents working on the Figma canvas through MCP, according to Figma.
• Brand and motion decisions become reusable building blocks: Figma Weave’s post describes creative judgment becoming a system, while Harvey’s write-up details shared component libraries.
• Human review happens on the canvas, with agents storyboarding and animating for team feedback in Figma’s workflow.

A roughly 750-line JavaScript engine turns scripted beats into films, then lays out contact sheets and flags clipped text, small type, and stray pointers. Harvey reports 36 films in 69 minutes, with another 97 scripted and voiced overnight after it hit its daily Figma call cap.

Harvey describes three reusable foundations in its production breakdown:

• Agentic Brand Guidelines: a Figma library running from visual foundations to templates with worked examples. Each project adds an AGENTS.md page with its own context and changelog, so agents read the brand, then the project, then task-specific material.
• Product Map: key product screens rebuilt as Figma components after agents crawled the app and clicked through its controls. Videos pull from this shared library.
• Motion Primitives: the clever bit, a library of reusable animations down to redlines arriving in a document. Fixing a component updates every film that uses it.

The guidelines began as Markdown files. Harvey says visual examples worked better for communicating relationships between elements in charts, layouts, and long-form documents.

Early demos needed 15 to 20 minutes of back-and-forth apiece, Harvey says in its account of the personalization workflow. The team subsequently built a menu of 44 company-agnostic flows across 13 categories, including a playbook redline in Word.

Account-specific production follows three steps:

1. Gather context: agents use Enterpret’s MCP to pull together Gong calls, Salesforce win-loss reports, and Slack material.
2. Write the script: an agent tailors the story while using a fictional company on screen.
3. Generate narration: ElevenLabs voices the script using a clone of narrator Ashleigh Whittaker, built from ten minutes of her footage.

Only one agent could work in a Figma file at a time, according to Harvey’s scaling account. Queuing agents in one shared file pushed calls to two minutes and caused timeouts.

The replacement coordination system uses:

• Three lane files, each with its own builder agent.
• A coordinator handling export, mixing, and delivery.
• A shared tracker, built as a Claude artifact, that agents and people both read and update. Each film gets a row containing its account, story, status, and links.

Harvey says it made its Artifacts launch film entirely with agents inside Figma. Each scene became a Figma Motion frame, with camera moves, UI states, and text keyed on its timeline.

The team sometimes left 50 comments in a review pass. The agent revised the storyboard and asked which notes should become reusable rules.

For music, humans marked where the beat should drop and the agent retimed the scenes. When the ending fell flat, it cut and EQ’d the track, added sound design, and produced four or five possible outros.

When a frame needs a photo, texture, or shot, agents call a model or a saved Weave workflow through the same MCP connection they use for design. They place the generated asset directly in the Figma file.

Harvey’s brand guidelines supply the art direction agents use to select a model and workflow.

Figma Motion is in open beta, available on any plan to people with edit access. Weave tools inside Figma Design are in open beta on Professional, Organization, and Enterprise plans, also requiring edit access.

Harvey’s setup includes Spectre, its internal agent platform. Colleagues tag it in Slack; it changes the Figma files and replies with what it made, what changed, and which decisions need checking.