Test Before You Invest: A Customer Validation Framework for Leaders Who Want to Stop Wasting Money

Here's a number worth remembering: 72% of new products fail. Not because the teams behind them lacked talent, budget, or ambition. They fail because nobody stopped long enough to ask the people writing the checks whether the thing being built was the thing they needed. Customer validation is the single most skipped step in product development, in process improvement, and in leadership decision-making. And skipping it is expensive in ways most leaders don't calculate until it's too late.

I've watched this pattern play out in organizations of every size. A leadership team identifies a problem. They brainstorm solutions. They pick the solution they're most excited about. They resource it, staff it, build it, and launch it. Then they wait for applause. When the applause doesn't come, they blame execution. They blame marketing. They blame timing. But the problem wasn't execution, marketing, or timing. The problem was the first five minutes, when the team skipped the step where they asked the people on the other end of the decision whether any of this mattered to them.

I want to walk you through a framework I use to pressure-test every big idea before committing real resources. It's called the Validation Loop, and it has four stages: Research, Prototype, Test, Decide. Each stage is designed to reduce risk, surface blind spots, and keep your customer's voice at the center of every call you make. It's not complicated. But it does require discipline, and more importantly, it requires you to accept your best idea might be wrong.

Let me start with a story.

The Breakfast Taco Experiment

I run a fictional business called Toby's Taco Truck. It shows up in a lot of my content because it's the perfect small-business sandbox for testing ideas. A few months ago (in this fictional world), I had a brilliant idea: breakfast tacos. The logic was airtight. I already had a truck, a grill, and a customer base. I'd roll up to my best morning commuter spots at 6:30 AM, catch the pre-office crowd, and double my revenue window. The concept felt like such a lock that I started planning immediately.

My first instinct was to go all in. Buy the breakfast ingredients. Test new recipes. Print new signage with a sunrise theme. Adjust my truck schedule to start at dawn. I was three clicks into ordering a bulk case of cage-free eggs when something stopped me. A nagging feeling. A voice in the back of my head asking a question I didn't want to hear: Have you talked to a single customer about this?

The answer was no. And honestly, I didn't want to. I was excited. The idea felt good. Asking people felt like slowing down. But I forced myself to try something different. Instead of buying eggs, I bought a clipboard.

