Revenue landed at $2.7B release · L10, about 3% above consensus. GOV reached $21.3B release · L11. The agent flagged ads growth and forward guidance language for review before the CFO prep call.
StreetDesk prepares earnings materials, analyst Q&A, and disclosure-safe messaging from the files your IR team already uses. Agents work fast. Approval stays human.
Revenue landed at $2.7B release · L10, about 3% above consensus. GOV reached $21.3B release · L11. The agent flagged ads growth and forward guidance language for review before the CFO prep call.
Product visual preview
A static HTML source of truth for the new product direction: Office-familiar review flows, visible source trails, approval gates, and an audit journal.
Reg FD-aware review gates·Investor confidentiality preserved·Human approval before distribution·Hash-chained audit journal
StreetDesk ships five building blocks. You write the instructions — the voice, the rules, the escalation paths your team already follows. Each agent runs those instructions exactly.
The orchestrator coordinates whatever team you build. Nothing ships without the approver you name.
“Write in the voice of last quarter's earnings script. Lead with the headline metric. Flag any forward-looking language for IR review.”
“Block the report if any metric lacks a source row. Reconcile this period against last period; flag deltas above 10%. Hold disclosures to the standard we registered.”
“Stress-test every claim. List the three questions our investors will ask. Surface anything a skeptical board member would push back on before they do.”
Instructions are plain text — write them the way you'd brief a new analyst. The agent follows them on every run.
StreetDesk outputs are auditable objects. Each claim links to the file that supports it. Each material action is journaled under the reviewer who approved it.
Revenue $2.7B, about 3% above consensus
IR lead reviewed the DoorDash Q3 briefing and cleared it for CFO prep.
Every action streams to your desk. You can pause any agent at any step or take over the keyboard yourself.
Disclosure flags resolve before external use. The watchlist assembles before IR sign-off. Nothing ships until approval is explicit. Each rule lives in code, not in a prompt.
The journal hashes every action. Your compliance or finance team can trace any distributed report back to the source row that supports it.
Investor Relations teams, CFOs, founders, and finance teams who report to investors. Public companies use it for earnings; private companies use it for board decks, investor updates, and lender packs.
Yes. Each role runs as a separate process with its own instructions, tools, and model. Opus for the orchestrator and narrative. Sonnet for analysis. Haiku for data ingestion. They share the workspace filesystem, not memory.
No. The system has no distribution path that bypasses human approval. The orchestrator stages the briefing and waits. External use only runs after explicit sign-off.
Your earnings release, consensus file, transcript archive, operating model, approved messaging, and disclosure policy. Every figure cites its source inline. Anything unsourced renders as [UNSOURCED] and blocks distribution.
A hash-chained journal of every action taken by every agent, timestamped and signed. The disclosure pack is assembled. They can trace any figure in a distributed report back to the source row.
Yes. Private companies use the same primitives for board decks, investor updates, lender packs, and fundraising updates. The DoorDash demo is public-company earnings because the stakes are easy to see.