Managing the First 90 Days of BPO

The first 90 days of a BPO relationship decide whether delivery stabilises or turns into a constant cycle of escalations. In financial services, that period carries extra weight because accuracy, auditability and regulatory discipline must be established early. A provider can be capable, but capability does not translate into results unless the client firm supplies timely decisions, clear rules and consistent inputs.

This article breaks the first 90 days into practical stages. Each stage outlines the internal effort required from the client firm, the milestone outcomes that should be true before progressing and best practice actions that reduce workload and risk.

First 90 Days Milestones

A useful way to interpret this is that client effort peaks early because internal approvals, exception decisions and knowledge transfer are the real bottlenecks. The faster those are resolved, the faster effort drops into a stable governance rhythm.

Day 0 (Effort: Low)

Day 0 is about getting the basics locked in quickly so the engagement does not start with ambiguity. At this stage, the work is mainly confirmation rather than deep coordination. The firm is validating scope boundaries, naming owners and finalising the transition plan so the provider can move forward without waiting on unresolved questions.

For financial services, day 0 also includes confirming any compliance boundaries that will shape access and evidence requirements. This does not require deep operational activity yet, but it does require clarity so the next steps do not trigger rework.

Milestone outcomes

• Scope boundaries confirmed and shared
• Owners assigned for process, approvals and escalation
• Transition milestones agreed with dates and dependencies

Best Practice: reduce effortKeep Day 0 limited to decisions that unblock the next 48 hours. If you try to solve every edge case on Day 0, you usually delay the work that needs to begin immediately.

First 48 Hours (Effort: Medium)

The first 48 hours introduce real coordination between teams. A kickoff meeting occurs, escalation paths are agreed and access approvals begin. Financial services firms often require cross-functional involvement here because access, compliance and evidence requirements influence how delivery will be governed.

This is not the highest-effort phase, but it demands timely responses. Delays here typically push out training, access provisioning and the start of any pilot activity.

Milestone outcomes

• Kickoff completed with clear points of contact
• Communication cadence agreed for the first month
• Escalation pathway defined with response expectations
• Access approval path started with ownership confirmed

Best Practice: reduce effortNominate a single internal owner to coordinate access approvals across systems. Access delays create the most unnecessary friction early, especially when approvals are split across multiple teams.

First Week (Effort: High)

The first week is where the firm spends the most energy because SMEs have to transfer knowledge that often lives in habits, not documentation. This is also where exception logic is clarified, reporting definitions are finalised and evidence expectations are translated into operational routines.

In financial services, this week carries an extra burden because accuracy and auditability expectations need to be embedded early. A provider cannot infer these requirements from a contract. They need them explained, demonstrated and validated through reverse shadowing.

Milestone outcomes

• Walkthroughs completed with documented clarifications
• Reverse shadowing confirms understanding
• Exceptions captured into a living register
• Reporting and evidence expectations defined clearly

Best Practice: reduce effortPrioritise the most frequent exceptions first. If the team spends all week debating rare edge cases, the high-volume exception pathways remain unclear and effort stays high for longer than it needs to.

Weeks 2 to 4 (Effort: Medium)

This phase typically introduces pilot delivery or a controlled go-live. Client effort reduces compared to the first week, but the firm still needs to be active. The key requirement here is decision speed on exceptions, process gaps and clarifications that are uncovered during real work.

In financial services, this period is where operational reality becomes visible. The firm should focus on removing blockers, refining SOPs and tightening exception pathways before habits become embedded.

Milestone outcomes

• Pilot outcomes reviewed on a consistent cadence
• Exception decisions made quickly enough to avoid queue build-up
• SOPs updated based on what happens in real delivery
• Early performance trends visible and interpretable

Best Practice:

‍Treat this stage as a decision window rather than a reporting window. If governance meetings become status updates without decisions, the same issues repeat and the engagement feels harder to manage than it should.

Weeks 5 to 8 (Effort: Low)

If earlier phases were handled well, delivery begins to stabilise here. The firm should not need to provide constant SME input. Instead, effort is mainly governance rhythm, trend review and ensuring the provider is not blocked by approvals or unclear rules.

For financial services firms, this is a critical period for validating that evidence is being produced consistently and that controls operate without ad hoc intervention. Stability is a sign that the operating model is working, not just that output is being produced.

Milestone outcomes

• Governance meetings focus more on trends than clarifications
• Exception volumes reduce and become more predictable
• Reporting becomes reliable and consistent
• The provider operates with higher independence

Best Practice:

‍Introduce a simple improvement backlog with priorities and due dates. This keeps governance disciplined and prevents the same friction points returning repeatedly.

Weeks 9 to 12 (Effort: Low)

By this stage the firm should be operating with a stable baseline. Client effort becomes more strategic, focused on validating evidence readiness, confirming performance baselines and deciding whether to scale. This is also when both sides typically formalise next-phase planning and document what is working well.

In financial services, this phase is where the firm confirms audit readiness and checks whether scaling scope or volume introduces any compliance gaps. The safest scaling decisions come from evidence, not optimism.

Milestone outcomes

• Performance baseline confirmed and repeatable
• Evidence and audit readiness validated
• Decision made on scaling scope, scaling volume or holding steady
• Next-phase transition plan documented if scaling will occur

Best Practice:

‍Write a short Day 90 review memo. Keep it simple and action-focused: what is stable, what is risky, what must change and what the next phase will include. Very useful to the BPO provider and identifying issues earlier is always cheaper at earliest discovery.

Final Thoughts

The first 90 days of a BPO engagement requires uneven effort. The firm’s energy peaks where knowledge transfer and exception handling are being defined, then drops as delivery stabilises. Financial services firms benefit most when they focus early effort on decision rights, exception pathways, access readiness and evidence discipline. Having this set up ready yo go before the engagement starts can reduce effort levels by 50% in oir experience.

When those foundations are set properly, the engagement becomes easier to govern and safer to scale. The relationship moves from constant clarification to predictable routines, which is the real signal of long-term success.