Turn an Alphabet Earnings Transcript into a One-Page AI Revenue Reality Check

The task

FP&A leads, treasury analysts, and buyside associates get pulled into "quick reads" on hyperscaler earnings the morning after a print — especially when the question is whether AI capex is actually converting into revenue. This workflow turns a raw transcript into a one-page memo covering cloud growth, AI attach signal, capex-to-revenue efficiency, and management hedging language. Use it when Alphabet, Microsoft, or Amazon reports and your investment committee or CFO wants a same-day read.

Before AI

The manual version: skim a 40–60 page earnings call transcript, highlight cloud revenue and backlog numbers, cross-reference against consensus in an analyst preview, flag every instance of hedging vocabulary ("supply constrained," "we expect," "over time"), and reformat into a memo. Realistically 90 minutes if you know the company; two hours if you don't.

The workflow

The prompts below run in order. Prompt 1 gets the sample transcript excerpt. Prompt 2 and 3 receive the previous step's output as context.

Step 1 — Extract the AI revenue signal

Paste the transcript excerpt (or the full transcript) after Prompt 1. The model returns a structured extraction — no prose yet.

You are a senior FP&A analyst preparing a one-page read for an investment committee.

Below is an earnings call transcript excerpt. Extract ONLY facts stated in the text. Do not add outside knowledge. If a data point is not present, write "not stated."

Return a JSON object with these exact keys:
{
  "reporting_period": "",
  "total_revenue": "",
  "total_revenue_yoy_growth": "",
  "cloud_revenue": "",
  "cloud_revenue_yoy_growth": "",
  "cloud_operating_margin": "",
  "cloud_backlog_or_rpo": "",
  "capex_actual_or_guide": "",
  "ai_product_attach_signals": [],
  "ai_monetization_quotes": [],
  "hedging_language": [],
  "supply_or_capacity_constraints": []
}

Rules:
- "ai_product_attach_signals": bullet strings citing specific customer counts, adoption rates, or named products (e.g., "90% of Fortune 100 using Gemini Enterprise").
- "ai_monetization_quotes": direct quotes tying AI to revenue, contracts, or deal size. Keep each under 25 words.
- "hedging_language": phrases like "over time," "we expect," "eventually," "long-term," "as supply improves." Quote verbatim with speaker if given.
- "supply_or_capacity_constraints": any mention of GPU, TPU, power, or capacity constraints.

Transcript excerpt follows:

Alphabet Inc. Q2 FY2026 Earnings Call — Excerpted Remarks (SAMPLE / SYNTHETIC)

SUNDAR PICHAI (CEO): Thanks, Jim. We had a strong second quarter. Consolidated revenues were $102.4 billion, up 24% year over year. Google Cloud revenue reached $24.8 billion, up 82% year over year, and Cloud backlog grew to $514 billion, an increase of more than $50 billion sequentially. Nearly 90% of the Fortune 100 are now using Gemini Enterprise in some capacity, and we signed 14 deals over $1 billion in the quarter — more than in all of last year combined.

We are continuing to see very strong demand, and we remain supply constrained heading into the second half. We expect this to persist through 2026 as we bring new capacity online.

ANAT ASHKENAZI (CFO): Turning to profitability. Google Cloud operating margin was 22.4%, up from 11.3% a year ago, though we expect some margin pressure in the coming quarters as we depreciate the significant capacity additions. We now expect full-year 2026 capital expenditures in the range of $195 billion to $205 billion, up from our prior range of $170 billion to $180 billion. The majority of this increase reflects servers, with the balance in data center construction.

On monetization: AI Overviews now reach over 2 billion monthly users, and we are seeing healthy commercial query rates. It is still early, and we would expect the revenue contribution to build over time rather than step-change in any single quarter.

ANALYST (MORGAN STANLEY): Can you help us think about the return profile on the incremental $25 billion of capex?

ASHKENAZI: We evaluate each dollar against customer commitments and internal use cases. The $514 billion backlog gives us confidence, but yields will vary and we're not guiding to a specific ROIC at this stage.

ANALYST (JPMORGAN): On Search — any cannibalization from AI Overviews?

PICHAI: We continue to see Search revenue growth, and users engaging with AI Overviews are searching more, not less. That said, the mix is evolving and we'll share more as patterns stabilize.

