Skip to main content
ARVATOBPO · LLC
All resources
Getting started

Is your function ready to outsource?

Eleven questions that decide whether a function is ready to hand over — volume stability, process documentation, systems access, and the escalation path. If you answer no to more than three, fix those first.

Checklist3 min read

Outsourcing fails far more often for readiness reasons than for vendor reasons. A partner can bring people, floor space, telephony and supervision. What a partner cannot bring is knowledge of how your business actually decides things — and if that knowledge lives only in the heads of four people who have been doing the job for six years, no transition plan survives contact with the first unusual ticket.

Work through the eleven questions below before you brief a single vendor. They are the same ones we ask on a first call, and the honest answers change what we quote.

Volume and stability

  • Do you have at least three months of interaction volume by day and by hour? Not a monthly total — a shape. Staffing is built from the shape.
  • Is the volume roughly predictable, or driven by campaigns nobody tells operations about? Unannounced spikes are survivable; unannounced spikes with an SLA attached are not.
  • Do you know your current handle time and your current abandon rate? If the answer is "we don't measure that", the pilot's first job is to measure it, and you should expect the first month's numbers to look worse than you assumed, because they were never true.

Process

  • Is the work written down anywhere a new starter could follow? A screen-recording and a list of five common cases beats a 90-page manual nobody opens.
  • Can you name the decisions an agent is allowed to make alone — refund limits, credit thresholds, when to waive a fee? Undefined authority is the single largest driver of escalations in a new pod.
  • Is there a genuine exception path, or does every unusual case end up in one person's inbox? That person becomes the bottleneck the day the volume doubles.

Systems and access

  • Can a third party be given scoped access to your CRM, helpdesk and telephony without a security exception? Find out before signing, not in week two.
  • Does your stack support named users and audit logging? Shared logins make quality scoring meaningless and make a security review impossible to pass.
  • Is there a test environment, or will training happen on live customer records? If it is the latter, say so up front so it can be handled properly rather than discovered.

Ownership

  • Who on your side owns this relationship day to day, and do they have the authority to answer questions the same week? A pod with no counterpart drifts within a month.
  • Are you prepared to sit in a weekly review for the first quarter? Not a report — a call, with the numbers open. The partnerships that work are the ones where somebody senior stayed interested past week three.

Reading your score

Nine or more yes answers: you are ready, and a pilot should start with a real target rather than a discovery phase.

Six to eight: outsource the parts you scored well on and keep the rest in-house for now. Splitting a function is normal and usually cheaper than delaying the whole thing.

Five or fewer: do not outsource yet. The three fastest fixes are almost always writing down the top ten cases, defining agent authority in writing, and pulling three months of volume by hour. That is a fortnight of work, and it changes the price of everything that follows.

A vendor who tells you that none of this matters is selling seats, not outcomes. The readiness gaps do not disappear when the work moves — they just start costing you in someone else's building.

Further reading

More on what is your function ready to outsource? means in practice.

Read on

Start the conversation

Want this applied to your numbers?

Bring what you have and we'll tell you honestly whether outsourcing your function makes financial sense — including when it doesn't.