


Understand the difference between time-based and output-based BPO engagements, pricing models, risk, control and best-use cases
An engagement model is the commercial framework that determines how a BPO provider charges for work and what the client is actually paying for. Time-based BPO charges for hours worked, making it ideal for fluctuating workloads. Output-based BPO pays for completed results like resolved tickets or processed applications, which incentivizes efficiency and quality over hours logged.
The distinction matters more than most people realize. When you pay for time, you're buying availability and effort. When you pay for outputs, you're buying deliverables and results. These two approaches create very different dynamics in how work gets done.
Your engagement model answers some fundamental questions about your outsourcing relationship: How do we measure success? What triggers payment? Who is accountable when targets aren't met?
A time-based engagement might look like three dedicated staff members working 40 hours per week on your compliance administration. An output-based engagement might instead specify 500 client file reviews completed per month to a defined quality standard. Both can deliver excellent results, but they create different incentives and require different management approaches.
Pricing creates incentives, and incentives drive behaviour. Under a time-based model, providers have little commercial reason to work faster or find efficiencies since they're paid the same regardless of output. Under an output-based model, there's pressure to optimise, though this can sometimes create tension between speed and quality.
Neither model is inherently better. The right choice depends on your process maturity, volume predictability and how much oversight you're prepared to provide.
An engagement model is about commercial terms. An operating model is about how work actually gets done: team structure, technology, workflows and governance.
You can have the same operating model with different engagement models. For example, a dedicated offshore team might be engaged on either a time-based or output-based basis depending on how mature and measurable the underlying processes are.
Time-based engagements charge for capacity rather than results. You're paying for a person's time, typically measured in hours worked or full-time equivalent (FTE) staff allocated to your account. This model is sometimes called input-based pricing because you're paying for the inputs (labour hours) rather than the outputs (completed work).
The most common structure is FTE-based pricing, where you pay a monthly rate for each dedicated staff member. Hourly pricing works similarly but charges per hour worked, which suits variable or project-based needs.
With time-based pricing, you're paying for availability and effort. The provider commits to having qualified people working on your account for agreed hours. What they produce during those hours is largely your responsibility to manage.
This means you retain significant control over priorities, workflows and quality standards. It also means you carry most of the productivity risk if output falls short of expectations.
Time-based engagements work well when processes are still evolving, volumes are unpredictable or the work requires close collaboration and judgement.
Financial planning practices often start with time-based models when first outsourcing paraplanning or compliance support. The work involves nuanced decision-making, and it takes time to document processes and establish quality benchmarks before moving to output-based arrangements.
Output-based engagements tie payment to specific deliverables or measurable outcomes. Instead of paying for hours, you pay for completed work units, achieved KPIs or business results. This model shifts accountability toward the provider since they're responsible for delivering agreed outputs regardless of how long it takes.
Output-based pricing typically uses a per-unit rate. You might pay a fixed amount per application processed, per client review completed or per transaction reconciled.
Outcome-based pricing goes further by linking payment to business results like customer satisfaction scores, error rates or revenue generated. However, outcome-based arrangements require mature processes and robust measurement systems to work effectively.
For output-based models to work, both parties need absolute clarity on what constitutes a completed unit of work. This includes quality standards, turnaround times and how exceptions are handled.
Vague definitions create disputes. If you're paying per "completed file review," you need to specify exactly what complete means, what quality checks are required and what happens when files are returned for rework.
Output-based models suit standardised, repeatable processes with predictable volumes:
The fundamental difference is what you're buying. Time-based models buy capacity and effort. Output-based models buy results and deliverables. Everything else flows from this distinction.
FeatureTime-basedOutput-basedPayment triggerHours loggedDeliverables completedPrimary risk holderClientProvider (shared)Management effortHigherLowerBest suited forEvolving processesStable, measurable workFlexibilityHighModerateCost predictabilityPer-unit predictablePer-outcome predictable
In time-based models, the client typically owns productivity outcomes. If your dedicated team processes fewer files than expected, that's your problem to solve through better training, clearer processes or performance management.
Output-based models transfer this accountability to the provider. They've committed to delivering specific results, so underperformance becomes their commercial problem to solve.
Time-based models offer flexibility to redirect effort as priorities change. Your dedicated team can shift between tasks without renegotiating commercial terms.
Output-based models provide cost predictability tied to volume. You know exactly what each unit of work costs, which simplifies budgeting and capacity planning. However, changing scope or adding new work types usually requires contract amendments.
Time-based engagements require more hands-on management. You're essentially managing an extended team, which means involvement in daily priorities, quality oversight and performance coaching.
Output-based engagements reduce this burden by making the provider responsible for how work gets done. Your focus shifts to defining requirements and monitoring outcomes rather than managing activities.
Time-based models suit situations where flexibility and collaboration matter more than efficiency optimisation.
Early-stage outsourcing relationships often benefit from time-based structures. You're still learning what works, documenting processes and building trust. Locking into output-based pricing before you understand true productivity levels can create problems for both parties.
Knowledge-intensive work like paraplanning, compliance review or complex client administration often fits better with time-based models. The work requires judgement, and quality is harder to measure through simple output metrics. At Felcorp Support, we find that many financial services firms start with time-based arrangements while processes mature, then transition to hybrid or output-based models over time.
Tip: If you can't clearly define what "done" looks like for a piece of work, you're probably not ready for output-based pricing.
Output-based models shine when processes are stable, volumes are predictable and quality can be objectively measured.
Mature operations with well-documented procedures and clear quality standards are ideal candidates. The provider can confidently price per unit because they understand the work and can optimise their delivery approach.
Efficiency-focused engagements benefit from output-based structures because the provider has commercial incentive to find better ways of working. Any productivity gains they achieve improve their margins, which aligns their interests with yours.
Moving to output-based pricing too early is perhaps the most frequent error. Without stable processes and clear quality definitions, you'll spend more time managing disputes than realising efficiency gains.
Treating time-based models as simple staff augmentation is another pitfall. Even with dedicated staff, you need governance, quality frameworks and performance management. The provider supplies the people, but you still need to lead them effectively.
Underestimating the design effort for output-based models catches many organisations off guard. Defining units of work, quality standards, exception handling and measurement systems requires significant upfront investment before the engagement begins.
For financial services firms navigating these decisions, working with a provider experienced in regulated environments can help avoid costly missteps. Book a call with Felcorp Support to discuss which engagement model fits your operational needs.
Not necessarily. Output-based pricing provides cost certainty per unit, but providers price in risk and margin to protect themselves. Time-based models can be more economical when you have strong internal management capability and can drive productivity improvements yourself.
Yes, and many do. A common pattern is starting with time-based pricing while processes mature, then transitioning to output-based models once volumes stabilise and quality metrics are established. This evolution typically takes 12 to 18 months depending on process complexity.
Time-based models offer more operational control because you direct daily activities. Output-based models offer more outcome control because you define what success looks like and hold the provider accountable for achieving it. The type of control you want depends on your management capacity and priorities.
Time-based SLAs typically focus on availability, responsiveness and quality standards. Output-based SLAs emphasise throughput, accuracy rates and turnaround times. Both types of agreements include escalation procedures and remediation processes for when things go wrong.