How We Validate a New Venture in 30 Days

In February of 2024, I had a venture idea I was convinced would print money. A logistics-aggregation platform for small Filipino agri-cooperatives — the kind of idea that sounds inevitable on a whiteboard. Three weeks earlier I had finished a customer-discovery sprint for AgriForge, our agritech venture, and I was riding the confidence of having built something that worked. So I did what every founder does when they think they've spotted a gap: I started building.

Thirty-eight days later I shut the project down. Not because it was a bad idea. Because the validation evidence I had accumulated was confirmation bias dressed up as research. Every cooperative leader I had spoken to was someone I already had a relationship with through Bayanihan Harvest. Every "yes, we'd use this" came from people who would have said yes to anything I built. I had validated my network's willingness to be polite to me. I had not validated demand.

That month cost roughly forty hours of my time and a small amount of cash. The version of me that didn't catch it would have raised capital, hired two people, and built a six-month runway around a market signal that wasn't real. I have watched founders do exactly that. The cost of skipping real validation is not the wasted month — it is the eighteen months that come after, when you can no longer pivot because the burn rate locked you into the wrong problem.

After that experience I rebuilt our validation process. We now run a 30-day sprint before any new venture receives shared resources from HavenWizards 88 — engineering capacity, content distribution, capital. The sprint has five gates. If the gates are not cleared in 30 days, the project does not get shut down. It gets frozen. The difference matters and I will explain why later in this article. But the operational structure of the 30 days is what makes validation produce signal instead of bias, so that's where we start.

Why 30 Days, Not 90

Most validation frameworks give you 90 days. Ninety days is wrong, and the reason it's wrong is operational, not strategic.

When you give yourself 90 days, you give yourself permission to delay the uncomfortable conversations. The cold outreach. The price test where someone has to actually pay. The version of customer interview where the customer says no and you have to write that down. With 90 days on the calendar, week three is still discovery. Week six is still "synthesizing learnings." Week nine is when you finally do the hard test — and by then you have psychological investment in the outcome being positive.

Thirty days forces triage. You cannot run a 30-day sprint and also wait for the right moment to talk to strangers, or wait until the deck is polished, or wait until the prototype feels ready. You have to run all five gates in parallel from week one, and that constraint is what produces real signal. You learn what you're avoiding because you literally don't have time to avoid it.

The other reason 30 days works: it forces a real cost decision at the end. If the gates haven't cleared in 30 days, you stop and freeze. You don't get to argue for "just another two weeks." Two weeks is half the original sprint. Two weeks of additional time is a 50% scope expansion, and we treat it as one. Founders who say "almost there, just two more weeks" 70% of the time end up another 60 days deep in a venture that should have been frozen at day 30. We have done this. We learned.

The 5 Validation Gates

Every venture passes through the same five gates. The gates do not change. The criteria for clearing each gate do not change. What changes from venture to venture is the evidence required to clear them — and that evidence has to be specific to the venture's actual market, not generic.

Gate 1: Problem Reality

The first gate asks one question: does the problem you think exists actually exist, in the form you think it does, for the people you think experience it?

This is not validated by interviewing twelve people. It is validated by finding three people who have already paid money — to anyone, for any solution, however imperfect — to attempt to solve this problem. If you cannot find three people who have spent money on workarounds, the problem is not painful enough to support a venture. The willingness to pay precedes the willingness to pay you specifically.

For HW88 Education, the proof was that we found seven people in our target audience who had each spent over ten thousand pesos on courses, coaching, or templates that didn't actually deliver execution capability. They had the money and the urgency. They were unsatisfied with what they had bought. That was Gate 1.

Gate 2: Audience Definition

You cannot validate a problem against a fuzzy audience. The second gate forces you to write down — in one sentence each — three answers: who specifically experiences this problem most acutely, where they currently spend their attention, and what they would have to believe before they'd pay you.

The mistake here is talking about "small business owners" or "early-stage founders" or "Filipino entrepreneurs." Those are not audiences. Those are categories that contain hundreds of distinct audiences with different problems. The audience for HW88 Education is not "founders." It is operators between thirty-two and forty-five years old who have already shipped a product that earns money but who are running into ceiling problems because their operational discipline lags their ambition. That sentence describes maybe eight thousand people in the markets we serve, and they read different newsletters, attend different events, and use different language than the broader founder category.

