A comparable cost baseline describes the same workload, period and acceptance requirements for each option. Separate transition work, recurring delivery, retained customer effort and incremental technology costs. Show existing shared expenses as allocations when useful, without counting them again as new spending. Missing estimates remain unknown until evidence or an agreed assumption fills the gap.
What to take into your scoping discussion
- Compare the same requests, service windows, outputs and responsibilities before comparing totals.
- Keep cash spending, allocated costs and proposed assumptions in separate columns.
- Name an owner and decision date for every unresolved cost input.
A supplier quote and an internal salary total are not automatically comparable. One may include checking and service management; the other may omit retained supervision, reporting or the work that waits during an absence. Before comparing numbers, describe what each option is expected to deliver.
The eLeaP outsourcing guide raises cost and ROI questions. The ledger below is LyndonAI’s own planning method. It uses your workload and evidence rather than importing the guide’s price ranges or savings claims.
Set the comparison boundary
Choose the period, request types, service windows and acceptance requirements. Identify whether the scope includes enrollment, publishing, learner support, reporting, session coordination or optional course production. Specify what stays with your team.
Keep the existing LMS in the baseline when platform replacement is not part of the decision. A comparison that charges one option for a new platform and assumes the other has none can answer a different question from the one your buyer actually needs to decide.
Use the same workload register for each option. If a supplier excludes a task, record the retained work instead of treating the exclusion as a saving. If an option offers additional capability, describe it separately so the buyer can decide whether that capability has value.
Use separate cost and evidence columns
A useful ledger can be reviewed without interpreting a single blended figure.
| Cost line | Evidence or input | Accounting view | Decision to confirm |
|---|---|---|---|
| Transition | Agreed discovery, handover and setup scope | One-time incremental spending where applicable | What is included in the engagement? |
| Recurring service | Comparable request volumes and checked outputs | Monthly incremental spending | What capacity and exclusions apply? |
| Retained customer work | Approval, source preparation and review effort | Internal effort or allocation | Which roles still own these tasks? |
| Technology | Required licenses, connectors or hosting changes | Incremental amount plus separate shared allocation | Is anything new actually required? |
| Optional content | Agreed assets, versions, languages and reviews | Separate work package | What triggers a production change? |
| Unresolved dependency | Unpriced access or technical requirement | Unknown until resolved | Who obtains the evidence and when? |
Add the period, source date and cost owner to each line. An estimate made during discovery should not acquire the appearance of an invoice simply because it appears in a spreadsheet.
Distinguish incremental spending from allocation
An existing LMS subscription may support the program before and after outsourcing. If the service does not change that subscription, its original payment is not a second new BPO expense. You may allocate part of it to the program to understand total resource use, but keep that allocation separate from the incremental cash decision.
Apply the same discipline to a shared server, authoring license or reporting tool. Identify the resource, the allocation basis and any genuine additional charge. Do not count the full shared bill and a percentage allocation of that same bill in the same total.
Internal time also needs a clear interpretation. Time spent reviewing approved content can be part of the operating model without becoming an additional supplier fee. Record the hours and agreed valuation method if you use one; avoid calling them realized cash savings merely because the outsourcing arrangement changes who performs the administration.
Treat transition as work with an output
Transition can involve procedure mapping, request sampling, permissions, testing and acceptance. In LyndonAI’s model, consulting and transition planning sit within the agreed BPO scope. Confirm their actual commercial treatment in the proposal rather than assume they are separately charged, unlimited or absent.
Document what the transition produces: a task catalog, responsibility map, current procedures and a checked pilot. If an option leaves those outputs to the customer, the comparison should show that dependency and retained effort.
Keep uncertainty visible until it is resolved
An unknown connector cost is not zero. Record the requirement, reason it remains unpriced, responsible owner and the decision that depends on it. Where useful, compare clearly labeled planning scenarios, then replace assumptions with verified inputs when available.
Do not conceal uncertainty inside a precise total. The decision record can distinguish an evidenced subtotal from unresolved items. That tells the buyer what can be compared now and what must be established before commitment.
Bring a like-for-like ledger to the service review
Ask each option to explain the same workload, exclusions, technology dependencies and acceptance checks. Review the ledger alongside the monthly scope-of-work method, then keep benefit measurement in a separate ROI evidence record.
This separation makes the decision more useful: the cost model shows resources and spending; the benefit record shows what changed and what evidence supports the value claimed. Neither replaces an agreed MTA service scope.
Buyer questions
Which retained costs belong in an MTA outsourcing comparison?
Include the customer work that remains necessary under each option: approvals, source-data preparation, subject-matter review and service oversight. Use comparable assumptions and record the evidence. Retaining a task does not mean it is a new cash expense, so show its treatment explicitly.
Should an existing LMS subscription be counted as a new BPO cost?
Only its incremental cost belongs in the new-spending column. You can also show an agreed allocation of the existing subscription for management reporting, but do not add both as though they were separate new charges. Confirm whether the proposed service requires additional licenses.
What if an integration or transition cost is unknown?
Leave it unknown, describe the dependency and identify who will resolve it. A planning scenario can use a clearly labeled assumption or range, with its source and review date. Do not silently turn an unpriced dependency into zero or a committed fee.
References & scope
- eLeaP: eLearning outsourcing costs, benefits and ROI
Broad topic context only. Published price ranges and savings claims are not used as LyndonAI prices or benchmarks. Checked 2026-11-11.
- LyndonAI monthly MTA scope and service measures
The proposed service boundary used for this original cost-ledger method. Checked 2026-11-11.
An original LyndonAI operating perspective. Examples are illustrative, not customer outcomes. Platform access, delivery capacity and automation are confirmed per engagement. This article does not activate a client connection.
Discuss the work you want to hand over.
Start with tasks, approximate volumes, systems, permissions and expected outputs.
Explore the related service →