HappyRobot

Blends company-claimed operating metrics with independently corroborated funding facts; every row is date-stamped and confidence-graded because scale figures are largely self-reported while valuation and round facts are externally verified.

The public record is founder-rich but governance-light, so the table lists the visible founding trio and flags the undisclosed board and executive layer rather than inventing roles.

Public investor evidence is directionally strong on lead identities but incomplete on ownership percentages, preference stacks, and any secondary activity, so the map emphasizes named participants and control-relevant diligence asks.

Chronology blends company announcements with independent trade and technology reporting; recent scale figures are company-claimed and are retained with date labels alongside the financing and adverse milestones.

Boundary table separates software-addressable workflow automation from broad logistics spend and status-quo labor substitutes; rows are directional rather than exhaustive market taxonomy.

Values use public analyst-market-data snippets in canonical sources; dollar values are USD billions where stated and should be treated as scenario inputs because publisher definitions diverge.

Segmentation is evidence-constrained from HappyRobot positioning, freight-agent workflow guides, and public customer signals; exact budget line ownership varies by account and remains a diligence item.

The table intentionally pairs demand drivers with adoption brakes because fast-growing agent markets can still see high pilot failure or budget cancellation rates.

Non-exhaustive competitive profile synthesized from the chapter signature sources and selected HappyRobot core sources; private companies generally do not disclose complete funding, revenue, customers, or realized pricing.

Cells are evidence-constrained ratings, not benchmark test results; unknowns are preserved where public sources do not disclose feature depth, integrations, security, or realized pricing.

All pricing rows are non-enumeration and evidence-constrained; public sources support absence of comparable list pricing more strongly than actual realized contract terms.

Risk register separates public evidence from private diligence asks; no row assumes exclusivity, exhaustive competitor coverage, or proven switching-cost economics.

Non-enumeration table; monetization units are inferred from public product and traction evidence because HappyRobot does not publish list pricing or contract metrics.

Pricing is treated as partially evidenced: official pages describe the workflow product and traction, while all price points and realized contract economics are private.

Every null or qualitative unit-economics field is intentional: HappyRobot is private and public sources do not disclose the management KPI package needed for CAC, gross margin, or payback modeling.

This table intentionally ranks missing private metrics because public claims are sufficient for a thesis but not for a financing model or investment committee underwriting package.

Funding chronology is restated with local Financials claims and sourceRefs; cash balance, burn, runway, and debt are private and therefore shown as gaps rather than modeled values.

Rows synthesize official product claims, technical documentation, and third-party review signals; maturity levels are public-evidence judgments, not internal roadmap commitments.

Use cases are representative of named public workflow coverage; benefit cells are public signals rather than audited ROI by workflow.

Architecture rows follow the company technical overview; risk cells translate disclosed components into diligence tests.

The table separates current public capability from roadmap items that require management evidence; no public dated roadmap was found in allocated sources.

Public controls are largely company-asserted; the adverse hallucination row is included because safe autonomy depends on both security and output reliability.

Segmentation is based on named customer proof, company-claimed logos, and public use-case descriptions; customer counts by geography, contract value, and vertical revenue mix are not disclosed.

Adoption metrics mix independently corroborated customer-count reporting with company-claimed operating KPIs; missing denominators should be requested before relying on conversion, retention, or expansion estimates.

This is a partial enumeration of public named-customer proof, not a full customer list; rows emphasize cases with workflow or outcome evidence and keep logo-only references separate from production proof.

Durability is inferred from workload depth and company-claimed retention proxies; no public cohort table, renewal schedule, or customer-level economics were found.

Expansion upside and concentration downside are analyzed together because the same few flagship accounts supply much of the public proof and likely influence references, upsell credibility, and valuation support.

Rows are severity ordered and combine official/legal AI Act and FMCSA sources with freight-fraud evidence; public coverage is partial because HappyRobot is private and does not publish its full compliance file.

Operational risks are scored from public product scope and adverse AI/fraud evidence; actual incident rates, false-positive rates, and service-level data require management disclosure.

Concentration cells are public-evidence estimates, not customer-revenue percentages; the key missing evidence is account-level ARR and architecture/vendor dependency detail.

People risks are derived from founder-led public evidence and the operating demands of regulated autonomous workflows; org-chart, retention, and staffing data are private.

Kill criteria translate the chapter's risk register into diligence triggers; thresholds should be replaced with portfolio-specific covenants once management data is available.

The table separates company quality from price risk; anti-thesis rows are not disqualifying unless the named diligence items fail.

Recommendation outputs are derived from public funding/comps evidence and estimated financial inputs; private audited statements could materially change the score.

Scenario math uses rounded ARR multiples, not a full DCF, because HappyRobot does not disclose audited financials, burn, margin, or precise ARR.

Enumeration is a representative public/private comp set built from analyst-market-data and filing sources; multiples are rounded and should be re-cut after audited ARR, revenue definition, and retention are provided.

These are diligence thresholds, not predictions; each trigger ties public uncertainty to a concrete investment action.

The asks are ordered by impact on valuation first, then legal and exit-readiness risk; every item should be requested before any priced commitment.