Stop pitching mockups. Pitch working software.
The mockup is a liability.
For decades, agencies pitched with static screens. Figma boards, Keynote decks, annotated wireframes: beautiful artifacts that show what something could look like, but not how it works. Clients learned to nod along, approve the comp, and then act surprised when the built product felt different from the picture.
That gap between mockup and reality was always a problem. Now it is unnecessary.
The new tools
v0, Lovable, Bolt, and Figma's Make feature have collapsed the distance between an idea and a clickable prototype to about an hour. You describe what you want. You get a working application, not a picture of one. It runs in a browser. You can click through it. You can show it to a user and watch what they do.
These tools are not perfect. The generated code is not production-ready. The designs lean toward a recognizable "AI aesthetic" that you will want to override. But the output is functional, and functional beats beautiful-but-static in every client meeting.
Why this changes the pitch
Clients can react to behavior, not just appearance. A static mockup invites feedback on colors, fonts, and layout. A working prototype invites feedback on flow, logic, and whether the thing actually solves the problem. The quality of client input goes up dramatically when they can use something instead of just looking at it.
Ambiguity dies early. Half the scope creep in agency projects comes from misaligned expectations that surface during development. When the prototype is built in week one instead of week eight, those misalignments surface before anyone has written real code.
Speed signals competence. Walking into a pitch with a working prototype that you built that morning communicates something that slides cannot: you can execute. In a market where clients have been burned by agencies that over-promise, showing a working thing is the strongest trust signal available.
Cost of exploration drops to near zero. Want to test three different approaches to the onboarding flow? Generate all three. Let the client try each one. Pick the winner. This used to require a week of design work and a difficult prioritization conversation. Now it requires an afternoon.
What to watch out for
The AI aesthetic trap. v0 and Lovable produce clean-looking interfaces that all look similar. If your prototype looks like every other AI-generated prototype, you have not differentiated. You have commoditized. Use the tool for structure and logic, then apply your own design language.
Prototype-to-production gap. The generated code is a starting point, not a codebase. Teams that try to ship a v0 prototype directly to production will regret it. Treat the prototype as a spec, not as the implementation.
Over-promising on timeline. Because the prototype came together in an hour, clients will expect the production build to come together in a week. Set expectations explicitly: the prototype proves the concept. The build is a different conversation.
The agency that still pitches with slides
Every pitch is now a competition between an agency that shows a deck and an agency that shows a working prototype. The agency with the deck explains what they will build. The agency with the prototype shows what they already started. The client will hire the one that reduced their risk. And a prototype you can touch reduces more risk than a slide you can read.
