AI entity
All 1 tracked stories fall under one category: funding. Accenture is the most frequent co-covered peer, appearing in 1 of the 1 tracked story. Each carries 2 original sources on average. We currently track 1 AI story that mention Lyzr, all published on July 10, 2026.
Last mentioned: Jul 10, 2026
Entity pulse
Coverage balance Positive coverage leads. Positive coverage exceeds negative coverage by 100 percentage points.
Figures are computed live from our source-verified story record — see our methodology for how impact and sentiment are derived.
All 1 tracked stories fall under one category: funding. Accenture is the most frequent co-covered peer, appearing in 1 of the 1 tracked story. Each carries 2 original sources on average. We currently track 1 AI story that mention Lyzr, all published on July 10, 2026.
Computed from the 1 stories linked to this entity, with beat comparisons drawn from all 5 AI stories published in the same date window. Shares are omitted below five stories and comparisons below a twenty-story baseline.
Coverage cohort
Other entities that clear the same relevance threshold in stories also covering Lyzr. Shared-story counts are live from our verified record — not editorial picks.
$100M Series B reportedly in progress
Bloomberg reports that Lyzr is raising a $100M Series B at a ~$500M valuation. The company discloses that its agent handled much of the process, attracting $400M in interest.
Lyzr raises $8M Series A
Rocketship.VC leads the round, Accenture participates, and Henry Ford III joins the board. Agent Sam is used for early investor Q&A.
Lyzr’s AI agent autonomously managed investor due diligence for a $100M Series B, drafting memos and prioritizing $400M in interest. The recursive deployment offers a rare glimpse into the real‑world rigor of agentic AI outside synthetic benchmarks.
Source: Cristian Dina · TechCrunch
Lyzr is linked from 1 story on this site, each scored at or above our 35% relevance threshold — see how these pages are built.
See something wrong on this page — a misattributed entity, a wrong stat, a broken source link? Report a data issue.
