Founded 01
2022 [CO001] Diligence report
Collaborative Robotics
Practical collaborative robots with early field traction but limited disclosure
Collaborative Robotics looks credible as an early practical-robotics platform, but it is still too opaque on economics and customer scale to underwrite aggressively.
Coverage and disclosure
Public coverage is strong enough to confirm founder, funding, office expansion, and early field deployment. Revenue, burn, and contract economics remain undisclosed; valuation is still based on secondary-market signals rather than a fresh financing.
Cover facts
Company profile
Collaborative Robotics is a Santa Clara-based robotics company founded in 2022 by Brad Porter that builds practical collaborative robots for shared workspaces and material handling. Public coverage indicates early field deployments in logistics, a Seattle AI expansion, and a broad investor syndicate led by General Catalyst; however, the company remains opaque on revenue, burn, and exact customer concentration.
- Founded
- 2022-01-01
- Founders
- Brad Porter
- Founding location
- Santa Clara, California, USA
- Headquarters
- Santa Clara, California, USA
- Product
- Practical collaborative robots for shared workspaces, especially logistics and material-handling workflows.
- Customers
- Logistics, manufacturing, healthcare, retail/e-commerce, and selected public-service environments.
- Business model
- Undisclosed; likely a mix of robot sales, deployment services, and support software, with pilots leading to larger deployments.
- Stage
- Series B
- Funding status
- $100M Series B in 2024; more than $140M total disclosed funding.
Executive summary
Top strengths
- Experienced founder with deep Amazon robotics credibility.
- Strong backing from General Catalyst, Sequoia, Khosla, and other strategic investors.
- Early field deployment evidence in logistics rather than a pure lab story.
- Clear positioning around practical collaborative robots instead of humanoid hype.
- Investment in foundation-model AI talent suggests a plausible technical path forward.
Top risks
- Revenue, burn, and gross margin are not publicly disclosed.
- Customer concentration and repeatability are still unclear.
- Shared-space safety and reliability remain central technical risks.
- Hardware-scale capital intensity will keep pressure on future financing.
- Competitive pressure from adjacent robotics and automation substitutes is high.
Open gaps
- Audited revenue and burn data are unavailable.
- Exact customer list, contract terms, and site counts are undisclosed.
- A fresh valuation mark is not publicly available.
- Technical benchmarks for uptime and manipulation performance are missing.
Contents
01Company Overview
1.1 Identity and leadership
Collaborative Robotics is a Santa Clara-based robotics company that presents itself as a builder of practical collaborative robots rather than humanoid showpieces. The public story is anchored by Brad Porter, whose Amazon robotics pedigree is the main founder-market-fit signal and still the most credible single-person explanation for why the company has attracted both strategic and generalist capital. Public profiles also point to a compact team that expanded into Seattle for AI work, plus Teresa Carlson as an advisor. Taken together, the company reads like an early commercial robotics platform with enough technical and investor credibility to matter, but without enough disclosure to underwrite it like a mature operating company.[CO001, CO002, CO003, CO004, CO007, CO009]
| Person | Role | Background | Founder | Key-person dependency |
|---|---|---|---|---|
| Brad Porter | CEO & founder | Former Amazon Robotics VP and Distinguished Engineer | Yes | Very high |
| Teresa Carlson | Advisor | Former Amazon/Microsoft public-sector leader | No | Medium |
| Michael Vogelsong | Foundation Models AI lead | Amazon Deep Learning Technologies co-founder | No | Medium |
| Alfred Lin | Board member | Sequoia partner and former board chair signal | No | Medium |
| Paul Kwan | Board member | General Catalyst MD and new board seat | No | Medium |
Partial public leadership map; board/advisor roles are based on disclosed coverage.
[CO002, CO006, CO007]1.2 Funding and operating scale
The financing story is clear enough to support a refresh: a $30 million Series A in 2023 followed by a $100 million Series B in April 2024, with total disclosed capital now above $140 million. General Catalyst led the later round and a wide investor base doubled down, which matters because robotics hardware rarely wins capital from both strategic and financial backers unless the story has already demonstrated some field traction. The company’s reported headcount remains small relative to its ambitions, with GeekWire describing roughly 40 people and a newly opened Seattle office. That is enough to suggest real execution, but not enough to imply a scaled manufacturing or revenue machine.[CO004, CO005, CO006, CO010]
| Metric | Value / status | Date | Confidence | Gap |
|---|---|---|---|---|
| Founded | 2022 | 2022 | high | Exact month not public |
| Headquarters | Santa Clara, CA | 2024-2026 | high | |
| Employees | ~40 | 2024 | medium | Headcount likely higher by 2026 |
| Series B | $100M | Apr 2024 | high | |
| Total raised | >$140M | Apr 2024 | high | No official cap table |
| Current valuation | Opaque / secondary mark only | 2024-2026 | medium | Use external estimates cautiously |
| Primary founder | Brad Porter | 2022-2026 | high | |
| Known advisors | Teresa Carlson | 2024 | medium | Public advisor list incomplete |
Public facts only; valuation and headcount are secondary estimates.
[CO001, CO004, CO005, CO007, CO008]| Stakeholder | Role | Importance | Diligence ask |
|---|---|---|---|
| General Catalyst | Lead Series B investor | High | How much follow-on support is reserved? |
| Sequoia Capital | Board / major backer | High | What milestone gates the next round? |
| Khosla Ventures | Strategic VC backer | Medium | How much technical commercialization support is active? |
| Mayo Clinic | Strategic investor / pilot ecosystem | Medium | What customer value did it validate? |
| Lux Capital | AI/robotics backer | Medium | What technical milestones are being tracked? |
| Neo / 1984 / MVP / Calibrate | Seed and Series A backers | Medium | How concentrated is ownership across early rounds? |
Stakeholder map is a public-signal summary, not a cap-table reconstruction.
[CO005, CO006]1.3 Milestones and open gaps
The key milestone is not a product launch but a progression from founding in 2022 to first field robots in 2024 and a public AI-team expansion in Seattle soon after. That sequence indicates the company has moved beyond pure research, yet the biggest diligence gaps remain public revenue, exact customer counts, and current valuation. The available secondary-market sources still treat those numbers as opaque or stale, so the report should treat any valuation read-through as a rough mark rather than an underwriting anchor. In practice, the company looks like an early-stage robotics platform with credible capital formation, modest operating scale, and still-limited disclosure.[CO008, CO011, CO012]
Key milestones from founding to first field robots and the Seattle AI expansion.
[CO001, CO005, CO010, CO007]02Market Analysis
2.1 Market definition
Collaborative Robotics is best understood as a shared-workspace automation company: the market is not generic industrial robotics, but robots that can operate near people while handling material movement and task coordination. The company’s own site and co.bot branding emphasize predictable behavior and real-world applicability, while external profiles place it inside mobile manipulation and cobot categories. That matters because the buyer is not just buying a robot arm; they are buying a workflow system that must fit existing safety, facilities, and labor constraints. In practice, the market is constrained as much by facility redesign and operator trust as by pure technical capability.[CM001, CM004, CM009, CM010]
| Lens | What it says | Confidence | Gap |
|---|---|---|---|
| Category definition | Shared-space cobots / mobile manipulators | high | |
| Growth signal | Category is expanding quickly in public market research | medium | Specific TAM varies widely by source |
| Buyer need | Labor relief + ergonomics + throughput | medium | No company-specific win-rate data |
| Adoption gating factor | Safety and workflow integration | high |
Sizing varies by analyst; treat as directional rather than precise.
[CM001, CM003, CM005]2.2 Buyer and adoption thesis
The first budget owner is likely a logistics or manufacturing operator with repetitive material-handling tasks, staffing pressure, and enough process discipline to tolerate a pilot. Public coverage repeatedly ties the category to warehouses, manufacturing floors, healthcare, retail, and service environments where physical strain and throughput matter. The economic case is therefore labor substitution plus ergonomics plus throughput, not a science-project bet on autonomy for its own sake. If the company breaks out, it will be because the robot makes a concrete workflow cheaper or more reliable than human-only execution. A durable market thesis also needs evidence that the robot can be deployed without turning every sale into a custom integration project.[CM002, CM006, CM007, CM010]
| Segment | Why it matters | Adoption posture |
|---|---|---|
| Logistics / 3PL | Best fit for repetitive material movement | Early pilots |
| Manufacturing | High pain, but safety and integration matter | Selective |
| Healthcare / biotech | Potentially attractive but highly process-driven | Pilot-only |
| Retail / e-commerce | Labor pressure and warehouse use cases | Selective |
| Municipal / public services | Possible niche use, not core GTM | Experimental |
Segmentation reflects public positioning, not a disclosed sales pipeline.
[CM002, CM007]| Barrier | Why it slows deals | Mitigation |
|---|---|---|
| Safety certification | Human-adjacent operation requires trust and controls | Barrier testing / safety case |
| Workflow integration | Must fit WMS/WES/ops stack | Systems integration |
| ROI proof | Buyers need payback before scaling | Pilot ROI data |
| Facilities changeover | Brownfield layouts are hard to redesign | Modular deployment |
Barrier analysis is qualitative; no customer-level loss data disclosed.
[CM005, CM006, CM009]2.3 Why adoption remains constrained
The biggest adoption drag is still safety and integration in brownfield environments. Shared-space robot deployments must navigate physical proximity, workflow redesign, and operator trust at the same time, which is why many buyers prefer fixed automation or AMRs when the task can be simplified. Public market pages suggest the cobot category is growing, but that does not mean the category is easy to sell. The diligence question is whether Collaborative Robotics can translate category tailwinds into repeatable deployments with enough ROI evidence to overcome the operational friction. If the answer is yes, the company could ride a broader shift toward human-centric automation; if not, the addressable market narrows sharply.[CM003, CM005, CM008, CM011, CM012]
Directional range for cobot adoption economics and the buyer’s ROI hurdle.
Layer widths indicate hierarchy, not quantitative proportions.
[CM003, CM005, CM006]03Competitors
3.1 Direct competitors
The competitive set is wider than one product category. Public sources point to humanoid robotics startups, mobile-manipulation platforms, and more conventional warehouse automation vendors all pulling budget from the same customer. That means Collaborative Robotics is competing not only with peers that look similar on a slide deck, but also with cheaper or more established automation substitutes that solve the workflow in a narrower way. The practical implication is that product positioning must be crisp: if the robot is “human-capable but not humanoid,” the company has to explain why that is superior to both a humanoid and a simpler AMR-based workflow. In a crowded field, vague positioning usually turns into a pricing problem.[CP001, CP002, CP003, CP006, CP009]
| Competitor | Why it matters | Relative threat |
|---|---|---|
| Humanoid startups | Capture attention and capital | High |
| Mobile-manipulation startups | Closest product adjacency | High |
| Incumbent warehouse automation | Cheaper substitute for many workflows | High |
| Conventional cobot vendors | Feature and price benchmark | Medium |
Positioning is a qualitative map, not a market-share study.
[CP001, CP002, CP003, CP009]| Dimension | Collaborative Robotics | Typical alternative |
|---|---|---|
| Human-adjacent operation | Core pitch | Varies |
| Humanoid form factor | Explicitly de-emphasized | Core pitch for humanoids |
| Workflow integration | Important | Important |
| Deployment speed | Critical | Critical |
| Brand / hype | Moderate | Often high |
Capability comparison is directional because public benchmarks are scarce.
[CP004, CP009]3.2 Moat and readiness
The best defense is likely not a patent wall but a deployment-learning loop: better workflow integration, accumulated customer trust, and operational data that smaller competitors cannot easily clone. Public market pages still do not show an obvious benchmarkable install base or performance leaderboard, which keeps the moat thesis at the level of a hypothesis rather than a proven fact. If the company is winning, it will probably be because it can ship a practical system that looks less glamorous than humanoid competitors but is easier to deploy in a real facility. The moat question therefore hinges on field learning and integration depth more than on branding.[CP004, CP005, CP007, CP010, CP011]
| KPI | Why it matters | Readout |
|---|---|---|
| Deployment count | Proof of repeatability | Opaque |
| Customer retention | Switching cost indicator | Unknown |
| Safety record | Trust and sales enablement | Not fully public |
| Benchmark performance | Differentiation proof | Not public |
No audited KPI pack is public; this is a diligence checklist.
[CP005, CP007, CP010]Qualitative map of the market tension between humanoid hype and practical deployment.
| Item | X (1–4) | Y (1–4) | Context |
|---|---|---|---|
| 1. Humanoid startups | 1 | 4 | High attention, uncertain deployment |
| 2. Mobile manipulation peers | 4 | 3 | Closest competitive overlap |
| 3. Incumbent automation | 2 | 2 | Cheaper and more mature |
| 4. Collaborative Robotics | 3 | 1 | Practical, deployment-first posture |
| 5. Conventional cobot vendors | 4 | 1 | Cheaper but narrower |
| 6. AMR / fixed automation | 1 | 2 | Often lower integration risk |
3.3 Competitive implication
The opportunity is real, but the field is crowded enough that weak execution would quickly erase any first-mover advantage. The company needs repeatable deployments, not just a clever robot concept, and it needs to prove that the non-humanoid positioning is a feature rather than a compromise. In a category that still lacks a universally accepted winner, market share can move quickly once a clearer product-market fit appears. That makes the competitive window valuable but fragile, especially over the next 12 to 24 months.[CP008, CP012]
04Financials
4.1 Funding history
The financing history is the clearest public part of the financial picture. The company completed a $30 million Series A in 2023 and a $100 million Series B in 2024, taking total disclosed capital above $140 million. The syndicate is unusually broad and includes both strategic and generalist investors, which is encouraging but also means the market is still funding the story on future potential rather than on a visible profit engine. The most useful inference from the capital stack is not that the business is mature; it is that the business has enough investor conviction to keep building hardware and field deployments.[CI001, CI002, CI003, CI010]
| Revenue stream | What public sources imply | Confidence |
|---|---|---|
| Hardware / product sales | Likely part of the mix | medium |
| Deployment services | Likely needed for pilots | medium |
| Software / fleet support | Possible but undisclosed | low |
| Recurring maintenance | Likely but unpriced | low |
Revenue model is inferred because no audited financials are public.
[CI006, CI012]| Item | Implication | Status |
|---|---|---|
| Series A | $30M funds early deployments | disclosed |
| Series B | $100M funds scale-up | disclosed |
| Burn rate | Unknown | not public |
| Runway | Unknown | not public |
| Gross margin | Unknown | not public |
No cash-flow statement is public; the map is a diligence proxy.
[CI001, CI002, CI012]Known financing milestones and the implied capital base.
| Item | Value | Context |
|---|---|---|
| Seed / early capital | 10 Approximate seed round | Approximate seed round |
| Series A (2023) | 30 Led by Sequoia | Led by Sequoia |
| Series B (2024) | 100 Led by General Catalyst | Led by General Catalyst |
| Post-money mark | 500 Secondary-market estimate around the Series B | Secondary-market estimate around the Series B |
| Reported total raised | 140 Publicly cited cumulative funding | Publicly cited cumulative funding |
| Current disclosure | 0 No audited financials or public revenue | No audited financials or public revenue |
Seed amount is approximate; total disclosed funding exceeds the charted milestones.
Seed / early capital [CI001]
Series A (2023) [CI001, CI003]
Series B (2024) [CI001, CI003]
Post-money mark [CI004]
Reported total raised [CI002]
4.2 Valuation and capital intensity
External secondary-market pages imply a roughly $500 million mark around the Series B, but the company itself does not appear to disclose a current valuation. That makes valuation analysis directional and dependent on how quickly the company can prove repeatable deployments. The funding cadence, plus the company’s hardware footprint and small team, imply a capital-intensive model that will keep needing milestones before it can look like a self-funding software business. For diligence purposes, the missing operating metrics matter more than the headline funding number. The valuation case remains fragile until the company can show that capital is converting into durable customer expansion.[CI004, CI005, CI007, CI009, CI011]
| Driver | Direction | Why it matters |
|---|---|---|
| Hardware BOM | High cost | Hardware scale-up needs capital |
| Field deployment support | High touch | Raises gross-margin pressure |
| Software attachment | Potential margin lift | Could improve retention |
| Manufacturing scale | Potential cost down | Key to eventual profitability |
Bridge is directional; no public cost stack exists.
[CI005, CI007]4.3 What is still missing
The most important unanswered financial questions are burn, gross margin, unit economics, and whether any customer contracts have moved beyond pilots. Public sources do not provide enough evidence to build a real P&L model. In other words, the company has funding credibility, but not yet financial transparency. That is normal for an early robotics company, but it keeps the underwriting case dependent on product and adoption proof rather than on accounting evidence. In practical terms, this is still a funding-led story rather than a finance-led one. Until those metrics appear, every valuation read-through should stay tentative.[CI006, CI008, CI012]
05Product & Technology
5.1 What the product is
The public evidence points to a mobile collaborative robot built for material handling in shared spaces. The company intentionally avoids a humanoid framing, and that distinction matters: the product is meant to be human-capable and practically useful, not a research showcase. The clearest independent signal is that the robot was already working in a live transload facility by 2024, which indicates the company had moved beyond simulation and into an actual deployment loop. That is still early, but it is materially more credible than a deck-only robotics startup. The main remaining question is whether the same system can be repeated across facilities without a bespoke engineering team.[CE001, CE002, CE005, CE010, CE012]
| Layer | What public sources imply | Why it matters |
|---|---|---|
| Robot chassis / mobility | Mobile collaborative robot | Movement through customer spaces |
| Perception / AI | Multimodal / foundation-model style | Generalization potential |
| Orchestration | Workflow integration layer | Makes the robot usable in operations |
| Safety / interaction | Shared-space operation controls | Required for human-adjacent work |
Architecture is inferred from public coverage, not a formal spec.
[CE001, CE003, CE006, CE007]5.2 How it likely works
The technical story centers on multimodal AI and shared-space behavior rather than on a fully disclosed hardware stack. The Seattle foundation-models team suggests a product strategy built around generalization, natural interaction, and task learning across environments. That could be powerful if it reduces the amount of hand-tuning customers need, but the flip side is that the public spec sheet remains thin. We know enough to say the product is not a science project; we do not know enough to say the company has solved the hard parts of autonomy, manipulation, and uptime at scale. That uncertainty is exactly why the diligence bar stays high.[CE003, CE004, CE007, CE008, CE009, CE011]
| Step | What happens | Risk |
|---|---|---|
| Identify task | Customer selects a repeatable material-flow problem | Selection error |
| Integrate system | Robot is tied into operations / controls | Integration complexity |
| Pilot and tune | Robot learns facility-specific behavior | Long tuning cycle |
| Expand use | Repeat in more zones or shifts | Safety and uptime risk |
This is a diligence workflow, not a disclosed implementation plan.
[CE005, CE007, CE009]5.3 Maturity and diligence gaps
The product appears to be in the deployment phase, not the demo phase, but technical diligence still needs concrete data. The key missing items are payload, sensor stack, autonomy benchmarks, uptime, and SDK or integration detail. Those gaps matter because the company’s differentiation claim depends on repeatability: if the robot only works in a narrow set of environments, then the market is more fragile than the branding implies. A second question is whether foundation-model improvements translate into cheaper deployments or merely more expensive experimentation. In a hardware business, that distinction drives the economics.[CE005, CE006, CE008, CE011, CE012]
| Dependency | Why it matters | Status |
|---|---|---|
| Foundation-model progress | Needed for generalization | Promising but unproven |
| Safety controls | Needed for shared-space deployment | Core requirement |
| Deployment data | Needed to improve autonomy | Likely scarce |
| Customer integration | Needed to scale sales | Likely bespoke |
Dependencies are inferred from public messaging and general robotics practice.
[CE004, CE006, CE011]A layered view of how the product moves from field deployment to repeatable scale.
- Field deployment
- Live use at a transload facility
- Items
- On-site robot activity
- Shared-space safety
- Must work near people
- Items
- Predictable behavior
- AI generalization
- Foundation-model direction
- Items
- Multimodal learning
- Workflow integration
- Customer systems and operations
- Items
- Operations APIs
- Repeatable scale
- Lower-touch deployment path
- Items
- Repeatable deployment
- Open diligence gaps
- Payload, uptime, SDK, benchmarks
- Items
- Missing spec sheet
06Customers
6.1 What customers are visible
The public customer picture is still narrow but real. The company says its first robots were in the field with a global logistics partner in 2024, and third-party coverage points to a transload facility deployment in the Seattle region. That is the kind of evidence investors want because it shows a robot living in a real workflow rather than a demo environment. Even so, the company still does not publish a broad customer roster, which means the report should treat the current base as credible but small and highly concentrated. It is enough to prove a customer exists, not enough to prove a scaled sales engine.[CU001, CU002, CU005, CU007, CU008]
| Segment | Why it fits | Evidence strength |
|---|---|---|
| Logistics / 3PL | Closest to the disclosed field deployment | Strong |
| Manufacturing | Repeatedly mentioned in public positioning | Moderate |
| Healthcare / biotech | Named in program language but less proven | Moderate |
| Retail / e-commerce | Plausible workflow fit | Moderate |
| Municipal services | Publicly claimed but least proven | Weak |
Segment strength is based on public evidence, not contract data.
[CU001, CU003, CU009]| Proof point | Source signal | Status |
|---|---|---|
| Global logistics partner | Company-disclosed field deployment | Confirmed |
| Seattle transload facility | Third-party reporting | Confirmed |
| Hospital / biotech | Program language / pilot references | Plausible but unconfirmed |
| Public customer list | Not disclosed | Missing |
Customer proof is intentionally sparse because the company does not disclose a public reference list.
[CU001, CU002, CU008]6.2 Who the customer is likely to be
The likely first buyers are logistics and manufacturing operators with repetitive material movement, limited labor slack, and enough operational discipline to run pilots. Public market research and case studies consistently show that cobot adoption depends on ergonomics, safety, and local workflow tuning. That means the customer profile is not just “large company”; it is “large enough to absorb integration work and process change.” Healthcare and biotech are possible, but the visible proof remains much stronger in logistics than in other verticals. In other words, the deal cycle probably starts with a pilot and ends with a workflow redesign.[CU003, CU004, CU006, CU009, CU011]
| Risk | Why it matters | Current read |
|---|---|---|
| Single-site concentration | No evidence of broad rollout | High |
| Pilot to production conversion | Many robotics pilots never scale | Unclear |
| Contract opacity | No disclosed contract volumes or terms | High |
| Cross-site expansion | Would validate repeatability | Unknown |
Expansion analysis is qualitative due lack of disclosed contract terms.
[CU005, CU007, CU010, CU012]Pilot-led path from first deployment to repeatable multi-site expansion.
[CU004, CU007, CU012]6.3 Adoption quality and gaps
The key diligence question is whether the company has moved from one notable deployment to a repeatable base of customers and sites. Public sources do not show retention metrics, contract volume, or a broad customer list, which keeps the adoption thesis fragile. The right next step is not to ask “is there a customer?” but “how many sites, how much uptime, and how much expansion?” Without those answers, the evidence still reads like early proof, not scaled proof. The difference between a single pilot and a scalable customer base is the difference between story and business.[CU004, CU010, CU012]
07Risks
7.1 Primary risks
The biggest risks are the ones that usually kill early robotics companies: safety, reliability, and the gap between a good demo and repeatable deployment. Because the robot is meant to work near people, any failure carries a trust penalty that a fenced-off system can avoid. The public literature on collaborative robotics reinforces that point repeatedly; safety is not an add-on, it is the product. On top of that, the company still lacks enough public telemetry to rule out uptime or edge-case failures, which means the downside is not theoretical. Even a single serious incident could reset customer confidence. Investors will price that risk immediately.[CR001, CR002, CR003, CR008, CR009]
| Risk | Severity | Why it matters |
|---|---|---|
| Safety / compliance | Critical | Near-human operation in shared spaces |
| Reliability / uptime | High | Field trust depends on repeatability |
| Commercial scale | High | One deployment does not equal a business |
| Capital intensity | High | Hardware growth consumes cash |
Risk ranking is qualitative and based on public signals.
[CR001, CR004, CR010]| Risk | Mitigation | Kill criterion |
|---|---|---|
| Safety | Limit scope; safety case; rigorous testing | Any material safety incident |
| Reliability | Start with narrow workflows | Persistent downtime or recall |
| Commercialization | Pilot-first GTM | No repeatable conversion |
| Capital | Control burn and capex | Need for emergency financing |
Kill criteria are diligence heuristics, not company guidance.
[CR008, CR011]7.2 Commercial and execution risk
The second risk layer is commercial: can the company turn a few deployments into a repeatable base of customers? Hardware companies often stall because deployments are bespoke, margins are thin, and each new site requires more engineering than sales teams expect. A small team raises the execution stakes because every customer issue can consume founder time. That risk is magnified by capital intensity: if the company needs more hardware, more integration work, or a longer sales cycle than planned, dilution or a reset round becomes more likely.[CR004, CR005, CR006, CR010, CR012]
| Dependency | Exposure | Status |
|---|---|---|
| Founder time | Very high | Small team |
| Customer trust | Very high | Not yet broadly proven |
| Safety evidence | Very high | Incomplete |
| Capital markets | High | Still venture-dependent |
Dependency map is intentionally conservative.
[CR005, CR006, CR007]Qualitative heatmap of safety, commercial, execution, and capital risks.
[CR001, CR004, CR005, CR010]7.3 What would make the risk acceptable
The mitigation path is straightforward in concept: narrower use cases, rigorous safety cases, better field data, and a willingness to slow expansion until the product is reliable. That is not a low-risk plan, but it is a survivable one. If the company can keep deployments narrow and learn quickly, the current risk stack is manageable. If it tries to scale before the product is repeatedly proven, the same stack becomes a company-killer. This is especially true if customers demand certification-like evidence before signing. The faster the company can show credible field telemetry, the easier it becomes to lower sales friction. That makes the next six to twelve months critical.[CR011, CR012]
08Valuation
8.1 How to think about the mark
The best-supported public valuation anchor is still the roughly $500 million mark associated with the 2024 Series B. That is not the same thing as a fresh fundamental valuation, and the difference matters: the company’s public signals are strong enough to suggest venture conviction, but not strong enough to justify a confident late-stage software-style multiple. In other words, the valuation story is real, but it is still a story built on potential and capital formation rather than on visible operating scale. The current mark should therefore be treated as a reference point, not a conclusion. It is a market signal, not a verified intrinsic value today.[CV001, CV002, CV003, CV011]
| Driver | Read | Effect on view |
|---|---|---|
| Funding quality | Strong | Supports continuation |
| Operating opacity | High | Keeps confidence low |
| Deployment proof | Real but limited | Prevents aggressive valuation |
| Customer expansion | Unproven | Caps upside today |
This is a valuation thesis table, not a public market quote.
[CV001, CV003, CV006]| Scenario | Implied stance | What must happen |
|---|---|---|
| Bull case | Buy / stronger | Repeatable deployments and clearer margin path |
| Base case | Track | More deployments, but still opaque financials |
| Bear case | Research more / avoid | Slow adoption or financing reset |
Sensitivity is qualitative because the company does not disclose a full financial model.
[CV004, CV005, CV008]8.2 Upside, downside, and why the stance is cautious
The upside case depends on repeatable deployments, expanding customer sites, and evidence that the product can scale without a one-off engineering tax at each customer. The downside case is a typical hardware trap: adoption slows, burn stays high, and the next valuation round resets lower than the current secondary signal. Because the public data are thin on revenue and customer expansion, the right posture is to track the company and wait for more operating proof rather than assume the current mark is durable. That keeps the view disciplined and avoids false precision.[CV004, CV005, CV006, CV008, CV009, CV010, CV012]
| Range | Interpretation | Confidence |
|---|---|---|
| $500M-ish secondary mark | Most visible current signal | Medium |
| Higher only if expansion proves repeatable | Upside needs operating evidence | Low |
| Lower if adoption stalls or burn rises | Downside on hardware risk | Medium |
This table is intentionally conservative and based on public signals only.
[CV001, CV003, CV012]Qualitative valuation sensitivity showing how operating proof changes the stance.
[CV001, CV003, CV009]8.3 Comparable framing
The comp set should be robotics-first, not software-first. Public pages show that investors and market-data providers still frame the company against other private robotics names with deployment risk and uncertain revenue, which is the right way to think about it. That makes the recommendation modest: the company is investable as a monitored robotics platform, but not yet as a fully underwritten growth asset. Any stronger view would need more customer proof and a cleaner path to gross margin. That also means the nearest comparables are still imperfect and should be used directionally. Markets will update the mark faster than fundamentals do materially.[CV007, CV008, CV011]
Disclaimer
This report is a public-evidence diligence snapshot, not investment advice. Important financial, legal, technical, and contractual facts remain non-public and should be verified directly with management and primary documents before any investment decision.
Evidence index
| ID | Statement | Confidence | Sources |
|---|---|---|---|
| CO001 | Collaborative Robotics was founded in 2022 and is based in Santa Clara, California. | High | SO001, SO002 |
| CO002 | The company is led by Brad Porter, whose prior Amazon robotics background is the central founder-market-fit signal. | High | SO002, SO007 |
| CO003 | Public profiles describe the company as a developer of practical collaborative robots or human-capable mobile manipulators for shared workspaces. | Medium | SO001, SO005 |
| CO004 | GeekWire reported the company employed about 40 people in 2024 after opening a Seattle office for AI research. | Medium | SO007, SO008 |
| CO005 | The disclosed Series B raised $100 million and brought total funding to more than $140 million. | High | SO007, SO008, SO001 |
| CO006 | The latest round was led by General Catalyst with participation from Sequoia, Khosla, Mayo Clinic, Neo, 1984 Ventures, MVP Ventures, Calibrate Ventures, Bison Ventures, Industry Ventures, and Lux Capital. | High | SO007, SO001, SO008 |
| CO007 | The company announced an advisor addition with Teresa Carlson, underscoring go-to-market ambitions beyond pure research. | Medium | SO007, SO008 |
| CO008 | Caplight and the private-market aggregators still show the company as opaque on current valuation and revenue disclosure. | Medium | SO003, SO004, SO005 |
| CO009 | The company’s public narrative emphasizes human-robot collaboration, trustworthiness, and a practical rather than humanoid form factor. | Medium | SO005, SO007 |
| CO010 | Public reporting indicates the first robots were in the field earlier in 2024, before the Series B announcement. | Medium | SO007, SO008 |
| CO011 | The company’s stated target sectors include logistics, manufacturing, healthcare, retail, and municipal services. | Medium | SO001, SO005 |
| CO012 | A material diligence gap remains around exact revenue, customer concentration, and burn because the company does not publicly disclose audited financials. | Medium | SO003, SO004, SO008 |
| CM001 | Collaborative Robotics sits in the shared-space cobot / mobile-manipulation segment, not in classic fixed-arm industrial automation alone. | High | SM001, SM002, SM003 |
| CM002 | The most plausible first buyer is a logistics or manufacturing operator with repetitive material-handling pain and a willingness to run pilots before full-scale rollout. | Medium | SM003, SM008 |
| CM003 | Public market reports still describe collaborative robotics as a fast-growing category with strong AI and sensor adoption tailwinds. | Medium | SM008, SM006, SM007 |
| CM004 | The company’s own public messaging emphasizes “real-world applicability,” predictable behavior, and safer collaboration rather than humanoid spectacle. | High | SM001, SM002 |
| CM005 | Safety, space-sharing, and workflow integration remain the primary blockers to rapid adoption in brownfield facilities. | Medium | SM003, SM008, SM006 |
| CM006 | The likely ROI story is labor substitution, reduced physical strain, and better throughput rather than fully autonomous general intelligence. | Medium | SM001, SM002, SM003 |
| CM007 | Warehouse, manufacturing, healthcare, retail/e-commerce, and municipal services are the recurring verticals mentioned in public sources. | Medium | SM003, SM001, SM006 |
| CM008 | Secondary-market pages still suggest the company is small relative to the broader automation opportunity and that its market position is not yet widely benchmarked. | Medium | SM004, SM005, SM008 |
| CM009 | The cobot market thesis depends on whether AI-driven adaptability can overcome the historical reluctance to place robots in direct human work zones. | Medium | SM001, SM006 |
| CM010 | Adjacent automation substitutes include AMRs, fixed conveyors, human labor, and narrower pick-and-place robots. | Medium | SM003, SM008 |
| CM011 | Dealroom and VCBacked style profiles suggest investors still frame the company as a venture-backed hardware platform rather than a mature category winner. | Medium | SM007, SM008 |
| CM012 | The market story is promising but still underspecified on share capture and concrete replacement economics. | Medium | SM004, SM005, SM006 |
| CP001 | Direct competitive pressure comes from robotics startups and incumbents pursuing mobile manipulation, warehouse automation, or humanoid form factors. | Medium | SP003, SP006, SP008 |
| CP002 | Likely named rivals include Covariant, Figure AI, 1X, Sanctuary AI, Agility Robotics, and other warehouse-automation players. | Medium | SP003, SP006 |
| CP003 | Incumbent and adjacent substitutes include fixed automation, AMRs, human labor, and narrower pick-and-place robots. | Medium | SP001, SP002, SP003 |
| CP004 | The company’s differentiation is a practical collaborative robot that is human-capable but explicitly not a humanoid demo product. | High | SP003, SP002, SP001 |
| CP005 | A likely moat would come from deployment learning, workflow integration, and customer trust rather than from pure mechanical novelty. | Medium | SP004, SP005, SP008 |
| CP006 | Productive Robotics represents a more conventional collaborative-robot automation competitor, useful as an incumbent benchmark for pricing and feature breadth. | Medium | SP001, SP002 |
| CP007 | Private-market aggregators still treat the company as early and hard to benchmark against public comparables. | Medium | SP004, SP005, SP008 |
| CP008 | The competitive field is crowded enough that a weak product deployment cadence would quickly compress perceived differentiation. | Medium | SP003, SP008, SP006 |
| CP009 | The company’s mobile-manipulation framing helps it avoid direct head-to-head comparison with humanoid robot hype, but it does not eliminate substitute risk. | Medium | SP003, SP002 |
| CP010 | Public sources do not show a clearly published performance benchmark or install base that would make the moat obvious today. | Medium | SP004, SP005, SP006 |
| CP011 | A strategic advantage could still exist if the company proves repeatable deployments in logistics before larger peers catch up. | Medium | SP003, SP008 |
| CP012 | The category is still early enough that market-share outcomes remain highly path-dependent, not locked in. | Medium | SP006, SP008 |
| CI001 | The company raised $30 million in Series A funding in July 2023 and $100 million in Series B funding in April 2024. | High | SI003, SI002 |
| CI002 | Public reporting puts total capital raised at more than $140 million, with the later round bringing the company to a larger commercial scale-up phase. | High | SI002, SI004, SI001 |
| CI003 | The Series B investor base includes General Catalyst, Sequoia, Khosla, Mayo Clinic, Neo, 1984 Ventures, MVP Ventures, Calibrate, Bison, Industry Ventures, and Lux Capital. | High | SI002, SI003 |
| CI004 | Caplight and similar private-market pages show a $500 million valuation estimate around the April 2024 Series B, but no current official valuation disclosure. | Medium | SI005, SI006, SI007 |
| CI005 | The company has not publicly disclosed audited revenue, ARR, gross margin, or a run-rate that would support a public-style financial model. | Medium | SI005, SI006, SI008 |
| CI006 | The fundraising language consistently emphasizes field deployment, manufacturing scale-up, and team expansion rather than profitability. | Medium | SI002, SI004 |
| CI007 | The funding cadence suggests a hardware business that remains capital intensive and still dependent on external capital for growth. | Medium | SI003, SI002, SI001 |
| CI008 | Headcount at the time of the 2024 coverage was still around the few-dozen range, which reinforces the early-stage operating profile. | Medium | SI003, SI008 |
| CI009 | The company’s external data pages still frame it as privately held with limited market activity, which is consistent with no public revenue disclosure. | Medium | SI001, SI008, SI007 |
| CI010 | The investor mix combines strategic robotics capital with deep-tech VCs, which usually signals both technical promise and commercialization risk. | Medium | SI002, SI004 |
| CI011 | The range of external valuation pages is still wide enough that any single mark should be treated as directional, not definitive. | Medium | SI005, SI006, SI007 |
| CI012 | Financial underwriting remains blocked mainly by missing burn, gross margin, and contract-revenue data rather than by lack of financing evidence. | Medium | SI001, SI008, SI002 |
| CE001 | Public descriptions frame the product as a mobile collaborative robot built for material handling in shared workspaces. | Medium | SE001, SE006 |
| CE002 | The company and press coverage explicitly describe the robot as human-capable but not humanoid, which is an important design distinction. | Medium | SE002, SE003 |
| CE003 | The AI story centers on multimodal or foundation-model-style perception and interaction rather than on a fully disclosed classical robotics stack. | Medium | SE002, SE003, SE006 |
| CE004 | The Seattle Foundation Models AI team suggests the company is investing in generalization and natural interaction as product differentiators. | Medium | SE008, SE006 |
| CE005 | Public reporting says the robot was already in field use at a transload facility in 2024, which is stronger than a lab-only posture. | Medium | SE006, SE008 |
| CE006 | Safety remains a core design constraint because the robot must work near people and in shared spaces. | Medium | SE001, SE003, SE002 |
| CE007 | The integration layer is likely a workflow orchestration stack that connects the robot to customer operations rather than a standalone point robot. | Medium | SE004, SE005, SE007 |
| CE008 | The company has not publicly disclosed exact payload, sensor stack, or SDK detail, so technical diligence still lacks a formal spec sheet. | Medium | SE001, SE006 |
| CE009 | The practical technology edge is plausible only if the robot can learn varied tasks without requiring an expensive re-engineering cycle for each customer. | Medium | SE003, SE002 |
| CE010 | The company’s public narrative prioritizes trustworthiness, predictable behavior, and real-world applicability over flashy research demos. | Medium | SE001, SE007 |
| CE011 | Public sources do not yet show a published benchmark pack for autonomy, manipulation success, or uptime, which limits technical comparability. | Medium | SE004, SE005, SE008 |
| CE012 | Technical maturity appears above prototype but below fully open, productized platform status because deployment details remain partial. | Medium | SE008, SE006, SE007 |
| CU001 | The company publicly says its first robots were in the field with a global logistics partner in 2024. | High | SU001, SU008 |
| CU002 | GeekWire reported a transload facility deployment in the Seattle region, which is the strongest public sign of real-world use. | High | SU001, SU002 |
| CU003 | The company’s stated target verticals include logistics, manufacturing, healthcare, retail/e-commerce, and municipal services. | Medium | SU001, SU007 |
| CU004 | The Cobot Flywheel / pilot-program language suggests a pilot-led commercial motion rather than an instant self-serve sale. | Medium | SU004, SU008, SU006 |
| CU005 | Customer concentration is probably high because only a handful of names or partner types are publicly visible. | Medium | SU005, SU006, SU007 |
| CU006 | Independent robotics literature and case studies show that cobot adoption depends heavily on ergonomics, safety, and local workflow tuning. | Medium | SU002, SU004, SU001 |
| CU007 | The public evidence is still stronger for “a deployment exists” than for “a repeatable customer base exists.” | Medium | SU001, SU008, SU007 |
| CU008 | Research and industry pages do not reveal any broad customer list, retention metric, or contract volume data. | Medium | SU005, SU006, SU008 |
| CU009 | The company’s likely first customer profile is a process-heavy operator with high labor pain and manageable deployment complexity. | Medium | SU003, SU002 |
| CU010 | The available public case-study style evidence is still too thin to infer net retention or expansion success. | Medium | SU002, SU004 |
| CU011 | A logistics / warehouse deployment is the clearest proof point, while healthcare and biotech remain more aspirational in the public record. | Medium | SU001, SU008, SU007 |
| CU012 | Customer diligence should focus on referenceability, uptime, and whether the robot is on a single site or multiple sites. | Medium | SU005, SU006, SU008 |
| CR001 | Safety and human-adjacent operation remain the most obvious risk because the product is designed for shared spaces rather than fenced-off cells. | Medium | SR002, SR007 |
| CR002 | Robotics literature consistently shows that human-robot collaboration requires careful safety design, sensing, and ergonomic tuning. | High | SR002, SR007 |
| CR003 | Community discussions and GitHub-topic style signals show that reliability and safety concerns are still common in collaborative robotics generally. | Medium | SR001, SR003 |
| CR004 | Commercial risk is high because the company must prove it can scale from a few deployments to repeatable field adoption. | Medium | SR004, SR005, SR006 |
| CR005 | A small team makes the company vulnerable to key-person and execution bottlenecks if deployment complexity increases. | Medium | SR008, SR006 |
| CR006 | Secondary-market pages still show the company as early and difficult to benchmark, which is a risk marker for underwriting confidence. | Medium | SR004, SR005, SR008 |
| CR007 | Customer or partner concentration likely creates outsized downside if a single deployment path stalls or disappoints. | Medium | SR006, SR008 |
| CR008 | The public record does not show enough technical telemetry to rule out uptime, manipulation, or edge-case safety issues. | Medium | SR002, SR003, SR001 |
| CR009 | Regulatory and insurance issues could slow adoption if customers require evidence that the robot can operate safely near people. | Medium | SR002, SR007 |
| CR010 | Any product-market-fit disappointment would be amplified by the capital intensity of hardware and manufacturing scale-up. | Medium | SR004, SR005 |
| CR011 | Mitigation would likely come from narrow use cases, rigorous safety cases, and more field data before broad expansion. | Medium | SR002, SR008 |
| CR012 | The current risk stack is real but not existential if the company can keep deployments narrow and learn quickly. | Medium | SR006, SR008 |
| CV001 | Caplight’s page still shows a roughly $500 million valuation signal tied to the April 2024 Series B. | Medium | SV005, SV006 |
| CV002 | Forbes and Crunchbase both framed the 2024 round as a unicorn-status or near-unicorn moment, which is more hype than exact pricing. | Medium | SV003, SV004 |
| CV003 | The public data do not show a newer official valuation, so the current mark should be treated as stale and directional. | Medium | SV002, SV005, SV009 |
| CV004 | The upside case depends on proving repeatable deployments and a real pathway to scale rather than just one or two high-profile pilots. | Medium | SV008, SV007 |
| CV005 | The downside case is a slow-sales, high-burn hardware path that forces a lower mark before the company can scale meaningfully. | Medium | SV005, SV006, SV009 |
| CV006 | A cautious underwriting stance is justified because the company has financing proof but limited financial transparency and only partial customer evidence. | Medium | SV003, SV004, SV008 |
| CV007 | Comparable companies and market pages imply that valuation should be judged against robotics peers with similar deployment risk, not against software multiples. | Medium | SV007, SV009, SV006 |
| CV008 | Because the company is still early and opaque, the right recommendation is to track the company rather than underwrite it aggressively today. | Medium | SV002, SV005, SV008 |
| CV009 | The market still lacks enough public operating data to support a confident fair-value range with tight error bars. | Medium | SV005, SV006, SV009 |
| CV010 | A more positive view would require repeatable customer expansion, better financial disclosure, and evidence that the product can scale without constant custom engineering. | Medium | SV003, SV008 |
| CV011 | The current public signal is stronger than a stealth startup but weaker than a company ready for a confident late-stage growth mark. | Medium | SV007, SV005, SV002 |
| CV012 | If adoption stalls, the company is exposed to a lower secondary-market mark and a dilution-heavy path to the next financing event. | Medium | SV005, SV006, SV003 |