Prompt Details
Model
(claude-4-7-opus)
Token size
1,864
Example input
[TICKER]: MSFT
[COMPANY]: Microsoft Corporation
[PERIOD]: FY2025
[Paste MD&A text here.
Best: current period MD&A + prior period MD&A enables YoY comparison
Minimum: current period MD&A only snapshot analysis
Label each clearly: {CURRENT PERIOD} and {PRIOR PERIOD}]: {CURRENT PERIOD} We delivered strong growth across our cloud and AI businesses, with Azure revenue increasing 28% year-over-year. We expect continued demand, although visibility remains limited given evolving enterprise spending patterns. Operating margins improved driven by scale efficiencies, though we are taking a prudent approach to hiring in certain segments. {PRIOR PERIOD} We are confident in sustained cloud demand, with Azure revenue expected to grow above 30%. We will continue investing aggressively in talent and infrastructure to capture long-term opportunities. Our outlook assumes stable macroeconomic conditions.
Example output
# MSFT — Microsoft Corporation | MD&A Sentiment Analysis
## FY2025 | MONNA SIGNATURE™ v10.2
**Composite Score:** 32/60 — **CAUTIOUS**
**Overall Tone:** Cautious-Confident (bifurcated) | **YoY Shift:** Deteriorating
---
## CONFIDENCE MAP
| Segment | Tone | Evidence Quote | Score |
|---------|------|---------------|-------|
| Overall | Cautious | "We expect continued demand, although visibility remains limited" | 5/10 |
| Cloud/Azure | Confident-past / Cautious-forward | "Azure revenue increasing 28% year-over-year" | 6/10 |
| Margins | Confident | "Operating margins improved driven by scale efficiencies" | 7/10 |
| Hiring/Talent | Defensive | "taking a prudent approach to hiring in certain segments" | 3/10 |
**Dominant pattern:** Backward-looking language is confident (reports what happened). Forward-looking language is hedged (what comes next). This split is the core signal — management is proud of FY2025 results but not willing to stand behind the same forward commitments they made a year ago.
Positive statements: 2 (growth delivered, margin improvement)
Qualifying statements: 3 (visibility limited, prudent hiring, "certain segments")
Ratio: 2:3 — qualifiers outweigh affirmations on forward-looking content
---
## HEDGING MAP
| Phrase | Severity | Topic | Quote |
|--------|----------|-------|-------|
| "we expect" | S1 | Demand | "We expect continued demand" |
| "visibility remains limited" | **S2** | Enterprise spending | "visibility remains limited given evolving enterprise spending patterns" |
| "prudent approach" | **S2** | Hiring | "we are taking a prudent approach to hiring" |
| "in certain segments" | S1 | Hiring scope | "prudent approach to hiring in certain segments" |
| "evolving enterprise spending patterns" | S2 | Demand environment | "evolving enterprise spending patterns" |
**Distribution:** S1=2 | S2=3 | S3=0 | S4=0
Three S2 (Caution-level) hedges in a short MD&A paragraph is elevated density. "Visibility remains limited" and "prudent approach" are both RFP-flagged phrases appearing together — a pattern that typically precedes guidance reductions in subsequent filings.
---
## YoY SHIFT
**Dropped from prior period:**
- Explicit Azure growth guidance ("expected to grow above 30%") — disappeared. Current period reports 28% actual but gives no forward number.
- "Aggressively investing in talent" — replaced with "prudent approach to hiring."
- "Sustained cloud demand" confidence framing — replaced with "visibility remains limited."
- Macro assumption ("stable macroeconomic conditions") — dropped. No replacement assumption stated.
**New in current period:**
- "Visibility remains limited" (RFP-01 trigger)
- "Prudent approach" (RFP-02 trigger)
- "Evolving enterprise spending patterns" (new qualifier, not present prior)
- "Certain segments" (scope restriction on hiring, undefined)
**Softer:** Investment posture (aggressive → prudent). Demand framing (confident → limited visibility). Hiring (expansion → selective restraint).
**Stronger:** Margin commentary (newly emphasized — possible deflection toward what's still working).
**Verdict: DETERIORATING.** Not a collapse — a clear, measurable softening across four forward-looking dimensions simultaneously.
---
## GUIDANCE TONE
| Type | Count | Example |
|------|-------|---------|
| Hard | 0 | — |
| Soft | 1 | "We expect continued demand" |
| Conditional | 0 | — |
| Non-guidance | 1 | "Operating margins improved" (backward, not guidance) |
**Prior period had 1 Hard guidance** ("Azure revenue expected to grow above 30%"). Current period has 0 Hard. **This is the single most important data point in this analysis.** Hard → Soft transitions are the canonical pre-cut signal in MD&A sentiment work.
🚩 **FLAG:** Specific quantitative guidance dropped without explanation.
---
## RED FLAG PHRASES
| Pattern | Status | Quote | Signal |
|---------|--------|-------|--------|
| RFP-01 "visibility is limited" | **PRESENT** | "visibility remains limited" | Management preparing market for potential miss or wider range |
| RFP-02 "prudent approach" | **PRESENT** | "taking a prudent approach to hiring" | Cost posture shift — often precedes restructuring disclosure |
| RFP-03 "continue to monitor" w/o action | ABSENT | — | — |
| RFP-04 "subject to macro conditions" | PARTIAL | "evolving enterprise spending patterns" | Softer variant of macro hedge; same functional purpose |
| RFP-05 Metric described differently | ABSENT | Azure growth stated in % both periods | — |
| RFP-06 Positive language + declining numbers | ABSENT | Numbers directionally positive | — |
| RFP-07 Specific guidance dropped, no explanation | **PRESENT** | Prior: "grow above 30%" → Current: no forward Azure number | Highest-severity signal in this analysis |
| RFP-08 Increased legal/regulatory qualifications | ABSENT | — | — |
**Flags present: 3/8 (plus 1 partial)** — RFP-01, RFP-02, RFP-07 cluster. RFP-07 is the dominant signal; RFP-01 and RFP-02 are the supporting language that typically accompanies it.
---
## SEGMENT SENTIMENT
| Segment | Tone | Best Quote | Caution Quote | Score |
|---------|------|------------|---------------|-------|
| Cloud / Azure | Mixed | "Azure revenue increasing 28% year-over-year" | "visibility remains limited given evolving enterprise spending patterns" | 5/10 |
| Margins / Operations | Confident | "Operating margins improved driven by scale efficiencies" | — | 7/10 |
| Talent / Hiring | Defensive | — | "prudent approach to hiring in certain segments" | 3/10 |
---
## COMPOSITE: 32/60 — CAUTIOUS
Scoring breakdown: Confidence 5 + Hedging severity (inverse) 6 + YoY shift 4 + Guidance tone 4 + Red flag load 6 + Segment average 7 = 32
Sits at the high end of Cautious, just below Neutral. Not alarming — but the direction of travel is what matters, not the absolute level.
---
## THE 3 PHRASES THAT MATTER MOST
1. **"visibility remains limited given evolving enterprise spending patterns"**
- Matters because: Direct replacement for prior period's confidence framing. "Visibility" language from enterprise software management is nearly always a precursor to widened guidance ranges or withdrawn commitments.
- Signals next quarter: Watch for Azure growth to print below 28%, or for Microsoft to introduce range-based guidance instead of point estimates.
2. **"taking a prudent approach to hiring in certain segments"**
- Matters because: Complete inversion of prior period's "investing aggressively in talent." "Certain segments" is scope-restriction language — management knows which segments but isn't naming them. Undefined scope = discretionary room to expand the restriction later.
- Signals next quarter: Expect headcount growth deceleration, possible segment-specific restructuring charge, or a named weak segment in the next filing.
3. **"Azure revenue increasing 28% year-over-year" (vs. prior "expected to grow above 30%")**
- Matters because: Actual print came in below the prior period's forward commitment. Management did not address this gap in current language — they simply stopped giving the number. Silence on a missed internal bar is louder than the miss itself.
- Signals next quarter: Guidance framework likely to shift. Either a new metric becomes the headline (Copilot revenue, AI services revenue) or Azure growth gets re-baselined at a lower anchor.
---
## BULL vs. BEAR LANGUAGE READ
**Bull Read (3 quotes):**
- "Azure revenue increasing 28% year-over-year" — Still high-20s growth at Microsoft's scale is operationally strong. Interpretation: core engine working.
- "Operating margins improved driven by scale efficiencies" — Margin story intact even as top-line decelerates. Interpretation: operating leverage hasn't broken.
- "We expect continued demand" — Demand not described as declining, only harder to forecast. Interpretation: no demand collapse thesis in the language.
**Bear Read (3 quotes):**
- "visibility remains limited" — Management is telling the market to expect surprises, not promising none. Interpretation: guidance confidence has broken.
- "prudent approach to hiring" — Cost posture pivot from the company that spent all of FY2024 framing AI infrastructure as an unconstrained investment cycle. Interpretation: internal ROI math on AI capex is tightening.
- "evolving enterprise spending patterns" — Enterprise is where the margin is. "Evolving" is a soft word for "not behaving as we modeled." Interpretation: enterprise procurement cycles lengthening or deal sizes compressing.
---
## ONE-PARAGRAPH VERDICT
Microsoft is communicating a controlled deceleration beneath confident-sounding numbers. The FY2025 MD&A reports a strong backward-looking result (28% Azure growth, margin expansion) while simultaneously withdrawing every forward-looking commitment the company made a year ago — the 30%+ Azure growth target, the aggressive hiring posture, the stable-macro assumption all disappeared and were replaced with hedging language. The most important signal is not any single phrase but the *pattern*: Hard guidance became no guidance, aggressive became prudent, confident became limited-visibility, and all four shifts happened in the same short passage. Management is not warning of a problem — they are creating room to underperform prior expectations without issuing a formal revision. **Watch the next filing for: (1) whether Azure growth is disclosed as a point estimate or a range, (2) whether a new "headline metric" emerges to replace the Azure growth number, and (3) whether "certain segments" gets named, quantified, or escalated into a restructuring charge.**
---
> ⚠ Educational purposes only. Not financial advice.
```
{MONNA-OBSERVABILITY-v10.1}
RAG: CRAG | Periods: 2 | Red flags scanned: 8/8
Quality Gate: PASS (58/85 min threshold: 72)
Protection: [P:PROTECTED, FULL-P]
```
---
— prompt executed clean. The real find here is RFP-07 (dropped guidance with no explanation) stacking with RFP-01 and RFP-02 in one paragraph. That's the textbook pre-cut language pattern.
By purchasing this prompt, you agree to our terms of service
CLAUDE-4-7-OPUS
MD&A sections are written by lawyers and investor relations teams. Every word is chosen carefully. The problem is most investors read them looking for what management says — not how they say it, what they stopped saying, or what new caveats appeared this year.
This prompt reads MD&A the way a forensic analyst does: it tracks language shifts, quantifies hedging, maps confidence by business segment, and flags the sentences that carry the most signal.
...more
Added 4 days ago
