Skip to content

Tooling Total Cost of Ownership Model

Use this model to calculate the 3-year TCO for any tool under evaluation. Compare across shortlisted tools — the tool with the lowest Year 1 cost is frequently not the tool with the lowest 3-year TCO.

Tool: Category: Prepared by: Date:


Cost ComponentEstimateBasis
Licensing / subscription (Year 1)Annual fee or first-year cost
Integration developmentEngineer-weeks × rate to build integrations with toolchain
Initial configuration and setupEngineer-days × rate to deploy and configure
Training and skills acquisitionTraining costs + lost productivity during learning curve
Infrastructure (compute, storage, hosting)If self-hosted: server/VM cost; if SaaS: included in licensing
Proof-of-concept / evaluationTime already spent; include as sunk cost
Year 1 Total

Cost ComponentEstimateBasis
Licensing / subscription (Year 2)Renewal cost (note any multi-year discounts)
Operational overheadEngineer-hours/month × rate × 12; who runs this in production?
Enhancement developmentNew integrations, feature additions, adaptations
Major upgrade effortIf a major version upgrade is likely in Year 2
Support costsVendor support contract if applicable
Year 2 Total

Cost ComponentEstimateBasis
Licensing / subscription (Year 3)
Operational overheadAs Year 2
Enhancement developmentLikely lower than Year 2 as platform matures
Upgrade / migration effortIf platform evolution requires migration work
Year 3 Total

YearCost
Year 1
Year 2
Year 3
3-Year Total
Annualised average

These costs are frequently omitted from initial estimates. Confirm each has been considered.

  • Key-person dependency: Is operational knowledge of this tool concentrated in one or two engineers? What is the cost if they leave?
  • Vendor lock-in: How difficult is it to migrate away from this tool if circumstances change? What would that cost?
  • Compliance overhead: Does this tool introduce additional compliance requirements (data residency, access logging, vendor assessment)?
  • Scaling cost: If the estate doubles in size, does the tool cost double? Does it require additional infrastructure?
  • Security overhead: Who manages credentials, certificates, and access controls for this tool?
  • Documentation debt: Who maintains the documentation for how this tool is configured and operated?

ToolYear 1Year 2Year 33-Year TCONotes

Recommended option:

Primary reason:

Key risk with this choice:

Network Automation HandbookPatrick Lau
This work is licensed under a Creative Commons Attribution-NonCommercial license.
You are free to use and adapt this material within your organisation for internal purposes. Republishing, selling, or distributing this content (in whole or in part) as a book, course, or other commercial product is not permitted without explicit permission.