Back to Forecasting
MDBActive

Will MongoDB provide a specific quantification of AI workload revenue contribution by Q2 FY2027 earnings?

Resolves September 15, 2026(159d)
IG: 0.64

Current Prediction

19%
Likely No
Model Agreement91%
Predictions9 runs
Last UpdatedMarch 2, 2026

Prediction History

Initial
25%
Feb 21
+6pp
Current
19%
Mar 2
Q4 FY2026 earnings update

Management again provided no AI revenue quantification on Q4 earnings call, reinforcing that specific disclosure remains unlikely near-term.

Why This Question Matters

The AI narrative-valuation bridge is the highest-variance element of the investment case (cross-lens insight X2). AI is priced into the valuation as necessary, acknowledged as 'not material' by the CEO, and untested from a unit economics perspective. Any concrete quantification would collapse this triple uncertainty. Disclosure would shift the NARRATIVE_REALITY_GAP assessment (DIVERGING-to-DISCONNECTED on AI) toward ALIGNED if material, or confirm DISCONNECTED if still immaterial.

NARRATIVE_REALITY_GAPEXPECTATIONS_PRICED

Prediction Distribution

0%25%50%75%100%
opus
sonnet
haiku
Range: 15%22%Aggregate: 19%
Individual Predictions(9 runs)
opusRun 1
18%

The Q4 FY2026 earnings call is now a resolved data point: no AI revenue quantification was provided despite vector search customers nearly doubling YoY and Voyage embedding customers doubling since acquisition. This is the most informative update possible — management had every incentive to quantify if the numbers were compelling, and they explicitly declined. CEO CJ Desai's new framing is notably more cautious than prior quarters: he refused to predict enterprise AI adoption timing, citing 2025 as a year that missed expectations. Only two earnings calls remain before resolution (Q1 FY2027, Q2 FY2027). The asymmetric disclosure incentive analysis becomes even more decisive: with vector search customers doubled and revenue still 'not yet a material driver,' we now know that customer count growth has not translated into revenue materiality. The probability of quantification by Sep 2026 has materially decreased from the prior batch's 25%. I estimate 18%.

Q4 FY2026 earnings passed without quantification — highest-information non-eventCEO explicitly more cautious: refused to predict timing, cited 2025 missed expectationsOnly 2 earnings calls remain vs. 3 in prior batch
opusRun 2
22%

This batch incorporates a critical update: Q4 FY2026 earnings have passed with no AI revenue quantification. The resolution window now has only Q1 and Q2 FY2027 earnings calls as opportunities. The calibration lesson from the mdb-fy2027-guidance-above-20 market (guided conservatively at 16-18%) reinforces that management systematically underguides and underdiscloses. However, there is an upside scenario worth weighting at roughly 20-25% probability: CJ Desai, having now established realistic AI expectations in Q4 FY2026, might use the next 2 quarters to proactively quantify an 'AI-native customer cohort' metric — following the pattern set by Salesforce and ServiceNow who disclosed small but growing AI percentages to anchor narrative credibility. The Voyage AI acquisition and Atlas Vector Search create a natural vehicle for such a disclosure. But the base case has shifted further negative: management is more cautious, not less, and the 'not material' language held even as customer counts doubled. I estimate 22%.

Management cautiousness increased post-Q4: strategic shift away from timing predictionsVoyage AI + Vector Search create a future disclosure vehicle but not yet materialPeer disclosure pattern (Salesforce, ServiceNow) remains a tail scenario
opusRun 3
16%

The structural case against quantification has strengthened with the Q4 FY2026 update. Management introduced new language that was more cautious than any prior quarter: 'I do not want to predict it because 2025 was supposed to be that year.' This signals that CJ Desai has learned that overpromising on AI timelines creates credibility risk. The rational response for a new CEO who cares about credibility is to NOT quantify AI revenue until it is unambiguously positive — i.e., to do the opposite of what the resolution question requires. The fact that vector search customers 'nearly doubled' while revenue remains 'not yet a material driver' suggests the monetization pathway from AI customer growth to AI revenue is long. Even if AI revenue triples in the next two quarters, it may remain below the materiality threshold required for management to frame it as a positive catalyst worth disclosing. Two earnings calls remain. The probability centers around 16%.

CEO's new language signals deliberate avoidance of AI timing commitmentsCustomer count growth not translating to revenue materiality — monetization lagStrict resolution criteria require specific numerical disclosure, not directional commentary
sonnetRun 1
19%

Q4 FY2026 earnings just closed without quantification. This is a strong negative signal. With one fewer opportunity remaining and management explicitly retreating from AI timing predictions, the probability is lower than the prior batch's 0.25. The CEO's statement — 'I do not want to predict it because 2025 was supposed to be that year' — is essentially a public commitment to not overpromise on AI. That framing makes proactive AI revenue quantification in the next two quarters unlikely unless the number is overwhelmingly positive. The resolution criteria need a specific number. Management's calibrated approach means they will not offer a small, potentially embarrassing percentage. I estimate 19%.

