CALLMSFT
Microsoft: the margin bridge has one bad assumption in it
The savings target has been reiterated without a revised timeline. Reiterating the number while moving the date is how these programmes fail slowly.
The operating leverage is in support cost per account, which does not scale with revenue. It scales with account complexity, and the accounts remaining after a migration are the complex ones by construction.
The headcount data undermines the bridge. Support headcount was flat sequentially against a plan that requires a double-digit decline, and no revised timeline accompanied the reiterated target.
The position: short on Microsoft, entry locked at publication and the exit dated rather than open-ended. The target is stated in the call block above and the horizon with it. Sized to the catalyst rather than to conviction, with the invalidation written into the kill-switch card instead of left implicit.
The risk is that the build cycle extends. If capacity commitments rise again the crossover resets, and the argument is postponed rather than wrong, which is the harder outcome to hold through.
Discussion · 0
No comments yet.