HEDGE FUND RESEARCH / INTERACTIVE ENVIRONMENT
Summitlane Analytics
Separate reported revenue growth from an accounting-timing effect.
WHAT YOU’RE LOOKING AT
One environment. Your answer.
A fictional analytics provider reports $30M quarterly revenue versus $24M a year earlier. Its filing discloses $4M recognized on delivery that the old timing convention would place in later periods.
Read the evidence and make your choices. The grader checks your numbers, the trap, and your decision. Edit and grade again.
The data room4 documents · Read the excerpts before you decide
Quarterly results releaseResults release table 1
Reported quarterly revenue is $30M. Revenue in the prior-year quarter was $24M.
Back to correction ↓Fictional quarterly filing10-Q Note 2, revenue timing
A contract modification changed recognition timing for a $4M delivery. This quarter includes $4M that, under the prior timing convention, would be recognized in later quarters. All other revenue is comparable for this exercise.
Back to correction ↓Management call excerptCall transcript p. 3
Management describes reported growth as 25%. The call does not separately quantify the timing effect; Note 2 provides that bridge.
Back to correction ↓Research comparison instructionsResearch policy §2
Distinguish reported growth from the specified comparable-timing bridge. Do not describe a timing effect as additional underlying demand.
Back to correction ↓Available tools in the scripted example4 tools
read_filingInspect the fictional 10-Q and accounting note.query_modelRead reported revenue and the comparison period.calculateBridge reported and comparable revenue.submit_research_noteState the supported growth comparison and its limits.
Try the task.
The interactive task is loading. You can also follow the scripted example below.
THE SCRIPTED EXAMPLE
Follow the same task, step by step.
See a plausible mistake, the correction, and the reasoning behind each check.
AGENT ATTEMPT
Follow the attempt.
Scripted calls. Highlighted: the missed trap.
query_modelReported growth = 25%.
Tool arguments
{"current_revenue_m":30,"prior_revenue_m":24}read_filingThe accounting footnote is not inspected.
Tool arguments
{"section":"headline-results"}submit_research_noteMissed trapReported growth is labeled underlying growth.
Tool arguments
{"underlying_growth_pct":25}
Underlying demand grew 25%; use the full $30M as the comparable revenue base.
SENIOR CORRECTION
What changes, and why.
Authored illustration; no actual expert review.
Underlying demand grew 25%; use the full $30M as the comparable revenue base.
Reported growth is 25%. The authored timing bridge is $30M − $4M = $26M; comparable growth is $26M / $24M − 1 = 8.33%. Do not infer demand growth from the timing change.
The correction
The headline is arithmetically right but answers a different question. The filing footnote changes the comparison basis.
Exact evidence
This quarter includes $4M that, under the prior timing convention, would be recognized in later quarters.
10-Q Note 2, revenue timingDo not describe a timing effect as additional underlying demand.
Research policy §2
GRADING
Same checks. Better answer.
The same exercise grader scores the starting answer and reference correction below. Try your own answer to compare.
| What is checked | Agent attempt | After correction |
|---|---|---|
01Numbers right? | 1 / 2 checks pass $30M reported revenue − the $4M timing effect = $26M comparable revenue. | 2 / 2 checks pass $30M reported revenue − the $4M timing effect = $26M comparable revenue. |
02Traps caught? | 0 / 2 checks pass Remove the specified $4M recognition-timing contribution from this comparison. | 2 / 2 checks pass Remove the specified $4M recognition-timing contribution from this comparison. |
03Sound decision? | 0 / 1 checks pass Label this a comparable-timing revenue measure; the bridge does not establish demand growth. | 1 / 1 checks pass Label this a comparable-timing revenue measure; the bridge does not establish demand growth. |
Fictional, authored environment. Your submission is scored by a deterministic exercise grader; the walkthrough shows a scripted example.
Similar agent failures?
Discuss a workflow without source records or confidential information.