The AI trade is not one ticker. Map the supply chain before you size the position.
All briefs
Wall Street Prompt · LinkedIn one-page
The AI CAPEX Map Investors Need
LinkedIn one-page
The AI trade is not one ticker. It is a supply chain. Map the chain before you size the position.
LinkedIn1080 × 1350
References & validationExact post missing
Reference creator resolved, but the exact source post was not captured. Capture the specific post (not just the profile) before treating as validated.
Reference creator: Beth Kindig / Deepwater / SemiAnalysis
Post content
Dense one-page content — sections, tables and frameworks
01 / The Single-Stock Trap
Most investors treat AI as one bet on one name. That is a narrative, not a position. The spend moves through a chain, and each link has different margins, different cyclicality, and different durability.
- Common mistake: you buy the most-quoted ticker and call it AI exposure.
- Failure mode: you own one link, take the volatility of the whole chain, and cannot tell when the story changes.
- Disciplined workflow: map the chain first, then decide where in the chain you actually want exposure.
Why it matters: a single ticker hides where the cash is going. The capex flow tells you who gets paid first, who gets paid on a lag, and who only gets paid if demand holds.
02 / The Capex Chain, Layer by Layer
Follow one dollar of AI capex from the hyperscaler budget to the end product. Each layer earns differently and carries different risk.
| Layer | What it does | Read it in the 10-K / call as |
|---|---|---|
| Demand source | Hyperscalers and large enterprises set the capex budget | Capex guidance, depreciation schedule, commentary on AI demand |
| Compute / silicon | Accelerators and the chips that train and serve models | Data-center revenue mix, gross margin, backlog and lead times |
| Equipment / tools | Gear that fabricates the chips upstream | Bookings, book-to-bill, China exposure, order timing |
| Infrastructure | Networking, memory, power, cooling, real estate | Utilization, contract length, power and capacity constraints |
| Software / apps | Models and products that monetize the compute | Revenue per user, retention, gross margin, inference cost trend |
Why it matters: the same headline lifts every layer, but only some layers convert that headline into durable cash. Know which layer you own.
03 / How Each Layer Earns and What Breaks It
A map is only useful if it shows risk, not just names. Pair every layer with its margin profile, its cyclicality, and the single thing that breaks the thesis.
| Layer | Margin profile | Main risk to watch |
|---|---|---|
| Demand source | Funds the chain from cash flow | Capex cut or pause in a budget cycle |
| Compute / silicon | High margin, pricing power today | Competition, customer in-house chips, supply normalizing |
| Equipment / tools | Cyclical, order-driven | Bookings roll over, export restrictions tighten |
| Infrastructure | Steadier, contract-backed | Power and capacity limits, build cost overruns |
| Software / apps | Variable, scaling-dependent | Inference cost stays high, monetization lags the hype |
Heads up: the risk column is where position sizing lives. A layer with order-driven cyclicality is not the same position as a layer with contract-backed revenue, even if both are AI.
04 / The Mapping Workflow
Run this before you build any AI position. It turns a narrative into an IC-memo-ready map.
| Step | Action | Output |
|---|---|---|
| 1 Trace | Follow the capex dollar from budget to end product | A drawn chain with named layers |
| 2 Source | Pull capex guidance and segment data from 10-Ks and calls | Numbers behind each layer, not headlines |
| 3 Comp | Compare names within each layer on margin and growth | Best risk-reward inside a layer, not across the whole trade |
| 4 Risk | Write the single thing that breaks each layer's thesis | An explicit failure mode per holding |
| 5 Size | Size each position to its own risk, not the chain's hype | A portfolio mapped to the chain, not one ticker |
Tip: if you cannot name the failure mode for a layer, you do not understand the position yet. Do not size it.
05 / Where AI Fits in This Workflow
The map is judgment work. The build is grunt work. Split the two.
- AI builds: pull segment data across filings, line up comps inside a layer, draft the risk lines, structure the IC memo.
- Human judges: decide which layer to own, weigh the failure modes, set the position sizes.
- Key: AI gives you the chain faster. It does not tell you where in the chain to stand. That is your call.
Why it matters: speed on the build means more time on judgment. The map gets cheaper to make. The decision stays yours. Human judges. AI builds.
Caption
LinkedIn post copy
Visual design notes
- Background near-black forest green (deep #0C1410 to #0A0F0C), single teal-green accent (#1FB57A) used only for the title keyword, the subtitle banner, table header rules, and the step numbers. Everything else off-white text. No second accent color.
- Header: heavy condensed sans (Anton or Druk Condensed) for the title, all caps, left-aligned, with CAPEX as the single emphasized word in the green accent. Title spans two lines max. Directly below, a full-width teal subtitle banner with the one-liner in medium-weight sans, left-aligned.
- Section numbers (01-05) set large in the accent green as a left-rail anchor, headings in condensed caps next to them, left-aligned throughout. No centered text anywhere.
- Tables are the core visual: dense 2- and 3-column layouts with a thin green top rule on the header row, hairline row dividers in muted green-gray, generous left padding, monospaced or tabular figures where numbers appear. Alternate row tint very subtle (5 percent lighter than bg) for scan-ability.
- Add a small horizontal capex-flow diagram between section 01 and section 02: five connected nodes (Demand to Silicon to Equipment to Infrastructure to Software) with a single green arrow line running left to right, showing the dollar moving through the chain. Keep it thin and schematic, not decorative.
- Why it matters notes set in italic or in a left-bordered callout block with a 2px green left border, slightly smaller type, to visually separate teacher framing from body.
- Footer locked to bottom margin: WSP wordmark left, the follow line in small caps muted, a thin green rule above it. Maintain consistent 64px outer margins on the 1080x1350 canvas. No em dashes anywhere in rendered copy.
Production checklist
- ☐Design the 1080x1350 one-pager on the WSP near-black forest template: set outer margins to 64px, lock the header block, subtitle banner, and footer rail before adding sections.
- ☐Build section 01 with the bullet list and Why-it-matters callout, then draw the 5-node horizontal capex-flow diagram beneath it with a single green arrow line.
- ☐Build the three core tables: the capex-chain layer table (sec 02, 3 col), the margin-and-risk table (sec 03, 3 col), and the 5-step workflow table (sec 04, 3 col), using the green header rule and hairline dividers spec.
- ☐Apply header and footer branding: title with CAPEX emphasized in accent green, teal subtitle banner, WSP wordmark and follow line in the footer, confirm no em dashes and no buy/sell/hold or target language anywhere.
- ☐Proof the full one-pager for density and left-alignment, then export PNG at 1080x1350 for the LinkedIn feed and a PDF version for the comment-to-DM lead magnet.
Follow Dave Wang · Wall Street Prompt · For more AI investing workflows · COMMENT & REPOST
CTA
Save this map and run the 5-step workflow on your own AI position before your next add. Comment CAPEX and I will send the one-pager as a PDF.