Enterprise 5G Connect (EVCN) runs at startup pace inside Ericsson: launch with operators across three continents, each market with its own language and its own brand on the product, and close every gap before go-to-market. Iterations came in short, high-pressure cycles. We had an advanced Figma prototype — genuinely advanced. And it still wasn't enough, because a prototype is a film: it shows the flow we scripted, at the click count we predicted, on the screen size we chose.
From prototype to place
When we got the green light for Claude Code — Opus 4.8 had just been released — we rebuilt our Figma designs as a working mockup site on the Ericsson Design System. Product-owner discussions moved off static screens and onto actual interaction: validating the behaviour, not a picture of it. Development quality rose with it, because the mockup already spoke the design system's language — and stress-tested it, screen size by screen size, before production code existed.
Off the script
A film audience follows; a visitor explores. In the mockup site, users aren't limited to a specific flow or a budgeted number of clicks — they wander the full solution, resize it, poke at edges we didn't plan to show, and meet it in their own language. That last part is what inclusion actually means on a multi-market product: nobody should have to evaluate their tools through a foreign tongue. Feedback from free exploration is a different species from feedback a guided prototype produces — it tells you about the product, not about the demo.
Minutes, not days
White-labeling was the sharpest operational gain. Onboarding a new operator brand or a new language used to mean days of rebuilding content, styles and a web of links in Figma. In the mockup site it takes minutes. Recorded multi-language demos now travel with the sales process, and the same build lets us put upcoming features in front of customers and our concept studio early — selling the roadmap more reliably because prospects touch the thing, and evaluating it with them long before delivery.
The practice generalizes: UX iteration, user research and pre-sales, served by one walkable build. The memo describes; the demo convinces. Demo, not memo.