The Prototype Is Not The Product

I like prototypes because they reduce lying. Not malicious lying. The softer kind. The kind that happens when everyone in a meeting says they understand the idea, but each person is imagining a different product in their head.

A prototype ends that nonsense quickly. You put the thing on the screen and suddenly the room becomes honest.

"That flow is too long." "This CTA is unclear." "Wait, where does the data come from?" "Would users even trust this?" Good. Now we are working.

The New Builder Stack

Tools like Lovable, v0, Bolt, Replit, and Figma Make have changed what a product manager or founder can do before involving a full team. You can create clickable interfaces, rough apps, landing pages, dashboards, onboarding flows, and internal tools in hours instead of weeks.

That does not make design, engineering, or research irrelevant. It makes bad ideas cheaper to expose.

Figma, FigJam, Miro and Excalidraw

These are still where I like to clarify the shape of the problem. Before I generate screens, I want the messy map: user journey, system boundary, decision tree, stakeholder friction, and the moment where value is supposed to happen.

v0, Lovable, Bolt and Replit

These are useful when the conversation needs a working surface. Not final production. Not architectural truth. A working surface. Something that helps the team feel the flow, question the assumptions, and catch the missing pieces early.

Webflow, Framer and WordPress

These sit closer to market expression: landing pages, waitlists, content, positioning, and quick GTM tests. Sometimes the most important prototype is not the app. It is the page that tells you whether the market understands the promise.

How PMs Should Use Prototypes

• Use them to align stakeholders before engineering commits.
• Use them to test language and user flow before investing in polish.
• Use them to expose missing states: empty, loading, failed, delayed, rejected.
• Use them to make tradeoffs visible.
• Use them to learn what the PRD forgot.

The worst prototype is the one that becomes theatre. The founder presents it like a finished product. The PM defends it like a strategy. The team applauds because it looks polished. Nobody asks whether users care.

Prototype The Argument

Every product idea is an argument. We believe a user has this problem. We believe this workflow will help. We believe this value is strong enough to change behaviour. We believe the business can support it.

The prototype should test that argument. If it does not, it is just decoration with a login screen.