The repeatable reads behind three unrelated stories — how to tell whether over-spending is a mistake or a coming business, how to value a conglomerate that's breaking itself apart, and how to strip a one-time windfall out of a "blowout" quarter. Not whether to buy, but what each move is really telling you.
1. Ask whether "over-spending" is a mistake or a business waiting to be sold
The repeatable method
- When a company is being punished for a massive CapEx line, don't stop at "they over-built" — ask whether the excess asset can be rented or resold, converting a cost into a revenue stream.
- Look for the tell that management sees capacity worth selling: a public comment ("on the table"), inbound demand ("people ask to buy it every week"), or an actual product launch — that reframes the spend from waste to option value.
- Anchor it to precedent: the same excess-capacity-becomes-a-product arc has played out before (Amazon's spare compute → AWS), so weight the base rate that a scaled owner of a scarce asset can monetize it.
Here: META, shunned all year for ~$145B of AI CapEx, jumped ~10% on a report it will rent out excess compute — the "Amazon move." Zuck had flagged it as "definitely on the table," with outsiders asking to buy compute weekly.
Watch for
- Whether the new line actually books revenue and at what margin; a management comment shifting a cost narrative to an option narrative; and which incumbents/customers it disrupts (below).
2. Trace who gets hurt when a big customer becomes a supplier
The repeatable method
- When a scaled buyer announces it will start selling what it used to buy, map its former suppliers/vendors — they face a double hit: losing the customer and gaining a competitor at once.
- Rank the exposure by how concentrated each vendor's revenue was on that buyer — the more dependent, the sharper the sell-off.
- Separate the share-price reaction (immediate, sentiment-driven) from the fundamental question (does the buyer actually have the will and cost structure to compete for third-party business).
Here: Meta's cloud entry sank CRWV −13% and NBIS −15% — both neoclouds that had counted Meta among their biggest customers now face it as a potential rival.
Watch for
- The disclosed customer-concentration on the newly-competing buyer; whether the sell-off overshoots (the buyer may never seriously chase third-party rental); pricing pressure as new supply lands.
3. Value a breakup on sum-of-the-parts, then check what the upside actually requires
The repeatable method
- For a conglomerate splitting up, value each piece on its own — a stable cash-throwing "utility" and a lumpy hit-driven business deserve different multiples, and bundling them tends to depress the blended valuation.
- Compare the sum-of-the-parts estimate to the current price: if SOTP is only modestly above today's price, the split alone isn't the catalyst — the extra upside must come from something else (usually M&A that the newly-independent equity currencies enable).
- Discount management's denials: a company that says a split is "absolutely not" a prelude to deals has just handed each half its own stock, board, and focus — the classic pre-condition for dealmaking.
Here: CMCSA is separating NBCUniversal + Sky from broadband/wireless. Wells Fargo's SOTP is ~$25/share — barely above the price — and explicitly says the upside "requires a transaction." A standalone NBCU becomes either the sector's next buyer or its next target.
Watch for
- The SOTP gap vs the current price; whether each spun entity gets a clean equity currency and independent board; the segment divergence that justified the split (see #4); tax-free-separation timing and any stake the parent retains to sell down.
4. Use segment divergence — not the blended number — to justify (or doubt) a split
The repeatable method
- Break the conglomerate into its reported segments and compare growth trajectories: a flat, declining annuity bundled with a volatile high-growth engine is the textbook case for separation.
- Strip out non-recurring boosts before judging the "growth" segment — a spike driven by one-off events isn't a run-rate.
- Ask which investor base each segment attracts; if they're incompatible (yield-seekers vs growth buyers), the bundle structurally under-earns its parts.
Here: Comcast's Q1 made the logic obvious — Connectivity −1% to $20.0B (an annuity under siege from fixed-wireless and Starlink) vs Content & Experiences +41% to $13.0B, but only because NBC aired both Super Bowl LX and the Winter Olympics (media +61% on events that don't recur). One utility, one hit engine — "changed our mind."
Watch for
- Whether the high-growth segment's spike is event-driven (non-recurring); each segment's structural threats (fixed-wireless/Starlink on connectivity); and management's own stated rationale.
5. Strip one-time items before believing a "blowout" — the margin-mirage test
The repeatable method
- When reported EPS or gross margin spikes, hunt the footnotes for a one-time item (a tariff refund, legal settlement, insurance recovery) and quantify its EPS and basis-point contribution.
- Recompute the "clean" number: subtract the one-off, then compare that against consensus and against the prior trend — a headline blowout can shrink to a modest beat.
- Confirm with the top line and constant-currency revenue: a genuine recovery shows up in growing sales, not just a flattered margin.
Here: NKE's Q4 EPS jumped 5x to $0.72, but a $986M tariff recovery added ~900bps to gross margin. Strip it and EPS was ~$0.20 (vs $0.13 est), reported 49% gross margin was really ~40% underlying, and revenue still fell 1% (−4% cc). The recovery is real only in North America and Running, not the P&L headline.
Watch for
- The size of any one-time item vs the headline beat; underlying (ex-item) gross margin vs the reported figure; constant-currency revenue direction; whether real green shoots (a segment or category) back the "recovery" claim before paying up (NKE ~28x forward, still "show me").
Methods distilled from the public App Economy Insights newsletter (article text in transcript.txt) for personal study. Not investment advice. © App Economy Insights for source material.