<p>From “<strong><a href="https://thescienceofhitting.com/p/microsoft-capex-conundrum">Microsoft: CapEx Conundrum</a></strong>” (August 2024): “Embedded in that valuation framework are two critical assumptions: the long-term ROI from this CapEx spend and whether management can / will meaningfully adjust if faced with adverse outcomes. From where we stand, it’s tough to answer those questions with a ton of confidence; the list of competitors in this space is daunting, including some who have clearly stated that they plan to invest aggressively despite a period that may appear bubble-like in the near term. This situation is a good example of why it is often difficult to parse between growth CapEx and maintenance CapEx, i.e., what is elective versus table stakes to remain competitive (‘the downside of being behind: you will be out of position for the most important technology of the next 10-15 years’).”</p><p>With another six months behind us, I think we’re still receiving some (early) mixed signals as we try to develop incremental confidence on those answers. First, on the key input, CapEx spend, the numbers keep galloping forward; as you can see below, despite double digit revenue growth in FY25e and FY26e, I expect CapEx spend at >30% of revenues for (at least) the next two years – <strong>roughly three times higher</strong> than CapEx intensity at Microsoft from FY14 to FY23. (As discussed in “<a href="https://thescienceofhitting.com/p/microsoft-capex-conundrum">CapEx Conundrum</a>”, there are important nuances to consider as we look underneath the headline figures; from the Q2 FY25 call: “more than half of our cloud and AI-related spend was on long-lived assets”.)</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" href="https://substackcdn.com/image/fetch/f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2ef0e7c0-4668-4123-9ae7-0e20512535a4_913x664.jpeg" target="_blank"><div class="image2-inset"><source type="image/webp" /><img alt="" class="sizing-normal" height="664" src="https://substackcdn.com/image/fetch/w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2ef0e7c0-4668-4123-9ae7-0e20512535a4_913x664.jpeg" width="913" /><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><div class="pencraft pc-reset icon-container restack-image"><svg class="lucide lucide-refresh-cw" fill="none" height="20" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" viewBox="0 0 24 24" width="20" xmlns="http://www.w3.org/2000/svg"><path d="M3 12a9 9 0 0 1 9-9 9.75 9.75 0 0 1 6.74 2.74L21 8"></path><path d="M21 3v5h-5"></path><path d="M21 12a9 9 0 0 1-9 9 9.75 9.75 0 0 1-6.74-2.74L3 16"></path><path d="M8 16H3v5"></path></svg></div><div class="pencraft pc-reset icon-container view-image"><svg class="lucide lucide-maximize2" fill="none" height="20" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" viewBox="0 0 24 24" width="20" xmlns="http://www.w3.org/2000/svg"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></div></div></div></div></a></figure></div><p>As we review the output from that spend, I’m focused on a few key buckets.</p>
<p>
<a href="https://thescienceofhitting.com/p/microsoft-the-ui-for-ai">
Read more
</a>
</p>