In 2023, we walked into a pitch meeting with a 47-slide deck. The client sat through it politely, asked three questions we'd already answered on slide 22, and passed. We'd spent two weeks on that deck.
A month later, we walked into a different meeting with a laptop, an open browser, and a rough prototype we'd built in three days. The client leaned forward. They started rearranging things. They asked their dev team to join the call. We closed the project that afternoon.
"A prototype answers questions that a deck can only approximate. It makes the abstract tangible before anyone signs anything.
The deck is a translation layer — and every translation loses something
Decks translate vision into slides. Slides translate into stakeholder understanding. Stakeholder understanding translates into buy-in. By the time you get to a decision, you're four layers removed from the actual thing you're trying to build.
Prototypes collapse that stack. When someone can click through a nav, read a headline in the right typeface, and see how a card animates on hover — they're experiencing the thing, not a representation of it. Their feedback is calibrated to reality instead of imagination.
What we changed in practice
- We stopped quoting before building a 3-day discovery prototype.
- Our proposals are now one page of text + a clickable Figma or deployed Next.js shell.
- We treat the prototype as the first deliverable, not a pre-sales expense.
- Clients who engage with the prototype before signing tend to scope better and change less.
This approach costs us more upfront. Some leads don't warrant a prototype. We've gotten better at knowing which ones do. The filter has improved our close rate and, more importantly, the quality of projects we take on.
The irony is that a prototype is often faster to build than a deck looks to assemble. Slides require consensus, copy reviews, brand alignment. A prototype just requires building. And building is what we're good at.
Eswar Aditya
Founder & Creative Director, Yarla Studios
Eswar leads design and strategy at Yarla Studios. He writes about the intersection of craft, systems thinking, and what it means to build things that last.
More from the journal
A studio retainer that actually retains.
Most retainers die in month four. We rebuilt ours around outcomes instead of hours.
→Designing systems that survive the team.
Our talk at Config 2026 on writing brand systems for the engineering team, not just the brand team.
→