A mid-market CX leader builds the customer-operations shortlist. The brief lands with the CIO and the COO. Two names come up in the first round of evaluation: Teleperformance, the global enterprise BPO most often associated with the category, and Invictus, the nearshore customer-operations company headquartered in Belmopan, Belize. The procurement question is real, but the deciding factor sits a layer underneath. Both are credible partners. The choice is which operating model fits the scope of work on the table.

This page lays out how the two compare on operating profile and where each scope fits best.

The Teleperformance profile

Teleperformance is a global enterprise BPO with a footprint that spans dozens of countries, broad language coverage across both nearshore and offshore delivery hubs, and established Fortune-scale relationships across most major verticals. The company sits among the largest customer-experience operators in the world by headcount and is built around an offshore-blended delivery model that gives its largest customers access to large-scale labor pools and a broad service portfolio across customer care, technical support, sales, collections, and trust-and-safety work.

The strength of that footprint is the breadth. A multinational enterprise that needs contact-center coverage across many time zones, regulatory environments, and language pairs at once gets that breadth handed to it on day one.

The Invictus profile

Invictus is a nearshore customer-operations company founded in 2012, headquartered in Belmopan, Belize. The business operates two complementary disciplines that share an operating model: a proprietary platform called iKunnect that unifies contact center, CRM, and multilingual AI in a single system of record, and a nearshore BPO that runs contact-center and back-office operations for clients across industries. Clients engage Invictus on either side independently or on both together.

Several details define what makes that model distinct in practice:

Unified system of record. iKunnect carries the contact-center layer (voice, chat, email, SMS, voicemail), the CRM and ticketing layer, and the multilingual AI layer in one platform with one database. There is no CRM-to-call-center handoff and no integration lag. Agent screens load the customer's full history at the moment of contact.
Multilingual coverage at dialect granularity. Real-time bidirectional voice and text translation across 150+ languages through an integrated OneMeta partnership (VerbumAgentis and VerbumSDK). Regional dialect coverage on Spanish (Cuban, Venezuelan, Mexican, Castilian) is in production, not on a roadmap.
Regrettable attrition under 4% on a trailing 12-month basis, against a 60%+ industry attrition baseline. Average agent tenure is 2.8 years. The agents handling a customer's contacts in month 18 of a program are largely the same agents who handled them in month 6.
Outcome-based pricing on offer where the operation supports it. Per-seat, per-interaction, and outcome-based pricing all available depending on the engagement shape. Outcome-based is reserved for operations with a clean, measurable business result (a defined volume of documents processed at a defined accuracy bar, a defined appointment-confirmed rate).
Vertical practice leads sit alongside operating teams. A supervisor making a real-time call on a healthcare contact has direct access to the healthcare practice lead, not a layer of generic management above them.

The operating base is two flight hours from most major US business hubs. When something needs hands on the ground, a leadership site visit can happen the same day.

Where each scope fits

The two names appear together on shortlists because both deliver customer operations. The deciding factor is the shape of the work.

A Teleperformance-shape engagement typically looks like:

Transactional volume distributed across many time zones and languages, where global coverage is the price of entry.
Account-level work where seat rate is the dominant cost lever and the program is sized in thousands of seats.
Offshore-blended delivery where the operating arithmetic depends on labor-cost arbitrage at the enterprise's largest scale.
Programs inside multinational enterprises with established procurement relationships across multiple geographies.

An Invictus-shape engagement typically looks like:

Mid-market scope where executive attention is part of the deliverable, and the buyer expects to talk to operating leadership rather than an account-management layer.
Revenue-line operations where the work compounds into the customer's top-line, not just into a cost-line. Outcome-based pricing fits cleanly here.
Multilingual quality at the dialect level, where a Venezuelan Spanish speaker on a healthcare appointment line should not be routed to a generic Spanish queue.
Contract sizes where the operations team can wire directly into Invictus's senior operating bench, and where the unified platform plus the BPO labor compose into one operating picture.
Complex vertical compliance where the documentation discipline matters as much as the contact volume — healthcare under HIPAA, financial services under PCI DSS, insurance under state-level handling guidelines.

Operating profile (Invictus)

The operating profile below describes Invictus in production today, against 2024 customer volume. These are the numbers a buyer should expect to see show up in operating reviews on an Invictus engagement.

2.4 million customer interactions per year (2024)
92.4% average CSAT across the operation
Sub-30-second answer time on inbound contacts
81%+ first-contact resolution rate
<4% regrettable attrition on a trailing 12-month basis, against a 60%+ industry attrition baseline
2.8 years average agent tenure
99.2% platform uptime
100% of contacts QA reviewed
42% cost savings versus comparable US-onshore programs

The attrition number is the one that compounds. An agent who has been on a healthcare client's account for 30 months knows the medication-adherence script, the prior-authorization queues, and the after-hours triage routing better than any onboarding process can deliver. That tenure is what turns "trained agents" into operating expertise.

Security and compliance

The Invictus platform runs under SOC 2 Type II, HIPAA, and PCI DSS controls in production. Healthcare clients run on the HIPAA-controlled instance with full audit logging on every contact. Financial-services clients run under PCI DSS for cardholder-data flows and SOC 2 Type II for service-organization controls. Vertical-specific compliance layers on top: state insurance-handling guidelines, federal financial-services disclosures, healthcare patient-privacy requirements.

Implementation and pricing

Implementation timelines. Platform-only configurations deploy in hours to days. A platform-plus-labor program typically deploys in 30 days. Emergency takeovers can deploy in 48 hours where the operation has to start immediately.

Pricing shapes. Per-seat (the familiar BPO model for steady-state operations), per-interaction (volume-driven), and outcome-based (where the operation has a clean, measurable business result). The arithmetic that wins the conversation on outcome-based engagements is revenue protected per dollar of customer-operations spend, not cost per seat.

A decision framework

Four questions to answer about the operation before picking a partner:

What is the unit of value the operation produces? A seat-hour, a resolved interaction, or a business outcome (a closed loan, a confirmed appointment, a retained policyholder). The answer shapes which pricing model fits and which operating cadence the partner needs to run.
How many seats and how many languages? A 3,000-seat program across 14 languages and 8 geographies and a 150-seat program across English and dialect-level Spanish are different operations. Both are valid; they ask different things of the partner.
Where does the platform sit in the operation? A buyer running on Salesforce Service Cloud or Genesys with a fixed CCaaS layer evaluates the BPO labor only. A buyer who wants the contact center, the CRM, and the multilingual AI in one system of record evaluates both the platform and the labor as a single decision.
How much executive attention is the operation worth? A program where the customer's COO expects to meet the partner's operating leadership monthly fits a different vendor shape than a program managed through an account-management layer at scale.
Where does vertical compliance sit? Healthcare under HIPAA, financial services under PCI DSS, insurance under state-level handling guidelines, logistics where multilingual coverage crosses shipper and driver languages on the same shipment. The compliance posture and the vertical practice depth on the vendor side should map to where the operation is regulated.

Answering these five questions usually collapses the shortlist faster than the procurement process does on its own.

Invictus vs Teleperformance