The pitch never changes: one platform to run ITSM, ITAM, SAM, and the CMDB. From the top of the house that expectation is reasonable. One vendor, one contract, one number to call. Nobody in that chair is being naive.
But the honest answer is not yes or no. It is: it depends on what you asked the tool to do ā and most shops never worked that out before the demo.
Start with what the four actually are. They are not four modules; they are four jobs with different shapes. Friday covered the first two ā service management linear, IT asset management relational. Software asset management runs its own chain: this license to this entitlement, to this installation, to this host, to this cluster, to this cost center. And the CMDB is a fourth job that gets confused with the second. CMDB relationships exist to support a service ā what breaks when this server goes down. Asset relationships answer what is configured to what, and who holds it. Same word, different job.
Which is why you cannot answer this question from a feature list. You answer it from requirements ā yours, written down, before a vendor shows you anything. Two failures follow when you skip that. You accept functionality the business does not need because it was in the demo. Or you discover functionality the business does need that the solution provider does not offer. Both end the same way: somebody starts keeping a separate spreadsheet or database on the side. That spreadsheet is the receipt for a requirement nobody wrote down.
What you cannot do is let the purchase decide for you.
Because a purchase order is cheaper than the alignment conversation, and it does not end it.
In this session of The ITAM Kitchen's series, ITAM Hard Truths, we take the question seriously in both directions. We talk about the four jobs and why the CMDB is not the asset relationship model, what a real requirements set looks like, how to assess fit and name the risk before signing, how to run a selection with vendors instead of at them, and what it means when the honest answer comes back as more than one tool.
You'll leave able to say which of the four jobs your platform actually serves, which one is getting a shape it was not built for, and where the side spreadsheet in your shop came from. One contract was never the same as one answer. That's one more hard truth.
AI Prompt:
š³ Bring your requirements to the table ā or the fact that you don't have any. Run this first: "Act as an IT asset management advisor with no vendor relationship. We are being asked whether one platform can cover ITSM, IT asset management, SAM, and the CMDB. Before anyone sees a demo, help me write the requirements that decide it: what each of the four jobs actually needs from a record, where those needs conflict, and which questions force a vendor to show me fit instead of walking me down a demo path. Then tell me what it would mean if the honest answer is more than one tool."
šÆ Built for: ITAM Professionals | SAM Managers | CMDB Administrators | CIOs | CTOs | CFOs
š Live: Monday, September 21 | 10:00 AM ET | YouTube & LinkedIn Live