Skip to main content
HW88
  • Our StoryTeamFounder
  • Ventures
  • Learn
  • CapabilitiesBuild PodsEngagement
  • Insights
  • Case Studies
  • Our StoryTeamFounder
  • Ventures
  • Learn
  • CapabilitiesBuild PodsEngagement
  • Insights
  • Case Studies
  • Contact
HavenWizards88

Venture Studio for high-stakes founders. We build and automate entire ecosystems for global scale.

Company

  • About Us
  • Team
  • Ventures
  • Case Studies
  • Learn
  • Insights
  • Media
  • Build Log

Services

  • Capabilities
  • Build Pods
  • Strategic Advisory
  • Technology Development
  • Growth Acceleration
  • FAQ

Legal

  • Privacy Policy
  • Terms of Service
  • Cookie Policy

© 2026 HavenWizards 88 Ventures OPC. All rights reserved.

Makati City, Philippines

  1. Home
  2. /Insights
  3. /Venture Sunset Criteria: When We Pause a Build
←Back to PlaybooksPLAYBOOK

Venture Sunset Criteria: When We Pause a Build

Pausing a venture is a discipline, not a defeat. Pretending a stalled venture is still working is the failure mode that costs the most.

D
Diosh
May 2, 2026 · 4 min read
playbookventure-sunsetportfolio-disciplineventuresexecution
Share

We have paused ventures. Quietly, deliberately, without writing a "lessons learned" Medium post. The criteria we use are practical — and they have prevented a worse outcome more than once. The sunset decision is not about giving up; it is about refusing to spend the next twelve months funding a venture that the previous three have already told us is not working.

Most operators do not have written sunset criteria. The result is portfolios that drift. Ours are below.

Key Takeaway

Pause when validation has not arrived by Day 30, when unit economics cannot close, or when founder capacity cannot sustain the operating rhythm. Pretending is the failure that costs the most.

The Problem

A venture rarely fails on a single day. It fails by degrees, with each degree easier to ignore than the previous one. A founder''s belief in the venture lasts longer than the evidence does. Without written criteria, the call to pause never gets made — until the venture has consumed enough capital and attention that pausing it is now expensive in its own right.

The criteria below are how we keep the call cheap.

The Framework

01 Validation by Day 30

What we look for:

  • A paying customer (or a written letter of intent) within the first 30 days
  • The validation is for the actual offer, not a watered-down version
  • The customer''s reason matches the thesis the venture was built around

Why it matters:

Day 30 is the discipline. If validation has not arrived in 30 days, the venture pauses — not killed, paused. Documentation feeds the next attempt. Bayanihan Harvest''s first revenue stream was validated in under three weeks by running the operation manually before any platform existed. Validation is cheap when the founder is willing to accept its absence.

02 Unit Economics Cannot Close

What we look for:

  • A modeled path to positive contribution margin within 18 months
  • Channel CAC measured in real spend, not estimated
  • A retention curve that supports the LTV the model assumes

Why it matters:

A venture with no path to closed unit economics is a hobby. The 18-month window is generous; ventures that cannot model the path are not asked to model harder — they are paused. We refuse to operate ventures whose math depends on assumptions we cannot test. The portfolio''s 60+ deployed systems all earned their spot by clearing this bar.

03 Founder Capacity Cannot Sustain

What we look for:

  • The founder can run the operating rhythm — daily, weekly, monthly — without burning out the rest of their portfolio
  • Energy is going into the venture, not into avoiding the venture
  • The founder is the right shape for the venture, not just the available shape

Why it matters:

This is the criterion most operators skip and most regret skipping. A venture that requires the founder to be someone they are not is a slow failure. Capacity is a real constraint; pretending it is unlimited is how multi-venture portfolios collapse from the inside. The pause protocol protects the rest of the portfolio more than it protects any single venture.

Implementation Checklist

  • Set the Day-30 validation gate before launch
  • Model the unit-economics path explicitly; if you cannot, pause
  • Track founder capacity as a real input, not as goodwill
  • Document the pause decision and what it teaches the next attempt
  • Reallocate the capital and attention quickly — drift is the enemy

What This Produces

  • A portfolio that does not drift on stalled ventures
  • A pause protocol that protects active ventures from leaking attention
  • A documented record that makes the next venture cheaper

Common Mistakes

  1. Pretending the venture is still working. The most expensive mistake. The signs were there at month four; the pause does not happen until month fourteen.
  2. Killing without documenting. A paused venture without a written record is the same lesson waiting to be re-paid in the next venture.
  3. Treating pause as defeat. Pause is a return decision, not a moral verdict. Operators who confuse the two are the operators whose portfolios collapse.

Next Steps

If your portfolio includes a venture you suspect should pause, our free training walks the decision rubric. To see ventures that cleared the criteria, the portfolio is the proof.


Arena-forged across 8 venture lines, with paused ventures off the public roster. See Bayanihan Harvest for the kind of validation the criteria are designed to demand.

THE ARSENAL IN ACTION

Systems Thinking, Applied

Explore the capabilities behind our playbooks.

HW-Automate

Automation principles we use to eliminate ops drag, reduce handoffs, and keep teams lean without slowing delivery.

8 playbooksRead Playbooks

HW-Insights

Data and analytics thinking from our ventures, including how we instrument decisions and spot growth inflection points.

5 playbooksRead Playbooks

HW-Scale

Infrastructure patterns that grow without complexity, with playbooks on reliability, ownership, and cost control.

6 playbooksRead Playbooks
D

Diosh

President & CEO, HavenWizards 88 Ventures

Building arena-forged execution systems and deploying governed Filipino talent across multiple venture lines. Every insight comes from real operations, not theory.

Related Playbooks

PLAYBOOK

The Multi-Venture Operating Rhythm: Daily, Weekly, Monthly

Running 8 ventures in parallel does not require working harder. It requires a rhythm — daily, weekly, monthly — that the calendar enforces, not the founder. The cadence behind the HavenWizards portfolio.

4 min read
PLAYBOOK

Governed Execution Defined: SOP + QA + Ownership

Governed Execution is a named term at HavenWizards. It has a structural definition: SOP (process outside the person) + QA (a reviewer who is not the builder) + ownership (a lead who carries the metric). All three are required.

5 min read
PLAYBOOK

Cost Discipline: The Spending We Refuse to Make

Three categories of spending HavenWizards refuses across 8 venture lines: tools that need GPU but run on CPU, headcount before outcome ownership, and vanity marketing before validation. The refusals matter more than the approvals.

4 min read

Get the Founder's Briefing

A bi-weekly, no-fluff dispatch of the systems, playbooks, and decisions we are using right now inside our ventures and partner builds. Expect short, tactical notes you can apply in the same week.

Join 2,000+ founders and operators.

No spam. Unsubscribe anytime.