AI-Powered
Live
Prototyping
Stakeholders struggle to give useful feedback on written requirements. I found that if you build something in front of them, the conversation changes completely. I started opening Replit in the meeting and building working UI from the brief in real time using Claude and Cursor.
- Role
- Design facilitator & developer, live in session
- Timeline
- Ongoing practice · 2024 – present
- Room
- Product, engineering, and stakeholders — together
- Stack
- Claude Code · Cursor · Replit · HTML/CSS/JS · Figma
Abstract requirements produce abstract feedback
When stakeholders review written requirements or wireframes, they often cannot picture what they are actually approving. They say it looks good in the meeting and come back two weeks later with significant changes after seeing the real thing for the first time.
The traditional solution is to build a prototype first, then bring it back for review. That adds a week to every cycle and still results in rounds of revision because the prototype was built based on assumptions rather than a live conversation.
I wanted to collapse that loop. If the prototype gets built during the meeting itself, stakeholders give feedback on something real while the context is still fresh.
Eighteen minutes, condensed
This is what stakeholders watch: an empty project becoming a working dashboard while the meeting is still happening. Scrub the timeline, or jump to any beat, and the build log tells you exactly what changed at that moment.
→ Brief pasted into Claude. Empty project, no components yet.
Recreated with fictional content — real sessions run on actual stakeholder requirements.
Building in the room
Before the session, I read whatever requirements exist and prepare a rough mental model of the UI. The goal is to understand the core interaction so I can build the right skeleton quickly when the session starts.
I open Replit in the meeting, paste the requirements into Claude or Cursor, and start building. Within a few minutes there is a working HTML/CSS/JS prototype on screen. Stakeholders watch it take shape and start reacting immediately.
When a stakeholder says "can we move that button?", I change it while they watch. The prototype becomes a shared artifact that the whole room is shaping together rather than something that gets handed back later with written notes.
After the session, I share the Replit link so stakeholders can continue reviewing at their own pace. I then take the aligned prototype and translate it into a proper Figma file for the developer handoff phase.
Tools used in session
Alignment happens in the room
What used to take days of async back-and-forth happens in a single meeting. Stakeholders leave with something they have already validated.
Because feedback is grounded in a real prototype rather than imagination, the "I didn't picture it like that" problem mostly goes away.
Watching a UI take shape in real time keeps the room engaged. People who usually disengage during design reviews start contributing specific, actionable feedback.
I run Learning Lab sessions where I teach other Labcorp designers how to use Claude Code, Cursor, and Replit in their own workflows. The technique is spreading across the team.