IT-BPM industry

How it works

IBPAP is the trade group. Voice and non-voice, GCCs, and captives live here. Dedicated remote hires are downstream of this machine even when they never badge into a park. AI is already bending long-range headcount targets; near-term seats still exist. For a U.S. company hiring one Filipino teammate, write this into the brief, the employment contract, and the peso payroll file before the start date. Slack habits do not override the Labor Code, BIR, or NPC. If the local employer of record holds the paper, they run the statutory step; you still owe a clean operating definition so the seat does not fail in week three. Put a number on the example when you budget loaded cost, because a nameless allowance always returns as a December surprise or a missed SLA.

Example: 2024-2025 reporting: about 1.82-1.89 million headcount and roughly $38-40B revenue, U.S. still the main buyer. Use as scale, not as your headcount plan.

How it differs

IBPAP is the voice. Voice vs non-voice is the split. BPO vs dedicated hire is how you buy from this world.

Common errors

Treating industry headcount as a personal inventory.

In practice

Treat IT-BPM industry as a week-one operating object. Use the sector fact as context for a slate, not as proof about one person. Headcount in the millions does not staff your Tuesday. Write an owner - founder, local employer, or worker - and a date you will look at it again: first cutoff, first holiday, or first miss. If nobody can show a contract clause, a payslip line, a calendar block, or a checklist box, you do not have it-bpm industry yet. You have a conversation. Convert the conversation before the person starts, while changing the deal still costs a paragraph rather than a resignation. Re-read the worked example above against the actual hire in front of you. If the numbers in that example cannot be swapped for this seat’s pesos, hours, and start date, the brief is still unfinished.