Figma AI Sites vs Runway ML Gen-4 Turbo

“Figma AI Sites solves the single most painful moment in the design-to-web pipeline: the moment a developer opens the Figma file and re-interprets every spacing decision. The output is AI-generated HTML and CSS, which means the tool is only as good as how faithfully it translates auto-layout constraints, component variants, and responsive breakpoints into actual DOM structure — and from what Figma has shown, the fidelity is genuinely high. The specific design decision that earns this ship is that it respects Figma's own component and constraint system as the source of truth rather than screen-shotting the design and guessing. The risk is edge cases: complex interactions, hover states, and scroll behaviors that Figma's prototyping layer doesn't fully express will still fall through the cracks.”

“The primitive here is: static-site generator with Figma as the schema, AI as the compiler. That's actually not a bad idea, but the DX bet is entirely wrong for developers — it routes complexity into the AI black box rather than into a deterministic build step you can debug, version, or extend. The first 10 minutes for a developer means opening the exported HTML and asking whether you can wire up a real CMS, add a custom component, or run it through a build pipeline — and the answer is almost certainly 'not without re-engineering it.' The weekend alternative is real: Webflow, Framer, and even Builder.io solve this problem with more developer surface area and established component ecosystems. The skip is because 'export to custom hosting' without a documented output schema or CLI is just a ZIP file with AI feelings about your design.”

“Category is design-to-code publishing, and the direct competitors are Framer, Webflow, and Builder.io — all of which have been doing this longer, have richer interaction models, and have established CMS pipelines. The specific scenario where Figma AI Sites breaks is the moment a client wants to update a blog post, add a product to an e-commerce section, or change a nav link without asking a designer — the CMS integration claim needs scrutiny because 'CMS integration' on launch usually means 'we support one CMS with five field types.' What kills this in 12 months: Figma's core business is design collaboration, not hosting infrastructure, and the moment this feature requires serious investment in CDN reliability, edge performance, and CMS depth, it either gets spun out or quietly deprioritized. To earn a ship, Figma needs to publish the full capability surface of the CMS layer and show production sites running on it at scale.”

“The sub-10-second latency claim is the one thing here that's actually verifiable and reportedly holds up, which is more than I can say for most video gen announcements. The motion brush is a real differentiator against Sora and Kling — both of which still treat motion as a prompt-level abstraction rather than a spatial control problem — but Runway's credit-burn rate at Pro tier will hit frequent iterators hard, and that's the exact user who benefits most from fast generation. What kills this in 12 months isn't a competitor, it's OpenAI shipping native video generation at cost into the existing ChatGPT subscription and eating the casual end of Runway's market, forcing a hard pivot to enterprise or prosumer.”

“The buyer is clear: design-led teams and agencies who already pay for Figma and want to eliminate the handoff cost to a developer or a separate publishing tool like Webflow. The pricing architecture is clever — burying this inside the Professional plan turns it into a retention feature rather than a new SKU, which means Figma doesn't have to win on publishing, they just have to make switching to Webflow slightly less obvious. The moat is the existing Figma file corpus: every team that publishes a site through AI Sites is now locked into Figma as their design AND publishing layer, which is real workflow lock-in. The stress test is whether Webflow or Framer responds by building a Figma import that's good enough — and the answer is they already have import features, so Figma's window to make this sticky is measured in months, not years. The specific business decision that earns the ship is using hosting as an expansion revenue vector inside an existing enterprise contract rather than trying to build a standalone publishing business.”

“The buyer is a creative professional or a marketing team, and the credit model makes sense until it doesn't — power users who actually drive word-of-mouth are precisely the ones who will hit credit ceilings and either upgrade to Unlimited at $95 or churn to a competitor with better unit economics. The moat question is the uncomfortable one: Runway's lead is measured in months, not years, and the motion brush is a UI-level innovation that Pika, Kling, or any well-funded competitor can ship in a sprint. The business survives if Runway builds deep enough workflow integration — timeline editors, API access, team collaboration — that switching costs accumulate faster than the competitive gap closes, but right now they're selling shots, not a platform, and that's a pricing architecture problem.”

“The motion brush is the thing here — you're painting velocity vectors onto regions of a frame, which means the output stops being a slot machine and starts being a collaborator. The 10-second turnaround changes the editing rhythm completely; you can now iterate on a shot the way you'd iterate on a comp in Figma rather than waiting for a render to come back from a farm. The outputs still carry the Runway texture — a certain liquid smoothness in motion that reads as AI to anyone who's been watching this space — but the directional control meaningfully reduces the homogeneity problem that makes most AI video look interchangeable.”

“The thesis Gen-4 Turbo is betting on: by 2027, video generation latency drops below the threshold of human patience and the constraint shifts from compute to creative direction, making spatial control primitives — not prompt quality — the primary differentiator. The motion brush is infrastructure for that world, not a feature for this one. The second-order effect that nobody's talking about is what happens to stock footage licensing when a creative director can generate a contextually correct 4-second shot in under 10 seconds mid-edit; that market doesn't shrink gradually, it falls off a cliff. Runway is riding the inference cost deflation curve and is roughly on-time — the risk is that the deflation benefits model providers more than application layers, and Runway has to build enough workflow gravity before that compression happens.”