Dynamics 365 TCO modelling

The headline cost of Dynamics 365 — per-user licence — is only part of the picture. Total Cost of Ownership (TCO) over 5 years includes implementation, integration, customisation maintenance, operations, training, and evolution. Building an honest TCO model exposes the real investment; without it, organisations underestimate cost by significant margins.

The TCO components.

• Software licences — ongoing subscription.
• Implementation — one-time but significant.
• Integration — initial + ongoing.
• Customisation — build + maintain.
• Infrastructure — Azure consumption, additional services.
• Operations — admin, support staff.
• Training — initial + ongoing.
• Evolution — periodic enhancements.
• Compliance / security operations.
• Vendor management.

Each compounds; total dwarfs licence cost.

Typical TCO breakdown over 5 years.

• Licences: 25-40%.
• Implementation: 20-30%.
• Operations: 20-30%.
• Evolution / customisation: 10-15%.
• Other (training, integration, etc.): 5-15%.

Specific ratios vary; pattern is consistent.

Year 1 vs ongoing.

• Year 1: heaviest. Implementation cost concentrated.
• Years 2-5: lower. Mostly licences + operations + evolution.

The 5-year average is meaningfully lower than Year 1.

License cost model.

• Per-user, per-month typically.
• Volume discounts for larger deployments.
• Enterprise Agreement further discounts.
• Add-ons — additional capacity.

Estimate users × edition × period.

Implementation cost factors.

• Scope — modules, processes.
• Complexity — customisation depth.
• Migration — data and systems.
• Number of users to train.
• Geographic spread.
• Industry-specific requirements.

Mid-market: $500K-$2M typical. Enterprise: multiples.

Operations cost factors.

• Internal admin — 0.5-2 FTE typical.
• Partner support — typically retainer.
• Microsoft premier support — for enterprises.
• Training refresh — ongoing.

Operations is steady-state cost; underestimated by many.

Customisation maintenance.

• Customisations age.
• New requirements add more.
• Some customisations need rebuild as platform evolves.
• 10-20% of original customisation cost annually for maintenance.

The "free customisation forever" myth costs organisations real money.

Microsoft platform evolution.

• Two waves per year — features added.
• Some breaking — require adjustment.
• Most additive — opt in if useful.

Plan for keeping up; lagging accumulates debt.

Integration cost.

• Initial integration — significant.
• Ongoing maintenance — schema changes, version updates.
• Connector licences — premium connectors cost.
• Custom integration — most maintenance.

Integrations are technical debt accumulator if not maintained.

Hidden costs.

• Productivity dip during transition.
• Change management.
• External consulting for specific issues.
• Compliance audits.
• Data quality remediation.

These exist; budgeting for them matters.

Soft benefits / cost avoidance.

• Decommissioned legacy — savings.
• Productivity improvement — measurable.
• Better decisions from data.
• Reduced manual work.

These offset cost; quantify for ROI calculation.

TCO modelling techniques.

• Spreadsheet model — line items per year.
• Sensitivity analysis — what if user count grows X%.
• Scenario modelling — best case, expected, worst.

Simple spreadsheet sufficient for most; specialised tools for enterprise.

Common modelling errors.

• Underestimating implementation. Partner low-balls; actuals exceed.
• No customisation maintenance. Built once; forgotten.
• No operational team cost. Assumes existing staff absorb.
• No evolution cost. Assume zero ongoing build.
• No training refresh. Train once, never again.
• No data migration cost. "Just lift and shift."
• No integration cost. "It's just an API call."

Each adds material cost; missing them creates surprise.

TCO vs ROI.

• TCO — total cost.
• ROI — return on the investment.
• Net benefit — ROI minus TCO.

Both needed for business case.

Comparison TCO. Sometimes:

• Stay on legacy TCO.
• Migrate to Dynamics TCO.
• Difference is the case.

Honest comparison includes legacy operating cost going forward.

Industry benchmarks.

• Per-user cost for similar organisations.
• Cost per process implemented.
• Implementation cost as % of annual revenue.

Benchmarks help validate estimates.

Reviewing TCO.

• Annually — actuals vs forecast.
• Pre-renewal — informs renewal strategy.
• Pre-major change — investment decisions.

TCO is living model, not one-time estimate.

Cost optimisation strategies.

• Rightsize licences continuously.
• Retire unused customisations.
• Consolidate integrations.
• Standardise on supported patterns vs custom.

Each saves cost without reducing capability.

Partner role in TCO.

• Implementation phase — bulk of partner cost.
• Steady-state — retainer or per-project.
• Periodic enhancements — incremental.

Partner relationships span the TCO lifecycle.

Microsoft pricing trajectory.

• Periodic price increases.
• Plan for 3-5% annual inflation in licence cost.
• Sometimes larger adjustments.

Build in pricing escalation in multi-year models.

Strategic positioning. TCO modelling is foundational financial discipline for Dynamics 365 ownership. Without it, organisations make decisions on incomplete information.

For decision-makers:

• Build TCO model upfront.
• Update annually with actuals.
• Use for renewal and investment decisions.
• Share with executive sponsors.

The model isn't decoration; it informs strategic choices about Dynamics. The teams that maintain TCO models make better investment decisions; the teams that don't repeatedly face surprise costs and difficult conversations about budget overruns.