Bayanihan is usually cited as a cultural virtue. Taken structurally, it is a governance model for coordinated collective action without formal hierarchy — and it rests on four properties: a bounded task, division without hierarchy, reciprocity over time rather than immediate exchange, and accounting at the community level rather than between pairs. Those four properties translate directly into how ventures in a portfolio can share resources, if you take the structure seriously and abandon the romanticism.
Bayanihan is cited frequently in Philippine public discourse as a cultural virtue — proof of Filipino communal spirit, evidence of national character, a reason for collective optimism. It is cited much less frequently as a governance model, which is the more useful framing.
The bayanihan practice — neighbors coordinating to carry a bahay kubo to a new location — is a specific organizational solution to a specific problem. A single household cannot move a house. The task requires coordinated group effort. There is no market for this service in the rural community, and no institution with the authority to conscript labor. What exists instead is a set of informal governance norms that make coordinated collective action possible without formal hierarchy: the task is defined and bounded, each participant carries a specific portion, leadership emerges from competence and proximity rather than formal authority, and the expectation is not immediate exchange but reciprocity over time in a community where everyone will eventually need what they cannot accomplish alone.
These are not merely cultural virtues. They are structural governance properties — and they translate directly into how ventures in a portfolio can relate to each other in ways that conventional venture capital models do not.
Why the Conventional Portfolio Model Strains for a Single Operator
The standard mental model for a venture portfolio comes from institutional fund management: each venture is independent, capital is allocated, returns are measured separately, and ventures compete for resources within the portfolio. This model is not wrong. It is optimized for a specific situation — a fund manager accountable to external limited partners who need the portfolio to be legible, auditable, and free of cross-subsidy that would distort the measurement of any single venture's performance.
That situation does not describe a single operator running a portfolio of ventures that serve interconnected markets. When the same operator stands behind every venture, when the ventures share clients, infrastructure, and community relationships, the strict independence model imposes friction it was never designed to remove. It forces the operator to treat as arm's-length transactions the kind of cooperation that would happen naturally if the ventures were simply allowed to help each other. The conventional model's clean separation, which is a feature for a fund, becomes an overhead for an operator.
The friction is not abstract. Under strict independence, a design pattern that one venture has already built and proven cannot move to a sibling venture without being framed as a transaction — priced, invoiced, accounted for as if the two were strangers. The accounting overhead frequently exceeds the value of the thing being shared, so the sharing simply does not happen, and each venture rebuilds what the portfolio already owns. Strict independence, applied to ventures that genuinely overlap, manufactures duplication. What is missing is a governance model for cooperation between ventures that is neither the rigid independence of the fund model nor the unstructured "we're all one portfolio" sharing that collapses under its own imbalances. The bayanihan practice, read structurally, supplies exactly that — a way to let ventures help each other that is disciplined enough to survive contact with asymmetry, but light enough that the cooperation actually happens.
The Structural Properties of the Bayanihan Model
To apply the bayanihan model to venture building, the romantic version has to be set aside. The romantic version emphasizes communal spirit, shared sacrifice, and cultural cohesion. These are real, but they're the emotional experience of the model, not its operating mechanism. The operating mechanism has four specific structural properties.
Bounded collective task. Bayanihan happens around a specific task with a clear completion condition. Neighbors don't commit to vague ongoing support — they commit to moving the house. When the house is moved, the obligation is discharged. This boundedness is what makes voluntary participation possible: the cost of participation is knowable in advance, and the contribution ends at a defined point. Unlimited mutual obligations cannot be voluntarily sustained; they become coercive or they dissolve. Bounded tasks can be voluntarily taken on because the commitment is finite.
Division without hierarchy. In the actual practice, different participants carry different parts of the house — the bamboo poles, the walls, the roof — based on physical location, strength, and proximity to each component. There is a coordinator, but the coordination is about synchronization, not about directing who does what. Each person knows their portion of the load. The division is practical rather than status-based. This matters because hierarchical division of labor creates dependency: the person at the top of the hierarchy can block everyone below. Division without hierarchy means each portion can be carried independently, with coordination but not permission.
Reciprocity over time, not immediate exchange. The participant who helps move the house today does not receive something immediately in return. The exchange is deferred and non-specified: at some future point, when the helper needs something they cannot accomplish alone, the community will help. This is a significantly more flexible arrangement than a transaction, because it doesn't require the exchange to be symmetric in timing, form, or magnitude. It only requires that the community maintain the norm — that helping is expected, and that failure to help when called upon carries social cost.
Community-level accounting, not bilateral accounting. The reciprocity norm is maintained at the community level, not between specific pairs of individuals. The farmer who helps ten neighbors move houses and receives help from only three of them has not been cheated — because the obligation isn't bilateral. The obligation is to the community, and the benefit comes from the community. This distinction matters enormously for how the governance model handles imbalanced contributions over time.
How These Properties Map to Venture Portfolio Governance
Running HavenWizards 88 Ventures OPC as a multi-venture portfolio has required working through the practical question of how ventures in the portfolio relate to each other. The conventional venture portfolio model treats each venture as independent: capital is allocated, returns are measured separately, and ventures compete for resources within the portfolio. This model works for institutional fund managers because it is legible, auditable, and aligns incentives with external limited partners. For a single-operator portfolio serving interconnected markets, it produces unnecessary friction.
The bayanihan structural properties suggest a different governance model. Each of the four properties has a direct counterpart in how ventures can share resources.
Bounded resource-sharing requests. Ventures in the portfolio can make specific, bounded requests of each other — not unlimited claims on each other's resources. Bayanihan Harvest, the agricultural cooperative platform, can request capacity from the education venture for curriculum design work on cooperative governance training. That request is specific (curriculum design, bounded scope), non-hierarchical (the education venture doesn't report to Bayanihan Harvest), and generates a deferred reciprocity obligation (at some point the education venture will need something from the agricultural domain). The bounded nature of the request is what makes voluntary participation possible — each venture can assess whether the request is reasonable against its own current capacity, rather than having to defend against open-ended claims.
Division of functions without portfolio hierarchy. Each venture carries a specific portion of the portfolio's total functional capacity. One venture handles the government relationship infrastructure that benefits the whole portfolio. Another venture manages the community networks that provide market access across multiple ventures. A third provides the technology platform that creates operational efficiency for the others. These are not equal contributions — nor do they need to be. What matters is that each contribution is real, each venture knows what portion it carries, and the coordination is about synchronization rather than about subordination.
Deferred reciprocity accounting at the portfolio level. Ventures don't keep bilateral accounts with each other. The portfolio maintains a holistic account of contributions and draws: which ventures are currently net contributors (providing more to the portfolio ecosystem than they are consuming) and which are net draws (consuming more than they're currently producing). This accounting is important not for generating claims — the reciprocity norm doesn't work by creating obligations to the net contributor — but for portfolio health monitoring. A portfolio where all ventures are net draws simultaneously is either in crisis or has a design problem. The portfolio-level accounting is governance information, not a ledger for bilateral debt.
Community-level sustainability norm. The equivalent of the bayanihan community norm is a portfolio-level norm that resource sharing is expected, that free-riding is socially costly, and that ventures that extract without contributing lose standing. This is not a contractual obligation — it's a governance norm that only works if the portfolio operator is consistent about maintaining it. The norm breaks down if contributions are consistently asymmetric without acknowledgment, if draws during periods of difficulty are penalized rather than recognized as the legitimate exercise of the reciprocity norm, or if the portfolio operator exempts their most commercially successful venture from the sharing expectation because it's inconvenient.
Specific Examples from the HavenWizards 88 Ventures Portfolio
The practical application in the portfolio has produced several working examples of bayanihan-structured resource sharing. None of them is a grand cooperative scheme. Each is a specific, bounded transfer that the conventional independence model would have forced into an arm's-length arrangement or prevented entirely.
Technology infrastructure sharing. Bayanihan Harvest, as the most technically sophisticated product in the portfolio, generates architectural expertise that is directly applicable to other ventures' operational needs. When the consulting venture needed a client-facing data reporting interface, the Bayanihan Harvest technical pattern — offline-first, low-connectivity resilient, transaction-safe — provided the design starting point that saved significant development time. This was a bounded resource-sharing request (interface design pattern, not full development capacity), without hierarchy (the consulting venture didn't subordinate to Bayanihan Harvest's team), and the obligation was deferred (cooperative client relationships that the consulting venture maintains provide industry access that benefits Bayanihan Harvest's business development).
Domain expertise as portable contribution. The PCU Graduate School teaching role is not a venture in the commercial portfolio sense, but it functions within the ecosystem as a domain expertise generator that benefits the portfolio's consulting and education ventures. Course development for cooperative governance and agricultural systems creates curriculum assets that are available to the portfolio, and the teaching relationship creates professional relationships and credibility that travel across venture lines. The reciprocity works in the other direction through venture case studies that provide the real-world grounding that graduate-level applied management education requires.
Network contribution without commercial interest. Some resource sharing in the portfolio is explicitly non-commercial: providing a reference for a cooperative client's government grant application, connecting two organizations in the network because they have a shared interest, reviewing a cooperative's bylaws as a service to the sector rather than as a billable engagement. These contributions are real costs — time and credibility — and they are contributions to a community-level account, not to any specific venture's bilateral account. The expectation is that this kind of contribution to the broader ecosystem is what makes the ecosystem worth being part of.
Why the Structural Reading Outperforms the Romantic One
It is worth being explicit about what the structural reading buys that the romantic one cannot. The romantic reading — communal spirit, shared sacrifice, we're all in this together — is motivating but ungovernable. It provides no way to decide whether a specific request is reasonable, no way to recognize when contribution has gone chronically asymmetric, and no way to distinguish legitimate reliance during a hard period from extraction dressed up as solidarity. It supplies feeling without structure.
The structural reading supplies the structure. Boundedness gives every request a knowable cost and a defined endpoint, so a venture can say yes without exposing itself to open-ended obligation. Non-hierarchical division means cooperation does not require a chain of command, which is what allows distinct ventures to help each other without one becoming subordinate to another. Community-level accounting tolerates the asymmetry that real cooperation always produces, because it measures contribution against the ecosystem rather than against a counterparty. And the sustainability norm gives the operator a basis for governance action — for naming a problem and acting on it — that "we're all in this together" never could. The romance is the experience of the model working. The structure is what makes it work. Confusing the two is precisely how the model fails.
The Failure Modes When Bayanihan Is Romanticized Rather Than Structured
The most damaging way to apply the bayanihan principle to venture building is to invoke the romantic version — communal spirit, shared sacrifice, we're all in this together — without the structural properties that make the model functional. Each failure mode below is what you get when one of the four structural properties is dropped.
Unlimited obligation collapse. The most common failure is treating bayanihan-style resource sharing as unlimited mutual obligation rather than bounded collective task. When a venture can make unlimited claims on another venture's resources because "we're a portfolio," the contributing venture loses the ability to protect its own operational capacity. Unlimited obligation is not sustainable voluntarily — it requires coercion or it produces resentment and withdrawal. The structural requirement is boundedness: every resource-sharing request must be specific, scoped, and completable.
Reciprocity without community-level accounting. When resource sharing happens without explicit tracking of contributions and draws, the norm becomes invisible — and invisible norms are not enforced. Ventures that are chronic net draws don't receive social feedback because no one has named what the pattern is. The solution is not a bilateral ledger that creates transaction-style obligations, but explicit portfolio-level reporting that makes contribution patterns visible enough to be governed.
The romanticism of asymmetric contribution. The genuine bayanihan practice includes participants with different physical capacity carrying different amounts of the house — but everyone carries something. The failure mode is when the romanticized version of the model is used to justify a portfolio member that makes no contribution while drawing on the shared infrastructure: the venture that benefits from shared client relationships, shared technology, and shared credibility, while contributing nothing to the portfolio ecosystem in return. This is not bayanihan — it's extraction justified by cultural vocabulary.
Norm enforcement avoidance. The bayanihan community norm that failure to help carries social cost only works if the community is willing to impose that cost. In a venture portfolio, the portfolio operator has to be willing to name chronic asymmetry when it exists, restructure ventures that aren't contributing, and — when necessary — exit ventures that are destroying more portfolio value than they create. Avoiding this enforcement to preserve the harmony narrative hollows out the governance norm over time.
Where the Model Reaches Its Limits, and What to Try First
The bayanihan model is not a universal portfolio governance solution, and it is worth naming where it does not apply. It depends on ventures that genuinely share something — clients, infrastructure, community relationships, a single operator who stands behind all of them. A portfolio of truly unrelated ventures with no shared market and no shared operator has nothing for the reciprocity norm to circulate; for that portfolio, the conventional independence model is the right one, and importing bayanihan structure would only add ceremony. The model also depends on an operator willing to do the enforcement, because the sustainability norm has no automatic mechanism — it works only to the extent that someone maintains it. Where these conditions hold, the model produces cooperation the independence model would have suppressed. Where they don't, it produces overhead.
If the conditions do hold, the smallest version to try first is a single bounded request. Pick two ventures that already touch the same market. Have one make a specific, scoped, completable request of the other — a design pattern, a curriculum module, an introduction — with no immediate exchange and no hierarchy implied. Then write down, at the portfolio level rather than between the two ventures, who contributed and who drew. The discipline that makes this work is resisting two reflexes: the reflex to price the exchange (which converts cooperation back into a transaction and reintroduces the accounting overhead the model exists to remove), and the reflex to keep a bilateral score (which turns a community norm into a debt between two parties and breaks the asymmetry tolerance that is the model's central advantage). That single transaction, recorded at the community level rather than the bilateral one, is the entire model in miniature. You do not need to restructure a portfolio to test whether the structure works; you need one bounded request and one honest line in a portfolio-level account.
The bayanihan principle, taken structurally rather than romantically, offers a genuine alternative to conventional portfolio governance for operators working in interconnected markets where ventures share clients, infrastructure, and community relationships. The alternative requires taking the structural properties seriously — boundedness, non-hierarchical division, community-level reciprocity accounting, and genuine norm enforcement — rather than using the cultural reference as cover for unstructured resource sharing that eventually collapses under its own imbalances.
Continue in this series
This piece is part of The Indie Operator's Complete Guide to Running a Venture Portfolio, my systematic guide to venture building and modular architecture. Related reading:
- The Holding Company Architecture for Indie Operators
- The Operating Model Problem: How to Run Multiple Ventures Without Losing Control of Any
- Portfolio Governance: Running Multiple Ventures Without Losing Coherence
- Running a Venture Portfolio as a Solo Operator in the Philippines
See how this plays out in practice across my portfolio of ventures.
