MVP to Market in 90 Days: How We Validate New Philippine Ventures

Our 90-day validation framework is not a timeline goal. It is a forcing function. If a Philippine venture cannot demonstrate a path to cost coverage in 90 days, the assumptions behind it are wrong — and discovering that at month 3 is far better than discovering it at month 12 after significant investment.

Author: Diosh Lequiron, PhD, MBA, CSM | Last updated: 2026-05-12

Why 90 Days as the Window

Philippine market validation cycles are compressed compared to Western markets. Consumer purchase decisions here are often social and faster-moving. Business purchasing decisions, while slower due to approval cycles, still resolve within 30–60 days for most SME buyers.

A founder who cannot generate 10 paying customers in 90 days in this market is not facing a timing problem — they are facing a positioning, pricing, or product problem that more time will not solve.

We have run this process eight times across our ventures. The ventures that showed early traction (5+ paying customers by day 45) all reached sustainable unit economics within 6 months. The ventures that struggled past day 60 to find their first 5 customers never recovered without significant pivots.

The 90-Day Framework: Week by Week

Days 1–14: Define and Pre-Sell

The first two weeks are not about building. They are about validating demand.

We write a one-page venture definition: the specific problem, the specific buyer, the specific outcome we promise, and the price point. This goes to 30–50 people in our professional network with a simple ask: "Would you pay this for this outcome? If yes, here is how to reserve your founding-cohort spot."

Our target: 10 reservations at 30% discount off intended price within 14 days.

If we reach 10, we build. If we do not, we rewrite the positioning and try once more. Two failed pre-sales means the venture idea needs fundamental rethinking, not another iteration.

By the end of Week 2 for Bayanihan Harvest's first product offering, we had 14 pre-sales. That number told us more than three months of market research would have.

Days 15–45: Build the Minimum Viable Product

The MVP covers exactly what we promised in the pre-sale. Nothing more.

For digital products: the core content modules, delivery automation via n8n, and a Supabase-backed enrollment system. For service-based ventures: a documented delivery process, communication templates, and a tracking system.

What we deliberately exclude from the MVP: onboarding polish, advanced features requested by potential users who did not pre-pay, and anything that requires more than 30 days of additional development.

Our first attempt at an MVP for one of our edtech ventures included a feature set that took 90 days to build. We were so focused on building the right product that we forgot to validate it. By the time we launched, two of our pre-sale buyers had moved on. We rebuilt the next venture's MVP in 28 days with half the features and launched to better outcomes.

Days 46–75: First Cohort Delivery and Signal Collection

The first cohort gets the MVP. We watch four things:

Completion rate: For course products, completion below 40% indicates value delivery failure, not learner motivation failure. We own the completion rate problem.

Support volume by type: Questions about navigation or access are product friction problems. Questions about applying the content are content gaps. We categorize every support request in week 1.

Referral behavior at day 14: Any unprompted mentions of the product to colleagues are logged. This is our earliest PMF signal.

Payment conversion for the standard-priced second cohort: If founding cohort members recommend the product to peers who convert at full price, we have positive price-to-value evidence.

Days 76–90: Decision Point

By day 76, we have 4–6 weeks of cohort data. The decision is binary: continue and scale, or pivot.

The pivot decision is made on evidence, not optimism. If completion rates are below 40%, referral behavior is absent, and second-cohort conversion is below 20%, we are not looking at a timing problem — we are looking at a product-market fit problem that requires a fundamental change.

What We Changed After Failing This Framework Once

In 2024, we ran a venture through this framework but violated one rule: we extended the Day 90 decision point by 30 days because we believed the market needed more time to warm up.

It did not. We spent 30 additional days hoping data would improve. It did not improve. We pivoted the venture at day 120 that should have pivoted at day 90.

The lesson: the framework only works if you honor the decision point. Extensions are rationalizations in disguise.

The Automation That Makes 90 Days Feasible

Running an MVP launch without an automation stack requires more operator hours than 90 days can sustain alongside other ventures. Our automation layer reduces the manual workload enough that one founder can run a new venture validation in parallel with existing operations.

• Lead capture to CRM: n8n captures pre-sale form submissions and adds them to our pipeline automatically
• Cohort communications: Make.com triggers the entire welcome and onboarding sequence for new enrollments
• Progress tracking: Supabase stores completion checkpoints; n8n alerts us when completion rate drops below threshold
• Referral tracking: Unique enrollment links per referrer track conversion without asking buyers to self-report

Without this stack, 90-day validation while running seven other ventures would require full-time support staff for each launch. With it, one operator manages the process part-time.

Implementation: The 90-Day Validation Checklist

Before Day 1:

• Written venture definition (problem, buyer, outcome, price)
• Pre-sale offer ready to send to 30–50 network contacts

Day 14 Gate: 10 pre-sales or fundamental rethink

Day 45 Gate: MVP complete and delivered to founding cohort

Day 76 Review: Completion rate, referral signals, second-cohort conversion data reviewed

Day 90 Decision: Continue and scale or pivot — no extensions

FAQ

What counts as a valid pre-sale for Philippine ventures? A payment. Not a "yes, I would buy this." Not a waitlist signup. Actual money collected at 30% discount for delivery within 60 days. Verbal commitments from people in your network are not validation — they are politeness.

How do you handle the 90-day framework for ventures that require regulatory approval? For regulated ventures in the Philippines — fintech, food, health — build the regulatory timeline into your validation separately. You can still run pre-sales and cohort delivery in parallel with regulatory work if your MVP does not require full regulatory clearance for pilot delivery. Know your specific regulatory requirements early and do not let them become a reason to extend product validation timelines.

What is the minimum team to run a 90-day Philippine venture validation? One founder with a clear process and automation tools. We have validated ventures as single-founder operations. The constraint is not headcount — it is process clarity and automation coverage for repetitive delivery tasks.