Talk to Humans, Not Just Your Screen

I’ve been there. You get that lightning bolt of an idea at 2 AM. It’s brilliant, it’s revolutionary, and you’re ready to pull an all-nighter to get the MVP running. But in my experience, the rush to code is exactly where most founders go wrong. I've found that the best code is the code you don't have to write—if you discover early on that nobody actually wants the feature.

Before you even open your IDE, you need to get out of the building. This isn't just a cliché; it’s the difference between a business and a hobby. Start by identifying the specific problem you're solving. Then, go find the people who have that problem. Don't pitch your solution yet; just ask about their pain. When I talk to potential users, I try to listen 90% of the time. If they aren't describing a problem that keeps them up at night, you probably don't have a business case yet.

The "Smoke Test" Landing Page

Once you have a vague sense of the problem, create a landing page. I’m not talking about a full marketing site; just a single page that explains your value proposition as clearly as possible. Tools like Carrd or even a simple WordPress install work perfectly for this.

The goal here isn't to collect credit cards; it's to collect emails. I've found that asking people to "Join the Waitlist" or "Sign up for Early Access" is a great way to gauge intent. If you drive 100 visitors to this page and 0 people sign up, you have a clear signal: your message isn't landing, or the problem isn't painful enough. It’s much better to find this out after spending $20 on ads rather than $20,000 on development.

The Concierge MVP: Do Things That Don't Scale

This is my favorite validation method because it’s so raw and honest. Instead of building an algorithm to automate a service, do it manually. Paul Graham famously advised this, and it holds up remarkably well. If you're building a tool for social media scheduling, manually schedule the posts for your first ten users using the native platforms.

In my experience, this does two things. First, it builds immense goodwill with your early adopters. Second, it teaches you exactly what features you need to build. You’ll learn the nuances of the workflow that you would have missed if you were staring at a database schema. By the time you actually write the code, you won't be guessing; you'll be translating muscle memory into software.

Crunching the Numbers Before You Build

Passion is great, but math pays the bills. Before you commit to building the full product, you need to know if the unit economics can actually work. I always tell founders to look at the long-term viability before the first sprint.

You need to understand how much it will cost to acquire a customer and how much that customer is worth over their lifetime. If you haven't thought about Understanding the Golden Ratio: Optimizing LTV to CAC in SaaS, you are flying blind. I've seen beautiful products fail because the cost of acquiring a user was higher than the revenue they generated. Validating your idea means validating the business model, not just the software. Sketch out your pricing tiers and estimated churn rates now. If the math looks scary on paper, no amount of elegant code will fix it later.

Choosing Your Path: Funding or Bootstrap?

Validation also helps you decide how to fund your dream. This is a critical juncture. I’ve met founders who assume they need venture capital immediately, only to realize their idea is better suited for a slow, profitable growth curve.

It’s worth taking a step back to evaluate the landscape. Read up on the debate of Bootstrapping vs. Venture Capital: Which Path is Right for Your SaaS?. If your pre-sales are strong and you can fund development yourself, you might retain more equity and freedom. However, if the market is massive and the winner takes all, you might need that war chest. Knowing this early changes your validation strategy. VCs want to see massive potential market size, while bootstrappers need to see immediate cash flow.

Planning Your Execution Strategy

Let's say you’ve done the interviews, the smoke test passed, and the concierge phase is working. Now you have to think about how you’re actually going to build this thing.

You might be a solo hacker right now, but if validation goes well, you’ll need a team. The nature of modern software development has changed dramatically. I've found that limiting your search to local talent often hinders your ability to find the best developers. You should seriously consider looking beyond your zip code. There are massive advantages to talent density when you aren't restricted by geography. If you’re thinking about scaling up after your validation phase, you should check out my thoughts on The Permanent Shift: Managing a Fully Distributed SaaS Team Effectively. It’s a skill set you’ll need sooner than you think.

Sell the Vision, Not the Features

Finally, try to get a verbal "yes" or, even better, a letter of intent. If you are selling B2B software, try to get a meeting with a decision-maker. Pitch the vision. Tell them how their life will change six months from now when they are using your tool.

If they say, "Call me when it's ready," that's a polite no. You want them to say, "I need this yesterday. When can you ship?" That desire, that pull from the market, is what validates your idea. In my experience, features will change, the UI will evolve, and the tech stack might get swapped out entirely. But if the core value proposition resonates with a human being enough to make them pull out their credit card or sign a contract, you have successfully validated your SaaS.

So, put down the keyboard. Go talk to a customer, run a quick ad, or do some manual work. Your future self—and your bank account—will thank you.