"We're Tech Agnostic" Is the Riskiest Strategy in BPO Right Now

I hear it all the time from BPO leaders: "We're tech agnostic — we work with whatever our clients bring to us."

The intent behind it is good. You want to be flexible. Client-friendly. Easy to work with. And for a long time, that posture made sense.

It doesn't anymore.

Here's the thing about tech agnosticism: it sounds like a strategy. But what it actually is — especially in this market — is an abdication of one.

The false sense of security

Think about what tech agnosticism actually looks like in practice. Your clients are planning their AI roadmap, a process that can take months or even years. Meanwhile, your team keeps running their programs. Volume stays steady. You might even be growing.

It's easy to look at that growth and conclude that AI is overblown, that the doomsayers are wrong, that you've got time.

Then, the music stops.

The client flips the switch on their new agentic AI capabilities. Contact volume starts dropping. They consolidate their vendor portfolio. Some BPOs will lose the client's business entirely. Others may find their revenues significantly diminished.

The work that remains is harder, higher-stakes, and slower to handle, and the team that was built for the old volume is not built for it. The firm begins upskilling at the speed of crisis, and margins compress in parallel.

This is where the talent problem comes into sharp focus. The interactions that survive automation aren't routine. They're complex or emotionally charged, and the agent who was great at handling a high volume of straightforward inquiries is not automatically the right person for that work.

You can't hire your way out of that overnight. And you can't train your way out of it fast enough when the volume is already gone.

Agnostic isn't neutral. It's passive.

When you don't take a position on technology, you're telling your clients — whether you mean to or not — that you don't have one to take. You're signaling that the expertise lives with them, not with you.

And there's an important nuance here: your client's tech stack is only one piece of this. Technology isn't just something that happens on the client's side of the relationship. It's a lever you should be pulling inside your own operations — and most BPOs aren't.

Think about what's possible. Sales calls fed into an LLM, with key themes and objections surfaced automatically and sent to your marketing team to inform content or ad strategy. Agent performance analyzed against behavioral assessments and recruiting profiles so your talent acquisition process gets smarter with every hire. Conversation intelligence that identifies coaching opportunities before a client ever has to flag a quality issue.

None of that requires your client to hand you a technology directive. That's your house. You get to decide what happens in it.

Clients may not want you dictating their tech stack. That's fair. But they do want a partner who brings ideas. Who's paying attention. Who can walk into a review and say, "Here's what we're seeing across the industry, and here's how we think it applies to you."

That's the difference between a vendor and a strategic partner. And increasingly, it's the difference between the BPOs that are winning new business and the ones that are quietly losing it.

You don't need to push a stack. You need a point of view.

This isn't an argument for going out and building proprietary technology or forcing your clients onto a platform they didn't ask for. It's an argument for being informed. Engaged. Opinionated.

Understand the landscape well enough to guide your clients through it. Know what agentic AI means for their contact center. Know where conversation intelligence creates value and where it doesn't. Know which problems in your own operations technology can solve — and start solving them.

That knowledge is what moves you up the value chain. It's what gets you a seat at the table when your client is making decisions, instead of a notification once they've already made them.

The BPOs that will thrive in this next chapter aren't the ones with the lowest price point or the most geographies. They're the ones who can credibly say: we know where this is going, and we can help you get there.

Know Where You Stand

Having a point of view on technology — inside your own operations and in front of clients — is one of four places a BPO's commercial motion typically breaks down. The Commercial Gap Check is a free, ten-question self-assessment across go-to-market narrative, sales process, business strategy, and account management. Results shown immediately, no email required.

Start the Gap Check →

Want to go deeper on this?

I'm joining the team at CallMiner for a live session on exactly this topic.

Adapt or Vanish: Transforming CX Outsourcing in a Disruptive Market 📅 Thursday, May 28 🕗 9 a.m. PT | 12 p.m. ET | 5 p.m. BST

We'll be talking about what it actually looks like for BPOs to lead with technology, how the outsourcing market is being reshaped right now, and what separates the firms that are positioning themselves to win from the ones that are hoping the tide doesn't come in.

FAQ: Building a Technology Point of View in BPO

If my clients want different technology stacks, doesn’t having a point of view alienate the ones who chose differently?

No — having a point of view isn’t the same as mandating a stack. It means having a documented opinion on what agentic AI or conversation intelligence should look like for a given use case, then applying it to whatever platform the client already runs. Clients resist being told what to buy; they don’t resist being told what to do with what they already own.

Where do we start if our BPO has genuinely stayed technology-neutral for years and has no internal point of view to draw on?

Start inside your own operations, not with clients. Pick one process you already run at volume — QA, coaching, or recruiting — and use it to build a documented opinion about where technology helps and where it doesn’t. That internal track record is what makes a point of view credible when you bring it to a client review.

We don’t have deep in-house AI expertise — how do we develop a credible point of view without becoming a technology company ourselves?

You don’t need to build proprietary technology to have an opinion about it. Track what’s actually happening across your client base and the broader market, form a view on what’s working and what isn’t, and bring that view into account reviews before the client asks for it. That’s a research and synthesis discipline, not an engineering one.