If you cannot write the audience sentence specifically enough that you could name three people in your network who fit it exactly, you have not cleared Gate 2.

Gate 3: Solution Hypothesis (Not Solution)

The third gate is where most founders short-circuit the entire process. They walk in with a solution already designed. They want to validate the design. That is not validation — that is asking strangers to grade your homework.

Gate 3 asks for a solution hypothesis: a one-paragraph description of the smallest possible thing that, if it worked, would solve the problem identified in Gate 1 for the audience defined in Gate 2. The hypothesis is not a product spec. It is a bet about what the customer would value if you built it. The bet has to be falsifiable — there has to be a version of the test where the customer says no, and you accept the no.

For Mr Pet Lover, our pet-care platform, the solution hypothesis was: "If we built a curation engine that surfaced veterinary-grade product recommendations for specific pet conditions — without ads, without affiliate optimization for revenue — pet owners would pay a small monthly fee for access." The hypothesis was wrong about the price model and right about the demand for curation. We learned that in Gate 4.

Gate 4: Willingness-to-Pay Test

This is the gate most founders fail and don't realize they failed. Willingness-to-pay is not "would you use this if it existed." That question gets you a yes from anyone polite. Willingness-to-pay is "I am taking your card number right now to charge you forty-nine dollars for a thing that will exist in two weeks." Or it is a pre-order page where the call-to-action button collects payment, not email.

Three real strangers — people who have not heard of you, are not in your network, and do not owe you a favor — must complete a payment action without you talking them through it. If the conversion happens because you DM'd them on LinkedIn and walked them to the checkout page, that is sales, not validation. It is good evidence of selling skill and bad evidence of demand.

For TAPS, our autism parenting venture currently in the building stage, Gate 4 looked like this: a landing page describing the parent-coaching system, a forty-nine-dollar pre-order option for the first cohort, distribution through three parent-focused communities where the founder did not personally know the moderators, and a target of three pre-orders in fourteen days. We hit four. That cleared Gate 4.

Gate 5: Resource Reality

The fifth gate is the one most validation frameworks skip entirely, and it is the one that has saved me from launching three ventures that would have failed for non-market reasons. The question is: do you have the time, money, technical capability, and emotional bandwidth to build this for at least eighteen months given everything else on your plate?

Gate 5 is not about whether the market exists. The market exists. Gate 5 is about whether you exist for this venture, in your current life, with your current commitments, for long enough to give it a real chance.

I have killed ventures at Gate 5 that cleared the first four gates cleanly. The ideas were real. The audience was real. The willingness to pay was real. But honest accounting of my own capacity made it clear that adding a fifth active venture to the portfolio in that quarter would degrade the operational quality of the four already running. Killing a Gate-5-failure venture is not a strategic mistake. Launching it would be.

What Happens at Day 30

If all five gates clear within 30 days, the venture moves to a 90-day build sprint and receives shared resources — engineering capacity, content distribution, capital allocation. This is the path most founder-content describes as success.

What most content does not describe is what happens when the gates do not clear.

We do not pivot. Pivoting is a verb that founders use when they don't want to admit that the evidence said no. Pivoting from "this product, this audience" to "different product, different audience" is not pivoting — it is starting over, except now you have sunk costs and emotional investment biasing your thinking. We treat that as a new sprint, with a new 30 days, and we explicitly reset the gate clock.

The actual outcome at day 30 if gates haven't cleared is a resource freeze. The venture goes into a frozen state — not killed, not active. The operator can keep working on it personally if they want. They cannot draw on shared resources. They cannot ask for engineering support, capital, or distribution capacity. The freeze is enforced by removing the venture from the active resource-allocation queue, not by any kind of permission gate.

The reason a freeze beats a kill is operational. Kills create emotional damage that compounds over a portfolio. Operators who feel that failed sprints get killed start avoiding sprints. They keep working on uncertain ideas in the background, hoarding effort, never bringing things forward. Freezes preserve the option to revive a venture six months later when conditions change — and they often do change. Two of the seven ventures currently in our building stage were frozen for between four and nine months before circumstances allowed them to clear gates that previously failed.