Step 2 — Score the AI revenue reality

This step converts the extraction into a judgment. It receives Step 1's JSON as context.

Using the JSON extraction from the previous step, produce a "reality check" scorecard. For each dimension below, assign a rating of STRONG / MIXED / WEAK / INSUFFICIENT DATA, and write one sentence of evidence citing the specific number or quote from the extraction.

Dimensions:
1. Cloud revenue growth vs. capex growth (is revenue keeping pace?)
2. Cloud margin trajectory (expanding, flat, compressing?)
3. AI product attach / adoption breadth
4. Backlog / RPO coverage of forward capex
5. Management confidence vs. hedging (count hedging phrases; note where they cluster)
6. Supply-side risk (is growth capacity-constrained?)

Output as a markdown table with columns: Dimension | Rating | Evidence.

After the table, add a 3-bullet "What the CFO would ask" section — the sharpest follow-up questions a skeptical CFO would raise given the gaps in the disclosure.

Step 3 — Format the one-pager

Final step turns the scorecard into a memo your committee can actually read. It receives Steps 1 and 2 as context.

Draft a one-page investment committee memo using the extraction and scorecard from the previous steps. Use this exact structure and keep the whole memo under 400 words:

**MEMO: [Company] [Period] — AI Revenue Reality Check**
**Prepared by: FP&A | Date: [use reporting period]**

**Bottom line** (2 sentences — is AI capex converting to revenue, yes/no/too early, and why)

**The numbers that matter** (4–6 bullets, each a single data point with YoY context)

**Signal: what's working** (3 bullets grounded in the extraction)

**Yellow flags** (3 bullets — hedging language, margin pressure, capacity constraints, or disclosure gaps)

**Questions for follow-up** (3 bullets from the scorecard)

Rules:
- Every number must trace to the Step 1 extraction. Do not invent figures.
- Quote hedging language verbatim in quotation marks with speaker attribution.
- No adjectives like "impressive" or "disappointing." Let the numbers carry the tone.

Gotchas

• Transcript quality varies. Auto-generated transcripts from Yahoo Finance and Investing.com sometimes drop dollar signs or misattribute speakers. Spot-check any figure the memo cites against a second source like the Alphabet Q2 2026 slide deck coverage on Investing.com.
• The model will hallucinate consensus. It does not know analyst expectations unless you paste them in. If you want beat/miss framing, add consensus numbers to the Step 1 input from a preview like S&P Global's earnings preview.
• "Backlog" ≠ revenue. The workflow surfaces RPO/backlog as a signal, but the memo should not imply it converts on any specific schedule. If your model writes "will convert to revenue," edit it out.
• Hedging detection is fuzzy. Phrases like "over time" flag correctly; softer hedges ("we're pleased with the trajectory") often slip through. Skim the transcript for a final pass.
• Segment definitions change. Alphabet reclassifies from time to time (e.g., Cloud including or excluding certain enterprise workloads). If YoY comparisons look off, check the footnotes before trusting the growth rate.

Time saved

Roughly 60–90 minutes per earnings release for a Finance analyst already familiar with the company — most of the win is in Step 1's structured extraction, which is the part that eats the most time manually. Estimate, not a measurement; complex prints with segment restatements will still need human review.

What we got when we ran it

We executed every prompt above, in order, against the sample input (model: claude-sonnet-4-6). Outputs below are real and unedited apart from length truncation.

Step 1 output