I showed up at my best morning spot the next Monday at 6:30 AM, stood next to the truck (which wasn't open yet), and asked 40 people walking by one question: "If a taco truck was open right here, right now, would you stop for breakfast?" I kept it simple. Yes, no, tell me more.

The answers surprised me. Seventeen said yes. Eight said they already eat breakfast at their desk and wouldn't stop. Fifteen said they don't eat before 9 AM and the timing wouldn't work for them. And here's the part I didn't expect: of the seventeen who said yes, eleven of them asked if I'd have coffee. Six asked if I'd have anything lighter than a taco, like a breakfast burrito bowl or a fruit cup. Two people specifically said they'd come every day if I had good coffee, and one of them said she drives past three coffee shops because none of them have food she likes with her latte.

One morning with a clipboard and a question gave me more actionable insight than a month of recipe testing would have. I learned the demand existed, but it was narrower and more specific than I assumed. If I'd gone all in on my original vision, scrambled-egg tacos with chorizo and salsa verde, I'd have been standing behind a truck full of heavy food while half my potential customers walked past asking for oat milk lattes and something light.

The lesson: your assumption about what customers want is a hypothesis, not a fact. Treat it accordingly. And the best way to treat it accordingly is to put it through the Validation Loop before it becomes a line item on your budget.

The Validation Loop: Four Steps to Smarter Decisions

The Validation Loop is a repeatable framework for testing ideas before they become expensive commitments. It works for product launches, process changes, service offerings, team restructures, and strategic pivots. The principle is always the same: get evidence before you get attached.

Step 1: Research (Talk to People)

Research is the step everyone thinks they do, but almost nobody does well. Real research means getting out of your head and into a conversation with the people who will be affected by your decision. Not a survey with leading questions. Not a focus group where the loudest voice wins, and everyone else nods along. Direct, open-ended, one-on-one conversations where you listen more than you talk.

Here's a rule of thumb: if your research doesn't surprise you at least once, you didn't go deep enough. The whole point is to surface what you don't know. If every answer confirms your existing belief, you're either asking the wrong questions, talking to the wrong people, or both.

Three practical moves for better research. First, ask "what" and "how" questions instead of "would you" questions. "Would you buy this?" invites a polite yes. "What did you do the last time you faced this problem?" gets you real behavior. People will tell you they'd buy your product to be nice. They won't lie about what they did last Tuesday.

Second, talk to people who chose a competitor or chose to do nothing. Your fans will tell you what you want to hear. The people who looked at your category and chose someone else, or chose to live without a solution entirely, will tell you what your idea is missing faster than anyone on your customer list.

Third, aim for 15 to 20 conversations minimum. Anything less and you're hearing anecdotes, not patterns. Patterns require repetition. By conversation 12 or 13, you'll start hearing the same themes, and those themes are gold. If you're still hearing new information at conversation 20, keep going. The signal isn't strong enough yet.

Step 2: Prototype (Build the Minimum)

A prototype is not a product. It's a question made tangible. Its only job is to help you learn something you didn't know before. The moment you start treating your prototype like a product, you've already invested too much emotion, too much time, and too much polish to hear honest feedback.

The most effective prototypes are embarrassingly rough. A landing page with a signup form and no backend. A paper sketch of a new workflow drawn on a napkin at lunch. A printed menu taped to a truck window. A slide deck walking a potential client through a service you haven't built yet. These rough versions serve a purpose: they invite honest reactions. People feel comfortable tearing apart a napkin sketch. They don't feel comfortable tearing apart something you clearly spent three months building. The roughness is a feature, not a bug.

The quality of the prototype should match the quality of the question you're trying to answer. If the question is "Do people want this category of thing?", you need a napkin sketch, not a polished MVP. If the question is "Will people pay this price?", you need a checkout page or a pricing conversation, not a focus group full of opinions. Match fidelity to the maturity of your question, and resist the urge to over-build.

I see leaders freeze at this stage because they confuse a prototype with a promise. They worry about putting something rough in front of a customer. They think it'll damage their brand or credibility. It won't. Framing matters. "We're exploring a few ideas, and we'd love your reaction" is an invitation. "Here's our new product" is a commitment. One of those creates space for honest feedback. The other creates pressure to perform.

Step 3: Test (Cheaply)

Testing is where your prototype meets real behavior, not opinions. The distinction matters enormously. People will tell you they love your idea in a survey and then completely ignore it when it's sitting right in front of them. Stated preference and revealed preference are two different things, and only one of them predicts what will happen when you launch. Testing measures what people do, not what they say they'll do.

The best tests share three traits. They're cheap: under $500 if possible, under $100 if you're creative. They're fast: one to two weeks from "let's test this" to "here's what we learned." And they produce a clear signal. A clear signal means you defined a success threshold before you started. "We'll know this works if 25% of people who see the landing page click Sign Up." "We'll know there's demand if 8 out of 15 interviewees describe this problem unprompted." Without a threshold, you'll rationalize any result into a green light. Three signups? "That's a start!" One positive review? "We're onto something!" A pre-set threshold keeps you honest.

For my breakfast taco experiment, the test was a single Saturday morning pop-up. I made three items: a classic breakfast taco, a breakfast bowl, and coffee. I promoted it with a handwritten sign and a quick social media post the night before. Total investment: about $85 in ingredients and cups. Sold 31 items in two hours. The breakfast bowl outsold the taco 3 to 1, and every single coffee sold. Data I never would have gotten from a survey, and data that directly contradicted my original vision of a taco-focused breakfast menu.

Step 4: Decide (With Data)

The final step is the one leaders struggle with most: using the data to make a call, even when the data disagrees with their gut.

Decisions after validation should answer one of three questions. Do we go? Do we pivot? Do we kill it? Notice "do we keep thinking about it" isn't on the list. Validation is designed to produce action, not more analysis. If you're using validation results to justify another round of meetings, you're not validating. You're stalling.

Going back to the taco truck: the data told me breakfast had legs, but not in the form I imagined. The move was a breakfast bowl and coffee menu, not a full taco spread. Smaller inventory, lower prep time, higher margins, and a product mix my customers actually wanted. The data reshaped the vision, and the vision got better for it. Not because I compromised. Because I learned.

Why Smart Leaders Still Skip Customer Validation

If validation is this straightforward, why do experienced leaders skip it? Three reasons come up consistently in every industry I've worked with and studied.

Speed addiction. In fast-moving organizations, "move fast and break things" became a badge of honor. Validation feels slow. It feels like hesitation. And in competitive environments, hesitation feels dangerous, like letting a competitor get to market first. But there's a critical difference between moving fast and moving recklessly. Validation doesn't slow you down. It keeps you from running full speed in the wrong direction. A two-week validation cycle is not a delay. Spending six months building the wrong thing is a delay.

Ego investment. The further you develop an idea in your head, the harder it becomes to hear someone say "I wouldn't use this." By the time most leaders seek feedback, they're not looking for truth. They're looking for permission. They've already decided. They're presenting the idea to stakeholders with the same energy they'll use to present the finished product. And when feedback arrives that contradicts their direction, they hear it as criticism of their judgment rather than information about their market.

Mistaking activity for progress. Writing specs, building decks, attending planning meetings, scheduling standups, running financial models: these activities feel productive. They create a sense of momentum. Calendars fill up. Status reports go out. It feels like the project is moving. But momentum without direction is a waste of energy. Every hour you spend polishing an unvalidated idea is an hour you could have spent learning whether it matters to a single person outside your building.

The Hard Truth

You don't know what your customer wants. Full stop. Your experience gives you an educated guess. Your instinct gives you a starting point. Your years in the industry give you pattern recognition. But none of those give you the right to skip the conversation. The leaders who build things people love are not the ones with the best ideas. They're the ones who refused to fall in love with their own assumptions. They're the ones who asked, listened, tested, and built based on evidence rather than enthusiasm.

THE MOST EXPENSIVE MISTAKE IN BUSINESS ISN'T A BAD IDEA. IT'S A GOOD IDEA NO ONE ASKED FOR.

Start This Week

Pick one idea, initiative, or project sitting on your plate right now. Before you spend another dollar or another hour on it, run it through the Validation Loop.

Schedule five conversations with the people it's meant to serve. Not your team. Not your stakeholders. The end users. The people whose behavior needs to change for your idea to work. Ask open-ended questions about their current experience, their frustrations, their workarounds. Listen for the surprise, the thing they tell you that doesn't match your assumptions. Write it down.

Then build the roughest possible version of your idea. Something you'd be embarrassed to show at a board meeting. Put it in front of three people and watch what they do. Don't explain it. Don't sell it. Watch. Where do they hesitate? What do they ignore? What question do they ask first? Their behavior will tell you more than their words.

Then set a threshold and run a cheap test. Define what success looks like before you start measuring. Run the test for a week. Look at the numbers. Make a call: go, pivot, or kill. And if the answer is kill, celebrate it. You saved yourself from a much bigger loss down the road.

Customer validation isn't a phase in a process. It's a mindset. And leaders who adopt it build faster, waste less, and earn trust from the people they serve. The best ideas don't need protection from feedback. They get sharper because of it.

For more frameworks, stories, and actionable strategies for leadership, process improvement, and professional development, head to toby-talks.com.

LEAD . IMPROVE . GROW