The Mistakes Most Founders Make

I have audited validation processes for operators outside our portfolio over the last two years. The same four mistakes show up consistently.

The first is validating the solution before the problem. They build a prototype, show it to friendly users, get positive feedback, and call that validation. Positive feedback on a prototype is not signal — it is the customer being polite about your craft. Real signal comes from people committing money or time before the prototype exists.

The second is talking to warm audiences. The people in your network want you to succeed. They will say yes to almost anything you propose. Validation that comes only from your network tells you about your relationships, not about market demand.

The third is treating "no" as something to overcome rather than something to record. When a stranger says they wouldn't pay for this, founders argue. They re-pitch. They ask follow-up questions designed to extract a softer no. The job in validation is not to win — it is to count yes and no honestly. If you find yourself debating, you are no longer validating.

The fourth is what I call the rolling validation problem: founders who treat validation as something they finish, then move on. Validation is not a phase that ends. Every venture in our portfolio runs micro-validations every quarter on the next major scope decision. The 30-day sprint clears the venture for launch. After launch, the question becomes "should we add this feature, this pricing tier, this geographic expansion" — and each of those questions deserves its own small validation, not a strategic decision made on instinct.

The One Signal That Overrides Everything

If I had to pick one piece of evidence that reliably predicts venture viability — across all 16 ventures and consulting engagements I've evaluated in the last three years — it is this: a stranger pays for it without being asked twice.

Not "would pay." Not "expressed interest." Not "added to email list." Pays. With a card. Without you walking them through the checkout. Without you offering a discount to close. Without you following up after a hesitation. They saw it, they wanted it, they bought it.

When that signal is present, the other four gates almost always clear because the underlying conditions are right — the problem is real, the audience is reachable, the solution is roughly correct, and the willingness to pay exists at a price that supports a venture. When that signal is absent, the other four gates can all show green and the venture will still fail, because what's missing is the only thing that actually matters: a person, alone, deciding this is worth their money.

This is why we structure Gate 4 the way we do. Three strangers, fourteen days, payment completed without intervention. Not "leads generated." Not "signups." Not "qualified pipeline." Money in the account, from people we did not know two weeks ago.

B2B vs. B2C: Where the Framework Bends

The five gates apply to both B2B and B2C ventures. The evidence required to clear them does not look the same.

In B2B ventures, the willingness-to-pay test rarely works as a credit-card transaction. Buyers don't impulse-purchase enterprise software. The B2B equivalent of Gate 4 is a signed letter of intent or a pilot agreement with a defined deliverable and a defined payment, even if the payment is contingent on delivery. We accept three signed LOIs from three different organizations as B2B Gate 4 clearance, with one important constraint: the buyer signing the LOI must be the person who would actually pay the invoice, not a champion who needs to convince a CFO later. Champions are great. They are not buyers. Champions sign LOIs all day and then disappear when procurement gets involved.

In B2C ventures, the audience-definition gate (Gate 2) is the one that bends. B2C audiences are larger, fuzzier, and harder to write down in one sentence. The trick is to define a beachhead audience — the smallest group of people who would buy first, before anyone else — and validate against that group exclusively. Mr Pet Lover did not validate "pet owners." It validated "owners of dogs over the age of seven who have spent money on supplements in the last six months." That sentence is small enough to test against and large enough to support a venture.

The framework holds for both. The execution looks different. Founders who try to run a B2B sprint with B2C tactics — or vice versa — usually fail Gate 4 and conclude the idea was wrong. The idea may have been fine. The validation method was mismatched.

What This Costs

A complete 30-day sprint, run honestly, costs roughly forty to sixty hours of operator time and somewhere between zero and five hundred dollars in tooling and ad spend, depending on whether you need paid distribution to reach the audience for Gate 4.

That is the price of knowing. The alternative is the price of not knowing — which, in our case, before we built this framework, was a venture that ran for three months on conviction and ended with nothing to show except sunk capital and a tired team. The forty hours of disciplined sprint work is the cheapest insurance policy a venture studio can buy. We run it on every new idea, including the ones we are certain will work.

The certain-to-work ones are the ones that tend to fail Gate 1.