All posts

May 17, 2026

From Idea to Stakeholder-Ready Mockup in 30 Minutes

You have a product idea, a client call in an hour, or a funding conversation on Friday. Here's exactly how to go from a sentence to a complete, shareable design that can anchor a real conversation.

There's a specific kind of pressure that product people know well. A conversation is scheduled — a client demo, a funding pitch, a team alignment session — and you need something to show. Not a deck of bullet points. Not a rough sketch on a whiteboard. Something that looks like a product, that people can react to, that can anchor a real conversation about what you're building.

The old version of this problem had limited solutions. Hire a designer and hope they turn it around in time. Build a rough prototype in Figma and accept that it'll look rough. Start coding and demo an incomplete half-working thing. None of these are great, and all of them take longer than the conversation requires.

The new version of this problem has a better answer. Here's the arc.

What "stakeholder-ready" actually means

Before getting into the mechanics, it's worth being precise about the target. A stakeholder-ready design is not the same as a finished design.

It needs to be:

  • Complete enough to be reacted to. All the core flows present, not just the hero screen.
  • Specific enough to be critiqued. Real labels, real content structure, an actual visual direction — not lorem ipsum and grey boxes.
  • Shareable. A link that opens without requiring the viewer to install or sign in to anything.
  • Prototypable. Ideally, clickable enough that someone can experience the core flow rather than having to imagine it.

It doesn't need to be:

  • Production-ready.
  • Pixel-perfect.
  • Final in any sense.

The goal is a concrete artefact that makes the conversation specific. Without it, conversations about product decisions are abstract — people talk past each other, form different mental pictures, and leave without real alignment. With it, everyone is responding to the same thing, and the feedback is useful.

Research on rapid prototyping consistently confirms this value proposition: companies that invest in early-stage prototypes experience significantly shorter feedback cycles and 30% cost savings in later development stages, because problems surface in the prototype rather than in the build.

The 30-minute arc

Minutes 0–10: the questionnaire

Mowgli starts with a structured questionnaire that extracts the product model: what the product is, who uses it, what the core flows are, what the edge cases are, what constraints apply. This isn't paperwork — it's the step that makes everything else coherent.

A founder with "Airbnb for boat storage" knows what their product does, but probably hasn't thought through: what the empty state looks like for a host with no listings yet, whether a renter can message a host before booking, what happens when a booking is cancelled, how search results are filtered. The questionnaire surfaces these gaps in ten minutes, before they show up as missing screens in the design.

The output is a PRD — a structured product spec that the rest of the generation is built from.

Minutes 10–12: moodboard

After the questionnaire, Mowgli surfaces 16+ design directions — fully realised aesthetic themes applied to screens from your actual product. Not abstract mood boards. Your product's content, your information hierarchy, in different visual languages.

You browse the grid, select up to four that catch your eye, and preview them side by side on a flagship screen from your app. This is the fastest possible path to an aesthetic decision: instead of describing what you want or iterating from a default, you react to concrete options. Most people pick a direction in two minutes. If you want to fine-tune — adjusting a colour, swapping a type style — that's another few minutes. Either way, you're not spending long here.

Minutes 12–15: generation and share

With the spec and the aesthetic direction set, Mowgli generates the full product — 20, 30, 40+ screens depending on the scope of what you described in the questionnaire, all in the theme you chose, all coherent with each other. Every core flow. Every screen type the product needs.

The result is a complete, prototypable design set. Share a link. Walk stakeholders through it. Let them click through the flow. If this is all you need, you're done at 15 minutes.

Minutes 15–30: ideate, prototype, and explore (optional)

The 30-minute window isn't a hard deadline — it's the upper bound for getting something genuinely useful. If you have the time, this is where the work gets interesting.

Generate a prototype. Link your screens together into a navigable flow that stakeholders can click through themselves. No narration required — they experience the product rather than watching you present it.

Explore alternative directions. If you're presenting to a client and want to give them a genuine choice, run the moodboard again on a second direction. Now you have two fully realised versions of the same product — same spec, different aesthetic — and the conversation becomes a concrete visual comparison rather than a hypothetical one.

Iterate on specific screens. Use the canvas to adjust layouts, rephrase copy, try a different navigation structure. Each change is instant. If something in the brief shifts after your first generation, updating the spec and regenerating takes seconds, not hours.

The 30 minutes is how long it takes to go from nothing to a complete, shareable, prototypable design with room to experiment. The core path — questionnaire, moodboard, generation — is closer to 15.

The client call scenario

The 30-minute arc above assumes you have 30 minutes before you need to show something. The more common scenario is that you have an idea and a call, and you want to walk into the call with something rather than nothing.

The practical move is to do the questionnaire and moodboard in the gap before the call — even if you only have 20 minutes, the spec is done and the aesthetic direction is chosen. In the call, you can either show the in-progress generation or share the screen while it generates. Either way, you're not showing a deck. You're showing a product concept with a specific visual identity, specific flows, and enough completeness to have a real conversation.

The value in the room isn't the fidelity of the screens. It's the specificity. When a client or investor or stakeholder is looking at an actual interface — real labels, real content structure, real layout — they give you real feedback. They tell you what's wrong with the flow, what's missing, what they assumed was in scope that isn't. That feedback is what the conversation is for.

The Friday deadline scenario

"I need to show stakeholders a UI by Friday" is a classic product pressure. The corollary is that the design produced under this pressure is often rushed and incomplete — happy path only, visual inconsistencies, missing states — and the feedback it generates reflects that incompleteness rather than the product itself.

The better path: spend 30 minutes on Monday creating a complete design in Mowgli. Share it for async feedback before Friday's meeting. By the time you're in the room, stakeholders have already reacted to the design, the obvious questions have been answered, and the Friday conversation can go deeper.

Rapid prototyping research shows that interactive prototypes save designers 10+ hours individually by surfacing issues before code is written, and that stakeholder feedback on working prototypes is qualitatively different from feedback on verbal descriptions or decks — more concrete, more actionable, more efficiently gathered.

What you can do from the 30-minute output

A complete Mowgli design isn't just a presentation artefact. It's a working basis for the actual product:

  • Prototype it — link screens together and share a navigable flow for user testing or investor demos
  • Iterate on it — use the canvas to try layout variations, adjust flows, or update the spec as requirements change
  • Export it — hand off to engineers or a coding agent with the full design as the source of truth, not a sketch
  • Redesign it — explore variations directly on the canvas, or start fresh with new directions in the moodboard and regenerate from there

The 30 minutes isn't just the path to something to show on Friday. It's the start of the actual product design process — with a complete first draft to build from rather than a blank canvas.

Sources