RESOURCES PHILIPPINES OUTSOURCING FAQ
Outsourcing to the Philippines.
The 100 questions executives ask before they outsource to the Philippines — costs, talent, English, compliance, setup, time zones and risk — answered straight by the people who run it on the ground in Manila.
100
Questions answered
10
Topic categories
Showing 100 of 100 questions
Cost & Pricing10 questions
Does the 13th-month pay and statutory load materially change the math?
Yes — mandated 13th-month pay, SSS, PhilHealth and Pag-IBIG contributions add a meaningful, non-negotiable layer to labour cost. Reputable providers build it into the loaded rate; cheaper quotes sometimes don’t, which is a red flag that other costs are being deferred too.
— Ralf Ellspermann, CSO
How do seat-leasing and fully-managed pricing actually compare once you load everything?
Seat-leasing looks 30–40% cheaper on paper but excludes recruitment, management, QA and attrition risk — which you then absorb. Fully managed is dearer per seat but caps your operational exposure. The right answer depends on whether you have the bandwidth to run an operation 8,000 miles away.
— Ralf Ellspermann, CSO
How fast are Philippine wages inflating, and how should we structure for it?
Wage inflation has been running mid-to-high single digits annually, faster for tech and bilingual roles. Lock a transparent annual escalator tied to a published index rather than provider discretion, and revisit your location mix every two years as tier-2 cities widen the arbitrage.
— Ralf Ellspermann, CSO
How much of the headline per-agent rate is actually pass-through versus provider margin?
On a fully-loaded voice seat, roughly 55–65% is direct labour and statutory cost, 15–20% facilities and technology, and the balance is provider overhead and margin. Margins typically run 12–20%. We open up the cost stack so you negotiate on the components that are genuinely movable.
— Ralf Ellspermann, CSO
How should we benchmark a quote to know if we’re overpaying?
Compare against three things: live market rates for the exact role and shift, the provider’s own rate card for similar clients, and the implied margin once you strip out loaded labour. We run all three, because a quote only means something against a real, current benchmark.
— Ralf Ellspermann, CSO
Is gain-share or outcome-based pricing realistic here, or do providers resist it?
It’s realistic for mature, well-instrumented processes — collections, sales, retention — where the baseline is agreed and attribution is clean. Providers resist it on noisy or jointly-owned outcomes. We help structure a hybrid: a floor on FTE cost plus upside on the metric you actually care about.
— Ralf Ellspermann, CSO
What FX exposure do we carry, and who absorbs peso movement?
Most contracts price in USD, so the provider carries peso risk — but they price a buffer in. On multi-year deals, negotiate an FX band beyond which rates adjust both ways, rather than a one-sided clause. It keeps pricing honest as the peso moves.
— Ralf Ellspermann, CSO
What hidden costs most often blow up the business case after go-live?
Transition and knowledge-transfer overruns, telecom and licence pass-throughs, backfill from early attrition, and governance time on your side. None are exotic, but they’re routinely omitted from the headline. A proper total-cost-of-ownership model carries them from day one so the savings survive contact with reality.
— Ralf Ellspermann, CSO
What’s a realistic blended rate for a US-night-shift senior CX team in Manila today?
Expect roughly $1,900–2,600 fully loaded per senior agent for US graveyard hours, inclusive of the night-shift differential. Tier-2 cities run 8–12% lower. Anything quoted far below that is usually under-staffing quality assurance or team leads, which surfaces as attrition later.
— Ralf Ellspermann, CSO
Where does the arbitrage stop making sense for a given role?
When the role demands deep, scarce domain expertise or carries unbearable latency or security cost, the saving erodes. For high-judgment niche work the gap narrows to 30% and may not justify the coordination overhead. We’ll tell you when a function is better kept onshore.
— Ralf Ellspermann, CSO
Talent & Attrition10 questions
Can we realistically hire for niche skills — clinical, legal, engineering — at scale?
Yes, but it’s recruitment-led, not instant. Licensed nurses, paralegals and CAD engineers exist in volume, yet building a 50-seat specialist team takes a deliberate sourcing runway and a higher rate. We scope the realistic ramp rather than promising headcount that the market can’t actually supply that fast.
— Ralf Ellspermann, CSO
How do we keep our best people from being rotated off our account?
Contract for named team continuity and a cap on provider-initiated reassignment, with tenure and backfill SLAs. Mega-providers move talent to whoever shouts loudest, so without these clauses your trained A-players drift to bigger accounts. We build the retention terms into the deal.
— Ralf Ellspermann, CSO
How do we verify a provider’s attrition and tenure claims before signing?
Ask for account-level — not company-average — attrition, 90-day and 12-month tenure curves, and references on programs like yours. Then have us validate it on the ground. Presented numbers and operating reality diverge often enough that independent verification is the single highest-value check before you commit.
— Ralf Ellspermann, CSO
How real is the night-shift health and attrition premium for US hours?
Real and worth pricing in. Graveyard shifts carry higher health attrition and absenteeism, so good providers add wellness programs, transport and a differential. Expect to pay it. The alternative — under-supporting night teams — shows up as turnover and quality dips three to six months in.
— Ralf Ellspermann, CSO
How tight is the talent market in Manila versus the tier-2 cities?
Metro Manila is the deepest but also the most competitive and attrition-prone pool. Cebu, Davao, Clark and Iloilo offer strong talent, lower poaching and better retention, at a modest quality trade-off for the most complex roles. Spreading across cities is often the smarter resilience and retention play.
— Ralf Ellspermann, CSO
Is there genuine depth for bilingual and harder-to-staff languages?
English depth is enormous; Spanish, Japanese, Mandarin and European languages are thinner and command a premium. The pool exists but competition for it is fierce, so lead times and rates are higher. For heavy multilingual volume we often blend the Philippines with a nearshore or EU hub.
— Ralf Ellspermann, CSO
What actually drives attrition on Philippine accounts, and how is it mitigated?
Night-shift fatigue, weak team leads, no progression, and being treated as interchangeable headcount. Mitigation is unglamorous: strong front-line leadership, genuine career paths, schedule stability and account identity. Providers who invest there hold people; those who compete only on price churn them and pass the cost to you.
— Ralf Ellspermann, CSO
What attrition rate should we actually expect, and what’s best-in-class?
Industry voice attrition runs 30–60% annualised; well-run dedicated teams hold it to 15–25%, and best-in-class back-office sits below 15%. The number depends far more on management quality, career pathing and account culture than on the country. Treat a low quoted figure as a claim to verify, not a given.
— Ralf Ellspermann, CSO
What does the supervisor-to-agent ratio tell us about real quality?
A lot. Healthy spans run around 1 team lead per 12–15 agents, plus dedicated QA and training. Stretched ratios — 1 to 25 — are how providers shave cost while presenting the same rate. It’s one of the first things we audit, because thin support guarantees drift.
— Ralf Ellspermann, CSO
What’s the realistic learning curve to full productivity for a complex program?
Simple CX reaches proficiency in 4–6 weeks; complex technical, healthcare or finance roles take 10–16 weeks to full productivity. Anyone promising fully-ramped output in two weeks on a hard program is setting you up to absorb the quality gap. We plan ramp to the real curve.
— Ralf Ellspermann, CSO
Language & Culture10 questions
Can the same team flex across US, UK and AU time zones credibly?
Accent and idiom differ enough that a single pool rarely serves all three seamlessly at the top quality bar. We usually anchor each market to a calibrated sub-team. For mid-complexity support, a blended team works; for premium voice, market-specific calibration is worth the modest extra cost.
— Ralf Ellspermann, CSO
Does culture add measurable value for sales and retention, not just support?
Yes. Rapport-building converts and saves accounts, and the Filipino service orientation lifts both. We routinely see retention and upsell rates here beat colder-toned markets. For relationship-driven revenue work, the cultural fit is a performance lever, not a soft nicety — it shows up in the numbers.
— Ralf Ellspermann, CSO
How do you keep brand voice consistent across a large offshore team?
Through a documented voice guide, calibrated QA against it, and tight feedback loops — the same discipline you’d use onshore, applied rigorously. Consistency is a management artefact, not a geography one. The providers who hold brand voice are the ones who instrument and coach to it relentlessly.
— Ralf Ellspermann, CSO
How do you screen for genuine written-English quality, not just spoken?
Through work-sample testing on real chat and email scenarios, not multiple-choice grammar quizzes. Written CX exposes register, tone and clarity that interviews miss. For chat-heavy or email programs we weight this heavily, because spoken fluency and crisp business writing are genuinely different skills.
— Ralf Ellspermann, CSO
How much accent and culture training is standard, and does it actually work?
One to three weeks of accent neutralisation and culture immersion is standard, and it measurably works for US programs. The gains plateau, though — training polishes a strong baseline, it doesn’t manufacture one. We screen for the baseline first, because training can’t fully fix a poor initial fit.
— Ralf Ellspermann, CSO
How neutral are Philippine accents really for a discerning US or UK audience?
For US audiences, neutral to barely perceptible after standard accent training — which is why the country dominates US voice. For UK and Australian programs, fit is good but slightly less seamless, so we screen and calibrate harder. We can arrange live call samples on your actual use case.
— Ralf Ellspermann, CSO
How well does the workforce understand US consumer brands and idioms?
Unusually well — strong cultural exposure to US media, brands and norms means idioms, holidays and expectations land naturally. That cultural fluency is a real, under-priced advantage over markets where agents technically speak English but miss the context that makes an interaction feel native to your customer.
— Ralf Ellspermann, CSO
What cultural friction should we anticipate in management, not just on calls?
A cultural deference to hierarchy can mean bad news travels up slowly and pushback is indirect. It’s manageable once you know it: build explicit escalation norms, invite dissent directly, and don’t mistake politeness for agreement. We coach client leaders on this because it quietly derails more programs than accent ever does.
— Ralf Ellspermann, CSO
Will agents handle nuance, sarcasm and de-escalation, or just scripts?
The strength here is exactly that — emotional intelligence and rapport, not just script adherence. Filipino agents read tone and de-escalate well, which is why empathy-heavy work routes here. The variable is training and empowerment: well-coached teams improvise within guardrails; poorly-run ones retreat to scripts under pressure.
— Ralf Ellspermann, CSO
Will customers be told, or able to tell, that support is offshore?
Disclosure is your policy choice; perceptibility is largely a quality outcome. With proper screening and calibration, most US customers don’t notice. We’d caution against competing purely on concealment — the durable win is quality good enough that location stops being a concern at all.
— Ralf Ellspermann, CSO
Data & Compliance10 questions
Can the provider segregate our data and team from other clients?
Yes — dedicated teams, segregated floors, isolated systems and ring-fenced access are standard for sensitive accounts, though they cost more than a shared-services pool. If your data demands it, contract for it explicitly. We confirm the segregation is real and audited, not just asserted in the proposal.
— Ralf Ellspermann, CSO
Can we run HIPAA, PCI-DSS and SOC 2 workloads compliantly from Manila?
Yes — established providers hold HIPAA, PCI-DSS and SOC 2 attestations and run dedicated, locked-down environments for them. The control is in the operating discipline, not the postcode. We verify current attestations, scope and audit history rather than taking a logo wall at face value.
— Ralf Ellspermann, CSO
How do you handle moonlighting and insider risk with remote or hybrid agents?
Work-from-home widened this risk, so controls tightened: secured endpoints, periodic access reviews, behavioural monitoring, biometric login, and contractual anti-moonlighting terms. For high-sensitivity work we recommend on-site-only delivery. Insider risk is a program-design decision, not an afterthought — we scope it to your data’s actual sensitivity.
— Ralf Ellspermann, CSO
How do you prevent data exfiltration in a voice or back-office floor?
Layered controls: clean-desk and no-phone floors, disabled USB and print, locked-down virtual desktops, DLP monitoring, restricted access by role, and CCTV in regulated zones. For sensitive programs we insist on a physically segregated, badge-controlled space. The maturity of these controls varies widely, which is exactly what an on-site audit reveals.
— Ralf Ellspermann, CSO
How does the Philippine Data Privacy Act interact with GDPR and our obligations?
The Data Privacy Act is closely modelled on GDPR principles — consent, breach notification, a regulator with teeth — so it maps well, but it doesn’t substitute for your own GDPR duties as controller. You remain accountable; the provider is processor. We make sure the DPA and your cross-border transfer basis line up.
— Ralf Ellspermann, CSO
How mature is enforcement of the Data Privacy Act in practice?
The National Privacy Commission is active, issues guidance and pursues breaches, so compliance is taken seriously by established providers. It’s a genuine regulatory regime, not a paper one. That maturity is part of why regulated industries trust Philippine delivery — but you should still verify the specific provider’s posture.
— Ralf Ellspermann, CSO
What audit and inspection rights should we insist on?
Right to audit on reasonable notice, access to SOC 2 and penetration-test reports, breach-notification within a defined window, and the right to inspect the physical floor. Reputable providers grant these readily. Resistance to audit rights is itself diagnostic. We make sure they’re in the contract, not just the sales deck.
— Ralf Ellspermann, CSO
What does cross-border data transfer compliance actually require from us?
A lawful transfer mechanism — standard contractual clauses or equivalent — plus a data-processing agreement, a documented impact assessment for sensitive data, and demonstrable provider safeguards. It’s procedural but non-trivial. We coordinate the legal and operational pieces so the transfer basis is airtight rather than assumed.
— Ralf Ellspermann, CSO
What’s the right governance cadence to stay continuously compliant, not just at audit?
Quarterly control reviews, live access dashboards, monthly security reporting and an annual independent audit, with named accountability on both sides. Compliance decays between audits without a cadence. We help stand up the governance rhythm so issues surface early, rather than as a nasty surprise at attestation time.
— Ralf Ellspermann, CSO
Who is liable if there’s a data breach offshore — us or the provider?
As data controller you retain regulatory accountability to your customers and authorities; the provider, as processor, carries contractual liability for breaches within its control. The split must be explicit — indemnities, breach-notification windows, liability caps. Vague clauses here are where post-incident disputes live. We pressure-test them before signing.
— Ralf Ellspermann, CSO
Engagement Models10 questions
Can we start managed and convert to captive later without rebuilding?
Yes, if you structure for it upfront — a BOT or a managed contract with explicit conversion, talent-transfer and IP clauses. Retrofitting it after the fact is messy and expensive. We bake the optionality in at the start so the path to captive stays open and cheap.
— Ralf Ellspermann, CSO
Captive GCC, managed BPO, or a build-operate-transfer — how do we choose?
It turns on control, scale and time horizon. A captive maximises control but you own the build, hiring and risk. Managed BPO is fastest and lowest-overhead. BOT is the hedge — provider builds and runs it, you take it in-house once it’s proven. We model all three against your scale and appetite.
— Ralf Ellspermann, CSO
How do we avoid being a small, ignored account at a mega-provider?
Either contract for dedicated leadership, named continuity and executive sponsorship with teeth — or place the work with a strong mid-tier provider where you’re a marquee client. Being seat #9,000 at a giant means your escalations queue behind bigger logos. Our matching weighs exactly this fit, not just capability.
— Ralf Ellspermann, CSO
How does build-operate-transfer actually de-risk going captive?
The provider absorbs the hardest parts — site, licences, initial hiring, early attrition, local compliance — and runs it to a proven baseline before you take ownership on a pre-agreed timeline and price. You get a captive without the cold-start risk. The critical terms are the transfer trigger, valuation and talent-retention guarantees.
— Ralf Ellspermann, CSO
How portable is our operation if we need to switch providers?
Only as portable as your contract makes it. Insist on documented processes, owned tooling and data, knowledge-transfer obligations and reasonable exit assistance. Without those, switching costs trap you. Portability is engineered in at signing — we treat the exit terms as seriously as the pricing, because that’s where leverage actually lives.
— Ralf Ellspermann, CSO
Is a multi-sourced model worth the coordination overhead?
For large or critical operations, yes — it prevents lock-in, benchmarks providers against each other and isolates risk. For smaller scope the governance cost outweighs it. The deciding factor is whether you have the vendor-management capacity to run more than one provider well. We’re candid when you don’t.
— Ralf Ellspermann, CSO
Should the statement of work price inputs or outcomes — and how do we avoid scope creep?
Price outcomes where the metric is clean and owned; price inputs where work is jointly delivered or noisy. Either way, a tight SOW with explicit scope boundaries, a change-control mechanism and defined deliverables is what stops creep. Most disputes trace to a vague SOW — we make yours unambiguous.
— Ralf Ellspermann, CSO
What contract length balances rate leverage against flexibility?
Two to three years is the usual sweet spot — long enough to earn ramp investment and rate concessions, short enough to retain leverage. Push for break clauses tied to performance, not just calendar. Five-year lock-ins favour the provider; we negotiate the term to keep you in the stronger position.
— Ralf Ellspermann, CSO
What’s the real difference between seat-leasing and a managed operation?
Seat-leasing rents you desks, infrastructure and a shell; you run recruitment, management and quality. Managed delivers the outcome end-to-end. Seat-leasing is cheaper and suits firms with offshore management muscle; managed suits those who want a result, not an operation to run remotely. The wrong pick is a common, costly error.
— Ralf Ellspermann, CSO
When does a captive GCC actually beat a managed provider?
At large scale, with strategic or highly sensitive work, and when you want the IP and talent on your own balance sheet long-term. Below a few hundred seats the overhead rarely pays off. We run the breakeven honestly — captives are seductive and frequently the wrong answer for mid-size scope.
— Ralf Ellspermann, CSO
Setup & Ramp10 questions
Can we pilot a small team before committing to the full build?
Yes, and you should. A 10–15 seat pilot proves quality, fit and the provider’s delivery before you scale, at modest cost and risk. It’s the cheapest insurance available. We routinely structure a gated pilot with a scale-up trigger, so commitment follows evidence rather than a sales promise.
— Ralf Ellspermann, CSO
How do you handle go-live if the pilot misses the quality bar?
You don’t go live — you diagnose, remediate and re-pilot. A gated model means the bar is the gate, not the calendar. Forcing a launch over a failed pilot just relocates the failure to your customers. We’d rather slip a week than ship a quality problem at scale.
— Ralf Ellspermann, CSO
How do you protect quality during an aggressive ramp?
Gated go-lives, a held quality bar that volume can’t override, surge QA during ramp, and a willingness to slow intake if scores dip. The temptation is to chase the headcount target; the discipline is to chase the quality target and let headcount follow. We hold that line for you.
— Ralf Ellspermann, CSO
How much of our team’s time will the transition realistically consume?
More than vendors imply — expect meaningful SME and management time for knowledge transfer, calibration and governance through the first quarter. Under-resourcing your side is a leading cause of rocky launches. We scope your internal effort honestly upfront so it’s planned for, not discovered painfully in week three.
— Ralf Ellspermann, CSO
Realistically, how fast can we stand up 50 seats versus 500?
Fifty seats on a mid-complexity program: roughly 8–12 weeks to live, fully ramped a few weeks after. Five hundred: a phased 4–7 month build, because recruitment, training throughput and floor space are the real constraints. Anyone promising 500 fully-productive seats in a month is quietly planning to disappoint you.
— Ralf Ellspermann, CSO
What does a credible 8-week stand-up actually look like, stage by stage?
Weeks 1–2 discovery and system mapping; 3–4 recruitment and environment build; 5–6 training and knowledge transfer; 7 pilot and calibration; 8 controlled go-live with a parallel run. Each gate is signed off before the next. The discipline is in the gates — skipping them is how go-lives fail loudly.
— Ralf Ellspermann, CSO
What infrastructure and redundancy should be in place before go-live?
Redundant power and connectivity, a documented business-continuity plan, a secondary site or work-from-home failover, and tested data backup. Given typhoon and outage exposure, resilience isn’t optional. We verify it’s real and tested — not a paragraph in the proposal — before a single live customer is routed.
— Ralf Ellspermann, CSO
What knowledge-transfer approach actually sticks versus just documenting?
Shadowing, reverse-shadowing and hands-on calibration beat document dumps every time. Documentation is necessary but inert; people learn the process by doing it under supervision. The best transfers pair your SMEs with the offshore team through live work, not slide decks. We structure it that way because retention depends on it.
— Ralf Ellspermann, CSO
What’s a parallel run, and should we insist on one?
It’s running the offshore team alongside your existing operation before cutover, reconciling output until quality matches. Yes, insist on it for anything material — it catches gaps before customers do. The cost of a parallel run is trivial against the cost of a bad cutover. It’s non-negotiable in our playbooks.
— Ralf Ellspermann, CSO
What’s the gating constraint on ramp speed — hiring, training or infrastructure?
Usually recruitment-and-training throughput, not desks. You can only screen, hire and train quality people so fast before standards slip. Pushing the ramp faster than the training pipeline trades speed for early attrition and quality holes. We plan the curve to the pipeline, then protect it from optimistic deadlines.
— Ralf Ellspermann, CSO
Operations10 questions
How do we benchmark our offshore operation against industry, not just last month?
Against external benchmarks for your function and geography — attrition, quality, cost-per-unit, resolution — refreshed periodically, not just internal trend lines. Internal comparison flatters a mediocre baseline. We bring market benchmarks so you know whether good-for-you is actually good, and where the next improvement should come from.
— Ralf Ellspermann, CSO
How do we maintain continuous improvement rather than a flat run-rate?
Contract for it — productivity or quality improvement targets, root-cause analysis on recurring defects, and a share of efficiency gains. Without an explicit mechanism, providers stabilise and stop improving. The good ones welcome a continuous-improvement clause; the rest reveal themselves by resisting it. We make it part of the deal.
— Ralf Ellspermann, CSO
How do we verify a provider’s quality scores aren’t graded on a curve?
Calibrate against your own definition of quality, audit a sample of their scored interactions, and watch whether QA findings actually change behaviour. Self-reported scores drift generous over time. Independent calibration — yours or ours — is the only way to know the number means what you think it means.
— Ralf Ellspermann, CSO
How do you handle peak and surge without permanent over-staffing?
A blend of cross-trained flex pools, planned overtime, and a part-time or work-from-home surge bench, sized to your demand curve. Permanent staffing to peak wastes money; staffing to average fails at peak. The art is forecasting and a flex mechanism — we size both to your actual volume pattern.
— Ralf Ellspermann, CSO
How do you keep SLAs from being met on paper while CX quietly degrades?
Balance the scorecard — pair AHT and service level with CSAT, first-contact resolution and quality, and watch the trade-offs. Optimising speed alone is how providers hit SLA while wrecking experience. We design the metric set so you can’t win one number by silently losing the one that matters.
— Ralf Ellspermann, CSO
What governance cadence keeps an offshore operation honest?
Daily ops huddles, weekly performance reviews, monthly business reviews and quarterly strategic reviews, each with named owners and an action log that’s actually tracked. Cadence without follow-through is theatre. The providers who perform are the ones where last month’s actions are closed before this month’s review opens.
— Ralf Ellspermann, CSO
What utilisation and shrinkage should we expect, and what’s hidden in the gap?
Plan for 65–75% productive utilisation after shrinkage — training, coaching, breaks, leave and attrition backfill consume the rest. Quotes built on 90% utilisation are fiction that surfaces as missed SLAs. We model staffing on realistic shrinkage so your capacity plan survives the first quarter intact.
— Ralf Ellspermann, CSO
What’s the realistic span of control before quality starts slipping?
Around 1 team lead to 12–15 agents for complex work, looser for simple transactional volume, plus separate QA and training functions. Beyond that, coaching thins and drift sets in. Stretched spans are a favourite hidden cost-saver — we audit the real ratio because it predicts quality better than the rate card.
— Ralf Ellspermann, CSO
What’s the right metric set so we’re not optimising the wrong thing?
Outcome metrics first — resolution, CSAT, retention, accuracy — with efficiency metrics as constraints, not goals. Handle time is a cost lever, not a quality one. We’ve watched programs chase AHT into a churn problem. The scorecard should reward the result you actually sell, not just the cost you pay.
— Ralf Ellspermann, CSO
Who owns process documentation and improvements — us or the provider?
You should, contractually. Process IP, runbooks and improvements developed on your account belong to you, with the provider granted use during the term. Otherwise your own operating knowledge becomes a switching barrier the provider controls. We make ownership explicit so leverage and portability stay with you.
— Ralf Ellspermann, CSO
Locations10 questions
Does work-from-home weaken security and quality, and how is it controlled?
It widens both risks, controlled through secured endpoints, virtual desktops, monitoring, biometric login and stricter access governance. For sensitive work we recommend on-site-only. Hybrid works well for many programs with the right controls. The decision should follow your data sensitivity and quality bar, not the provider’s cost preference.
— Ralf Ellspermann, CSO
How concentrated is our risk if everything sits in one building?
Highly — single-building, single-city concentration is a real continuity risk for critical operations. Power, connectivity, civil disruption or a localised event can take you fully offline. We push for at least a failover site or work-from-home capability, and a city split for anything you genuinely can’t afford to lose.
— Ralf Ellspermann, CSO
How does the time-zone overlap actually work for US, UK and AU coverage?
Manila runs night shifts for live US daytime coverage, comfortable overlap with Australia, and partial overlap with the UK morning. True follow-the-sun for global 24/7 often pairs the Philippines with a nearshore or EU site. We design the coverage model around your customers’ clock, not the provider’s convenience.
— Ralf Ellspermann, CSO
How exposed are operations to typhoons and power outages, and how is it mitigated?
Real exposure — seasonal typhoons and grid instability happen. Mitigation is redundant power and connectivity, geographic split across cities, work-from-home failover and a tested continuity plan. The risk is manageable and routinely managed; the failure mode is a provider who treats BCP as a document rather than a drill we can verify.
— Ralf Ellspermann, CSO
How robust is the telecom and power infrastructure for 24/7 delivery?
In established BPO zones and major buildings, robust — redundant fibre, backup generators and enterprise-grade connectivity are standard. Quality varies by building and city, which is why the site audit matters. We verify the actual infrastructure of the actual floor, not the city’s general reputation.
— Ralf Ellspermann, CSO
Is the infrastructure ready for AI-augmented and high-bandwidth delivery?
In the major hubs, increasingly yes — bandwidth and cloud access in established zones support AI-assisted workflows and high-data operations. It’s not uniform, so for AI-heavy programs we verify the specific site’s connectivity and tooling. The leading providers are investing here precisely because the work is moving this way.
— Ralf Ellspermann, CSO
Manila versus Cebu, Davao or Clark — how should we choose a city?
Manila for the deepest pool and complex multi-skill programs; Cebu for strong quality with lower attrition; Davao and Clark for cost, retention and resilience away from the capital. Many clients split across two cities deliberately. We match the city to your role mix, risk appetite and continuity needs.
— Ralf Ellspermann, CSO
Should we split delivery across two cities for resilience, and what does it cost?
For critical operations, yes — a two-city split protects against localised disruption and concentration risk, at a modest premium in management overhead and slightly higher per-seat cost. For non-critical work it’s overkill. We weigh the continuity benefit against the cost for your specific risk tolerance.
— Ralf Ellspermann, CSO
What government incentives or zones affect where we should locate?
PEZA-accredited economic zones offer tax and operational incentives that shape provider economics and, indirectly, your rates. The relevance is mostly that established providers operate within them. We factor zone status into the cost and stability picture, though it rarely drives the city choice on its own.
— Ralf Ellspermann, CSO
What’s the real case for a tier-2 city beyond cost?
Lower poaching and attrition, stronger loyalty, less traffic disruption, and geographic risk diversification away from Metro Manila’s concentration. The cost saving is real but secondary. For retention-sensitive or resilience-critical programs, a tier-2 city is often the better operational choice, not just the cheaper one.
— Ralf Ellspermann, CSO
Labour & Statutory10 questions
Are there restrictions on data, IP or work leaving the country?
The Data Privacy Act governs cross-border data handling, and IP ownership must be explicit in contract, but there’s no blanket barrier to delivering offshore for foreign clients. The discipline is contractual — clear IP assignment and a lawful transfer basis. We make sure both are watertight rather than implied.
— Ralf Ellspermann, CSO
How does co-employment risk arise and how do we avoid it?
It arises when you direct the provider’s staff as if they were yours, blurring the employer line. Avoid it by managing through the provider’s leadership, not individual agents, and keeping direction outcome-based. We structure the operating model so control stays with you without creating an employment relationship you don’t want.
— Ralf Ellspermann, CSO
How does Philippine labour law affect our ability to scale a team down?
Separation pay and due-process requirements make workforce reduction more regulated than in at-will jurisdictions, and that risk usually sits with the provider in a managed model. It’s a reason to favour managed delivery if your volume is volatile — the provider absorbs the labour-law exposure. We make sure the contract reflects that.
— Ralf Ellspermann, CSO
How stable and business-friendly is the regulatory environment long-term?
The government actively champions the BPO sector with incentives and supportive policy, giving it long-run stability and a constructive regulatory posture. Specific rules evolve, as everywhere, but the strategic direction is firmly pro-industry. That political alignment is part of why the Philippines is a low-risk long-term bet, not just a cheap one.
— Ralf Ellspermann, CSO
How unionised is the BPO workforce, and does it create risk?
BPO unionisation is relatively limited compared with some sectors, but it exists and the legal right is protected. For most programs it’s a minor consideration; for large captives it warrants labour-relations planning. We flag where it’s genuinely relevant rather than treating it as a blanket concern.
— Ralf Ellspermann, CSO
What are the rules and costs around night-shift and holiday work?
Night-shift differential, holiday premium pay and rest-day rules are statutory and add cost to 24/7 US-hours operations. They’re built into a proper loaded rate. The relevance for you is that round-the-clock coverage genuinely costs more than a day-shift program — a quote that doesn’t reflect that is incomplete.
— Ralf Ellspermann, CSO
What happens to the team and obligations if we exit the contract?
Depends entirely on your exit terms — in managed delivery the provider retains employment obligations, but knowledge transfer, talent-retention options and wind-down support must be contracted. A clean exit is engineered, not assumed. We treat the offboarding clauses as seriously as onboarding, because that’s when leverage and continuity are tested.
— Ralf Ellspermann, CSO
What statutory costs and benefits are mandatory, and how do they affect our rate?
Mandatory 13th-month pay, SSS, PhilHealth, Pag-IBIG, holiday and night-shift differentials, and service-incentive leave — a meaningful, fixed layer on labour cost. Reputable providers load it into the rate; suspiciously cheap quotes often haven’t. It’s not optional, so a rate that ignores it is hiding cost elsewhere.
— Ralf Ellspermann, CSO
What’s the regular-employment and tenure regime we should understand?
Employees generally regularise after a probationary period, gaining stronger security of tenure, which shapes how providers hire and release. In a managed model this is the provider’s responsibility, but it influences their cost and flexibility — and yours indirectly. We translate how it affects your scaling and exit options.
— Ralf Ellspermann, CSO
Who carries employment liability in a managed model versus a captive?
In managed BPO, the provider is the legal employer and carries employment liability; in a captive, you do. That transfer of liability is a core reason managed delivery is lower-risk for many buyers. The line must be unambiguous in the contract — we make sure it is, including co-employment edge cases.
— Ralf Ellspermann, CSO
AI & The Future10 questions
Can Philippine providers credibly deliver AI data, RLHF and model evaluation work?
Yes — the country is moving up exactly this value chain, with growing capability in annotation, RLHF, evaluation and red-teaming. The English depth and judgment that suit CX transfer well to human-in-the-loop AI work. We can match you to providers genuinely building this muscle, not just rebadging support teams.
— Ralf Ellspermann, CSO
How do we avoid AI washing — providers claiming automation they don’t really have?
Demand evidence: live deflection metrics, a demo on your actual workflow, and references where the AI is in production, not pilot. AI is the new buzzword on every deck. We separate the providers genuinely operating it from those gesturing at it, because the cost case depends on which is true.
— Ralf Ellspermann, CSO
How do we future-proof a delivery strategy as AI reshapes the model?
Favour flexible contracts, portable tooling and data, a provider investing in AI-augmented delivery, and a commercial model that rewards productivity. Rigid, headcount-locked, long-term deals are the thing to avoid. We build a strategy that bends with the technology rather than betting on a snapshot of how the work looks today.
— Ralf Ellspermann, CSO
How do we keep humans-in-the-loop quality high as AI takes the front line?
By treating review as skilled work — calibrated QA on AI outputs, trained reviewers who own the final answer, and feedback loops that improve the model. AI makes errors faster and more confident, so the human gate matters more, not less. We design the review discipline so quality scales with automation.
— Ralf Ellspermann, CSO
How is AI changing the pricing model, and will per-seat still make sense?
AI deflects routine volume, so pure per-seat pricing is giving way to blended models — fewer agents on higher-value work, plus outcome and consumption components. The cost-per-contact falls even as per-agent value rises. We help restructure commercials so you capture the AI saving rather than the provider keeping it.
— Ralf Ellspermann, CSO
How should we structure a contract to capture AI productivity gains, not the provider?
Build in productivity-share clauses, declining unit costs as automation matures, and transparency on deflection rates. Without them, the provider banks the AI saving while you pay the old rate. We’ve seen both outcomes — the difference is entirely in how the commercial mechanism is written. We write it in your favour.
— Ralf Ellspermann, CSO
If AI handles the easy tickets, are we left paying premium rates for only hard ones?
That’s the real shift — automation removes the cheap volume, leaving complex, judgment-heavy work that costs more per contact but less in total. The trap is a contract still priced for the old mix. We renegotiate the model so your blended cost reflects the new, harder-but-smaller workload.
— Ralf Ellspermann, CSO
Is it better to bring AI tooling ourselves or use the provider’s stack?
Depends on control and portability. Your own stack keeps the IP, data and switching freedom with you; the provider’s is faster to deploy but can become a lock-in. For strategic programs we lean toward client-owned tooling with provider operation. We weigh speed against the leverage you’d be giving away.
— Ralf Ellspermann, CSO
What work is safe to automate now versus still genuinely needs people?
Routine, high-volume, rules-based contacts automate well today; nuanced, emotional, ambiguous or high-stakes work still needs people, often AI-assisted. The line moves yearly. We help you sequence automation so you capture the easy wins without degrading the interactions where human judgment is still the product you’re selling.
— Ralf Ellspermann, CSO
Will offshore headcount shrink, and what does that mean for our cost trajectory?
Headcount on routine work shrinks while higher-value roles grow, so total cost-per-outcome falls even as average per-seat value rises. The trajectory is favourable if your contract captures it. The risk is paying yesterday’s headcount-based price for tomorrow’s automated reality — which is precisely what we restructure against.
— Ralf Ellspermann, CSO
No questions match that search.
Try a different keyword or clear your filters.
FROM TERMS TO A SHORTLIST
Know the terms. Now scope the work.
Tell us the model, geographies and compliance frameworks you need and we’ll return a vetted, best-fit supplier shortlist — free and with no obligation.