Most retail options content on earnings stops at "buy a straddle" or "sell the IV". Both of those trades have negative expected value across a wide sample because they don't use the actual content of the call. This post walks through the standard mechanics (expected move, IV crush) and then connects them to what you can extract from the transcript in the 5–60 minutes after the call ends.
Expected move — the only number that matters pre-earnings
The expected move is the market-implied 1-day price change priced into the options chain. For a stock at $100 with an at-the-money straddle (call + put, expiring this week) priced at $5, the expected move is roughly $5, or 5%.
If you don't trust the math, the shortcut: take the price of the ATM straddle, divide by the stock price, multiply by 100. That's the expected % move.
What it tells you:
- If the actual post-earnings move is bigger than the expected move, your long-vol trade pays. If smaller, your short-vol trade pays.
- 60–70% of the time the actual move is smaller. That's not a free trade though — when it's bigger, it's often a lot bigger.
IV crush is real and predictable
Implied volatility on the front-week options ramps into earnings (sometimes 50–80% IV the day before the call) and collapses immediately after the print (back to ~25–35%). This is "IV crush" and it's the dominant P&L driver in front-week earnings options.
Selling premium directly into IV crush has known expected value > 0 if (a) you're sized to survive the tail, and (b) you exit positional within hours of the print. The tail is the killer — one or two big surprises a year wipes out a season of premium-selling. Most retail traders don't survive.
What the transcript adds that the chain doesn't
The chain prices a probability distribution. The transcript tells you which side of the distribution you're actually on. Specifically, in the 5-60 minutes after the call ends, three signals from the transcript matter for your post-call positioning:
1. Did management hedge their guidance language?
Front-month options often re-price during the Q&A, not on the headline. If management raised guidance but every sentence has "subject to", "we'll see how the second half plays out", "depending on tariff resolution" — that's the kind of language that takes the legs out of a long-vol thesis. Sentiment-laden guidance ≠ confidence.
2. Did the Q&A reveal a tension?
Analysts ask the same 2-3 questions every call. The interesting one is when the management answer is meaningfully different from the prepared remarks. Examples that have been profitable bear-vol catalysts:
- Prepared says "strong demand"; Q&A reveals one segment in mild decline.
- Prepared says "operating leverage"; Q&A reveals hiring resumption.
- Prepared says "premium positioning"; Q&A admits price concessions in one geo.
These tensions are why the speakers endpoint matters — you can pull just the Q&A block and read it without the PR fluff.
3. Did they tee up a forward catalyst?
Phrases like "we'll have more to share at Analyst Day in November" or "we expect to formally launch in Q1" are options-trader gold for the next dated expiry, not this week. The stock often doesn't move on this call but the next monthly expiry's IV stays elevated.
A 5-minute post-earnings workflow
# 1. Get the new transcript
curl "https://earningscalls.dev/api/v1/companies/ticker/NVDA/latest?mic=XNAS" \
-H "X-API-Key: $KEY"
# 2. Pull just the Q&A speakers
curl "https://earningscalls.dev/api/v1/search?q=*&type=speakers&ticker=NVDA&speaker_type=analyst&limit=20" \
-H "X-API-Key: $KEY"
Read the analyst questions. Each question maps to a thesis someone smart already had. Reading them takes 3-4 minutes and is the single highest-EV pre-trade workflow most options traders are skipping.
What this isn't
This isn't a recipe for "edge". The pre-earnings market is well-priced. What the transcript gives you is the ability to make a post-call directional position with much better calibration — turning what was an OTM lottery ticket into a position with a thesis you can defend.
For systematic event-trading, pair the transcript signal with:
- Cross-call comparison (this quarter vs. last four quarters — language drift)
- Cross-sector comparison (is this an idiosyncratic call or a sector-wide pattern?)
Both are one API call away.