Growing Operators, Not Just Employees: The HavenWizards Talent Model
The BPO-shaped definition of Filipino talent — reliable, process-following, task-completing — undersells what Filipino operators can actually do when given genuine ownership and documented systems to work within. We have built a small team that runs eight ventures simultaneously. Here is what that talent model actually looks like.
Author: Diosh Lequiron, PhD, MBA, CSM | Last updated: 2026-05-12
The BPO Model Is Not the Only Model
Most international founders hiring Filipino talent import a BPO mental model: hire for a defined role, give detailed instructions, monitor output against task completion. This works for BPO work. It does not work for venture operations.
Venture work requires judgment under ambiguity, prioritization without complete information, and ownership of outcomes rather than tasks. BPO-trained operators have been systematically trained away from these behaviors — because in BPO work, judgment deviations from script are errors, not assets.
When we started building our team, we made the mistake of hiring excellent BPO-profile candidates and expecting them to operate with venture-level judgment. The first three hires were technically competent and completely unable to make decisions without explicit instruction. We spent more time writing instructions than they spent executing them.
We rebuilt our hiring and development model around a different profile entirely.
What We Mean by Operator vs. Employee
An employee executes a defined task. An operator owns a defined outcome.
The difference shows up in how they respond to blockers. An employee facing a blocker waits for instruction. An operator facing a blocker documents the blocker, proposes two or three solutions with their recommendation, and flags it for decision — then executes the moment they have a response.
This behavior is not natural for most people new to venture work. It is developed through explicit expectation-setting, feedback, and graduated ownership.
Our hiring criterion is not "does this person already operate this way?" It is "does this person's learning pattern suggest they can develop this way?" The distinction matters because genuine operators who already operate at this level are rare and expensive. Operators-in-development who are coachable are more accessible and, when developed correctly, produce equivalent outcomes.
The Build Pods Model
We organize our team into what we call Build Pods — small groups of 2–3 operators each responsible for a specific venture or venture cluster. Each pod has:
- A Lead Operator: responsible for the venture's daily operations, stakeholder communication, and first-level decision-making
- A Systems Operator: responsible for the automation stack serving that venture — building, maintaining, and improving the n8n and Make.com workflows
- A Content or Delivery Operator (venture-dependent): responsible for the specific output of that venture, whether that is content production, training delivery, or customer success
Each pod operates with documented systems rather than supervisor instruction. If the systems are documented correctly, the pod can run for weeks without founder involvement.
This is the practical alternative to BPO-model management: not less oversight through trust, but less oversight through documentation and automation that makes founder oversight unnecessary for routine operations.
How We Develop Operators in Practice
Operator development follows a four-stage progression:
Stage 1 — Process Execution (Weeks 1–4)
New operators follow documented processes exactly as written. No deviation. This stage is about building trust in the documentation — learning that the system works, that the documentation is accurate, and that following it produces good outcomes.
We do not give creative freedom at Stage 1. It produces inconsistent output and confuses the new hire about what good looks like.
Stage 2 — Process Improvement (Weeks 5–12)
At Stage 2, operators are expected to identify gaps in the documentation. Every week they submit one improvement suggestion — either a step that could be clearer, an automation that would remove manual effort, or a case the documentation does not cover.
This is not optional. An operator who has been executing a process for 4 weeks with no improvement suggestions is not fully engaged with the work — they are performing compliance rather than developing ownership.
Stage 3 — Process Ownership (Months 3–6)
Stage 3 operators write and maintain documentation for their own process areas. When something new happens in their venture, they document how it was handled and update the playbook.
This shift — from following documentation to creating it — is the transition from employee to operator. It is also where most development programs fail: they treat documentation as a management responsibility rather than an operator responsibility.
Stage 4 — Venture Stewardship (Month 6+)
Stage 4 operators run their venture pod with minimal founder involvement for routine operations. They escalate decision-points that require founder judgment, but they identify and surface those escalation needs proactively rather than waiting to be asked.
Less than half of operators reach Stage 4. This is not a failure — Stage 2 and 3 operators run most of our daily operations effectively. Stage 4 is a threshold for operators we invest in for longer-term leadership development.
What DOLE Compliance Means for This Model
The Build Pods model does not eliminate DOLE compliance requirements — it makes them cleaner to implement.
Each operator has a clear employment classification: regular employee with documented roles, performance standards, and a 6-month probationary period per Labor Code standards. The venture pod structure does not create ambiguity about who is employed by whom — all operators are employed under the HavenWizards 88 Ventures OPC entity.
When we have contractors rather than employees — for project-based system builds, for example — we use proper service agreements with deliverable-based payment rather than time-based arrangements that could create employer-employee relationship ambiguity.
We have not had a labor compliance issue in our operations. The documentation culture that underpins our operator model also makes compliance documentation straightforward.
The Philippine Talent Market in Practice
Finding operators rather than BPO-profile employees in the Philippine market requires different search channels.
Where we find operator-profile candidates:
- Former startup employees who chose to exit corporate or BPO careers
- Self-taught freelancers who have been managing client accounts independently
- University graduates from entrepreneurship programs who have built something, even small-scale
Where we do not find operator-profile candidates:
- High-volume BPO recruitment channels
- Job postings emphasizing task compliance and process-following
The interview signal we look for: "Tell me about a time you identified a problem your manager did not know existed and fixed it." Operators have multiple concrete answers. Employee-profile candidates describe situations where they reported a problem and waited for instruction.
Implementation: Building Your Operator Development System
- Write your processes before you hire — operators cannot own what is not documented. The documentation is the operating system; the operator runs it.
- Stage your autonomy explicitly — tell new hires which stage they are in and what the criteria are for advancement. Ambiguity here produces confusion, not judgment development.
- Make documentation contribution mandatory — weekly improvement suggestions are not optional at Stage 2. Set the expectation in week 1.
- Separate employment and contractor arrangements clearly — DOLE requirements apply to the substance of the relationship, not the label. Document both clearly.
- Hire for learning pattern, not current behavior — operators are developed, not found fully formed
FAQ
How many operators does it take to run a Philippine venture at the early stage? One to two operators at early stage with strong automation coverage. A venture with a complete n8n and Make.com automation stack for customer communications, lead handling, and delivery can run with a single part-time operator at validation stage. Adding a second operator for delivery and customer success unlocks the ability to run two ventures simultaneously from one founder.
How do you retain good operators in the Philippine market? Beyond compensation (which needs to be at or above market rate — below-market retention strategies do not work), the primary retention factor in our team is genuine ownership and advancement clarity. Operators who know what Stage 4 looks like and have a documented path to get there stay longer than operators in undefined "growth opportunity" roles.
What is the difference between your Build Pods model and a traditional Filipino VA arrangement? VA arrangements are task-based: you give instructions, the VA executes, you review. Build Pods are outcome-based: the pod owns the venture's operational results. The accountability structure is different, the documentation requirements are higher, and the capability ceiling is significantly higher. A VA arrangement scales by adding more VAs. A Build Pod scales by advancing operators to higher stages of autonomy.