IT Sourcing Sorcerer · 2026-06-13 · 3 min
Key moments - from our scoring
Substance score
13 / 100
Five dimensions, 20 points each
The SDM Formula presents a data-driven model for optimizing service delivery manager capacity, challenging the 'it depends' approach with concrete recommendations. The core thesis: a single SDM should manage no more than four accounts, with stricter limits (below three) for high-value customers scoring at mean plus one standard deviation in contract value. The document dismisses traditional workload drivers - SLA counts, project volume, customer IT team size - as weak indicators, instead anchoring capacity planning to three factors: customer value, customer happiness, and operational time required for service reporting, invoicing, governance, and frequent engagement. This framework builds in approximately 20% flexibility for incident management and escalations. Finance leaders, service delivery directors, and account management teams should evaluate this model against current SDM-to-account ratios; companies overstretching SDMs across 25+ accounts will find little support for maintaining quality or governance. The recommendation prioritizes competitive service standards and proactive account management over arbitrary utilization metrics.
The SDM Formula recommends a maximum of four accounts per SDM as the operational limit, with below-three accounts required for premium high-value customers (those at mean plus one standard deviation in contract value).
Such high account loads are unrealistic and result in dropped responsiveness, declined service quality, and inability to maintain effective governance because SDMs cannot handle the operational bandwidth required for service reporting, invoicing, and governance.
The formula dismisses conventional complexity drivers like the number of SLAs, project volume, and the size of the customer's IT team as weak indicators, instead focusing on customer value, customer happiness, and practical time requirements for operations.
The 20% buffer exists to accommodate incidents, escalations, and unexpected demands, ensuring SDMs remain proactive rather than purely reactive in managing their assigned accounts.
Our reviewer’s read on each dimension, with quotes from the episode.
The entire episode reduces to a single claim - four accounts per SDM - restated multiple times with minimal elaboration. There is almost no new information per minute beyond the bare thesis, and the episode is only three minutes long to begin with.
The main thesis is a single SDM should cap their accounts at 4 with stricter limits for high value customers.
To summarize, four accounts per SDM is the practical upper limit.
Dismissing conventional workload drivers like SLA count and project load in favour of contract value and customer happiness is a mildly contrarian angle, but it is asserted rather than argued and the reasoning behind it is never developed or challenged.
Factors like number of SLAs, projects or the customer's IT team are considered weak indicators. The formula doesn't depend on those.
The document challenges the traditional it depends stance.
There are no real guests; the episode is two scripted voices reading summaries of an unnamed internal document. No practitioner credentials, company affiliations, or lived experience are presented at any point.
Today we're exploring findings from the document titled the SDM Formula How Many Accounts Can One SDM Manage?
The only concrete figures offered are the numbers 4 and 5 and a vague statistical reference to 'mean plus one standard deviation.' No methodology, no named companies, no real data set, and no source beyond 'the document' are ever provided.
If a customer falls at the mean plus one standard deviation in contract value, the formula tightens.
That operational limit creates about 20% flexibility for managing incidents, escalations and unexpected demands.
The exchange is transparently scripted call-and-response with no genuine follow-up or challenge; every question exists solely to cue the next pre-written answer, and no claim is ever probed or contested.
So why reject extreme account loads like 25 or even 100 accounts per SDM?
What about exceptions, particularly for high value customers?
Computed from the transcript - who did the talking, and the words that came up most.
Are your IT services delivering real business value… or just keeping the lights on? In this latest episode of the IT Sourcing Sorcerer Podcast , I break down the core ideas from my ebook “The SDM Formula” - and why Service Delivery Management is the missing link in many organisations. We explore: How to move from reactive IT to value-driven service delivery Why Governance, Performance & Relationships matter more than ever How to drive measurable outcomes across multi-vendor environments In today’s world of cloud, outsourcing, and AI - strong service delivery isn’t optional. It’s a competitive advantage. Tune in now and turn IT into a business enabler. And understand why the answer to this particular IT question if 4!
Transcribed and scored by The B2B Podcast Index.
Host: Welcome to this professional discussion focusing on service delivery manager account ratios. Today we're exploring findings from the document titled the SDM Formula How Many Accounts Can One SDM Manage? Which offers a data driven approach to optimizing SDM capacity.
Co-host: Right. The document challenges the traditional it depends stance. Its goal is to establish a practical quantitative model for service delivery management. We'll be reviewing the objectives, implications and operational perspectives in depth.
Host: The scope covers the recommended SDM to account ranges, special exceptions for premium clients, dismissed workload drivers, and ultimately how these recommendations safeguard service quality in customer operations.
Co-host: The main thesis is a single SDM should cap their accounts at 4 with stricter limits for high value customers. This positions quality above vague workload metrics, which is essential for maintaining competitive service standards.
Host: It's an important model for anyone managing customer accounts. By setting precise limits, organizations avoid overstretching SDMs and ensure consistent, reliable service delivery. Let's start with the SDM account management formula itself. The document recommends a range 1 to 5 accounts per SDM. That calculation comes from operational bandwidth. Enough time for service reporting, invoicing, governance and frequent engagement.
Co-host: Interesting. So why reject extreme account loads like 25 or even 100 accounts per SDM?
Host: According to the document, assigning such high numbers is unrealistic responsiveness drops and quality declines. SDMs can't maintain effective governance when stretched that thin.
Co-host: I see. The operational recommendation sets the magic number at four accounts per SDM. Uh, that's a sharper cutoff than the theoretical five.
Host: Correct. That operational limit creates about 20% flexibility for managing incidents, escalations and unexpected demands, ensuring the SDM remains proactive.
Co-host: What about exceptions, particularly for high value customers?
Host: If a customer falls at the mean plus one standard deviation in contract value, the formula tightens. In those cases, the maximum drops below three accounts per SDM premium accounts require more focused attention.
Co-host: The document also dismisses conventional workload drivers, right?
Host: Yes. Factors like number of SLAs, projects or the customer's IT team are considered weak indicators. The formula doesn't depend on those.
Co-host: Instead, the drivers that matter are customer value, customer happiness and the practical time required for strong operations.
Host: Exactly. Keeping account numbers realistic allows SDMs to be responsive and maintain governance directly. Supporting customer confidence. To summarize, four accounts per SDM is the practical upper limit. Premium accounts need fewer assignments and conventional complexity drivers should be ignored in capacity planning.
Co-host: Ultimately, these recommendations protect service quality and support proactive account management.
E365 IT Services explained - vCIO45 / 100
Microsoft Work Trends Index 2025 Summary35 / 100
What’s wrong with outsourcing?39 / 100
Size Doesn’t Matter: The Truth About IT Sourcing Deals
The 5 Dimensions of Sourcing Value