Why Plujo Validates Before It Builds

What we talked about.

In this episode of the Sunny Ray Show, Sunny sits down with Jeremy, founder of Plujo, a venture studio and consultancy built around one core idea: validate before you build. After nearly 30 years writing code and building startups, including a painful two year detour building agency management software that landed only two paying clients, Jeremy explains why founders keep inverting the obvious. He argues entrepreneurs fall in love with their own ideas, mistake themselves for their market, and chase investor feedback instead of customer demand. Jeremy walks through Plujo's structured process, a 12 week launch protocol that tests problems with ads and waitlists before a line of code is written, a capital bridge protocol for founders who already have proof, and a lean scale protocol using AI agents to multiply operational leverage without adding headcount. The conversation moves from Jeremy's early days consulting for businesses during the internet's rise through the mistakes that shaped Plujo's philosophy, offering a candid, practical look at why proving demand first changes everything for early stage founders.

A 30 year startup veteran explains why validating demand before building saves founders from years of expensive, invisible failure.

The questions, and the answers.

What is Plujo and what are you building? Why should someone care?

Plujo is a venture studio and consultancy helping businesses navigate the AI age, moving from stuck to unstuck. The venture studio side takes people from problem to product, not product to market. We start by confirming people actually want the idea, then build, then scale. It sounds simple, but I talk to 25 founders a day and rarely hear that discipline applied.

What's the through line connecting nearly 30 years of failures and successes to Plujo?

I got into business early during the internet's rise, so companies brought me in for real problems instead of hiring expensive consultants. I consulted with thousands of businesses and saw the barriers firsthand. The lesson was that business isn't easy, you have to iterate and listen instead of getting stuck in your own head doing what you've always done, especially as a startup founder.

Why is validating before building so counterintuitive when it seems obvious on paper?

It's logical when you draw it out, people agree instantly. But in reality you get so passionate about your own idea that you start creating a narrative in your head about what people want instead of actually asking them. You imagine an audience and market and convince yourself they'll want it. It's part of the psyche, we get excited about our own ideas and stop checking reality.

You've called Plujo the culmination of everything you learned building startups. What did it specifically take from each earlier company?

The biggest realization is that there actually is a formula, a series of steps to go from problem to product, even though every founder insists their situation is too unique for a process. You need to talk to your market, get them to pay and commit. The real mistake across 30 years was saying go when it should have been a no go, that's where the failures and wasted money came from.

You've said most founders run to investors or start building without properly validating with customers. Can you tell me about a time that cost you?

We had a content management platform working through an agency network, and agencies kept asking us to build full account management software. We built it all before having a single customer, eventually putting half our 10 to 12 person team on it. After two years and roughly 10,000 agency conversations, we landed only two clients. Meanwhile tools like ClickUp and Monday came in and just did it right.

Why do so few founders follow the validate first approach even when they agree with it in theory?

People get deeply committed to an idea because our brains work in stories, we can write a narrative about becoming the next unicorn almost instantly. Business isn't built on ideas though, it's built on identifying a real problem people want solved badly enough to pay for. Founders skip that first step of proving the problem because they're already emotionally attached to their solution.

How do you build discipline into a studio so founders under pressure don't skip validation?

Most entrepreneurs I meet are already pitching investors and changing their business model based on rejection feedback. But investors are focused on market demand, not on seeing the actual problems on the ground. Schools teach you to write a pitch deck and chase funding, not to validate a problem first. If you walk in with paying customers instead of just an idea, investors rarely say no.

Can you walk me through the 12 week launch protocol, the capital bridge protocol, and the lean scale protocol?

The 12 weeks start with validating the idea and market, then testing demand through ads and waitlists before writing code, building only a proof of concept with the few features people actually wanted. That produces an MVP plan and a marketing plan grounded in real signals. Capital bridge comes next with proof already in hand. Lean scale then uses AI to boost efficiency and revenue, not to cut headcount.