Q4 FY2026: AI still not material despite doubled vector search and Voyage customersCEO public commitment to avoid AI timing predictions reduces disclosure probabilityOnly Q1 and Q2 FY2027 remain as resolution opportunities
sonnetRun 2
21%

I weigh the updated evidence carefully. Against disclosure: Q4 FY2026 passed with no quantification despite a strong customer growth story (vector search customers nearly doubled), management is explicitly more cautious on enterprise AI timing, and only 2 earnings calls remain. For disclosure: analyst pressure for AI metrics will intensify as peers continue to quantify (Databricks, Snowflake have both disclosed AI workload metrics), and Emergent Labs ($100M run rate, 6M apps) and Eleven Labs ($330M ARR) as disclosed customer examples suggest the AI-native cohort may be approaching a scale worth highlighting. A partial disclosure scenario — such as 'AI-native customers now represent X% of new Atlas ARR' — remains plausible if those customers' growth accelerates sharply in H1 FY2027. But the base case is unchanged: management avoids quantification because the number would be underwhelming relative to the AI narrative supporting the valuation. I settle at 21%, down from 25% in the prior batch.

Peer quantification pressure (Databricks, Snowflake) is a tail upside scenarioEmergent Labs + Eleven Labs examples hint AI-native cohort approaching scaleBase case: quantification would disappoint relative to AI-supported valuation
sonnetRun 3
18%

The Q4 FY2026 update is unambiguous: despite doubled vector search and Voyage customers, revenue from AI workloads remains 'not yet a material driver.' This is the clearest possible confirmation that customer count growth has not driven revenue materiality within the resolution window timeline. The prior batch's debate about whether 3 remaining earnings calls provided enough opportunities has been partially resolved — Q4 passed without disclosure. Now with 2 calls remaining and management explicitly retreating from AI timing predictions, the probability of specific quantification is lower than 25%. The asymmetric disclosure logic remains: if AI revenue were growing fast enough to quantify positively, management would already have done so given the competitive and investor pressure. I estimate 18%, reflecting a moderate downward revision from the prior 0.23-0.25 cluster.

Prior batch's 3 opportunities reduced to 2 — Q4 passed without disclosureAsymmetric disclosure logic unweakened by Q4 dataManagement MORE cautious post-Q4 reinforces non-disclosure base case
haikuRun 1
17%

Q4 FY2026 passed — no AI number provided. CEO explicitly said he won't predict AI timing. Two chances left. Vector search customers doubled but revenue still not material. Strong case for NO. 17% reflects the two remaining opportunities plus small chance of surprise disclosure.

Q4 FY2026 non-disclosure is high-information updateCEO: will not predict AI timing — signals avoidance of quantification2 earnings calls remain as only resolution opportunities
haikuRun 2
15%

Management explicitly more cautious post-Q4. AI still not material despite strong customer growth. Resolution bar is high — needs specific numbers. CEO's language signals deliberate avoidance of AI timing commitments. Only 2 more calls before Sep 2026 resolution. Most bearish estimate in the ensemble at 15%.

CEO increased caution signals strategic retreat from AI timing claimsCustomer growth ≠ revenue materiality — monetization lag confirmed15% reflects low probability given 2 remaining calls and high quantification bar
haikuRun 3
19%

Two reporting periods remain. Q4 FY2026 confirmed AI revenue not material despite vector search customers nearly doubling. CEO tone shifted toward caution — less likely to proactively quantify. Prior batch estimated 24% with 3 remaining calls; updating to 19% with 2 remaining calls reflects both the lost opportunity and the more negative management framing. Small upside from competitive disclosure pressure and possibility of analyst-driven forcing function at Q1 or Q2.

2 remaining calls vs. 3 in prior batch — opportunity count reductionQ4 earnings: AI not material despite customer count doubling, confirming slow monetizationCompetitive disclosure pressure from Databricks/Snowflake is residual upside tail

Resolution Criteria

Resolves YES if MongoDB management provides a specific quantitative disclosure of AI workload revenue contribution (e.g., percentage of Atlas revenue from AI workloads, dollar amount from AI-native customers, or AI-attributed ARR figure) in any earnings call, investor day, SEC filing, or official press release through Q2 FY2027 earnings. Qualitative statements like 'early traction' or 'growing interest' do not qualify. Resolves NO if no specific quantification is provided by the Q2 FY2027 earnings release.

Resolution Source

MongoDB earnings calls, investor presentations, SEC filings, official press releases through Q2 FY2027

Source Trigger

AI workload revenue quantification — any quantification of AI-native customer revenue or workload contribution

myth-meterNARRATIVE_REALITY_GAPMEDIUM
View MDB Analysis

Full multi-lens equity analysis