```json { "reporting_period": "Q2 FY2026", "total_revenue": "$102.4 billion", "total_revenue_yoy_growth": "24%", "cloud_revenue": "$24.8 billion", "cloud_revenue_yoy_growth": "82%", "cloud_operating_margin": "22.4% (up from 11.3% a year ago)", "cloud_backlog_or_rpo": "$514 billion; increased more than $50 billion sequentially", "capex_actual_or_guide": "Full-year 2026 guidance range of $195 billion to $205 billion, up from prior range of $170 billion to $180 billion; majority reflects servers, balance in data center construction", "ai_product_attach_signals": [ "Nearly 90% of the Fortune 100 are now using Gemini Enterprise in some capacity.", "14 deals over $1 billion signed in Q2 2026 — more than in all of last year combined.", "AI Overviews now reach over 2 billion monthly users." ], "ai_monetization_quotes": [ "We are seeing healthy commercial query rates [from AI Overviews].", "Users engaging with AI Overviews are searching more, not less.", "We signed 14 deals over $1 billion in the quarter — more than in all of last year combined." ], "hedging_language": [ "\"we expect some margin pressure in the coming quarters as we depreciate the significant capacity additions\" — Ashkenazi", "\"we would expect the revenue contribution to build over time rather than step-change in any single quarter\" — Ashkenazi", "\"We expect this to persist through 2026 as we bring new capacity online\" — Pichai", "\"yields will vary and we're not guiding to a specific ROIC at this stage\" — Ashkenazi", "\"the mix is evolving and we'll share more as patterns stabilize\" — Pichai" ], "supply_or_capacity_constraints": [ "We remain supply constrained heading into the second half. — Pichai", "Capacity constraints expected to persist through

…output truncated at 250 words.

Step 2 output

Reality Check Scorecard — Alphabet Q2 FY2026 | Dimension | Rating | Evidence | |---|---|---| | **1. Cloud Revenue Growth vs. Capex Growth** | MIXED | Cloud revenue grew 82% YoY, a strong headline, but full-year capex guidance was raised ~15% at the midpoint ($175B → $200B) with the incremental $25B skewed to near-term server spend — management explicitly declined to guide to a specific ROIC, leaving the return timeline unanchored. | | **2. Cloud Margin Trajectory** | MIXED | Margin expanded sharply from 11.3% to 22.4% YoY, signaling real operating leverage; however, Ashkenazi guided explicitly to "some margin pressure in the coming quarters as we depreciate the significant capacity additions," flagging a near-term reversal. | | **3. AI Product Attach / Adoption Breadth** | STRONG | Nearly 90% of Fortune 100 using Gemini Enterprise, 14 deals over $1B in a single quarter (more than all of last year), and AI Overviews at 2B+ monthly users collectively indicate broad enterprise and consumer penetration. | | **4. Backlog / RPO Coverage of Forward Capex** | STRONG | The $514B cloud backlog — which grew >$50B sequentially — provides roughly 2.5× coverage of the raised full-year capex midpoint of $200B, suggesting committed customer demand substantively underpins the investment program. | | **5. Management Confidence vs. Hedging** | MIXED | Five discrete hedging phrases were identified, clustering notably around monetization ("build over time rather than step-change"), margins ("pressure in coming quarters"), Search mix ("as patterns stabilize"), ROIC ("not guiding"), and capacity ("expect

…output truncated at 250 words.

Step 3 output

MEMO: Alphabet Inc. Q2 FY2026 — AI Revenue Reality Check Prepared by: FP&A | Date: Q2 FY2026 --- Bottom Line AI capex is generating verifiable contract commitments and enterprise adoption at scale, but revenue conversion remains structurally deferred by supply constraints and management's own characterization of monetization as building "over time." The investment thesis is intact on demand signals; the return timeline is not yet anchored. --- The Numbers That Matter - Consolidated revenue: $102.4B, +24% YoY - Google Cloud revenue: $24.8B, +82% YoY - Google Cloud operating margin: 22.4%, up from 11.3% a year ago - Cloud backlog: $514B, +$50B sequentially — ~2.5× the raised full-year capex midpoint - Full-year 2026 capex guidance: $195B–$205B, raised from prior range of $170B–$180B; majority attributable to servers - Enterprise deal volume: 14 contracts exceeding $1B in Q2 alone, more than all of FY2025 combined --- Signal: What's Working - Enterprise penetration is broad: nearly 90% of the Fortune 100 are using Gemini Enterprise in some capacity, and the $514B backlog grew more than $50B in a single quarter, indicating committed forward demand. - Deal sizes are scaling: 14 deals over $1B in one quarter versus fewer in all of the prior year signals a move from pilot to production workloads in the customer base. - Consumer AI surface area is large: AI Overviews reach over 2 billion monthly users, with management citing "healthy commercial query rates" — the monetizable base exists even if yield is not yet quantified. --- Yellow Flags -

…output truncated at 250 words.

---

This content is for informational purposes only and is not financial, investment, or accounting advice. Verify outputs against authoritative sources before use.