Most founders think they're hiring a team. They're actually buying a compliance structure. BPO is designed for high-volume, process-defined work where outputs are interchangeable. If you need someone to process invoices or handle tier-1 support at scale, BPO is the right model. If you need someone who can figure out what to build next, run experiments, and own the outcome — you need something different.
By Diosh Lequiron, PhD, MBA, CSM — President & CEO, HavenWizards 88 Ventures OPC Last updated: May 9, 2026
What BPO Is Actually Designed For
Business Process Outsourcing is a procurement model. It was designed to take a defined, repeatable business process and move it to a lower-cost provider without degrading the output quality.
The model works well when:
- The process is fully documented
- Success is measurable (tickets closed, invoices processed, calls handled)
- The work doesn't require judgment — only execution of predefined steps
- Scale matters more than speed of learning
Philippine BPO is a legitimate industry serving real business needs. The Philippines processes a significant portion of the world's customer service, back-office finance, and data management work. The infrastructure exists, the talent is real, and the value proposition is well-understood.
The problem is when founders apply this model to work that isn't BPO.
What Execution Teams Are Actually Designed For
An execution team — what we call a Build Pod at HavenWizards 88 — is a different structure. The difference is in what's being purchased.
BPO model:
- You define the process
- They execute the process
- Success = process compliance and volume
Execution team model:
- You define the outcome
- They figure out the process and execute it
- Success = outcome achieved
This seems like a subtle distinction. It isn't. It determines:
- Whether you get headcount or results
- Whether your team improvises when something breaks or waits for instructions
- Whether your product gets better when your team learns something new
What a Build Pod Looks Like in Practice
At HavenWizards 88, our Build Pods are small, cross-functional teams (typically 3-5 operators) embedded in a single venture for a fixed period. They ship, they measure, they adjust.
A Build Pod working in Bayanihan Harvest (our agritech platform) doesn't wait for us to define every task. They own the farmer onboarding flow. When a bottleneck appears — farmers dropping off at step 3 of registration — they diagnose it, propose a fix, test it, and report the outcome. That's not what a BPO contract buys you.
The Accountability Inversion
The most telling structural difference: in a BPO engagement, the founder absorbs the system design risk. You design the process, they execute it. If the process is wrong, that's your problem.
In an execution team model, the team absorbs execution risk. You define the goal — "reduce farmer registration drop-off from 42% to under 20% by quarter end." How they get there is theirs to figure out.
This inversion is why execution teams are more expensive per headcount and why they compound over time. A BPO team gets better at your defined process. An execution team gets better at achieving your class of outcome.
When to Use BPO (Honest Assessment)
We are a venture studio with execution teams. We are also honest: BPO is the right answer for some problems.
Use BPO when:
- You have a high-volume, fully-documented, repeatable process
- Quality is defined by SLA compliance, not creative output
- The work is genuinely interchangeable (any trained person produces the same output)
- You need scale quickly and the process design is locked
Use an execution team when:
- The process isn't fully known yet (you're building, not operating)
- Success requires judgment, not just execution
- Learning and adaptation matter as much as throughput
- You need someone who will tell you when the plan is wrong
The mistake founders make is applying BPO to the second category because it's cheaper per hour. It costs more in outcomes.
The Philippine Talent Advantage (and What It Isn't)
Filipino operators bring specific advantages that make them effective execution team members — not just BPO workers:
- English fluency at native or near-native levels (the Philippines has 90M+ English speakers)
- Strong process orientation combined with relational intelligence (useful when work involves clients or stakeholders)
- Cultural familiarity with global brands, platforms, and startup operating styles
- Time zone overlap with both Asia and early US mornings
What Filipino execution team members are NOT: cheaper versions of US/EU team members doing identical work. When operators are treated as interchangeable, you get BPO performance regardless of the contract type.
The HW88 Build Pod model works because we embed operators into ventures with real ownership — not task lists. The outcome improvement comes from that ownership structure, not from the Filipino talent alone.
Frequently Asked Questions
Is there a cost difference between BPO and execution teams? Yes. BPO is typically priced on headcount and hours (₱20,000-40,000/month per full-time equivalent in the Philippines). Build Pod arrangements are priced on outcome delivery — typically higher per operator, but with a defined deliverable (a launched feature, a reduced funnel drop-off, an automation system deployed). The ROI comparison requires accounting for what actually gets done.
Can I transition a BPO arrangement into an execution team? Sometimes. It requires changing what the team is accountable for — from process compliance to outcomes. Many BPO-trained operators can make this shift given time and the right incentive structure. The harder change is on the founder side: letting go of process control in exchange for outcome ownership.
What's the minimum team size for a Build Pod? Our smallest Build Pods are 2 operators + 1 technical lead (for development-focused ventures). For pure operations, a single senior operator with execution ownership can function as a pod when the scope is narrow. Below that, you're in freelancer territory — which is a different model again.
Are Build Pods available for non-Philippine ventures? Yes. HW88 Build Pods serve international founders seeking Philippine execution talent. The team members are Filipino; the ventures they support are global.
Related Reading
AI Automation for Philippine Startups → — how our execution teams use 60+ automation systems to eliminate the work that doesn't require human judgment.
Explore Build Pods → — structure, pricing, and engagement models.
Diosh Lequiron is the founder of HavenWizards 88 Ventures OPC. He holds a PhD, MBA, and CSM and has operated Build Pods across agritech, e-commerce, edtech, pettech, and fintech ventures. View the full portfolio →