Botshare
Very young Chinese robot-leasing unicorn candidate with real demand signals but limited disclosure and aggressive valuation.
Botshare addresses a real adoption pain point in robotics, but the company is too young and too lightly disclosed to justify strong conviction at a unicorn valuation.
Cover facts
Company profile
Botshare is a Pudong, Shanghai-based robot-leasing platform that positions itself as a Robot-as-a-Service marketplace and service layer between robot supply, local service partners, and enterprise users. Public materials show strongest early traction in event, retail, restaurant, office, and promotional deployments, while management and policy-linked coverage frame industrial manufacturing, warehousing, logistics, and park operations as the next expansion lane. The company is closely tied to the Agibot ecosystem and reached unicorn-level valuation headlines within months of launch, but public disclosure remains thin on recurring revenue, retention, margins, governance, and unit economics.
- Website
- www.botshare.com
- Founded
- 2025-12-01
- Founders
- Zhiyuan Robotics (Agibot), Flycode
- Founding location
- Pudong, Shanghai, China
- Headquarters
- Pudong, Shanghai, China
- Product
- Robot-leasing platform plus service orchestration layer spanning sourcing, booking, partner fulfillment, insurance, delivery coordination, maintenance, and on-site support.
- Customers
- SMEs, event and retail operators, restaurants, property managers, and early industrial or logistics adopters in China.
- Business model
- Robot-as-a-Service leasing with daily, monthly, and annual rental fees plus deployment, maintenance, insurance, and support services.
- Stage
- Series A
- Funding status
- Series A and A+ financing were reported by May 2026 at a RMB 7 billion valuation, with Crunchbase News rounding the company to a $1 billion unicorn.
Executive summary
Top strengths
- Leasing lowers upfront robot-adoption barriers for SMEs and mid-market customers.
- Launch footprint, partner network, and insured fleet suggest rapid ecosystem assembly.
- Strong China policy tailwinds support RaaS, embodied-AI deployment, and automation experimentation.
Top risks
- Unicorn valuation was reached within months of launch despite no public revenue, margin, or retention disclosure.
- Demand evidence is still skewed toward event, retail, and promotional use cases rather than proven recurring operations.
- Botshare's model is operationally heavy and tightly linked to Agibot, raising execution and neutrality risk.
Open gaps
- Audited revenue, gross margin, burn, and cash-flow data are not public.
- Contract length, renewal, churn, NRR, and top-customer concentration remain undisclosed.
- Board composition, related-party controls, and safety or compliance audit artifacts are not publicly visible.
Contents
01Company Overview
1.1 Identity and business model
Botshare markets itself in English as BOTSHARE and in Chinese as 擎天租, operating as a robot leasing and rental platform rather than a single-robot OEM. Official site copy and launch coverage consistently frame the service as a Robotics-as-a-Service marketplace that connects demand-side customers with supply-side robot makers, service partners, and operators. The near-term product is not a software subscription in isolation; it is a coordinated fulfillment layer that bundles robot selection, booking, on-site deployment, trained operators, and increasingly insurance and maintenance. Launch materials show the company starting from high-visibility scenarios such as retail activations, exhibitions, weddings, receptions, and education, while management says the strategic goal is to migrate into industrial manufacturing, park operations, warehousing, logistics, and other more repeatable workflows. That combination makes Botshare simultaneously asset-light in ownership claims, but operationally heavy in dispatch, local service quality, and uptime execution.[CO001, CO002, CO004, CO005, CO006, CO007]
| Metric | Value / status | Date | Confidence | Source / gap |
|---|---|---|---|---|
| Brand names | BOTSHARE / 擎天租 | 2025-2026 | medium | Official English and Chinese site copy plus launch coverage |
| Legal entity registration | 2025-12-09 | 2025-12 | medium | Reported by Cover News and Baidu Baike; needs registry pull for primary corroboration |
| Public launch | Pudong, Shanghai | 2025-12-22 | high | TechNode and Shanghai government coverage |
| Business model | Robot leasing / RaaS platform | 2025-2026 | high | Official site and financing coverage |
| Launch footprint | 50 core cities | 2025-12 | high | TechNode, Shanghai government, and launch feature coverage |
| Launch service partners | 600+ service providers | 2025-12 | high | TechNode and Sohu launch feature |
| Launch device base | 1,000+ devices | 2025-12 | high | TechNode and Sohu launch feature |
| March deployable robots | 3,000+ | 2026-03 | medium | IPO Zaozhidao/Sina and Baidu Baike |
| March cumulative orders | 5,500+ | 2026-03 | medium | IPO Zaozhidao/Sina and Baidu Baike |
| Latest reported valuation | RMB 7B (~$1B headline) | 2026-05 | high | Multiple May 2026 financing reports; FX translation needs explicit normalization |
| 2026 ecosystem target | 10+ OEMs / 200+ partners / 3,000+ creators / 400,000+ customers | 2026 target | high | Shanghai government and TechNode launch summary |
| Revenue / headcount | Not publicly disclosed | N/A | low | Private-undisclosed; management has not published core financial KPIs |
Figures combine official launch targets with third-party financing and traction coverage. Valuation is reported in RMB and separately rounded to $1B by Crunchbase News.
[CO002, CO003, CO004, CO007, CO021, CO023]The platform sits between robot OEMs, local service partners, creators, and customers, and monetizes coordination rather than pure hardware ownership.
[CO001, CO007, CO009, CO027, CO030, CO031]1.2 Leadership, founders, and governance context
Leadership appears to be split between the Agibot ecosystem and a consumer-internet operating bench. Independent and quasi-reference coverage identifies Jiang Qingsong as chairman, a partner at Zhiyuan AGIBOT, and the legal representative of the Shanghai operating entity. Li Yiyan is consistently identified as chief executive officer and the main spokesperson explaining why the company exists: lowering adoption friction is only the first step, while the harder problem is stable and repeatable service delivery in real production settings. Chinese-language reference material further says the platform was co-founded by Zhiyuan Robotics-related entities and Flycode, and that former Alibaba and Ele.me executives joined in early 2026 to expand operations and strategy. What remains missing is normal late-seed governance disclosure: there is no public board list, no shareholder rights summary, and no disclosed controls around related-party dependence on the Zhiyuan ecosystem. For diligence purposes, founder-market fit is strong, but governance transparency is still thin.[CO003, CO010, CO011, CO012, CO013, CO014]
| Person | Role | Background / ecosystem role | Founder / sponsor link | Key-person note |
|---|---|---|---|---|
| Jiang Qingsong | Chairman | Partner at Zhiyuan AGIBOT; public launch spokesperson | Agibot ecosystem sponsor | Critical for upstream robot supply and ecosystem credibility |
| Li Yiyan | CEO | Public operating spokesperson focused on real-scene delivery and repeatable fulfillment | Co-founder / Flycode link reported by 36Kr | Critical for execution narrative and marketplace build-out |
| Li Liheng | Co-president | Former Alibaba executive, joined February 2026 per Baidu Baike | Hired executive | Signals internet-operations scaling ambition |
| Wang Mingfeng | Chief Strategy Officer | Former Alibaba executive, joined February 2026 per Baidu Baike | Hired executive | Suggests strategy and ecosystem role, but duties not fully disclosed |
| Chen Yanxia | COO | Former Ele.me vice president, reported by Baidu Baike | Hired executive | Operational scaling and city network execution are likely concentrated here |
| Li Kewei | CMO | Founder of Miaozhanggui per Baidu Baike | Hired executive | Brand and scenario commercialization role is lightly documented |
Leadership table relies on a mix of official launch coverage and Baidu Baike aggregation. Public board composition, director independence, and equity-linked voting rights remain undisclosed.
[CO010, CO011, CO012, CO013, CO014, CO015]1.3 Funding history, ownership signals, and early scale
Botshare compressed an unusual amount of financing activity into less than six months of public life. Baidu Baike and March financing coverage point to a January 2026 seed round, a March angel and angel+ package worth more than RMB 100 million at a reported RMB 3 billion valuation, an April Pre-A led by industrial and listed-company capital, and May 2026 A and A+ rounds that multiple outlets say lifted valuation to RMB 7 billion. Crunchbase News separately counted Botshare among May 2026’s new unicorns and listed it at a $1 billion valuation, which is directionally consistent with the Chinese reporting even though the RMB-USD conversion is slightly lower at spot rates. Operationally, public traction metrics are still marketplace-style rather than financial: 50 core cities at launch, 600-plus service providers, more than 1,000 devices initially, more than 3,000 deployable robots by March 2026, and more than 5,500 cumulative orders. These are meaningful network-effect indicators, but they are not substitutes for disclosed revenue, margins, or utilization.[CO015, CO016, CO017, CO018, CO019, CO020]
| Stakeholder | Role / round | Why it matters | Evidence status | Diligence ask |
|---|---|---|---|---|
| Zhiyuan Innovation (Shanghai) Technology | 55% shareholder per Baidu Baike | Implied control anchor and supply-side ecosystem owner | Single-source reference only | Pull registry records and shareholder agreement |
| Zhiyuan Qingtian partnership vehicle | 20% shareholder per Baidu Baike | Likely management or strategic holding layer | Single-source reference only | Confirm GP/LP composition and voting rights |
| Hangzhou Flycode leasing partnership | 15% shareholder per Baidu Baike | Explains Flycode co-founding link and operating collaboration | Single-source reference only | Confirm beneficial owners and related-party economics |
| Qingtian Guangying partnership | 10% shareholder per Baidu Baike | Residual equity pool / incentive structure signal | Single-source reference only | Confirm whether this is employee or strategic equity |
| Hillhouse Venture Capital | Reported seed lead investor | High-signal institutional validation very early in company life | Reported by Baidu Baike aggregation | Obtain original seed announcement or term sheet summary |
| Fosun Venture Capital / Muhua Kechuang / Dafeng-linked capital | Reported seed participants | Connects the company to industrial and state-linked networks | Reported by Baidu Baike aggregation | Verify exact ticket sizes |
| Dayang Motor / Muhua Kechuang / Minzhuo Jidian | Angel / angel+ lead investors | Shows listed-company and industrial-buyer ecosystem interest | Reported by Sina and Baidu Baike | Confirm board or observer rights |
| CP Robotics / Changxin / Meig Smart / Lens Technology | Pre-A industrial investors | Potential channel, procurement, and ecosystem leverage beyond cash | Reported by 36Kr and Sina | Map any commercial exclusivity or preferred access |
| Unspecified A and A+ investors | Latest May 2026 round participants | Important because valuation step-up happened here | Public round amount is vague | Request full investor roster and post-money cap table |
This table mixes public financing reports with a secondary ownership summary. Botshare disclosed headline valuation signals, but not a full official cap table or round-size ledger.
[CO015, CO016, CO017, CO018, CO019, CO020]Point-in-time operating and financing markers that matter most for later diligence chapters.
[CO021, CO023, CO024, CO026, CO027, CO028]1.4 Milestones, operating footprint, and immediate execution risks
The milestone pattern since December 2025 is clear: launch the platform in Shanghai, use early financing to build a national service network, add ecosystem services such as insurance, and then broaden the platform with strategic partners such as JD.com and Rui’an Office. Public sources also show that management is trying to move the narrative away from “robots at events” toward broader operational workflows. However, the same evidence already surfaces the main execution risks. Sohu’s June 2026 analysis argues that falling rental prices compress the arbitrage opportunity for pure marketplace operators and make logistics, maintenance, insurance, and recovery the real moat. Xinhua adds that current demand is still heavily entertainment-led, that repeat customers remain scarce, and that current deployments often still need one operator per robot. In other words, Botshare reached visibility and headline valuation quickly, but the company still has to prove that its service network can support industrial-grade utilization and sustainable unit economics instead of novelty-led growth.[CO018, CO023, CO034, CO035, CO036, CO037]
| Date | Event | Type | Amount / status | Participants | Implication |
|---|---|---|---|---|---|
| 2025-12-09 | Qingtian Rent (Shanghai) Technology registered | founding | Registered capital RMB 10M reported | Legal representative Jiang Qingsong | Formal legal start predates public launch |
| 2025-12-22 | BOTSHARE / 擎天租 publicly launched in Shanghai | product | Platform launch | Jiang Qingsong, Zhiyuan ecosystem, service partners | Created the national robot-leasing narrative |
| 2025-12-22 | 1234 strategy announced | scale | 2026 target stack published | Botshare management | Provides the canonical target set reused in later coverage |
| 2026-01-15 | Seed round announced | financing | Round size undisclosed | Hillhouse Venture Capital and other reported participants | Started the financing cadence before commercial scale was proven |
| 2026-03-18 | Angel and angel+ rounds announced | financing | RMB 100M+ cumulative; RMB 3B valuation reported | Industrial and entertainment investors | Funded city-network rollout and platform upgrades |
| 2026-04-24 | First embodied-robot insurance claims completed with PICC | partnership | 1,000+ robots insured; RMB 200M+ coverage | Botshare and PICC | Added trust and loss-absorption infrastructure |
| 2026-04-29 | Pre-A round disclosed by 36Kr | financing | Several hundred million RMB reported | CP Robotics, Meig Smart, Lens Technology and others | Brought in industrial capital and hardware-adjacent partners |
| 2026-05-06 | Rui’an Office partnership announced | partnership | Use-case deployment | Botshare and Shui On WorkX | Signals premium commercial-space experimentation |
| 2026-05-20 | A and A+ rounds announced | financing | Several hundred million RMB; RMB 7B valuation | Botshare and unnamed latest investors | Established unicorn headline positioning |
| 2026-05-21 | JD cooperation announced | partnership | Online and offline service integration | Botshare and JD Group | Adds logistics, maintenance, recycling, and transaction infrastructure |
| 2026-06-09 | Crunchbase News lists Botshare among new unicorns | governance | $1B valuation headline | Crunchbase News editorial team | Provides global-market recognition of unicorn status |
| 2026-06-11 | Sohu analysis highlights falling prices and heavy operations burden | adverse | Risk signal, not funding | Sohu commentary | Marks visible skepticism about unit economics |
Milestones intentionally combine company-building events, financing, ecosystem additions, and the first adverse market commentary so later chapters can reuse one chronology of record.
[CO003, CO004, CO017, CO018, CO019, CO021]Public milestones from incorporation through unicorn-label recognition and the first visible skepticism about operating economics.
[CO003, CO004, CO017, CO018, CO019, CO021]1.5 Exhibits
02Market Analysis
2.1 Market boundary and sizing lenses
Botshare does not compete in the entire robotics economy. Its addressable market is narrower and should be defined as robot access and deployment spend where a customer chooses temporary use, pay-per-project service, or operating-lease style access instead of outright hardware ownership. In practice, that means event and activation rentals, retail and reception deployments, short-duration education and tourism use cases, and a future wedge into warehouse, park, inspection, and industrial workflows where customers want robot capability without immediate capex. Multiple Chinese 2025-2026 sources cluster around a similar short-term market estimate: about RMB 1 billion of domestic robot-rental volume in 2025 and roughly RMB 10 billion in 2026, implying a tenfold jump during the first year of broad commercialization. That rental niche remains tiny relative to the wider industrial and service robotics economy, but it is strategically important because it acts as the trial, distribution, and data-collection layer that can accelerate adoption of more expensive hardware.[CM001, CM002, CM003, CM004, CM005, CM006]
| Segment / category | Included spend | Excluded spend | Buyer / payer | Relevance to Botshare |
|---|---|---|---|---|
| Event and activation rentals | Short-duration robot hire, operators, choreography, delivery | Permanent hardware purchases | Event agencies, brands, mall operators | Current demand core |
| Retail / reception deployments | Temporary or recurring service packages for stores, offices, lobbies | Long-term owned service robot fleets | Store operations, facilities, commercial real-estate teams | Near-term expansion path |
| Education / tourism / exhibitions | Scenario-based rentals for demos, museums, training, attractions | Education hardware purchases unrelated to renting | Schools, museums, tourism venues, expo organizers | Important demand bridge for trial use |
| Warehouse / logistics pilots | AMR, sorting, handling, inspection, and pilot deployments via service model | Warehouse capex purchases and full integrator capex projects | Operations, logistics, warehouse managers | Future growth wedge |
| Industrial and park operations | Inspection, maintenance, assistance, and repetitive support tasks via service contract or lease | Industrial robot hardware sales and components | Plant operations, engineering, industrial parks | Strategic longer-term upside |
The market boundary focuses on access-and-deployment spend rather than all robotics revenue. Excluded categories matter because Botshare is a commercialization layer, not a full-stack robot OEM.
[CM004, CM010, CM011, CM012, CM013, CM014]| Lens | Geography / year | Value | Methodology / publisher | Confidence | Limitation |
|---|---|---|---|---|---|
| Chinese robot-rental market (current) | China 2025 | ~RMB 1B | Shanghai government, Xinhua, Seetao, City News Service | medium | Projection-heavy and still niche |
| Chinese robot-rental market (next-year) | China 2026 | ~RMB 10B | Xinhua, Seetao, City News Service, RoboHorizon | medium | Forward-looking estimate, not audited revenue |
| China robotics industry revenue | China 2024 | ~RMB 240B | SCIO/Xinhua explainer citing MIIT | medium | Broader robotics industry, not rental niche |
| Global industrial robotics market | Global 2026 | USD 54.28B | Mordor Intelligence | medium | Analyst model, not China-specific |
| APAC industrial robotics share | APAC 2025 | 44.36% of global revenue | Mordor Intelligence | medium | Regional proxy, not China-only |
| Global robotics market | Global 2026 | USD 88.27B | Mordor Intelligence | medium | All robotics, much broader than Botshare |
| APAC robotics market | APAC 2025 | USD 42.33B | Market Research Future | medium | Regional forecast, not China rental TAM |
This chapter uses multiple sizing lenses rather than a single TAM claim because direct China-only robot-rental market datasets remain scarce and projection-based.
[CM001, CM002, CM003, CM022, CM023, CM024]Botshare’s realistic market sits on top of the far larger robotics economy: a small rental niche inside a much larger robotics stack.
[CM002, CM022, CM023, CM030, CM035]The directly Botshare-relevant market is small but accelerating, with pricing and volume expanding faster than stable unit economics.
[CM001, CM002, CM007, CM008]2.2 Buyers, users, payers, and adoption path
The buyer map is heterogeneous. Near-term demand is led by event organizers, malls, tourism venues, retailers, schools, and marketing teams that value novelty, traffic generation, and short-duration staffing alternatives. In these cases, the buyer and payer often sit in brand, event, or store-operations budgets rather than factory capex committees. The next layer includes facilities managers, office operators, commercial landlords, and park operators that may care more about recurring reception, patrol, or cleaning workflows. Only after those layers does the market begin to overlap with industrial and logistics buyers, where procurement logic changes materially: operations, engineering, and warehouse managers need uptime, safety, and integration rather than spectacle. Several sources explicitly frame robot leasing as a low-risk trial mechanism for customers and a real-world feedback loop for manufacturers. That is why adoption funnels tend to start with one-off projects, move into repeat service packages, and only then become candidates for standardized operational budgets. The pathway is intuitive, but repeatability remains unproven in many categories.[CM004, CM005, CM006, CM007, CM012, CM013]
| Segment | Buyer | User | Payer / budget owner | Workflow | Adoption trigger |
|---|---|---|---|---|---|
| Events and weddings | Agency or organizer | On-site operators and guests | Marketing / event budget | Stage, greeting, novelty performance | Need for short-duration spectacle without purchase |
| Retail promotions | Brand or store manager | Store staff and customers | Trade marketing / local operations budget | Footfall and engagement campaigns | Traffic generation and differentiation |
| Education and tourism | School, museum, venue operator | Teachers, students, visitors | Program or venue operating budget | Interactive demos and guided experiences | Trial demand and audience engagement |
| Commercial offices / parks | Facilities or landlord | Reception, patrol, service teams | Facilities or property-operations budget | Front-desk, tour, or amenity services | Labor substitution and premium tenant experience |
| Warehousing and logistics | Warehouse or ops manager | Pick, sort, or support teams | Ops budget or pilot automation budget | Sorting, movement, inspection, repetitive assistance | Low-risk pilot before capex commitment |
| Industrial services | Plant or engineering manager | Maintenance / line-support teams | Capex, Opex, or innovation budget | Inspection, maintenance, repetitive support tasks | Need for uptime with lower initial commitment |
Buyer, user, and payer are often separated in robotics adoption. Botshare benefits when temporary use or pilot budgets can avoid a formal hardware procurement cycle.
[CM004, CM005, CM006, CM012, CM013, CM014]Near-term buyers are mostly non-industrial, while industrial and logistics demand requires stronger service reliability and ROI proof.
[CM012, CM013, CM014, CM038, CM039]The market still begins with demonstration demand, but durable value requires progress toward repeat operational use.
[CM004, CM006, CM014, CM025, CM040]2.3 Policy support and structural demand drivers
The broader robotics backdrop is unusually favorable in China. IFR, Statista, and SCIO/Xinhua materials all show that China is already the world’s largest industrial robotics market by stock and annual installations, while national policy is now deliberately steering the sector from traditional automation toward embodied and intelligent robotics. The June 2026 MIIT-SASAC action plan is especially relevant for Botshare because it explicitly names industrial, service, and special-scenario deployments across manufacturing, inspection, maintenance, warehousing and logistics, retail, healthcare, and emergency response. It also encourages commercial innovation such as Robot-as-a-Service, operating leases, and pay-by-effect models to reduce user investment thresholds. In parallel, China’s standard-setting effort, real-scenario training infrastructure, open data programs, and shared testing bases are intended to shorten the path from demo to deployable product. For Botshare, these policies matter less because they hand it subsidies directly, and more because they widen the set of scenarios in which renting a robot can become institutionally acceptable procurement behavior.[CM014, CM015, CM016, CM017, CM018, CM019]
| Driver / constraint | Direction | Timing | Implication for Botshare | Diligence ask |
|---|---|---|---|---|
| High upfront robot prices | Positive for rental demand | Immediate | Leasing lowers trial barrier for SMEs and short-duration users | Model average customer ROI vs outright purchase |
| Price correction in rental market | Negative for margins | Immediate | Shrinks simple arbitrage economics and increases need for service moat | Track gross margin after fulfillment |
| MIIT/SASAC 2026 scenario push | Positive | 2026 onward | Widens enterprise acceptance of real-scenario deployment | Map target sectors and qualification requirements |
| National standards system | Positive | 2026 onward | Could reduce fragmentation and improve interoperability over time | Identify timing of usable standards adoption |
| Industrial robot scale in China | Positive | Structural | Creates supply depth, domestic manufacturing, and service ecosystem density | Determine whether Botshare can access enough OEM supply |
| Humanoid maturity limits | Negative | Near to medium term | Factory and household scale-up likely slower than hype suggests | Separate demo demand from repeat operations |
| After-sales service expectations | Constraint | Current | Users want better software, performance, and support | Benchmark service partner quality and repair SLA |
| Need for real-world data and training loops | Positive but costly | Current | Platforms that aggregate deployments can improve products and collect data | Check whether Botshare owns or merely passes through data rights |
The market is driven by lower threshold access and policy support, but monetization depends on service quality, standards maturity, and whether novelty demand converts into repeat operations.
[CM005, CM006, CM014, CM016, CM018, CM020]2.4 Constraints, timing, and commercialization risks
The market is expanding, but the friction is obvious in the source base. IFR is explicit that humanoids should not be confused with mature industrial robots: high-speed precision manufacturing will keep using specialized industrial systems for the foreseeable future, and wide humanoid adoption in factories or households is still a later-plan outcome, not a near-term baseline. IDC adds a different bottleneck from the demand side: users broadly accept the value proposition of industrial robots, but still want better performance, software, after-sales service, and easier systems integration. Sohu’s June 2026 rental analysis shows the commercial consequence of those gaps. As supply increases, rental prices fall quickly, shrinking the spread economics available to simple matchmakers and shifting differentiation toward logistics, maintenance, insurance, choreographing, repair, and recovery. In short, Botshare’s market opportunity is real, but the investable version of that market depends on whether platforms can turn show-driven demand into repeatable service workflows before price compression destroys margins.[CM008, CM009, CM018, CM021, CM022, CM023]
2.5 Exhibits
03Competitors
3.1 Domestic platforms and OEM-linked channels already contest the same access layer
Botshare’s Chinese direct landscape is broader than a simple list of lookalike rental apps. The category now includes a second platform-style aggregator in Wanjiyi Rental, retailer-led distribution through JD’s self-operated robot rental launch and JoyInside ecosystem, and OEM-linked booking channels that let customers rent Unitree machines directly with delivery, operator support, and damage cover. That matters because Botshare’s current value proposition is not exclusive robot IP; it is convenient access, city-level dispatch, and bundled service. Wanjiyi copies the marketplace logic directly, while JD and Unitree-linked channels attack it indirectly by combining rentals with retail discovery, logistics, financing, and after-sales service. The result is a domestic field where Botshare may have strong brand momentum, but does not yet own the national standard for how a customer books, receives, repairs, or returns a robot.[CP001, CP002, CP003, CP004, CP005, CP006]
| Competitor / channel | Category | Scale / adoption signal | Target segment | Differentiation | Limitation |
|---|---|---|---|---|---|
| Botshare | Open robot-rental platform | 50-city launch footprint and 600+ service providers in public launch coverage | Events, retail, education, and aspirational industrial/logistics use cases | Multi-brand access plus delivery, operators, insurance, and programming | Public proof of repeat industrial wins is still thin |
| Wanjiyi Rental | Domestic platform-style aggregator | Launched Jan. 2026 as a full-scenario robot-rental ecosystem platform with city-partner expansion | Service, cleaning, companionship, performance, education, families, SMEs | Alliance model combining hardware makers, finance, insurance, and mini-program ordering | Scale and quality consistency are still early-stage in public evidence |
| JD robot rental / JoyInside | Retailer- and infrastructure-led channel | 27 JD MALL stores, self-operated rentals, 10M-device JoyInside target, 50+ city repair ambition | Consumers, enterprises, retail, education, logistics-adjacent users | Combines discovery, transaction, logistics, repair, insurance, and recycling | Economics of the rental layer itself are not publicly disclosed |
| ZMProbots / Unitree G1 rental | OEM-linked direct rental page | Online booking with self-service and full-service event packages | Events, creators, agencies, short-term demos | Direct access to flagship humanoid hardware with delivery and operator options | Single-brand focus and event-centric framing |
| Futurobots / Unitree Go2-A2 | OEM-linked robot-dog rental channel | 1,370+ customers in 65+ countries; 7-day minimum rental | Industrial inspection, education, events, R&D pilots | Delivery, pickup, training, damage cover, and SDK-friendly models | Primarily quadruped focus rather than broad humanoid marketplace |
| Locus Robotics | Warehouse RaaS substitute | Hundreds of deployments cited on official page | Warehouses and fulfillment operators | Subscription robotics with deployment, maintenance, analytics, and flexible fleet scaling | Not built for short-term public event rentals |
| inVia Robotics | Warehouse RaaS substitute | Throughput-based subscription and remote robotics operation center | Warehouse operators seeking goods-to-person automation | Pay-for-productivity model with software plus remotely managed robots | Use case is narrower than a general multi-scenario rental marketplace |
| Vecna Robotics | Warehouse RaaS substitute | Annual-fee model with 24/7 monitoring and SLA framing | Material handling and warehouse operations | Transparent annual-fee RaaS with maintenance and support included | Focused on internal logistics, not broad commercial activation demand |
| Geek+ | Warehouse automation substitute | Global modular solutions for eCommerce, 3PL, retail, pharma, and grocery | Distribution centers and warehouses | Modular robotics across picking, sorting, replenishment, pallet handling, and transport | Public rental or daily-pricing transparency is low |
| ABB / KUKA / FANUC service channels | Industrial incumbent substitute | Large global service networks, lifecycle support, and dense installed bases in factories | Plant engineers, integrators, and industrial buyers | Installed-base trust, maintenance, training, modernization, and support depth | Less flexible than open rental for one-off or short-duration scenarios |
Rows prioritize the competitive routes most relevant to Botshare: another domestic platform, retailer/OEM-linked channels, global warehouse RaaS substitutes, and incumbent industrial service channels.
[CP001, CP002, CP003, CP004, CP005, CP007]Ordinal map of the routes most likely to intercept Botshare demand before it hardens into durable platform share.
Axes are ordinal scores based on evidence quality, service maturity, and job overlap rather than published market share or revenue data.
[CP023, CP027, CP029, CP030, CP033, CP034]3.2 Global RaaS and logistics substitutes are operationally more mature in warehouses
For logistics or warehouse buyers, the most relevant substitute is often not another humanoid-rental marketplace at all. Locus, inVia, Vecna, and Geek+ sell or operate recurring automation programs whose promise is throughput, uptime, and labor productivity inside real fulfillment environments. Those vendors do not need to win the same event-rental demand that powers much of China’s near-term humanoid excitement. They only need to persuade a warehouse manager that subscription robotics with monitoring, software, maintenance, and fast scaling is safer than experimenting with a general-purpose rental platform. That makes Botshare’s industrial and logistics expansion structurally harder than its commercial-show expansion: in those buyers’ eyes, the benchmark is no longer “Can I book a robot quickly?” but “Can this provider hit SLAs, integrate into my workflow, and keep the fleet running at predictable cost?”[CP012, CP013, CP014, CP015, CP016, CP027]
| Company / channel | Public short-term rental | Multi-brand access | Warehouse / logistics fit | After-sales depth | Industrial trust | Best-fit buyer |
|---|---|---|---|---|---|---|
| Botshare | Strong | Strong | Moderate | Moderate | Low-Moderate | Commercial buyer testing robots without purchase |
| Wanjiyi Rental | Strong | Strong | Low-Moderate | Moderate | Low | SMEs or institutions wanting broad scenario choice |
| JD / Unitree channels | Strong | Moderate | Moderate | Strong | Moderate | Buyers who value retail access plus repair/logistics |
| Locus Robotics | Low | Low | Strong | Strong | Moderate | Warehouse operators wanting subscription automation |
| inVia Robotics | Low | Low | Strong | Strong | Moderate | Fulfillment operators paying for throughput gains |
| Vecna Robotics | Low | Low | Strong | Strong | Moderate | Material-handling teams buying uptime and SLAs |
| ABB / KUKA / FANUC | Low | Low | Strong | Strong | Strong | Factories prioritizing proven service relationships |
The matrix separates short-term booking convenience from logistics fit and industrial trust because those are the clearest buyer trade-offs in the source set.
[CP005, CP007, CP009, CP010, CP011, CP012]| Company / channel | Public pricing signal | Contract model | Included capabilities | Unknowns | Implication |
|---|---|---|---|---|---|
| Botshare | Public coverage ranges from sub-CNY2,000 promotions to premium custom packages | Short-term rental and scenario package model | Robot, delivery, operators, insurance, and custom programming depending on package | Take rate, realized margin, and utilization are private | Competes on packaged service breadth more than pure listing fees |
| Wanjiyi Rental | No clean public list price found | Platform-style rental with alliance-backed support | Robot matching, standardized O&M, ecosystem alliance enablement | Realized pricing and partner economics remain undisclosed | Positioning pressure comes from broad scenario coverage, not transparent prices |
| JD / Unitree channels | Official rental launch disclosed flexible daily or long-term access, but not a stable rate card | Retailer-led rental plus after-sales infrastructure | Discovery, booking, logistics, repair, insurance, recycling, and data services | Unit economics between retail and rental layers are private | JD can compete even without the clearest public day-rate table |
| ZMProbots / Unitree G1 | From $299/day self-service or about $1,875/day full-service event package | Direct rental page with self-service or operator-led event package | Delivery, collection, protection cover, and optional trained operator | Cross-country pricing and utilization are not comparable to China day-rates | OEM-linked direct rental can bypass neutral marketplaces for flagship humanoids |
| Futurobots / Unitree Go2-A2 | 7-day minimum with live country-specific pricing | Direct multi-day rental | Delivery, pickup, training, damage cover, technical support | Pricing varies by country and duration | Useful analogue for how vendors monetize trial, inspection, and education use cases |
| Locus / inVia / Vecna | Opex subscription or annual-fee framing rather than public day-rates | RaaS subscription contract | Hardware, software, maintenance, monitoring, analytics, and scale flexibility | Public list pricing is limited and usually quote-based | For warehouse buyers, recurring subscription economics matter more than event-style daily rental |
| ABB / KUKA / FANUC | Customized service contracts; no public daily rental analogue | Lifecycle service, maintenance, modernization, and support | Planning, training, repairs, upgrades, spares, and installed-base service | Comparable pricing and SLA detail are private | Incumbents compete on procurement confidence, not on visible list prices |
Public evidence is far better on packaging and support structure than on normalized realized pricing, so this table emphasizes contract logic rather than a false apples-to-apples price comparison.
[CP008, CP009, CP010, CP012, CP013, CP014]Compressed view of how the main competitor classes differ on marketplace breadth, service execution, and industrial credibility.
Values summarize what the reviewed sources support at the competitor-class level; they are ordinal, not survey scores.
[CP011, CP016, CP021, CP031, CP032, CP034]3.3 Industrial incumbents compete through service-channel trust, not open marketplaces
In factories, Botshare’s hardest substitute may be the incumbent service stack of ABB, KUKA, and FANUC. Their competition is less visible on consumer-facing rental pages, but more powerful in procurement reality. Each offers lifecycle support, training, modernization, spare-parts or maintenance infrastructure, and long-standing relationships with plant engineers. IFR’s 2024 data show how large that installed base already is in China: 295,000 industrial robot installations in one year and more than 2 million robots in operation. In that context, a plant manager does not need another app to discover robotics demand; the manager already has trusted vendors, support teams, and qualification paths. Botshare can still matter where flexible access lowers trial risk, but factory buyers may view incumbent channels as the safer answer whenever uptime, compliance, and long-term support carry more weight than short-term asset access. Another way to frame the risk is that factory procurement teams already have escalation paths, training routines, and spare-parts habits tied to these vendors. Even if Botshare can source a compatible machine, it still must prove the equivalent reliability of field service, troubleshooting, and accountability when something fails during production.[CP017, CP018, CP019, CP020, CP021, CP035]
3.4 Price pressure and fulfillment quality now matter more than novelty
The adverse evidence is consistent across Chinese coverage: public attention created demand, but it also accelerated oversupply and pricing pressure. Xinhua, Yicai, Sohu, RoboHorizon, and China Daily all describe a market where event-led demand remains important, prices have fallen sharply from peak hype, and the spread economics of simple matchmaking are shrinking. Local operators in multiple cities are already monetizing rentals, which means Botshare must coordinate a fragmented supply base while defending against JD-style infrastructure bundles and warehouse RaaS substitutes. That pushes moat analysis away from storytelling and toward operations. The scarce capabilities are rapid maintenance, reliable dispatch, insurance handling, partner density, and repeatable scenario execution. What remains missing in public is the hard underwriting evidence—take rates, utilization, gross margin, and industrial win-loss data—that would prove Botshare can convert category momentum into durable economics before competitors normalize the same service bundle. That missing evidence keeps the moat story provisional rather than proven.[CP022, CP023, CP024, CP025, CP026, CP036]
| Moat claim | Threat | Severity | Evidence-backed rationale | Mitigation / diligence ask |
|---|---|---|---|---|
| Open marketplace leadership | Wanjiyi and other domestic aggregators | High | Botshare does not own the platform model exclusively; Wanjiyi launched with alliance, finance, and insurance backing. | Request city-level supply share, monthly active providers, and buyer repeat rates by scenario |
| OEM access advantage | JD and Unitree-linked direct channels | High | Retailer and OEM channels already provide booking, delivery, and support without a neutral marketplace. | Request channel conflict data, OEM exclusivity, and share of supply locked to JD or direct pages |
| Industrial expansion optionality | Warehouse RaaS specialists | High | Locus, inVia, Vecna, and Geek+ already sell recurring warehouse outcomes with support and scaling logic. | Show named industrial deployments, SLAs, and repeat order evidence versus logistics substitutes |
| Factory trust and support | ABB / KUKA / FANUC installed-base service channels | High | Incumbent channels already sit inside factories with training, spares, and maintenance infrastructure. | Collect factory RFQs, incumbent displacement cases, and required certification pathways |
| Pricing edge | Rapid rate compression | Medium-High | Chinese coverage shows mainstream rents cooling while service-heavy fulfillment remains the real bottleneck. | Track blended realized price, gross margin, and service attachment by scenario over time |
| Narrative moat | Commodity convenience messaging | Medium | Competitors also use Didi-like or simple-access framing, so top-of-funnel storytelling is not defensible alone. | Measure customer acquisition source, referral loop, and conversion after first booking instead of relying on brand slogans |
Severity is an underwriting judgment based on reviewed public evidence as of 2026-06-16, not a market-share forecast.
[CP021, CP025, CP029, CP030, CP032, CP033]Five compact indicators summarizing where competitive pressure is most credible and where public proof is still missing.
[CP024, CP025, CP036, CP037, CP038]3.5 Exhibits
04Financials
4.1 Revenue model, monetization architecture, and pricing evidence
Public evidence supports a specific shape of business model but not a clean income statement. Botshare does not market itself as a robot OEM that books hardware sales; it presents as a RaaS-style application platform connecting robot suppliers, local service partners, creators, and end customers. The most concrete monetization signal comes from April Tencent reporting, where CEO Li Yiyan described an early-stage fully light-asset structure: strategic partners own or purchase the robots, Botshare operates the assets, and the platform earns operating-management and service fees. That matters because it lowers direct fleet capex but shifts economic dependence toward take rate, utilization, and service execution. Pricing is also more heterogeneous than a simple per-robot card. Launch, Xinhua, and Tencent coverage point to basic dogs or long-duration entry plans at a few hundred renminbi per day, mainstream domestic rentals around low-thousands per day, and premium bundles or custom packages rising into five figures or even nearly RMB 100,000. The result is a business whose topline probably blends platform fees, packaged-solution charges, and scenario customization, but whose realized pricing remains undisclosed.[CI010, CI011, CI012, CI013, CI014, CI016]
| Stream | Mechanism | Unit | Current value / status | Quality | Diligence ask |
|---|---|---|---|---|---|
| Platform operating-management fees | Partners hold robot assets while Botshare operates dispatch and fulfillment | Per order / managed asset / service package | Explicitly described in Tencent April coverage; exact take rate not public | Medium | Request fee schedule by partner type and scenario |
| Service fees / delivery fees | On-site deployment, technical support, programming, and orchestration around each rental | Per job / service bundle | Supportable from light-asset interviews and service-heavy coverage; actual split undisclosed | Medium | Break out service revenue versus pure platform revenue |
| Bundled scenario solutions | Packaged pricing for annual meetings, retail activations, education, tourism, and custom shows | Per package / day / campaign | Public packages start at RMB 13,300 or RMB 16,900 per day in Tencent launch coverage | Medium | Request realized ASP by package and attach rate of custom work |
| Industrial and logistics scenario expansion | RaaS deployment into warehouse, park, and production workflows | Per deployment / contract | Management says new capital targets these scenarios, but no revenue disclosed yet | Low to medium | Provide signed industrial contracts, pilot-to-renewal conversion, and margin by scenario |
| Overseas rentals | Localized rentals through regional partners in 13 countries | Per day / solution package | Public high-price anecdotes exist, but booked overseas revenue is not disclosed | Low to medium | Provide overseas bookings, local partner economics, and country-level margin |
| Hardware sales | Direct robot sales recognized by Botshare itself | Unit sale | No reviewed public source supports Botshare as a primary hardware seller | Low | Confirm whether the company books any direct robot resale revenue |
Public evidence supports fee-based, bundled, and scenario-solution monetization, but no source discloses Botshare’s realized take rate or stream-by-stream revenue split.
[CI010, CI011, CI012, CI014, CI015, CI016]| Offer / signal | Public price or unit | List vs. realized pricing | Included capabilities | Unknowns | Implication |
|---|---|---|---|---|---|
| Basic robot-dog entry rentals | RMB 200-499 per day | Mostly list-style or promotional | Hardware access and basic delivery window | Utilization, subsidy cost, and partner payout unknown | Low entry price expands demand but likely leaves little margin without scale |
| Mainstream domestic humanoid rental | RMB 1,499-5,000 per day | Observed market pricing, not disclosed average realized price | Robot, operator or safety support, on-site handling in many cases | Discounting, travel charges, and downtime unknown | Shows prices are falling into lower-thousands, pressuring arbitrage economics |
| Premium custom packages | Up to roughly RMB 100,000 per day | Package card / scenario quote | Technicians, custom programming, performance design, multi-robot coordination | Actual gross margin and repeatability unknown | High-priced bundles can offset low-end price compression if service quality holds |
| Tencent launch packages | RMB 13,300 or RMB 16,900 per day starting price | Public package offer | Pre-defined rental bundles plus optional customization | Conversion rate and upsell mix unknown | Supports bundled-solution revenue rather than only per-robot billing |
| Europe Lingxi X2 rentals | EUR 2,000-3,000 per day | Public anecdotal pricing from management | Local service partner delivery and support | Local compliance, labor, and partner share unknown | International pricing could lift ASPs but adds execution cost |
| North America Expedition rentals | Up to USD 6,000 per day | Public anecdotal pricing from management | Localized deployment with partner support | Sustainability of price ceiling untested | Potential upside exists, but it should not be modeled as base case without volume data |
Rows reflect public list, package, or interview-level pricing signals. None of them provides Botshare’s realized average price, contribution margin, or customer-level retention economics.
[CI013, CI014, CI015, CI017, CI042]Public evidence points to a fee-based RaaS platform layered on third-party robot ownership and local service execution.
Exact take rates, partner payouts, and split between management fees and service fees are not publicly disclosed.
[CI010, CI011, CI012, CI016, CI041]4.2 Service-heavy unit economics and margin path constraints
The core underwriting issue is that Botshare may be light on owned hardware but it is not light on operations. Multiple independent sources now describe the heavy work after the booking: cross-city dispatch, on-site debugging, choreography or custom programming, operators, maintenance, insurance, and failure recovery. Xinhua’s quote that the rational human-robot ratio is still about one operator per robot is especially important, because it makes current labor burden hard to ignore. Meanwhile, market pricing is falling fast. Xinhua and China Daily both describe domestic daily rents resetting sharply from early-2025 peaks above RMB 10,000, while Sohu argues that simple information arbitrage is disappearing. That combination means Botshare’s moat has to come from service reliability, local partner density, and asset utilization rather than from headline rental rates alone. The industrial thesis could still be attractive if repeatable, high-frequency demand emerges, but IFR and MIIT materials together suggest that large-scale real-world humanoid deployment is still early. Until Botshare discloses utilization, refund, maintenance, and renewal data, margin path remains more narrative than model.[CI015, CI016, CI017, CI018, CI019, CI020]
| Metric | Value / status | Confidence | Why it matters | Diligence ask |
|---|---|---|---|---|
| Owned-asset intensity | Low on platform balance sheet | Medium | Management says partners buy or hold robots, reducing direct fleet capex | Verify owned versus managed robot mix by month |
| Operator intensity | ~1 operator per robot in current deployments | High | Labor is a direct service cost that caps software-like margin assumptions | Provide operator-hours per booking by scenario |
| Domestic price trend | Down materially from >RMB10k/day peaks | High | Falling price points compress spread economics for simple brokers | Show monthly realized ASP and discount rate since launch |
| Insurance coverage | 1,000+ insured robots / >RMB200m insured amount | Medium | Insurance is part of the operating model and may protect cash from damage events | Provide premium cost, claims frequency, and deductible structure |
| Repair and after-sales dependence | High | Medium | JD and other service-network links suggest uptime infrastructure is integral to delivery quality | Provide downtime, MTTR, and recovery cost per incident |
| Industrial utilization evidence | Not publicly disclosed | Low | Industrial margin upside depends on repeatable uptime and ROI, not event demand alone | Provide utilization and renewal data for industrial pilots |
| Public revenue / ARR | Not disclosed | High | Without topline disclosure, investors cannot test scale, growth, or monetization quality | Provide monthly revenue, recognized revenue, and GMV-to-revenue conversion |
| Cash conversion cycle | Not disclosed | Low | Partner payouts, refunds, receivables, and maintenance timing determine working-capital load | Share receivables and payables aging by counterparty class |
This table mixes observed cost drivers with deliberate nulls. The missing rows are the key blockers preventing a usable public unit-economics model.
[CI016, CI017, CI018, CI019, CI020, CI021]The public record suggests contribution margin is driven less by robot list price and more by labor, uptime, and partner-service efficiency.
No public source discloses actual gross margin, partner payout, refund rate, or downtime cost, so the bridge is qualitative rather than numeric.
[CI017, CI018, CI019, CI020, CI021, CI024]Public pricing anchors show wide dispersion across domestic low-end, mainstream, premium, and overseas scenarios.
The overseas row mixes euro and U.S. dollar quotes because the public sources do not provide normalized realized pricing or cost data by region.
[CI013, CI014, CI015, CI017, CI042]4.3 Capital adequacy, financing dependency, and investor mix
Funding is the clearest public financial data point, but it should be read as forward fuel rather than proof of earnings power. Botshare moved from seed to angel, pre-A, and then A/A+ within months, culminating in a reported RMB 7 billion valuation and a Crunchbase $1 billion unicorn headline. That speed signals strong investor appetite, yet the composition of that appetite matters: 36Kr, Baidu Baike, and Tencent all point to a mix of strategic industrial investors, listed companies, ecosystem insiders, and entertainment or consumer-facing capital. In other words, the cap table appears designed to open scenarios and channels as much as to provide cash. The newest round reduces immediate financing risk, but it also funds a very ambitious rollout: more cities, more partners, more creators, more industrial scenarios, global app and SaaS tooling, and potentially international expansion. Even under a light-asset model, that implies meaningful spending on partner enablement, sales, dispatch systems, insurance, maintenance links, and receivables support. Because the company still does not disclose cash, burn, runway, or round terms, the prudent reading is that Botshare remains funding-dependent until management proves that service fees and scenario solutions can finance network growth.[CI001, CI002, CI003, CI004, CI005, CI006]
| Item | Public value / status | Confidence | Why it matters | Diligence ask |
|---|---|---|---|---|
| Latest valuation anchor | RMB 7B in May 2026; Crunchbase also called it $1B | Medium | Sets the external expectation for growth and margin but not the company’s cash position | Confirm post-money, primary/secondary split, and FX-normalized internal valuation |
| Latest raise amount | Several hundred million RMB across A and A+ | Medium | Fresh capital reduces short-term financing stress | Provide exact gross proceeds, net cash in, and close dates by tranche |
| Funding chronology pace | Seed in Jan, angel/angel+ in Mar, Pre-A in Apr, A/A+ in May | Medium | Shows very fast capital formation and potentially fast spending needs | Provide cap-table evolution and dilution by round |
| Investor mix | Industrial strategics, listed companies, ecosystem sponsors, and entertainment capital | Medium | Strategics can open channels but may also distort price discovery | Classify investors by strategic value, board rights, and follow-on capacity |
| Cash on hand / burn / runway | Not publicly disclosed | Low | Core solvency and financing dependency cannot be judged without these figures | Provide cash balance, monthly burn, runway, and minimum liquidity covenant |
| International expansion burden | 13 countries announced, local partners already identified | Medium | Can widen pricing ceilings but adds localization, compliance, and partner-management cost | Provide country-entry budget and expected payback by region |
| Registry verification | Primary registry page blocked in this chapter | Medium | Control, related-party exposure, and registered-capital changes remain only partially verified | Pull direct registry record and reconcile with Baidu Baike |
Funding history is visible, but capital adequacy is still mostly inferred because cash, burn, runway, and round-term detail remain private.
[CI001, CI002, CI003, CI004, CI007, CI008]Botshare’s cash exposure clusters in working-capital and service-network layers rather than in direct owned-fleet capex.
Matrix scores are qualitative because no public source discloses cash spend by cost bucket.
[CI028, CI029, CI030, CI031, CI032, CI038]4.4 Disclosure gaps, governance risks, and financial verdict
The public record is still missing the variables that matter most for investment underwriting. There is no disclosed revenue, ARR, gross margin, burn, runway, CAC, payback, or net retention figure in the reviewed source set, and there is no direct public filing in this chapter that cleanly verifies current ownership from a primary registry page because automated access to Qichacha was blocked. Botshare’s own privacy policies add a second layer of financial risk: the platform collects order, scenario, budget, transaction, and partner-application data, and says some registration or transaction data may be synchronized to affiliates or business partners. Those disclosures support the idea that Botshare is building a real operating platform, but they also raise governance, compliance, and cross-party data-handling costs as the business scales across more cities and countries. The adverse case from Tencent and Sohu is therefore coherent: valuation has outrun disclosed economics, and high service intensity could force further dilution if price compression arrives faster than utilization gains. Financial verdict: Botshare may become a meaningful robot-services infrastructure layer, but today it remains a service-heavy, privately disclosed business whose revenue quality, margin path, and capital efficiency cannot yet be fully underwritten from public evidence alone.[CI026, CI027, CI033, CI034, CI035, CI036]
| Missing private metric or proof | Impact on verdict | Why public sources are insufficient | Exact diligence path | Priority |
|---|---|---|---|---|
| Recognized revenue and take rate | Blocks revenue-quality underwriting | Orders and robot counts do not translate into booked revenue without fee share and cancellation data | Request monthly revenue bridge from GMV/order value to recognized revenue by stream | Critical |
| Gross margin by scenario | Blocks margin-path underwriting | Service-heavy delivery, operators, repairs, and insurance can dominate economics | Request contribution margin by event, retail, industrial, and overseas scenario | Critical |
| Cash balance, burn, and runway | Blocks solvency view | Recent funding is visible, but liquidity and burn are not | Request treasury snapshot and monthly cash-flow statement | Critical |
| A/A+ investor list and terms | Weakens valuation interpretation | Public sources name amount and valuation but not the full buyer list or protections | Request legal close memo, term-sheet summary, and board-rights schedule | High |
| Direct registry verification | Leaves control and related-party questions partially open | Qichacha blocked automated access and no primary registry extract is in this chapter | Pull GSXT or manual registry extract and compare with secondary summaries | Medium |
| Industrial utilization and renewals | Limits long-term thesis confidence | Public evidence says industrial expansion is the goal, not that it already earns attractive returns | Request customer cohort data with uptime, operator hours, renewals, and refunds | High |
These are the missing items that matter most for underwriting. The chapter can describe the shape of the model without them, but it cannot close the financial diligence loop.
[CI026, CI027, CI029, CI033, CI034, CI035]4.5 Exhibits
05Product & Technology
5.1 Product surface and ordering workflow
Botshare presents the customer-facing product as a scenario-led rental workflow rather than a bare equipment marketplace. The English and Chinese sites both push a WeChat mini-program or app entry point, assisted by customer service for quoting and scenario adaptation, while the iOS listing adds concrete buyer controls such as scenario selection, rental duration, device quantity, operator add-ons, custom content, and multiple payment methods. Public launch and seasonal-demand coverage show the platform leaning into weddings, annual galas, exhibitions, mall activations, temple fairs, and school or parent-child events because those use cases can tolerate current robot limitations while still paying for novelty and service. In practice, the product promise is convenience plus offline fulfillment: users browse a package, configure a job, place an order, and rely on Botshare’s network to deliver a robot, operator, and script that can actually run on site.[CE001, CE002, CE003, CE004, CE005, CE006]
| Module / asset | User / buyer | Current maturity | Differentiation | Diligence gap |
|---|---|---|---|---|
| Mini-program / app ordering surface | Event organizer, venue, SME buyer | Live | Scenario-led ordering, guided quote flow, multiple payment methods | No public conversion funnel, API, or enterprise admin documentation |
| Humanoid rental offers | Marketing, events, reception | Live but operator-heavy | High visual impact and packaged choreography | Autonomy and uptime still depend on optional features and local operators |
| Quadruped rental offers | Patrol, education, demo buyers | Live | Lower price point and stronger terrain adaptability than humanoids | Short battery life and light payload limit heavier workflows |
| Bionic service robots | Hostessing, experiential retail, exhibitions | Showcase / early commercial | Lifelike appearance extends event and reception scenarios | Public proof is marketing-led; reliability data absent |
| Exoskeletons | Industrial and logistics users | Showcase / pilot | Expands catalog beyond pure spectacle into labor-assist use cases | Botshare has not published deployment case studies or safety KPIs |
| Operator and custom-content package | Customers needing polished performance | Live | Trained operators and custom skill packs reduce setup burden | Operator curriculum, staffing mix, and reusability are undisclosed |
| Insurance layer | Risk-sensitive buyers and partners | Live | Body-loss plus third-party liability cover lowers adoption friction | Policy terms, exclusions, and deductibles are not public |
| JD after-sales / recovery layer | Service partners and OEMs | New 2026 extension | Adds maintenance, recycling, and logistics infrastructure | Botshare-specific repair SLA and contractual scope are not public |
Rows mix Botshare-owned surfaces with launch and partner coverage. “Maturity” reflects public evidence quality, not an engineering certification.
[CE001, CE003, CE004, CE005, CE009, CE010]| User job | Current workflow | Botshare solution | Measurable benefit | Limitation |
|---|---|---|---|---|
| Corporate gala / exhibition stunt | Short-term event with little appetite for capex | Humanoid or mixed-robot package with choreography and operator support | High attention value without asset purchase | Novelty may not repeat and staffing remains heavy |
| Wedding / proposal ceremony | One-off ceremony needing a signature moment | Ring-delivery or greeting robot package | Differentiated guest experience for a single day | Task tolerance is narrow; failures are highly visible |
| Mall / holiday promotion | Traffic-building activation across a few days | Greeting, performance, and host-style robots | Lower cost than buying equipment and easy seasonal scaling | ROI still depends on footfall and human supervision |
| School / education demo | Short classroom or campus program | Humanoid or quadruped demo unit with scripted interaction | Accessible trial for institutions without owning hardware | Battery life and technical support remain constraints |
| Security patrol / inspection pilot | Light patrol or site inspection experiment | Quadruped deployment with remote operation and optional follow-on development | Cheaper field trial than buying and integrating a permanent fleet | Payload, endurance, and autonomy remain limited |
| Industrial / logistics assist | Exploratory use in warehousing, maintenance, or assisted work | Future-oriented exoskeleton or embodied-robot pilot path | Policy alignment and low upfront access to new hardware | Public proof of repeatable industrial ROI is still sparse |
Benefits summarize why leasing lowers adoption friction. Limitations summarize the public technical or operating constraints that still appear in current sources.
[CE004, CE011, CE012, CE013, CE014, CE015]The public workflow runs from scenario-led order intake to local deployment and then into insurance or after-sales support if something breaks.
[CE002, CE003, CE005, CE006, CE016, CE018]5.2 Multi-brand catalog and fulfillment architecture
What Botshare actually delivers is a layered orchestration stack. Supply comes from multiple robot OEMs and adjacent hardware makers; launch reporting names AgiBot humanoids and robot dogs, AheadForm bionic robots, and ULS exoskeletons, while management targets more than 10 onboarded OEMs and 200 premium service partners by 2026. The company’s own surfaces emphasize city partners, manufacturing partners, RaaS partners, and creator partners, which means catalog breadth depends as much on local service coverage and custom content as on robot inventory. Fulfillment is similarly externalized: after an order is booked, local partners handle transport, deployment, operators, and on-site execution, with insurance and JD-linked maintenance or recycling layers sitting around that process. In other words, Botshare is closer to a service-network coordinator than to a monobrand robot storefront, and each incremental city or scenario requires both hardware availability and a local execution layer that can show up on time. This architecture scales reach faster than a centralized fleet would, but it also makes Botshare dependent on partner quality, OEM compatibility, and after-sales infrastructure outside its direct control.[CE008, CE009, CE010, CE016, CE017, CE018]
| Layer / process | Role | Dependency | Risk |
|---|---|---|---|
| Discovery and ordering surface | Mini-program, app, and customer-service entry points gather scenario, timing, and payment details | Apple/Xiaomi app distribution and WeChat/customer-service reach | No public enterprise API or admin-tool documentation |
| Matching and recommendation layer | Maps scenario, budget, and quantity into a proposed robot package | Botshare app logic and human-assisted quoting | Recommendation quality and conversion metrics are undisclosed |
| OEM / asset catalog layer | Provides humanoids, quadrupeds, bionic robots, and exoskeletons from multiple brands | AgiBot and other participating manufacturers | Cross-brand compatibility and software-standard mismatch remain visible risks |
| Local service partner layer | Handles transport, setup, operators, and on-site execution | 600+ launch-stage providers and future 200+ premium partners target | Service quality varies by city; Botshare does not publish SLA or operator ratios by task |
| Risk and after-sales layer | Covers insurance, repair, recycling, and uptime support | PICC-style insurance plus JD service infrastructure | Exact claim terms and Botshare-specific response times are not public |
| Data / secondary-development loop | Captures field feedback for product iteration and custom workflows | OEM docs, partner customization, and JD-linked data infrastructure | No public Botshare SDK, integration guide, or data-rights policy for customers or partners |
The architecture table describes the operating model required to deliver rentals, not a disclosed internal software architecture.
[CE003, CE005, CE008, CE017, CE022, CE023]Botshare layers consumer ordering, multi-brand supply, local fulfillment, and external trust infrastructure into one service product.
[CE001, CE005, CE007, CE017, CE022, CE023]Botshare depends on OEMs, app-distribution surfaces, local partners, insurers, and JD-like after-sales infrastructure to make rentals work at scale.
[CE008, CE017, CE021, CE022, CE023, CE035]5.3 Capability maturity by robot type
The catalog breadth is real, but maturity differs sharply by robot class. AgiBot’s official surfaces show commercially listed humanoids and quadrupeds, yet those pages still frame the X2 humanoid around entertainment and commercial performance and the D1 quadruped around performances, inspection, and education rather than deeply integrated industrial autonomy. The product pages also disclose concrete limitations: autonomous navigation can require optional packages, manual technical problem-solving sits with the user beyond hardware warranty, the quadruped’s payload is only about 5 kilograms, and battery life is closer to one or two hours than full-shift operation. AheadForm and ULS broaden the perceived catalog into service-humanoid and exoskeleton territory, but public proof still centers on demonstrations and scenario framing rather than standardized production outcomes. The result is a viable event and pilot catalog today, with a much thinner evidence base for repeatable industrial or logistics performance.[CE027, CE028, CE029, CE030, CE031, CE032]
| Date / stage | Feature / milestone | Status | Implication | Source |
|---|---|---|---|---|
| 2025-12 launch | Open robot-leasing platform with 50-city network, 600+ service providers, and multi-brand showcase | Complete | Established national event-first operating footprint | TechNode / Shanghai government / City News Service |
| 2025-12 launch packaging | Scenario bundles, trained operators, insurance options, and 1234 ecosystem targets announced | Complete | Shows product is a managed service bundle, not only robot inventory | Shanghai government / Sohu launch feature / City News Service |
| 2026 Spring Festival | Holiday order mix concentrated in greetings, temple fairs, malls, proposals, and parent-child events | Observed | Confirms current demand concentration in spectacle and light-service scenarios | China Daily |
| 2026-04 | First embodied-robot insurance claims completed with 1,000+ robots insured | Complete | Risk-transfer layer moved from concept to real claims handling | Jiemian |
| 2026-05 to 2026-06 | JD strategic cooperation widened into transactions, logistics, maintenance, recycling, and data-linked after-sales | In progress | Raises fulfillment ambition beyond ordering alone | TechNode / Sohu / Gasgoo |
| 2026+ target state | Expand to 10+ OEMs, 200+ partners, 200+ cities, and more industrial/logistics use cases | Target | Roadmap depends on moving from events into higher-repeat workflows | TechNode / Shanghai government / MIIT 2026 action plan |
Status labels distinguish completed public milestones from still-prospective expansion goals and partner rollouts.
[CE008, CE009, CE013, CE020, CE022, CE035]Ordering is the most standardized layer today; robot execution maturity drops as use cases move from event performance toward industrial autonomy.
[CE029, CE030, CE031, CE032, CE033, CE034]5.4 Trust, safety, and technical control environment
Botshare does have real trust-building layers, but most are ecosystem-level rather than platform-certified controls. Public coverage points to trained operators, bundled insurance, and JD-supported repair or recycling, while app-store disclosures at least show a maintained mobile surface with explicit privacy notices. At the policy level, China’s 2026 humanoid standards and deployment action plan are highly relevant because they focus on real-scene operation, maintenance, data governance, privacy, collision detection, force limits, emergency stops, black-box logging, and long-duration reliability. Those frameworks help explain why Botshare wants to move from spectacle into more standardized service and industrial scenarios. They also imply that future growth into logistics, inspection, or assisted-work deployments will require much tighter operating discipline than a wedding or mall activation package. The gap is that Botshare itself does not publicly disclose uptime SLAs, incident rates, operator-certification standards, insurance exclusions, or platform-level API and integration documentation, so diligence still depends on private operating evidence rather than public compliance artifacts.[CE019, CE020, CE025, CE026, CE035, CE036]
| Control / framework | Status | Scope | Gap |
|---|---|---|---|
| Trained operators / “machine-with-human” service | Publicly described | Operator support for risky or complex tasks; training/certification mentioned in launch coverage | No public curriculum, audit standard, or staffing matrix by robot type |
| Robot insurance | Live | Robot body loss plus third-party liability; claims already processed | No public wording on exclusions, deductibles, or premium logic by scenario |
| Mobile privacy disclosure | Public | Apple and Xiaomi listings disclose data categories or permissions | No public platform privacy architecture or enterprise data-governance white paper |
| National humanoid standards system | Active 2026 framework | Application, operation, maintenance, safety, ethics, and data/model lifecycle rules | No public Botshare attestation that partner workflows are aligned to these standards |
| Industrial robot safety standard | Effective since 2025-03-01 | Provides national application-spec baseline for robot safety practices | No public mapping from Botshare service SOPs to this standard |
| JD repair / recycling network | Announced and expanding | After-sales, diagnostics, field repair, recycling, and engineer training | No public Botshare SLA, MTTR, or partner-service scorecard |
The control environment is mostly ecosystem-level. Botshare has public trust signals, but not the deeper certification or service-metric package a later-stage infrastructure platform would usually publish.
[CE018, CE019, CE020, CE021, CE025, CE026]5.5 Exhibits
06Customers
6.1 Customer segments, sectors served, and buying surfaces
Botshare is not selling to one homogeneous customer class. Official site copy positions the platform as a matchmaker between robotics service providers and end clients, and explicitly highlights restaurants, retail, and corporate events as target sectors. Launch and trade-show coverage broadens that set into conferences, weddings, education, malls, exhibitions, cultural tourism, celebrations, and reception workflows. That matters because the payer often differs from the user: a brand manager may fund a mall activation, a restaurant chain may use the robot to improve guest engagement during a holiday campaign, while an office operator or landlord may care more about tenant experience and property traffic. The official material and later deployment reporting consistently suggest that Botshare wins first where customers want short-duration robotic capability without owning hardware, while management keeps framing industrial, logistics, and routine service scenarios as the next expansion wedge rather than the current revenue center.[CU001, CU002, CU003, CU017, CU018, CU019]
| Segment | Buyer / payer | Primary user | Public proof quality | Current evidence | Key gap |
|---|---|---|---|---|---|
| Events, weddings, and celebrations | Event agency, organizer, or brand budget | Guests, operators, on-site staff | High | Launch, Xinhua, and Global Times all show weddings, annual galas, and performances as early demand | No disclosed repeat-purchase rate by organizer cohort |
| Retail, malls, and commercial promotions | Mall operator, store manager, or trade-marketing budget | Store staff and shoppers | High | Spring Festival order mix and Rui'an/KIC reporting both show mall and street-retail traffic-driving | No disclosed conversion from one-off activations to recurring store contracts |
| Restaurants and hospitality | Restaurant chain or local venue operator | Front-of-house staff and diners | Medium | Official site names restaurants; Global Times names Haidilao as first major client | Only one named restaurant account is public |
| Office, landlord, and mixed-use property | Property operator or commercial-space manager | Tenants, visitors, reception, and community users | Medium-High | Rui'an Office / Shui On WorkX gives direct office-commercial deployment proof | No disclosure of contract duration, renewal, or property count |
| Industrial, logistics, and routine service pilots | Operations, engineering, or automation budgets | Warehouse, maintenance, or site teams | Low-Medium | MIIT and Sohu describe this as the next expansion lane rather than a scaled current base | No named Botshare industrial customer with recurring spend is public |
Public proof is strongest in event and retail-style scenarios; industrial and recurring operational demand is described mostly as an expansion thesis rather than disclosed current customer revenue.
[CU001, CU002, CU003, CU017, CU019, CU023]Botshare's typical public customer path starts with a scenario-specific need, moves into short-term deployment, and only later has a chance to become recurring service revenue.
Nodes summarize the adoption sequence implied by public sources; they are not an internal sales-funnel disclosure.
[CU001, CU002, CU027, CU042, CU044]6.2 Adoption trajectory, order mix, and named deployment proof
The strongest hard demand signal in the public pack is the 2026 Spring Festival surge. People's Daily Online and China Daily both say Botshare had already logged more than 1,000 holiday orders by February 12 and expected to exceed 5,000 by the end of the holiday period. The same two sources say more than 54 percent of those orders were concentrated in Chinese New Year greetings, temple fairs, and shopping-mall performances, which is useful because it reveals not just volume but mix: Botshare had real demand, yet the mix leaned heavily toward promotional and experiential work rather than recurring operational automation. Global Times adds the clearest named brand example, reporting that Haidilao became Botshare's first major client and planned to place leased robots in select stores before Spring Festival for calligraphy, dance, and customer interaction. Public proof therefore exists, but it is still mostly campaign-like or seasonal, so the chapter should not overstate durability.[CU012, CU013, CU014, CU015, CU016, CU017]
| Metric | Value | Date | Source | Confidence | Implication | Missing denominator |
|---|---|---|---|---|---|---|
| Launch city footprint | 50 core cities | 2025-12 | TechNode, Shanghai government, City News Service, ITHome | high | Shows national intent from day one rather than a single-city pilot | No city-level order density |
| Launch service-partner network | 600+ service providers | 2025-12 | TechNode, Shanghai government, City News Service | high | Suggests Botshare scales through partner nodes instead of owned branches | No active-vs-signed split |
| Launch device base | 1,000+ devices | 2025-12 | TechNode, City News Service, ITHome | high | Enough supply breadth to support multi-city fulfillment | No utilization disclosure |
| Spring Festival orders | >1,000 booked by Feb 12; >5,000 expected by holiday end | 2026-02 | People's Daily Online, China Daily | high | Strongest public demand spike in the pack | No revenue or cancellation rate |
| First city-partner cohort | 100+ signed partner teams across 60+ cities; near-1,000 robots of first deployment demand | 2026-03 | Yangtse / Ziniu News | medium | Shows network expansion after launch and local demand capture | Partner signings are not the same as recurring end-customer spend |
The table mixes network-scale metrics and demand spikes because Botshare discloses marketplace breadth more often than recurring customer economics.
[CU004, CU005, CU006, CU007, CU009, CU010]| Customer / attributed surface | Segment | Deployment / use case | Production vs pilot | Outcome / proof | Limitation |
|---|---|---|---|---|---|
| Haidilao (select stores) | Restaurant chain | Pre-Spring Festival in-store robots for calligraphy, dance, and customer interaction | Seasonal campaign deployment | Global Times calls Haidilao Botshare's first major client | No follow-on store count, renewal, or revenue disclosed |
| Shui On WorkX / KIC Knowledge Art Festival | Office and mixed-use commercial property | Robot parade, stage performance, NPC interaction, pop-up retail, and merchant traffic-driving | Launch deployment with stated plan for normalized use | Two separate Rui'an/China.com reports describe first landing and wider office-commercial rollout intent | No property portfolio count or contract term disclosed |
| AWE 2026 East Hub expo surface | Brand marketing and exhibition customers | Guided interaction, reception, stage performance, and booth traffic-driving | Demonstration-heavy but customer-facing deployment proof | PEdaily describes active customer consultations around store traffic and brand interaction at the event | End customers are not individually named |
| Flash-shop / mobile retail brand merchants | Retail and brand-channel merchants | Robot-assisted mobile retail, themed pop-up stores, and brand interaction | Early ecosystem launch | 163 report shows Botshare entering structured retail operations with Flash Shop and downstream brand merchants | This is ecosystem/channel proof more than disclosed Botshare merchant cohort data |
The public named-proof set is real but still narrow and campaign-skewed; it does not yet amount to broad disclosure of recurring enterprise accounts.
[CU017, CU018, CU019, CU020, CU021, CU022]Public evidence narrows from broad scenario marketing to a much smaller set of named accounts and an even smaller set of disclosed durability metrics.
Counts summarize the reviewed public evidence in this chapter and are not company-reported funnel or CRM figures.
[CU017, CU019, CU023, CU039, CU045]Proof is strongest on deployment existence and weakest on recurrence, revenue materiality, and retention disclosure.
[CU017, CU019, CU023, CU031, CU045, CU046]6.3 Geography, city-partner network, and office/retail deployment model
Geographic coverage is more than a slogan. Multiple launch sources converge on a 50-city starting footprint with more than 600 service providers and over 1,000 devices, and later partner-network reporting says the first signed city-partner cohort already covered more than 60 cities with more than 100 partner teams and nearly 1,000 robots of initial deployment demand. The Yangtse report is especially useful because it explains the operating design: Botshare handles product integration, technology support, order orchestration, and brand endorsement, while local city partners act as service nodes for delivery and customer support. That same structure underpins the platform's office and retail deployments. Rui'an Office / Shui On WorkX used Botshare at KIC Knowledge Art Festival and described the appeal as a light-asset way to add robot parades, stage performance, pop-up retail, and merchant traffic-driving without heavy capex or maintenance staffing. The geography story is therefore not just expansion into more cities, but expansion through local fulfillment partners and property-channel relationships.[CU004, CU005, CU006, CU007, CU008, CU009]
Botshare scales customer coverage by keeping orchestration at the platform layer while pushing delivery into local service nodes.
The flow abstracts repeated operating roles from launch, partner-network, and JD-service reporting rather than a single disclosed SOP.
[CU027, CU029, CU030, CU042, CU043]6.4 Retention visibility, expansion limits, and concentration risk
The weakest part of Botshare's customer case is durability. No reviewed public source discloses NRR, GRR, churn, renewal rates, contract length, repeat-purchase frequency, or top-customer revenue share. Xinhua is explicitly cautionary: repeat customers are rare, many rentals still depend on novelty and entertainment, and the market has to move from “show” to “service.” The same Xinhua feature says current deployments often still require manual scripting and roughly one operator per robot, while Sohu argues that the commercial moat is shifting away from listing robots online and toward logistics, maintenance, insurance, repair, and recovery. Those points matter for customer concentration as much as for margins. If more than half of Spring Festival orders are greetings, temple fairs, and mall shows, then current demand is likely concentrated in event calendars and promotional budgets. Botshare may broaden into office operations, store service, light industry, and logistics, but public evidence still describes that as an expansion path rather than a proven recurring base.[CU028, CU029, CU030, CU032, CU033, CU034]
| Metric | Value / status | Segment | Confidence | Diligence ask |
|---|---|---|---|---|
| NRR / GRR / churn | All customer segments | high that it is undisclosed | Request cohort retention, gross churn, and net expansion by segment | |
| Contract length / renewal rate | Office, retail, restaurant, and event contracts | high that it is undisclosed | Request standard contract term, renewal frequency, and minimum commitment | |
| Repeat-customer prevalence | Xinhua says repeat customers are rare | Event and promotional rentals | medium | Request monthly repeat-order share and top repeat verticals |
| Operator intensity | Xinhua quotes a rational 1:1 operator-to-robot ratio | Complex humanoid deployments | medium | Request operator hours per deployment and labor cost per order |
| Trust / risk mitigation proxy | 1,000+ robots insured with aggregate coverage above RMB 200M | Cross-segment fleet operations | medium | Request claims frequency, incident rate, and whether insured fleets have better renewal behavior |
Null means Botshare has not publicly disclosed the metric in reviewed sources; the table uses indirect durability proxies where direct retention reporting is absent.
[CU028, CU033, CU034, CU039]| Expansion driver / concentration risk | Why it matters | Current evidence | Impact | Diligence path |
|---|---|---|---|---|
| Holiday and event concentration | Promotional budgets can spike quickly but may not renew like operating contracts | People's Daily / China Daily say >54% of Spring Festival orders were greetings, temple fairs, and shopping malls | Could create seasonal revenue volatility and weak cohort durability | Request monthly revenue mix by event, retail, office, and industrial categories |
| Named-account concentration opacity | One named restaurant account and one named office-property deployment do not reveal revenue concentration | No public top-customer share is disclosed | A few large accounts could dominate marketplace GMV without investors seeing it | Request top-10 customer mix and largest-account share |
| City-partner execution dependence | Botshare scales through local service nodes, not just software | Yangtse says city partners handle local delivery while platform handles orchestration | Quality variance or partner churn could hurt fulfillment and reputation | Request partner SLA compliance, churn, and city-level fill rates |
| Service-layer moat vs commoditization | Price compression weakens simple listing arbitrage and shifts value to logistics, repair, and insurance | Sohu says differentiation is moving to delivery, maintenance, and recovery capabilities | If Botshare cannot out-operate peers, customer acquisition may not translate to durable margins | Request delivery SLA, repair turnaround, and gross margin by service bundle |
| Lack of recurring retention disclosure | Without NRR, GRR, churn, or renewal data, logos may overstate durability | No public retention metrics are disclosed and Xinhua says repeat customers are rare | Underwriting confidence stays low even if deployment count is real | Request cohort retention, repeat-order frequency, and contract renewal data |
The risk table separates adoption breadth from durability so the chapter does not over-credit marketplace activity as recurring customer quality.
[CU012, CU013, CU033, CU034, CU035, CU037]6.5 Exhibits
07Risks
7.1 Regulatory, legal, and safety risk
Botshare already sits inside a heavier regulatory perimeter than a generic classifieds marketplace because the product bundles physical robots, payments, user identities, delivery coordination, on-site operations, and increasingly public-scene interaction. The company’s own privacy policy says the service spans its app, mini-program, website, and third-party integrations, and that it collects device identifiers, order details, addresses, budgets, use scenarios, photos, video, and payment-linked information. Meanwhile, the 2026 MIIT/SASAC deployment action and CAC’s smart-agent implementation opinion both push the sector toward stronger lifecycle management, privacy controls, behavior boundaries, collision detection, black-box traceability, and explicit responsibility allocation before large-scale deployment. That is positive for long-run industry legitimacy, but it also means a young operator like Botshare can be pulled into compliance work faster than its public disclosures suggest. The presence of insurance products covering third-party liability, product liability, and information leakage is useful corroboration that the real-world risk set is already understood by insurers. The problem is not absence of mitigation; it is that public evidence of board-level governance, certifications, and incident-governance maturity is still thin relative to the pace of commercial rollout.[CR001, CR002, CR003, CR004, CR005, CR006]
| Risk | Jurisdiction / trigger | Current evidence | Likelihood | Residual severity | Mitigation maturity | Diligence path |
|---|---|---|---|---|---|---|
| Data privacy and consent burden | App, mini-program, website, payments, media capture, location and order flows | Botshare privacy policy covers broad data collection, third-party SDKs, and third-party service links | high | high | early | Request full data map, retention schedule, DPIA-style review, and third-party processor list |
| Public-scene safety and incident accountability | Crowded malls, festivals, stores, venues, and mixed human-robot environments | MIIT 2026 action requires collision detection, force limits, emergency braking, black-boxes, and risk-warning / exit channels | high | high | partial | Obtain safety SOPs, incident logs, and responsibility allocation with service partners |
| Smart-agent and embodied-AI governance | Robots and agent systems collecting, deciding, and acting in public or sensitive settings | CAC opinion raises behavior control, privacy protection, traceability, and misuse-prevention expectations | medium-high | high | early | Map product behavior controls and audit trails to CAC / local requirements |
| Third-party liability / product liability / information leakage | Hardware failures, operator mistakes, damaged property, or leaked usage data | Insurance products already price these risks, implying they are expected not theoretical | medium-high | high | partial | Review insurance coverage limits, exclusions, and who bears deductibles by contract |
| Governance and disclosure opacity | Fast-scaling private company with limited public board / controls disclosure | Public sources still do not show a normal governance artifact set for a unicorn-valued operator | medium | medium-high | low | Request board list, committee structure, compliance owner, and certification roadmap |
Ordered by residual severity. The key issue is not whether rules exist, but whether Botshare’s current operating and disclosure stack is mature enough for wider public-scene and enterprise deployment.
[CR001, CR002, CR003, CR004, CR005, CR006]Botshare’s highest-residual risks cluster around service execution, pricing pressure, and the gap between regulatory expectations and public governance maturity.
[CR004, CR007, CR018, CR024, CR037, CR041]7.2 Service-network, maintenance, and operational burden
The most important near-term risk is execution burden. Botshare’s launch materials and interviews repeatedly describe a business that does far more than match demand and supply: users place orders through the platform, local partners fulfill, engineers tune parameters on site, operators monitor live runs, and the company promises service guarantees across many cities. Shanghai holiday reporting makes the hidden labor visible. Engineers describe a routine of pre-delivery checks, live monitoring, parameter adjustment, and emergency response, especially in dense public venues where robots may face collisions, unexpected commands, crowding, and long operating hours. Securities Daily’s June 2026 insurance feature widens the point from Botshare to the category: transport, cross-scene deployment, third-party injury, system faults, and expensive repairs are core rental risks, not edge cases. Sohu’s adverse take is therefore important—the moat may belong to whoever can coordinate logistics, maintenance, insurance, and recovery at scale, not whoever lists the most robots. That makes Botshare’s service network both the company’s best asset and its largest operating liability.[CR010, CR011, CR012, CR013, CR014, CR015]
| Failure mode | Why it matters now | Likelihood | Residual severity | Mitigation maturity | Open evidence gap |
|---|---|---|---|---|---|
| City-by-city fulfillment inconsistency | Botshare promises nationwide reach, but delivery quality depends on local partners, engineers, and uptime discipline | high | high | partial | No public SLA, MTBF, or by-city incident-rate disclosure |
| Maintenance and repair cost overhang | Transport, crowd interaction, and repeat deployments raise breakage and wear risk | high | high | partial | Need maintenance cost curve, spare-parts policy, and refurbishment economics |
| Human-heavy onsite operations | Engineers still tune parameters, monitor robots live, and respond to incidents in dense scenes | high | medium-high | partial | Need staff-to-order ratio and remote-ops automation data |
| Security / privacy incident spillover | More devices, sensors, and SDKs expand the attack and data-loss surface | medium | high | early | Need penetration testing, vendor-security review, and breach-response process |
| Seasonal demand spikes stressing operations | Holiday and event surges can overload scheduling and support before standard workflows are mature | medium-high | medium-high | partial | Need order concentration by season, queue times, and failed-fulfillment rate |
This register focuses on execution bottlenecks likely to hit margin, service quality, or brand trust before legal issues become existential.
[CR010, CR011, CR012, CR013, CR014, CR015]7.3 Ecosystem dependence, governance opacity, and financing fragility
Botshare is marketed as an open platform, but the public record still ties it tightly to the Agibot ecosystem. Agibot co-hosted the launch, Jiang Qingsong appears publicly as both an Agibot partner and Botshare chairman, and Tencent coverage frames the platform as a way for Agibot’s own robots and capabilities to reach more scenarios while the broader ecosystem fills gaps. That dependence can be helpful while supply is scarce and standards are immature, but it creates real concentration risk around product access, partner neutrality, and related-party economics if third-party OEMs or service partners believe Agibot receives preferential treatment. Governance opacity amplifies the issue. Public materials discuss investors, executives, and growth plans, yet still leave board composition, formal risk oversight, related-party rules, and unit-economics disclosure largely absent. Financing pace adds pressure rather than comfort. Botshare moved from seed financing to unicorn-level headlines within months, and adverse commentary already questions whether order volume and disclosed operating proof justify the valuation step-up. If financing expectations outrun visible economics, later rounds can become more fragile even if top-line activity still looks busy.[CR021, CR022, CR023, CR024, CR025, CR026]
| Dependency | Counterparty / layer | Failure scenario | Concentration signal | Residual severity | Mitigation / current offset | Diligence path |
|---|---|---|---|---|---|---|
| Agibot ecosystem | Chairman, launch sponsor, upstream robot / content / ecosystem access | Third-party OEMs perceive bias or supply access is constrained by Agibot priorities | High origin concentration | high | Botshare publicly claims openness to multiple brands | Review SKU mix, OEM share, and related-party commercial terms |
| Local service partners | City rental / fulfillment nodes | Service quality varies by city and damages brand trust | 600+ partners claimed but quality undisclosed | high | Partner network provides local reach | Ask for partner scorecards, churn, and training standards |
| Insurance providers | PICC / Ping An style coverage stack | Coverage exclusions or weak limits leave platform bearing losses | Insurance now used as confidence layer | medium-high | Insurance products and first claims already exist | Inspect policy wording, deductibles, and claim settlement timelines |
| Logistics / recovery capability | Cross-city delivery, setup, return, repair, recycling | Falling prices expose whether fulfillment cost absorbs gross margin | Service-heavy market structure | high | JD-style partnerships may help recovery and logistics | Request blended logistics cost per order and reverse-logistics KPI |
| Policy / standards environment | MIIT, CAC, Shanghai scenario and standards push | Rules tighten before Botshare has reliable industrial-grade processes | Sector still in build-out mode | medium-high | Policy is supportive, not hostile | Track whether Botshare joins standards / pilot programs and passes validations |
Botshare’s platform story depends on turning each dependency into leverage rather than hidden concentration. Agibot linkage is the most strategically important dependency to underwrite.
[CR021, CR022, CR023, CR024, CR029, CR032]| Role / function | Dependency or gap | Why it matters | Likelihood | Residual severity | Mitigation / diligence path |
|---|---|---|---|---|---|
| National operations leadership | Need to standardize partner onboarding, SLAs, and incident response at scale | Marketplace growth fails without operating system discipline | high | high | Validate org design, city coverage per manager, and support escalation ladder |
| Field engineers and operators | Current deployments still require parameter tuning, monitoring, and emergency response | Labor intensity can suppress margin and limit concurrency | high | high | Request staffing ratios, training curriculum, and automation roadmap |
| Compliance / privacy owner | Public-facing legal disclosures exist, but governance artifacts remain thin | Rising privacy and public-scene safety expectations need accountable ownership | medium-high | medium-high | Identify named compliance lead, counsel, and audit cadence |
| Industrial solution specialists | Industrial and logistics expansion requires workflow redesign, not event choreography | Policy support could outrun customer-ready deployment capability | medium-high | high | Ask for named industrial design wins, case studies, and customer references |
The biggest execution risk is that Botshare scales demand generation faster than it scales the human systems required to deliver safe, repeatable service.
[CR011, CR012, CR018, CR029, CR030, CR040]Botshare’s growth story depends on coordinating parent-ecosystem supply, local service partners, insurers, and policy channels without losing neutrality or control.
[CR021, CR022, CR023, CR024, CR029, CR032]7.4 Price compression, demand quality, and industrial timing risk
The clearest market risk is that Botshare may be correctly reading the direction of the robot-rental market while still being early on durable economics. Multiple sources show that current demand is real, but the mix still skews toward festivals, exhibitions, retail activations, tourism, and other high-visibility but not yet deeply embedded workflows. Shanghai’s spring-holiday report shows orders up sharply, yet more than half came from holiday scenarios; Tencent interviews explicitly say 2025 demand was still largely novelty-driven rather than habitual operational usage. At the same time, pricing is already moving. Sohu and Tencent report that rental rates have fallen materially as supply expands, and adverse commentary warns that six-month payback stories depend on temporary scarcity and high prices that may not survive wider mass production. Policy ambition is not the same thing as customer readiness. MIIT’s 2026 action and Shanghai’s embodied-intelligence plan both point toward industrial, logistics, retail, and service deployment, but they describe those categories as validation and demonstration tracks requiring safety, reliability, standards, and long-run economic proof. If Botshare cannot migrate from event-led bursts into repeat enterprise workflows before pricing normalizes, the market may grow while the platform’s margin pool shrinks.[CR033, CR034, CR035, CR036, CR037, CR038]
7.5 Mitigations, monitoring signals, and kill criteria
Public mitigations exist, but they are partial and should be judged by operating evidence rather than narrative. Botshare has put basic privacy terms on the record, insurers have started underwriting the category, government policy is actively opening real-world deployment scenarios, and the company has recruited experienced operators to build a national network. Those are necessary conditions. They are not sufficient. The thesis breaks if repeat enterprise usage does not replace event-led demand, if city-level uptime and incident handling cannot be standardized, if Agibot dependence discourages ecosystem neutrality, or if valuation expectations continue compounding faster than revenue and margin disclosure. The right monitoring frame over the next 12 months is concrete: share of orders from repeat operational accounts rather than festivals, service-level reliability and incident rates by city, evidence of multi-brand supply without conflict, and whether fundraising still requires headline valuation leaps unsupported by public economics. Botshare does not look legally blocked today; it looks execution-constrained. That distinction matters because the company can still succeed, but only if its service infrastructure matures faster than hype fades and faster than price compression erodes the spread available to intermediaries.[CR045, CR046, CR047, CR048]
| Risk | Monitorable trigger | Threshold / event | Action implication |
|---|---|---|---|
| Repeat-demand weakness | Order mix remains dominated by festivals, weddings, and promo events | No visible shift toward recurring enterprise workflows within 12-18 months | Treat service demand as novelty-led and underwrite lower terminal margin |
| Service-network underperformance | By-city outages, missed deliveries, or incident rates stay opaque or worsen | Management cannot show standardized SLA / incident reporting across top cities | Pause underwriting until operating-system proof improves |
| Agibot concentration | Multi-brand supply remains nominal while Agibot devices dominate volume | Third-party OEM share or partner satisfaction looks weak | Discount platform-neutrality claims and assume concentration risk |
| Valuation / financing fragility | New rounds continue stepping ahead of revenue and margin disclosure | Fundraising depends on headline markups without economics transparency | Assume down-round or structured-financing risk rises materially |
| Industrial timing miss | Industrial / logistics pilots do not convert into validated repeat deployments | No named production references or validation reports despite policy push | Push out industrial TAM realization and compress base-case adoption |
| Compliance maturity lag | Privacy / safety governance remains policy-only with no certification or audit proof | No disclosed compliance owner, audit process, or safety playbook | Escalate diligence and price in higher legal / reputational downside |
These kill criteria emphasize measurable evidence rather than narrative milestones. Botshare should be monitored like an operations company, not only like a marketplace or hardware story.
[CR045, CR046, CR047, CR048]The main risk chain runs from novelty-heavy demand and service burden into margin pressure, financing stress, and weaker ability to fund industrial expansion.
[CR018, CR026, CR037, CR039, CR046, CR047]7.6 Exhibits
08Valuation
8.1 Headline valuation versus public operating disclosure
Botshare’s May 2026 financing headline is easy to repeat and much harder to underwrite. Multiple English and Chinese sources agree on the core fact pattern: the company completed Series A and A+ rounds worth several hundred million renminbi, the new mark reached RMB 7 billion, and management intends to use the money to shift from event-led deployments toward a broader RaaS platform for industrial, park, warehousing, logistics, and commercial-service use cases. That is enough to establish that the valuation exists and that investors are paying for a platform thesis rather than a single project. It is not enough to establish that the current price is supported by disclosed economics. The same source set that confirms the headline also shows what is missing: there is still no public revenue, ARR, gross margin, burn, runway, or cap-table-term disclosure, and public operating markers still lean heavily toward dispatchable fleet, city coverage, order anecdotes, and scenario breadth. Publicly, the raise reads like a strategic scarcity trade on category leadership in robot deployment infrastructure. The diligence burden is therefore not to prove that demand exists at all; it is to test whether the $1 billion equivalent mark is being paid for a real operating flywheel or for a fast-moving narrative whose financial shape remains private.[CV001, CV002, CV003, CV004, CV005, CV006]
8.2 Comparable lenses for an early robotics-orchestration platform
There is no perfect public comparable for Botshare, which is exactly why false precision would be a mistake. Serve Robotics is helpful because it is a public autonomy platform with real SEC disclosure, real losses, and real liquidity; Richtech is helpful because it explicitly pitches RaaS and recurring contracts while still showing how financing structure and control quality can complicate the valuation story; Knightscope shows how a service-heavy robotics business can trade when recurring revenue exists but growth and profitability remain contested; and Symbotic shows what scaled industrial automation looks like when revenue and cash are finally large enough to justify a multi-billion-dollar market cap on operating proof. Taken together, those peers do not produce one clean multiple for Botshare. Instead, they create a valuation ladder. On one end, public microcap robotics names can trade far below Botshare’s headline even with audited statements, recurring revenue, and cash disclosure. On the other end, truly scaled automation leaders trade much higher but only after delivering billions of dollars of revenue and far deeper customer proof. Botshare currently sits between those poles: strategically more interesting than a generic microcap, but still far closer to the proof burden of an early platform than to the maturity profile of an industrial automation leader.[CV015, CV016, CV017, CV018, CV019, CV020]
| Lens | Bull / pro-thesis | Anti-thesis / why it may fail | What would change the view |
|---|---|---|---|
| Market timing | Robot-rental demand and policy support are real, with public sources showing rapid category awareness. | Demand can stay real while economics stay novelty-led and episodic. | Evidence that industrial and enterprise demand becomes repeat rather than showcase traffic. |
| Business model | A platform that coordinates OEMs, partners, and scenarios could become the operating layer for robot deployment. | The platform may remain a heavy service coordinator with limited software-like margin. | Take-rate disclosure and contribution-margin by scenario. |
| Strategic scarcity | Fast fundraising and unicorn status may reflect category leadership in an emerging bottleneck. | Fast fundraising can also reflect hype, not durable economics. | Proof that later fundraising follows operating progress, not just narrative momentum. |
| Comparable set | Public peers show room for large outcomes if automation platforms scale. | Public peers also show brutal compression when scale, controls, or recurring economics disappoint. | More mature disclosure that clarifies which peer bucket Botshare actually belongs in. |
| Execution moat | Local delivery, uptime, insurance, and partner management could be hard to replicate. | Those same layers can absorb margin and make scaling operationally messy. | City-level SLA, incident, and retention metrics. |
| Exit path | If Botshare industrializes, it could become an attractive strategic or growth-equity platform asset. | Weak governance, thin controls, or thin KPIs can delay IPO-readiness and compress exit value. | Board-quality reporting, audit readiness, and cleaner cap-table disclosure. |
The table pairs upside and downside arguments so the recommendation stays evidence-sensitive rather than company-quality-only.
[CV006, CV009, CV012, CV014, CV028, CV029]| Comparable | Public value / metric | Operating disclosure signal | Why it helps | Why it does not fit perfectly |
|---|---|---|---|---|
| Serve Robotics | $0.61B market cap; $2.7M 2025 revenue; $233.4M liquidity | Public SEC-reported delivery-robotics platform with large losses and significant cash. | Useful lens for a disclosed autonomy platform still trading heavily on option value. | Different delivery model and cash-rich balance sheet distort simple multiple reads. |
| Richtech Robotics | $0.47B market cap; $5.0M FY2025 revenue; 55 RaaS contracts; $193.6M cash | Model-adjacent RaaS story with public filings and explicit recurring-revenue positioning. | Shows how early public RaaS names can still depend on financing structure and control quality. | ATM-funded balance sheet and control weakness make it an imperfect clean peer. |
| Knightscope | $35M market cap; $11.3M 2025 revenue; 70% service-revenue mix | Service-heavy robotics operator with real recurring service footprint and public results. | Useful floor for what public markets can pay when service-model economics remain contested. | Security robotics is not humanoid rental or deployment orchestration. |
| Symbotic | $25.18B market cap; $2.247B FY2025 revenue; $1.245B cash | Scaled industrial-automation and warehouse platform with deep customer proof. | Useful upper-bound maturity lens showing what large valuation support looks like when revenue and cash are huge. | Far more mature, vertically different, and not an early marketplace or deployment layer. |
| Botshare headline | $1B-equivalent May 2026 private mark; public revenue undisclosed | Headline supported by financing news, market enthusiasm, and scenario breadth rather than public financial statements. | Useful anchor for assessing whether current price sits closer to option value or scaled execution. | Not directly pressure-tested by disclosed revenue, margin, or round-term detail. |
Comparable rows mix market-cap, revenue, and disclosure-style lenses intentionally. The goal is scenario framing, not a false claim that all five rows deserve the same multiple methodology.
[CV015, CV016, CV017, CV018, CV019, CV020]At a fixed $1B headline, implied revenue multiples collapse quickly only if Botshare is already at substantial undisclosed scale.
Bars show implied market-cap-to-revenue multiples using the roughly $1B headline and hypothetical revenue levels because Botshare does not publicly disclose revenue.
[CV035, CV036]8.3 Scenario framing, not point-estimate certainty
The right way to frame Botshare today is through scenarios rather than a single-number target. The bull case assumes the company becomes the default orchestration layer for embodied-robot deployment in China: industrial and enterprise workflows start to recur, dispatch density improves, partner neutrality remains credible, and monetization comes from reliable platform and service economics rather than one-off event bursts. The base case is more modest. Botshare still becomes a real category company, but its economics remain hybrid and labor-influenced for longer than investors hope, with industrial deployment scaling slower than the financing story suggests. The bear case is not that robot demand disappears; it is that demand stays real but mostly episodic, pricing keeps compressing, human support and repair stay heavy, and later investors refuse to keep paying step-up marks without audited evidence. Under that framing, the current headline already leans into upside. A $1 billion mark can be rationalized only if Botshare proves it belongs materially above the public microcap robotics bucket and begins to close the disclosure gap around revenue quality, repeatability, and unit economics. Until then, scenario width matters more than decimal-point precision.[CV006, CV007, CV008, CV009, CV010, CV012]
| Scenario | Core assumptions | Indicative valuation range | Probability signal | What it means for investors |
|---|---|---|---|---|
| Bear | Demand remains event-led, pricing compresses, service labor stays high, and new rounds require better proof than the company can publicly show. | $0.30B-$0.60B | Meaningful if industrial renewals and unit economics stay opaque through the next refresh. | Today’s headline would look early and vulnerable to a flat or down round. |
| Base | Botshare becomes a real national deployment platform, but industrial recurrence and margin structure take longer to prove than the financing narrative implies. | $0.60B-$0.95B | Most consistent with the current public source set. | Headline valuation looks full; a better entry would come from either time or more disclosure. |
| Bull | Industrial, logistics, and enterprise workflows start renewing, partner density improves utilization, and disclosed KPIs support a durable orchestration model. | $1.10B-$1.60B | Requires several proof points that are still private today. | Current headline can work, but only if the company quickly validates recurring economics. |
| Current headline | May 2026 fundraising mark treated as roughly $1B-equivalent in outside coverage. | $0.95B-$1.05B | Already visible in the market. | Investors buying here are underwriting a large share of the upside before disclosure catches up. |
Ranges are intentionally broad and scenario-based. They reflect public-evidence framing, not a discounted-cash-flow model built on missing private metrics.
[CV001, CV014, CV035, CV036, CV037, CV038]Wide scenario bands are more defensible than a point estimate because the largest debate is still proof quality rather than spreadsheet precision.
Ranges are illustrative scenario bands anchored to public comparison lenses and missing-disclosure penalties, not to a DCF based on unavailable company financials.
[CV001, CV038, CV039, CV040, CV044, CV045]8.4 Recommendation, entry discipline, and thesis-break signals
The practical investment conclusion is to keep Botshare on the front foot strategically while staying conservative on price. Public evidence is strong enough to reject the view that Botshare is a fake company or a pure concept deck: the financing happened, the market exists, service demand is real, and multiple public sources show a platform trying to solve deployment infrastructure rather than only leasing hardware. But the evidence is still too thin for a buy-style call at the current headline. The company has not yet shown the audited financial and cohort data needed to tell investors whether it deserves to be compared to speculative option-value names, to service-heavy robotics operators, or eventually to scaled automation platforms. That is why the cleanest stance is research-more with medium confidence, high risk, and a stretched valuation posture. The next diligence cycle should focus on revenue recognition, take rate, renewal and retention, industrial pilot conversion, uptime and incident data, and round-term detail. If those checks are strong, the current mark may look prescient. If they remain private while valuations keep stepping up, the thesis should be treated as increasingly fragile rather than increasingly confirmed.[CV013, CV014, CV033, CV034, CV040, CV041]
| Dimension | Current view | Why it is the right posture now | What would improve the view |
|---|---|---|---|
| Recommendation | research-more | Strategic momentum is real, but public financial disclosure is too thin for a clean buy call at the current headline. | Audited revenue, margin, retention, and round-term detail. |
| Confidence | medium | There is enough evidence to frame the market and the proof gap, but not enough to collapse scenario width. | Named industrial renewals plus KPI disclosure. |
| Risk rating | high | Service intensity, financing dependency, and commercialization timing remain unresolved. | Better unit economics and lower execution volatility by scenario. |
| Valuation stance | stretched | A ~$1B mark leans into upside before public operating proof catches up. | Either more disclosure or a lower effective entry price. |
| Decision implication | Track closely, do not chase headline price. | The company could still become important, but investors need a more favorable information-to-price ratio. | A diligence package that converts narrative optionality into measurable operating proof. |
This table intentionally summarizes posture rather than pretending the public source set can support a tighter valuation point estimate.
[CV041, CV042, CV043, CV044, CV045]| Trigger | Threshold to watch | Why it matters | Action implication |
|---|---|---|---|
| No industrial repeatability | Next refresh still shows no named renewals, no pilot-to-production conversions, and no uptime proof. | The bull case depends on recurring operational workflows, not only event demand. | Treat current valuation as over-earning its evidence base. |
| Service burden overwhelms pricing | Pricing keeps compressing while operator, repair, and logistics cost disclosure remains absent or negative. | The business could stay busy but economically thin. | Move stance toward avoid unless price resets sharply. |
| Financing keeps outrunning disclosure | Another valuation step-up arrives without audited KPI release or clearer round terms. | Narrative compounding without proof raises down-round risk later. | Assume preference risk is rising even if the headline mark goes up. |
| Partner neutrality weakens | A small set of OEMs or related ecosystem actors dominates supply and economics. | Concentration can cap marketplace credibility and bargaining power. | Discount platform optionality and strategic-exit upside. |
| Incident profile worsens | Claims, failures, or compliance friction rise faster than service controls mature. | Operational reliability is central to repeat enterprise adoption. | Reassess whether Botshare is a scalable platform or a brittle services coordinator. |
These triggers are designed as decision rules for the next diligence cycle, not as claims that any single failure automatically kills the company.
[CV039, CV043, CV045, CV046, CV047]| Topic | Missing evidence | Why it matters | Owner / diligence path |
|---|---|---|---|
| Revenue quality | Audited 2025 revenue plus 2026 monthly bridge from orders to recognized revenue. | Without it, the valuation cannot be anchored to scale or growth. | CFO data room and auditor package. |
| Take rate and margin | Scenario-level take rate, gross margin, operator cost, logistics cost, and repair cost. | This decides whether Botshare is a platform or a labor-heavy services business. | Finance team plus operating KPI workbook. |
| Industrial renewals | Named industrial pilots, contract length, renewal rate, and customer ROI references. | The bull case depends on recurrence in operational scenarios. | Customer calls and contract sample review. |
| Retention and concentration | Cohort retention, repeat-booking rate, top-customer exposure, and cancellation/refund data. | Demand activity is not the same as durable revenue quality. | CRM export and cohort deck. |
| Fleet economics | Owned versus managed fleet mix, utilization by scenario, and working-capital cadence. | Investors need to know where capital intensity really sits. | Ops + finance reconciliation. |
| Round terms | Preference stack, anti-dilution, investor rights, and ownership concentration. | Headline valuation may overstate common-equity economics if terms are investor-friendly. | Legal diligence on cap table and signed term sheet. |
These are the few questions most likely to change the recommendation quickly if management can answer them with primary evidence.
[CV013, CV036, CV041, CV045, CV046, CV047]The recommendation follows from real demand and strategic potential colliding with thin public economics and wide scenario uncertainty.
This flow compresses the chapter’s judgment into decision nodes; it is not a disclosed company process map.
[CV006, CV009, CV012, CV013, CV032, CV040]IC-style scores on a 1-5 scale translate the chapter into a decision snapshot grounded in public evidence only.
Scores are directional and intentionally conservative because they use only public June 2026 evidence.
[CV013, CV028, CV029, CV041, CV042, CV043]8.5 Exhibits
Disclaimer
This report-meta artifact synthesizes only the public evidence cited in the chapter YAMLs as of 2026-06-16. Because Botshare is a newly launched private company, key valuation and risk judgments are highly sensitive to undisclosed financials, governance terms, and customer-retention data.
Evidence index
| ID | Statement | Confidence | Sources |
|---|---|---|---|
| CO001 | Botshare is a robot leasing and rental platform that connects robotics service providers with end clients. | Medium | SO001, SO002 |
| CO002 | The platform uses BOTSHARE as its English brand and 擎天租 as its Chinese brand. | High | SO001, SO002 |
| CO003 | Qingtian Rent (Shanghai) Technology was registered on 2025-12-09. | Medium | SO004, SO016 |
| CO004 | Botshare was publicly launched in Pudong, Shanghai on 2025-12-22. | High | SO003, SO012 |
| CO005 | Shanghai government and tech-media launch coverage described Botshare as an open robot leasing platform. | Medium | SO003, SO012 |
| CO006 | Crunchbase News identified Botshare as a Pudong, China-based company in June 2026. | Medium | SO014 |
| CO007 | Botshare’s business model is framed publicly as RaaS, or Robot-as-a-Service. | Medium | SO004, SO009 |
| CO008 | Official site copy shows the platform initially serving event, retail, reception, and corporate-activation scenarios. | Medium | SO001, SO011 |
| CO009 | Management says the platform is pushing from event rentals into industrial manufacturing, park operations, warehousing, logistics, and commercial-service scenarios. | Medium | SO004, SO009, SO014 |
| CO010 | Jiang Qingsong serves as Botshare’s chairman. | Medium | SO003, SO016 |
| CO011 | Jiang Qingsong is also a partner at Zhiyuan AGIBOT. | Medium | SO003, SO011 |
| CO012 | Li Yiyan is Botshare’s chief executive officer. | Medium | SO004, SO016 |
| CO013 | 36Kr reported that Botshare was co-founded by Zhiyuan Robotics and Flycode. | Low | SO008 |
| CO014 | Baidu Baike lists Jiang Qingsong as the legal representative of Qingtian Rent (Shanghai) Technology. | Low | SO016 |
| CO015 | Baidu Baike lists Zhiyuan Innovation (Shanghai) Technology as a 55% shareholder of the company. | Low | SO016 |
| CO016 | Baidu Baike lists additional partnership vehicles tied to Zhiyuan, Flycode, and Qingtian as the remaining public shareholders. | Low | SO016 |
| CO017 | Baidu Baike says Botshare announced a seed round on 2026-01-15 led by Hillhouse Venture Capital. | Low | SO016 |
| CO018 | Sina and Baidu Baike reported that Botshare announced angel and angel+ rounds on 2026-03-18 totaling more than RMB 100 million and implying a RMB 3 billion valuation. | Medium | SO007, SO016 |
| CO019 | 36Kr reported that Botshare disclosed a several-hundred-million-RMB Pre-A round on 2026-04-29. | Medium | SO008 |
| CO020 | 36Kr said the Pre-A investor group included CP Robotics, Changxin Shares, Meig Smart, and Lens Technology. | Medium | SO008, SO006 |
| CO021 | Multiple May 2026 reports said Botshare’s A and A+ rounds valued the company at RMB 7 billion. | Medium | SO004, SO005, SO010 |
| CO022 | Chinese financial media described Botshare as the first publicly reported unicorn in the robot-leasing segment. | Medium | SO005, SO006 |
| CO023 | Crunchbase News listed Botshare among May 2026’s new unicorns at a $1 billion valuation. | Medium | SO014 |
| CO024 | TechNode and Shanghai government launch coverage said Botshare’s 2026 target was to connect 10+ robot manufacturers, 200+ premium leasing partners, 3,000+ creators, and 400,000+ rental customers. | High | SO003, SO012 |
| CO025 | TechNode and City News Service said Botshare planned to expand from 50 core cities to more than 200 cities by the end of 2026. | Medium | SO003, SO013 |
| CO026 | At launch, public coverage said the platform already covered 50 core cities in China. | High | SO003, SO012 |
| CO027 | Public launch coverage said the service network included more than 600 local service providers. | Medium | SO003, SO013 |
| CO028 | Public launch coverage said the platform had more than 1,000 robots or devices available at launch. | Medium | SO003, SO011 |
| CO029 | The Chinese launch feature said Botshare rents robots from around RMB 200 per day up to four- and five-digit event packages. | Medium | SO011 |
| CO030 | Official site and launch coverage say customers can place orders through a mini program or online marketplace. | High | SO001, SO002, SO011 |
| CO031 | Launch coverage said Botshare bundled trained operators and insurance into standardized delivery for some rentals. | Medium | SO011, SO013 |
| CO032 | Baidu Baike says the platform had already connected multiple robot brands including AgiBot, Unitree, and Jiasu Jinhua/Accelerated Evolution. | Low | SO016 |
| CO033 | Baidu Baike says Botshare offers humanoid and quadruped robot rentals and package-based solutions for specific scenarios. | Low | SO016 |
| CO034 | Jiemian reported that Botshare and PICC completed the first embodied-robot insurance claims cases in April 2026. | Medium | SO018 |
| CO035 | Jiemian reported that more than 1,000 robots on the platform were insured and total coverage exceeded RMB 200 million. | Medium | SO018 |
| CO036 | TechNode reported that JD’s robot ambulance service covered humanoid robots, quadruped robots, AI companion robots, and related maintenance tasks. | Medium | SO017 |
| CO037 | Sohu said Botshare and JD agreed to cooperate on online transactions, offline delivery, supply chain collaboration, maintenance, insurance, recycling, and data-related services. | Medium | SO022, SO025 |
| CO038 | Sina said Botshare and Rui’an Office launched a strategic commercial-space partnership in May 2026. | Medium | SO023 |
| CO039 | IPO Zaozhidao/Sina and Baidu Baike said that by March 2026 Botshare had completed more than 5,500 orders. | Medium | SO007, SO016 |
| CO040 | IPO Zaozhidao/Sina and Baidu Baike said that by March 2026 the platform could dispatch more than 3,000 robots. | Medium | SO007, SO016 |
| CO041 | Baidu Baike reported that national city-partner registrations had exceeded 20,000 by March 2026. | Low | SO016 |
| CO042 | Baidu Baike and China Daily said Spring Festival 2026 orders accelerated sharply, with Baidu reporting roughly 60% sequential growth and China Daily saying bookings were packed through the holiday period. | Medium | SO016, SO021 |
| CO043 | China Daily said more than 54% of Spring Festival Botshare orders were linked to greetings, temple fairs, and shopping-mall performances. | Medium | SO021 |
| CO044 | 36Kr said 60%-70% of Botshare’s early service scenarios were still concentrated in travel, culture, and entertainment. | Medium | SO008 |
| CO045 | 36Kr characterized Botshare as an asset-light platform that does not directly hold robot assets and instead matches supply and demand while adding services such as insurance and secondary-market support. | Medium | SO008 |
| CO046 | Sohu’s June 2026 analysis said falling rental prices were shrinking the room for simple rental spread economics. | Medium | SO025 |
| CO047 | The same Sohu analysis said maintenance, logistics, insurance, asset recovery, and on-site troubleshooting were becoming the real operational bottleneck for robot rental platforms. | Medium | SO025 |
| CO048 | Xinhua said the broader market still suffers from novelty-led demand, scarce repeat customers, and an often necessary one-operator-per-robot deployment ratio. | Medium | SO020 |
| CM001 | Multiple Chinese sources put China’s robot-rental market at roughly RMB 1 billion in 2025. | Medium | SM001, SM011, SM017 |
| CM002 | Multiple 2025-2026 sources project China’s robot-rental market could reach about RMB 10 billion in 2026. | Medium | SM001, SM011, SM014 |
| CM003 | The implied 2025-to-2026 growth rate for China’s robot-rental niche is roughly 10x. | Medium | SM001, SM011 |
| CM004 | Current rental demand is concentrated in events, retail activations, weddings, exhibitions, education, and tourism. | Medium | SM002, SM011, SM012 |
| CM005 | High humanoid purchase prices—often several hundred thousand to more than one million yuan—are a core adoption barrier for smaller users. | Medium | SM011, SM002 |
| CM006 | Rental acts as both a low-risk trial mechanism for customers and a real-world feedback loop for manufacturers. | Medium | SM011, SM025 |
| CM007 | Field pricing in 2025-2026 often ranged from roughly RMB 200-500 per day for simple robot dogs and RMB 2,000-5,000 per day for mainstream humanoid rentals. | Medium | SM002, SM012 |
| CM008 | Peak hype periods previously pushed daily humanoid rental pricing into the RMB 10,000-20,000 range before price correction. | Medium | SM011, SM012 |
| CM009 | Seasonality, unstable pricing, and event-heavy demand indicate that the robot-rental niche is still immature. | Medium | SM002, SM012, SM015 |
| CM010 | Botshare’s relevant market includes temporary access and deployment spend, not the entire robotics hardware market. | Medium | SM002, SM011, SM024 |
| CM011 | Outright robot hardware purchases and component sales should be excluded from Botshare’s directly relevant access-and-service market. | Medium | SM003, SM024 |
| CM012 | Near-term buyer segments include event organizers, retailers, tourism venues, educators, and commercial-space operators. | Medium | SM002, SM011, SM012 |
| CM013 | Budget ownership differs by segment, shifting from marketing or event budgets toward facilities, operations, or warehouse budgets as use cases become more operational. | Medium | SM006, SM011, SM015 |
| CM014 | The June 2026 MIIT-SASAC action plan explicitly targets industrial, service, and special scenarios including manufacturing, maintenance, warehousing and logistics, retail, healthcare, and emergency response. | Medium | SM006 |
| CM015 | The same action plan seeks 100+ high-value application scenarios and 10,000-scale deployment capability by the end of 2026. | Medium | SM006 |
| CM016 | China’s 2026 action plan explicitly encourages Robot-as-a-Service, pay-by-effect, and operating-lease style commercialization to lower user investment thresholds. | Medium | SM006 |
| CM017 | IFR says China’s 15th Five-Year Plan places robotics at the heart of the country’s modern industrial system and shifts AI focus toward physical applications. | Medium | SM018 |
| CM018 | China’s manufacturing sector had an operational stock of around 2 million industrial robots and took 54% of annual global installations in 2024. | Medium | SM003, SM018 |
| CM019 | Statista says China installed a record 295,000 industrial robots in 2024. | Medium | SM003, SM025 |
| CM020 | Statista says China reached 470 industrial robots per 10,000 employees in 2023, ranking third globally. | Medium | SM003 |
| CM021 | IFR says local suppliers increased their share of domestic industrial-robot installations in China from 30% in 2020 to 57% in 2024. | Medium | SM018 |
| CM022 | IFR says industrial robots are likely to remain the backbone of high-speed, precision-driven manufacturing environments. | Medium | SM018 |
| CM023 | IFR says mass adoption of humanoids as universal factory helpers or household assistants will not happen in the near or medium term. | Medium | SM018 |
| CM024 | APAC robotics market revenue is forecast at about USD 42.33 billion in 2025 and USD 141.21 billion in 2035, according to Market Research Future. | Medium | SM022 |
| CM025 | IDC says Chinese users broadly recognize industrial robots for labor substitution, cost reduction, and production stability. | Medium | SM020 |
| CM026 | IDC also says users still want better product performance, software capability, after-sales quality, and easier system integration. | Medium | SM020 |
| CM027 | China’s first national standard system for humanoid robotics and embodied AI was released in March 2026. | Medium | SM007, SM008 |
| CM028 | The standard system has six parts: basic commonality, brain-like and intelligent computing, limbs and components, complete machines and systems, application, and safety and ethics. | Medium | SM007, SM008 |
| CM029 | SCIO/Xinhua says 2025 was China’s first year of humanoid mass production, with more than 140 domestic manufacturers releasing 330+ models. | Medium | SM008 |
| CM030 | SCIO/Xinhua says China’s robotics industry generated nearly RMB 240 billion of revenue in 2024, and first-half 2025 revenue rose 27.8% year over year while industrial robot production hit 370,000 units. | Medium | SM025 |
| CM031 | SCIO/Xinhua says government-backed innovation centers, training facilities, and shared datasets are reducing commercialization frictions and lowering entry barriers. | Medium | SM025 |
| CM032 | Mordor Intelligence estimates the global industrial-robotics market at USD 54.28 billion in 2026, reaching USD 94.38 billion by 2031 at an 11.7% CAGR. | Medium | SM021 |
| CM033 | Mordor says Asia-Pacific contributed 44.36% of global industrial-robotics revenue in 2025. | Medium | SM021 |
| CM034 | Mordor estimates the global robotics market at USD 88.27 billion in 2026 and USD 218.56 billion by 2031, with logistics and warehousing taking 39.10% share in 2025. | Medium | SM024 |
| CM035 | Statista’s industrial-robot stock chart says China held over 2 million robots in operation out of roughly 4.66 million globally in 2024. | Medium | SM003 |
| CM036 | IFR’s World Robotics materials position China as the largest current market for industrial robotics and the anchor of factory automation demand. | Medium | SM009, SM019 |
| CM037 | City News Service framed Botshare’s launch against an industry expectation that China’s robot-rental market could reach 10 billion yuan. | Medium | SM014 |
| CM038 | Sohu’s June 2026 analysis says falling rental prices are shrinking simple spread economics for rental platforms. | Medium | SM015 |
| CM039 | The same Sohu analysis says robot-rental operators must solve logistics, setup, choreography, repairs, battery issues, insurance, and asset recovery after the sale. | Medium | SM015 |
| CM040 | Xinhua says the market’s core challenge is moving from “show” demand into repeat service or operational value. | Medium | SM011 |
| CP001 | Botshare publicly positions itself as a multi-brand robot-rental platform that bundles booking with delivery, operators, insurance, and programming support rather than as a single-robot OEM. | Medium | SP001, SP002, SP003 |
| CP002 | Wanjiyi Rental launched in January 2026 as a full-scenario robot-rental ecosystem platform in Shanghai. | Medium | SP004 |
| CP003 | Wanjiyi says it serves service, cleaning, companionship, performance, and education scenarios through online-offline rental operations. | Medium | SP004 |
| CP004 | Wanjiyi’s alliance publicly includes robot makers, insurers, financial institutions, and city partners, creating a competing supply-and-fulfillment stack. | Medium | SP004 |
| CP005 | JD officially launched self-operated robot rentals with daily or long-term periods and connected that offer to 27 JD MALL experience centers. | Medium | SP005 |
| CP006 | JD said JoyInside is expected to connect with more than 10 million terminal devices in 2026 and already integrates robot brands such as Unitree and Noetix. | Medium | SP006 |
| CP007 | JD’s robot ambulance service covers diagnostics, battery replacement, testing, and repairs and is planned to expand to more than 50 cities. | Medium | SP007, SP008 |
| CP008 | Chinese coverage describes JD’s competitive offer as a full fulfillment stack spanning online transactions, logistics warehousing, maintenance, insurance, recycling, and data collection. | Medium | SP008, SP009 |
| CP009 | ZMProbots markets the Unitree G1 as directly bookable with self-service or operator-led event packages, delivery, collection, and damage cover. | Medium | SP010 |
| CP010 | Futurobots rents Unitree Go2 and A2 robot dogs from seven days with delivery, pickup, training, damage cover, and technical support included. | Medium | SP011 |
| CP011 | JD, ZMProbots, and Futurobots show that retailer-linked or OEM-linked channels can offer robot access directly without requiring a neutral marketplace. | Medium | SP005, SP010, SP011 |
| CP012 | Locus describes its RaaS model as subscription-based OPEX that includes deployment, maintenance, monitoring, analytics, and the ability to scale robot count up or down. | Medium | SP012 |
| CP013 | inVia says it owns, operates, and continuously optimizes robots for customers under a monthly subscription aligned to throughput requirements. | Medium | SP013 |
| CP014 | Vecna wraps robots, software, training, maintenance, and 24/7 monitoring into a low annual fee with flexible multi-year terms. | Medium | SP014 |
| CP015 | Geek+ competes for warehouse budgets with modular picking, sorting, replenishment, pallet, and internal-transport automation that integrates into existing facilities. | Medium | SP015 |
| CP016 | The global warehouse RaaS cohort sells recurring productivity, throughput, and scaling outcomes rather than event-style robot access, making it a stronger substitute in logistics than in promotions. | High | SP012, SP013, SP014, SP015 |
| CP017 | KUKA publicly competes through lifecycle support that spans planning, simulation, commissioning, preventive maintenance, modernization, and used robots with warranty. | Medium | SP016 |
| CP018 | ABB’s robotics services emphasize preventive, recovery, data-driven, and modernization support backed by 1,750 service specialists in 53 countries and more than 100 locations. | Medium | SP017 |
| CP019 | FANUC says it provides lifetime maintenance through more than 280 service locations supporting over 100 countries. | Medium | SP018 |
| CP020 | IFR reported that China installed 295,000 industrial robots in 2024, equal to 54 percent of global deployments, and exceeded 2 million operational robots. | Medium | SP019 |
| CP021 | Because factory buyers already operate within dense installed-base service ecosystems, incumbent OEM channels can compete with Botshare on trust, spares, training, and uptime rather than on discovery alone. | High | SP016, SP017, SP018, SP019 |
| CP022 | Xinhua says China’s rental demand is still led by weddings, corporate galas, shopping-mall promotions, and other show-driven uses, while industrial and logistics deployments are framed as the next frontier. | Medium | SP020 |
| CP023 | China Daily names operators such as Yunji, Shanghai Qingbao, and Ningbo-base businesses as active local participants in the rental market, indicating fragmented city-level supply. | Medium | SP021 |
| CP024 | Public Chinese coverage shows mainstream humanoid day-rates cooling toward roughly CNY3,000-CNY5,000 while lower-end robot dogs can rent for hundreds of yuan per day and premium packages can still reach very high prices. | High | SP020, SP023, SP024 |
| CP025 | Sohu argues that falling rates reduce the room for pure matchmaking arbitrage and move competition toward logistics, on-site tuning, choreography, maintenance, insurance, and recovery speed. | Medium | SP008 |
| CP026 | RoboHorizon and China Daily together show wide public price dispersion across robot dogs and humanoids, which makes apples-to-apples channel pricing difficult to normalize. | Medium | SP021, SP022 |
| CP027 | JD is blending rentals with offline experience centers, retail sales, and auctions, expanding competitive substitution beyond a standalone rental app. | Medium | SP005, SP006 |
| CP028 | Botshare’s own materials and launch coverage already promise local delivery, operators, insurance, and custom programming, so those service features are not unique moat assets by themselves. | Medium | SP001, SP002, SP003 |
| CP029 | Wanjiyi’s “Didi + Taobao” framing and broader market coverage comparing robot rental to power-bank-like convenience imply that ease-of-access messaging is already commoditizing. | Medium | SP004, SP022 |
| CP030 | Wanjiyi’s alliance model suggests another domestic aggregator can scale through partner supply, finance, and city partners rather than through proprietary robot ownership. | Medium | SP004 |
| CP031 | Unitree-linked rental pages and JD’s official launch together show that direct hardware channels can bypass neutral marketplaces while still offering booking, delivery, and support. | Medium | SP005, SP010, SP011 |
| CP032 | Global warehouse RaaS vendors set buyer expectations around SLA-like support, uptime, monitoring, and scaling flexibility, raising the bar for Botshare’s industrial expansion. | High | SP012, SP013, SP014 |
| CP033 | The nearest direct Chinese pressure on Botshare appears to be a mix of Wanjiyi and fragmented city-level operators rather than another clearly dominant national neutral marketplace. | Medium | SP004, SP021 |
| CP034 | The strongest logistics substitute pressure comes from JD and warehouse RaaS operators that sell fulfillment outcomes rather than short-term humanoid access. | High | SP005, SP008, SP012, SP013, SP014, SP015 |
| CP035 | The strongest factory substitute pressure comes from incumbent OEM service channels, not from another app-based rental marketplace. | High | SP016, SP017, SP018, SP019 |
| CP036 | Public sources do not disclose comparable take rates, utilization, or gross margins for Botshare, Wanjiyi, or JD rental channels. | Low | SP004, SP005, SP008 |
| CP037 | Public evidence of repeat industrial or warehouse win-loss outcomes for Botshare versus Wanjiyi, JD-linked channels, or global warehouse RaaS vendors is still absent. | Low | SP003, SP004, SP005, SP020 |
| CP038 | The moat that matters today is localized fulfillment density and after-sales execution rather than exclusive robot access or simple convenience messaging. | High | SP008, SP016, SP017, SP018, SP020 |
| CI001 | Botshare said it recently completed Series A and A+ rounds totaling several hundred million yuan and reaching a reported RMB 7 billion valuation. | Medium | SI004, SI009, SI010, SI024 |
| CI002 | Crunchbase News listed Botshare among May 2026 new unicorns and described the company at a $1 billion valuation. | Medium | SI006 |
| CI003 | The RMB 7 billion valuation reported in Chinese coverage and the $1 billion Crunchbase headline are directionally consistent around the unicorn threshold rather than materially contradictory. | Medium | SI004, SI006, SI024 |
| CI004 | Chinese coverage and Baidu Baike indicate Botshare had already compressed at least six disclosed financing rounds into less than half a year after launch. | Medium | SI004, SI007, SI024 |
| CI005 | Baidu Baike and 36Kr say the January 2026 seed round was led by Hillhouse Venture Capital with strategic industrial participants including Fosun Capital, Tsinghua-affiliated capital, Dafeng, and Zhangjiang-linked investors. | Medium | SI005, SI007 |
| CI006 | The March 2026 angel and angel+ rounds reportedly exceeded RMB 100 million and valued the company at about RMB 3 billion, bringing in industrial, listed-company, and entertainment-linked investors. | Medium | SI005, SI007, SI016 |
| CI007 | 36Kr reported that the April 2026 Pre-A round included CP Robot, Changxin, Meg Smart, Lens Tech, and oversubscribing prior investors, showing a cap table oriented toward channel and scenario resources as well as cash. | Medium | SI005 |
| CI008 | Management said the newest round would be used mainly for RaaS system build-out and expansion into industrial manufacturing, park operations, warehousing, logistics, and commercial services. | Medium | SI004, SI009, SI010 |
| CI009 | Gasgoo and EqualOcean both said Botshare had over 4,000 dispatchable robots and a team of more than 100 people by May 2026, indicating that the new round funds operating scale as well as software systems. | Medium | SI009, SI010 |
| CI010 | Botshare presents itself as an application-service platform that connects robot supply, service partners, creators, and end customers rather than as a single-robot OEM. | High | SI001, SI002 |
| CI011 | CEO Li Yiyan said the platform was fully light-asset in its early stage, with strategic partners purchasing and holding robots while Botshare operated the assets. | Medium | SI014 |
| CI012 | Li Yiyan also said Botshare collects operating-management and service fees under that model, making the most visible revenue mechanism a fee-based platform layer rather than direct hardware sales. | Medium | SI014 |
| CI013 | Public price points range from about RMB 200 to 499 per day for basic or longer-term entry rentals to roughly RMB 1,499 to 5,000 per day for mainstream domestic rentals, with premium packages approaching RMB 100,000 per day. | High | SI011, SI012, SI015 |
| CI014 | Tencent launch coverage showed packaged offers starting at RMB 13,300 and RMB 16,900 per day, indicating that realized pricing can be sold as bundled scenarios instead of one robot at a time. | Medium | SI015 |
| CI015 | Tencent overseas coverage said European daily rents for Lingxi X2 reached about 2,000 to 3,000 euros while North American daily rents for Expedition-series robots could reach $6,000. | Medium | SI014, SI016 |
| CI016 | The product increasingly looks like a rented solution rather than rented hardware because delivery bundles operators, choreography or programming, insurance, technical support, and after-sales recovery. | High | SI012, SI017, SI023 |
| CI017 | Chinese rental prices have dropped materially from early-2025 peaks above RMB 10,000 per day, compressing the spread economics available to simple middlemen. | High | SI012, SI013, SI017 |
| CI018 | Sohu argued that the defensible moat in robot leasing is shifting toward logistics, maintenance, insurance, repair, recovery, and local fulfillment rather than pure device matching. | Medium | SI017 |
| CI019 | Xinhua quoted Botshare CEO Li Yiyan saying the rational human-robot ratio is still about 1:1, indicating labor remains a material cost driver in current deployments. | Medium | SI012 |
| CI020 | The JD-Botshare cooperation scope includes logistics, maintenance, repair, insurance, recycling, and data collection, confirming that uptime infrastructure is part of the core economics rather than a side service. | Medium | SI017, SI023 |
| CI021 | Jiemian reported that more than 1,000 robots on the platform had insurance coverage exceeding RMB 200 million, showing that risk transfer is already a real operating input. | Medium | SI008 |
| CI022 | MIIT and SASAC’s June 2026 action plan explicitly encourages Robot-as-a-Service and operating-lease models to lower upfront user investment thresholds. | Medium | SI020 |
| CI023 | IFR’s May 2026 assessment said real-world humanoid production use remains mostly at demonstrator or pilot stage, limiting near-term assumptions about industrial utilization. | Medium | SI021 |
| CI024 | Botshare may be light on owned robot assets, but it is heavy on human coordination, partner enablement, and service orchestration, so it should not be modeled like a pure SaaS marketplace. | Medium | SI011, SI012, SI014, SI017 |
| CI025 | Public traction disclosures emphasize network and order counts—thousands of robots, dozens to hundreds of cities, thousands of orders, and hundreds of partners—rather than recognized revenue. | Medium | SI009, SI010, SI011, SI014, SI016 |
| CI026 | No reviewed public source in this chapter disclosed Botshare’s revenue, ARR, gross margin, burn, cash balance, runway, CAC, payback, or NRR. | Medium | SI001, SI002, SI004, SI009, SI010, SI016 |
| CI027 | Order counts and dispatchable-device counts are poor substitutes for underwriting because they do not disclose take rate, utilization, cancellation, payment terms, or service cost. | Medium | SI012, SI016, SI017 |
| CI028 | The light-asset operating model reduces direct robot capex on Botshare’s own balance sheet compared with vertically integrated fleet owners. | Medium | SI005, SI014 |
| CI029 | Even with low owned hardware, the model still likely requires significant working capital for partner onboarding, training, dispatch software, insurance, maintenance coordination, and receivables timing. | Medium | SI014, SI017, SI018, SI023 |
| CI030 | The fresh A and A+ rounds lower immediate financing risk relative to the seed and pre-A stage, but management still frames the business around scale build-out rather than profitability or self-funding. | Medium | SI004, SI009, SI010 |
| CI031 | The investor roster across seed, angel, pre-A, and A rounds suggests the cap table is being used to buy channels, industrial scenarios, and ecosystem access as much as pure financial capital. | Medium | SI005, SI007, SI016 |
| CI032 | Launch messaging targeted 200 cities, 200-plus premium partners, 3,000-plus creators, and 400,000-plus customers in 2026, a growth plan that likely requires continued external funding if monetization lags network expansion. | Medium | SI003, SI011 |
| CI033 | Direct registry verification remained incomplete in this chapter because Qichacha blocked automated access to the company page on 2026-06-16. | Medium | SI022 |
| CI034 | Botshare’s privacy policies show that the platform collects order, location, scenario, budget, transaction, and partner-application data as part of normal operations. | High | SI018, SI019 |
| CI035 | The privacy policies also say registration and transaction data may be synchronized to affiliates or business partners, creating governance and compliance exposure as the business scales. | High | SI018, SI019 |
| CI036 | Tencent’s skeptical April profile argued that a RMB 3 billion valuation on roughly 5,500 orders and about 3,000 devices already implied aggressive forward assumptions about platform leverage. | Medium | SI016 |
| CI037 | The same adverse source warned that shared-economy style platform build-outs historically burned very large sums before durable market position emerged, making future dilution risk non-trivial if Botshare’s margins stay thin. | Medium | SI016 |
| CI038 | Overseas rollout to 13 countries may expand price ceilings, but it also adds regulatory, data-privacy, logistics, and local-competition costs before unit economics are proven domestically. | Medium | SI014, SI016, SI018 |
| CI039 | Industrial, park, and logistics scenarios are strategically more attractive than event rentals because they offer higher-frequency demand, but public evidence still does not prove uptime or ROI in those workflows. | Medium | SI010, SI020, SI021 |
| CI040 | Botshare should be underwritten today as a funded service-operations network with software leverage and ecosystem optionality, not as a disclosed recurring-revenue software company. | Medium | SI011, SI016, SI017 |
| CI041 | The privacy-policy disclosures and partner-application workflow show that Botshare is directly processing enterprise-partner data and transaction data itself, which supports platform take-rate optionality but not disclosed pricing. | Medium | SI018, SI019 |
| CI042 | Domestic price compression and overseas higher pricing can coexist because the commercial spread is driven by service density and labor cost by geography, not just by hardware availability. | Medium | SI012, SI014, SI016 |
| CI043 | Tencent overseas coverage said recurring operating scenarios had reached 62 percent of order structure while entertainment had fallen to 27 percent, suggesting demand is broadening even though revenue quality is still undisclosed. | Medium | SI014 |
| CI044 | Launch and Xinhua coverage still show a large share of near-term demand tied to festivals, annual meetings, exhibitions, malls, and other novelty-led use cases, so seasonality and churn risk have not disappeared. | Medium | SI011, SI012, SI015 |
| CE001 | Botshare defines itself as a rental platform connecting robotics service providers with end clients rather than as a single-robot OEM. | Medium | SE001, SE002 |
| CE002 | Botshare’s English site routes buyers into a WeChat mini-program plus customer-service-assisted recommendation flow. | Medium | SE001 |
| CE003 | Botshare’s Chinese site says users can enter through a mini-program or app, review scenario cases, and place orders online. | Medium | SE002 |
| CE004 | The iOS app advertises at least 16 mainstream scenarios, including annual meetings, exhibitions, weddings, mall promotions, cultural-tourism service, and school activities. | Medium | SE012 |
| CE005 | The iOS app lets users choose rental days, equipment quantity, operator add-ons, and custom content, and it claims smart recommendations based on scenario, budget, and timing. | Medium | SE012 |
| CE006 | The iOS app publicly lists WeChat Pay, Alipay, and corporate bank transfer as payment options. | Medium | SE012 |
| CE007 | Botshare’s own surfaces market scenario-based solutions, end-to-end quality assurance, and customized solutions rather than a pure listing board. | Medium | SE001, SE002 |
| CE008 | Launch reporting said Botshare started with 50 core cities, 600-plus localized service providers, and more than 1,000 devices. | Medium | SE003, SE004, SE005 |
| CE009 | Management’s 2026 target stack called for 10-plus OEMs, 200-plus premium leasing partners, 3,000-plus creators, 400,000 customers, and expansion into 200-plus cities. | Medium | SE003, SE004, SE010 |
| CE010 | Public launch coverage showed a multi-brand lineup that included AgiBot humanoids and robot dogs, AheadForm bionic robots, and ULS exoskeletons. | Medium | SE005, SE020 |
| CE011 | Launch demonstrations highlighted weddings, corporate annual galas, event hosting, and education-oriented demos as current scenarios. | Medium | SE005, SE006, SE020 |
| CE012 | Xinhua described Botshare as standardizing more than 10 scenarios and offering premium technician or custom-programming packages. | Medium | SE006 |
| CE013 | China Daily said that more than 54 percent of Spring Festival demand was tied to greetings, temple fairs, and shopping malls, while proposals and parent-child activities were rising. | Medium | SE007 |
| CE014 | A December 2025 Sohu launch feature said customers could choose among 13 mainstream scenario buckets and buy customized skill packages. | Medium | SE010 |
| CE015 | Launch pricing coverage put Botshare’s day-rate range at roughly RMB 200 to above RMB 10,000 depending on robot type and task complexity. | Medium | SE005, SE010 |
| CE016 | Botshare’s official site says local service partners execute on-site delivery and deployment after an order is placed. | Medium | SE001 |
| CE017 | Botshare’s official supply model depends on qualified service partners rather than a fully centralized in-house field team. | Medium | SE001, SE002 |
| CE018 | Public launch coverage says trained operators and insurance can be bundled when scenarios are riskier or more complex. | Medium | SE005, SE010 |
| CE019 | Jiemian reported that Botshare and PICC launched embodied-robot insurance covering robot body loss and third-party liability. | Medium | SE009 |
| CE020 | By April 2026, Botshare said more than 1,000 robots were insured with aggregate coverage above RMB 200 million and first claims had already been processed. | Medium | SE009 |
| CE021 | JD’s robot ambulance service covers humanoids, quadrupeds, and AI companion robots with repair, diagnostics, battery service, testing, cosmetic maintenance, and recycling. | Medium | SE008 |
| CE022 | Sohu’s June 2026 analysis said Botshare’s JD cooperation spans online transactions, offline delivery, logistics, maintenance, insurance, recycling, and data collection. | Medium | SE011 |
| CE023 | Gasgoo said JD Service already operates a robot after-sales SaaS platform with fault alerts, automated work orders, and on-site or depot maintenance. | Medium | SE021 |
| CE024 | Gasgoo said JD’s circular-economy service already covers humanoid, quadruped, exoskeleton, cleaning, serving, and greeting robots. | Medium | SE021 |
| CE025 | The Xiaomi app-store listing shows the Botshare app requests sensitive permissions including location, camera, microphone, phone information, file access, notifications, and package-install privileges. | Medium | SE013 |
| CE026 | Apple’s App Store listing publicly discloses linked data categories including purchases, contact information, and identifiers, plus unlinked user content and diagnostics. | Medium | SE012 |
| CE027 | AGIBOT’s official site lists A2, G1, X2, and X1 robots and says the company is entering commercial mass production of general robots. | Medium | SE014 |
| CE028 | AGIBOT’s store collection shows humanoid, quadruped, and dexterous-hand modules commercialized through a common catalog surface. | Medium | SE015 |
| CE029 | AGIBOT markets the X2 as a half-size humanoid for entertainment and commercial performance with multimodal interaction, 25 degrees of freedom, and optional autonomous navigation or charging packages. | Medium | SE016 |
| CE030 | The X2 FAQ says autonomous movement and navigation are unavailable without an advanced package and that technical issues beyond hardware warranty remain largely the user’s responsibility. | Medium | SE016 |
| CE031 | AGIBOT’s D1 Pro page positions the robot dog for entertainment, research and education, industrial inspection, and security patrols, but says typical payload is about 5 kilograms and battery life is only one to two hours. | Medium | SE017 |
| CE032 | The D1 Edu version needs secondary development to achieve autonomous following, which signals ongoing engineering work for more advanced quadruped workflows. | Medium | SE017 |
| CE033 | AheadForm says it focuses on ultra-bionic humanoid service robots with lifelike appearance and interaction built on AI, robotic control, and bionic skin research. | Medium | SE018 |
| CE034 | ULS says its exoskeletons target automotive, airport ground service, manufacturing, logistics, and emergency or custom projects, broadening Botshare’s potential catalog beyond event robots. | Medium | SE019 |
| CE035 | MIIT’s 2026 action plan explicitly names industrial, service, special, warehousing, logistics, maintenance, retail, medical, and emergency scenarios for humanoid or quadruped deployment. | Medium | SE023 |
| CE036 | The same 2026 action plan requires data governance, privacy protection, collision detection, force limits, emergency stops, black-box logging, fatigue resistance, and long-duration reliability. | Medium | SE023 |
| CE037 | SCIO and CCTV summarize the 2026 humanoid standards system as covering application, operation, maintenance, safety, and ethics across the full lifecycle. | Medium | SE024, SE025 |
| CE038 | MIIT’s 2023 humanoid guidance plus the 2026 action plan show policy support for service-style commercialization, including operating lease or pay-per-use models that lower upfront barriers. | Medium | SE022, SE023 |
| CE039 | Xinhua said current rentals still rely heavily on scripted or manual operation and quoted Botshare CEO Li Yiyan that a rational human-robot ratio is 1:1. | Medium | SE006 |
| CE040 | Xinhua said current demand is still novelty-heavy, repeat customers remain scarce, and the next frontier is industrial, commercial, and household use rather than performances alone. | Medium | SE006 |
| CE041 | RoboHorizon argued that Botshare’s future depends on stabilizing pricing, seasonal demand swings, and incompatible software standards between robot brands. | Medium | SE020 |
| CE042 | Sohu’s June 2026 analysis said the real moat in robot rental is logistics, setup, choreography, maintenance, insurance claims, and asset recovery rather than pure pricing arbitrage. | Medium | SE011 |
| CE043 | The same Sohu analysis said real-world deployments face ground variation, crowd interference, lighting shifts, network interruptions, and collisions that are hard to simulate in the lab. | Medium | SE011 |
| CE044 | Apple’s listing shows the Botshare app is actively maintained close to the run date, suggesting the ordering surface is not abandoned. | Medium | SE012 |
| CE045 | China’s public standards database shows an industrial robot safety application standard that took effect on 2025-03-01. | Medium | SE026 |
| CE046 | Botshare’s English site offers tailored scenario adaptation and transparent quotes by email, implying assisted sales still complements self-serve ordering. | Medium | SE001 |
| CE047 | Botshare’s partnership surfaces emphasize city partners, manufacturing partners, RaaS partners, and creators, so growth is tied to external operator and content coverage. | Medium | SE001, SE002 |
| CE048 | No public Botshare platform API, SDK, or integration manual is visible on Botshare’s own surface; the public technical documentation currently comes from OEM pages such as AGIBOT instead. | Medium | SE001, SE002, SE016, SE017 |
| CU001 | Botshare's official site says it aims to accelerate deployment across restaurants, retail, and corporate events. | Medium | SU001, SU002 |
| CU002 | Botshare's official English site says demand-side clients range from grand openings and marketing activations to corporate events and reception services. | Medium | SU001 |
| CU003 | Launch coverage says early demand centered on conferences, weddings, and education alongside broader commercial scenarios. | Medium | SU003, SU005 |
| CU004 | At launch, Botshare publicly claimed coverage across 50 core Chinese cities. | High | SU003, SU004, SU005, SU007 |
| CU005 | At launch, Botshare said its network included more than 600 service providers. | High | SU003, SU004, SU005 |
| CU006 | At launch, Botshare said more than 1,000 devices were available on the platform. | High | SU003, SU005, SU007 |
| CU007 | Botshare's public 2026 expansion target is more than 200 cities. | High | SU003, SU007, SU008 |
| CU008 | Botshare's public 2026 target includes serving more than 400,000 rental customers. | Medium | SU003, SU005, SU011 |
| CU009 | Yangtse reported that Botshare's first signed city-partner cohort covered more than 60 cities. | Medium | SU014 |
| CU010 | Yangtse reported that more than 100 partner teams formally signed during the first city-partner release. | Medium | SU014 |
| CU011 | Yangtse reported that the first city-partner release locked in nearly 1,000 robots of initial deployment demand. | Medium | SU014 |
| CU012 | People's Daily Online and China Daily both reported that Botshare had already received more than 1,000 Spring Festival orders by February 12 and expected to exceed 5,000 by the end of the holiday period. | High | SU009, SU010 |
| CU013 | People's Daily Online and China Daily both reported that more than 54 percent of Botshare's Spring Festival orders were for New Year greetings, temple fairs, and shopping-mall performances. | High | SU009, SU010 |
| CU014 | People's Daily Online and China Daily said the main consumer markets for robot rentals included Beijing, Shenzhen, and Changsha and were expanding to lower-tier cities. | Medium | SU009, SU010 |
| CU015 | People's Daily Online and China Daily said customers commonly booked two or four robots at a time during the Spring Festival peak. | Medium | SU009, SU010 |
| CU016 | Global Times reported one Shanghai robot-rental provider had nearly fully booked its 30 humanoid robots and robot dogs from January through mid-February because of year-end corporate events. | Medium | SU011 |
| CU017 | Global Times reported that Haidilao had become Botshare's first major client. | Medium | SU011 |
| CU018 | Global Times reported that leased Botshare robots were set to enter select Haidilao stores before Spring Festival 2026 to write calligraphy, perform dances, and interact with customers. | Medium | SU011 |
| CU019 | Sina and China.com.cn both reported that Botshare and Shui On WorkX announced a strategic cooperation that first landed during the May Day period at KIC Knowledge Art Festival. | High | SU012, SU013, SU026 |
| CU020 | The Shui On WorkX / KIC deployment included robot parades, stage performances, NPC-style interactions, and traffic-driving for commercial street merchants. | High | SU012, SU013, SU026 |
| CU021 | Rui'an / Shui On WorkX described Botshare's model as a light-asset way to add robotics into office and commercial-space operations without heavy hardware capex or maintenance burden. | Medium | SU012, SU013 |
| CU022 | Rui'an / Shui On WorkX said Botshare would offer dedicated robot-rental discounts to tenant enterprises and merchants. | Medium | SU012, SU013 |
| CU023 | PEdaily said Botshare was using AWE 2026 to show customer-facing deployments across exhibitions, malls, cultural tourism, brand marketing, celebrations, and education. | Medium | SU015 |
| CU024 | PEdaily said customers at AWE were specifically asking how robots could support store traffic-driving, event propagation, brand interaction, and on-site reception. | Medium | SU015 |
| CU025 | Xinhua said Botshare offered standardized rentals across more than 10 specific scenarios ranging from weddings to exhibitions. | Medium | SU008 |
| CU026 | Xinhua said Botshare's price range started at 499 yuan per day for basic models and reached nearly 100,000 yuan for premium packages with technicians and custom programming. | Medium | SU008 |
| CU027 | Xinhua said platform operators manage booking, payment, insurance, on-site technical support, and standardized service protocols. | Medium | SU008 |
| CU028 | Jiemian reported that more than 1,000 robots on Botshare had embodied-intelligence insurance with aggregate coverage above RMB 200 million. | Medium | SU016 |
| CU029 | Botshare's JD partnership covers equipment leasing, supply-chain logistics, after-sales repair, insurance, asset recovery, second development, and data collection. | Medium | SU017, SU018 |
| CU030 | TechNode said JD's robot ambulance service started in Beijing and is planned to expand to more than 50 cities over three years, improving after-sales infrastructure for rental deployments. | Medium | SU019 |
| CU031 | MIIT's 2026 action plan and SCIO's explainer both frame manufacturing, warehousing and logistics, restaurant retail, healthcare, and emergency response as core deployment scenes for embodied robots and explicitly encourage RaaS or operating-lease models. | High | SU022, SU024 |
| CU032 | IDC said Chinese industrial-robot users want better software capability, after-sales service quality, and easier systems integration, which matches the service-heavy burden Botshare would face outside event scenarios. | Medium | SU023 |
| CU033 | Xinhua said repeat customers are rare because much current robot-rental demand is still for novelty and entertainment. | Medium | SU008 |
| CU034 | Xinhua said current rentals still rely heavily on pre-programmed scripts and manual operation and quoted a rational human-to-robot ratio of 1:1. | Medium | SU008 |
| CU035 | Xinhua said some daily rental prices had fallen by more than 40 percent from peak levels as supply increased and platform competition intensified. | Medium | SU008 |
| CU036 | Sohu said demand is extending from event and exhibition work into store service, commercial marketing, cultural-tourism interaction, and light industrial assistance, but current order flow remains concentrated in short-cycle scenarios. | Medium | SU018 |
| CU037 | Sohu argued that robot-rental competition is shifting from who can source hardware to who can execute logistics, on-site service, maintenance, insurance, and asset recovery. | Medium | SU018 |
| CU038 | Sohu said JD's self-operated robot-rental GMV in January 2026 grew more than 100 percent month on month, while Spring Festival search volume tripled, inquiries quadrupled, and orders doubled versus normal levels. | Medium | SU018 |
| CU039 | No reviewed public source discloses Botshare's NRR, GRR, churn, renewal rate, or standard contract length. | Medium | SU001, SU002, SU003, SU012, SU015, SU018 |
| CU040 | No reviewed public source discloses top-customer revenue share or customer concentration by account. | Medium | SU001, SU002, SU003, SU012, SU015, SU018 |
| CU041 | Because more than half of Spring Festival orders were greetings, temple fairs, and shopping-mall performances, the best-disclosed demand spike is concentrated in promotional rather than operational use cases. | High | SU009, SU010 |
| CU042 | Yangtse described city partners as Botshare's local service nodes while the platform kept product integration, technology support, order coordination, and brand endorsement centralized. | Medium | SU014 |
| CU043 | Yangtse said Botshare wanted to extend its network from more than 60 cities toward hundreds of cities and eventually a two-hour service circle covering China's counties and districts. | Medium | SU014 |
| CU044 | Across official and trade-show sources, the buyer, payer, and user often differ, with brands, event planners, restaurants, and property operators funding deployments that are experienced by shoppers, diners, visitors, or guests. | Medium | SU001, SU003, SU015 |
| CU045 | Botshare's public studies and deployment proof still emphasize generic performance categories such as kung fu, matchmaking/proposals, and stage performance rather than a broad set of named customers with outcomes. | Medium | SU001 |
| CU046 | Seetao, RoboHorizon, and Sina financing coverage all frame 2026 industrial and operational scenarios as the next growth lane, implying that today's public customer mix is earlier and more activation-heavy than a mature recurring-service base. | Medium | SU020, SU021, SU025 |
| CU047 | Tencent News reported that Botshare's current customer structure remained B-end led, with SMEs accounting for 65% of demand and demand shifting from renting devices to renting full solutions. | Medium | SU028 |
| CU048 | Pandaily reported that robot-performance rentals were fully booked a month in advance during the Spring Festival period, reinforcing the holiday-demand spike seen in other sources. | Low | SU029 |
| CR001 | Botshare’s public privacy policy applies across its app, mini-program, website, and other services using the policy. | High | SR014, SR015 |
| CR002 | Botshare says it collects device identifiers, account information, images, videos, addresses, budgets, use scenarios, order details, and transaction records as part of service delivery and account security. | High | SR014, SR015 |
| CR003 | Botshare’s privacy policy discloses third-party SDK and payment dependencies including payment, login, and push-notification components. | High | SR014, SR015 |
| CR004 | The June 2026 MIIT/SASAC action requires embodied-robot deployments to improve collision detection, force-control limits, emergency braking, and black-box safety capabilities before scaled deployment. | High | SR019, SR025 |
| CR005 | The same MIIT/SASAC action calls for lifecycle management, deployment validation, risk-warning mechanisms, and exit channels for fast-changing large-scale deployments. | High | SR019, SR025 |
| CR006 | CAC’s May 2026 smart-agent implementation opinion emphasizes privacy protection, behavior controls, supply-chain security, and traceable governance for intelligent agents in public and commercial settings. | Medium | SR018 |
| CR007 | Shanghai and Wuhan finance-policy sources show robot-rental insurance products already covering third-party liability, product quality responsibility, and information leakage responsibility. | High | SR016, SR017 |
| CR008 | The public source set does not surface a detailed board roster, risk committee description, or public certification set for Botshare despite unicorn-level valuation headlines. | Medium | SR001, SR002, SR006, SR013 |
| CR009 | Botshare has published privacy terms, but those terms disclose only policy-level controls and not the broader governance artifact set investors would expect from a scaled operational platform. | Medium | SR014, SR015, SR001 |
| CR010 | Botshare’s operating model includes platform ordering, service guarantees, partner participation, and local execution rather than pure lead generation. | Medium | SR003, SR013, SR023 |
| CR011 | Botshare and launch coverage claim a national network spanning roughly 50 core cities, 600-plus service providers, and 1,000-plus devices at launch. | Medium | SR003, SR004, SR013 |
| CR012 | Shanghai government reporting describes field engineers checking robot status before arrival, adjusting parameters on site, monitoring live runs, and handling emergency response during deployments. | Medium | SR021 |
| CR013 | Holiday deployments described by Shanghai sources often require robots to operate more than eight hours in dense public environments with unexpected interactions and crowding. | Medium | SR021 |
| CR014 | Securities Daily’s insurance feature says rental operations amplify transport risk, third-party injury risk, data-security risk, and costly repair exposure in cross-scene deployment. | Medium | SR017 |
| CR015 | A Botshare-affiliated robot already generated a paid insurance claim after tipping over and damaging a camera and accessories. | Medium | SR011, SR017 |
| CR016 | Insurance is now positioned by industry sources as a prerequisite for scaling robot-rental orders across regions rather than a nice-to-have add-on. | Medium | SR016, SR017 |
| CR017 | Public sources note that robot rental often bundles onsite technical support and human-robot interaction services in addition to hardware delivery. | Medium | SR017, SR013 |
| CR018 | Sohu’s June 2026 adverse analysis argues that falling rental prices shift defensibility toward logistics, maintenance, insurance, repair, and recovery rather than simple order matching. | Medium | SR008 |
| CR019 | Current public evidence still shows many scenarios relying on operators, choreography, monitoring, or现场运维 rather than fully self-running workflows. | Medium | SR012, SR013, SR021 |
| CR020 | Current Botshare-visible demand is concentrated in entertainment, marketing, holiday, tourism, and other short-duration scenarios rather than deeply embedded industrial workflows. | Medium | SR009, SR010, SR021, SR012 |
| CR021 | Agibot co-hosted Botshare’s launch and publicly presented Jiang Qingsong as both an Agibot partner and Botshare chairman. | Medium | SR013, SR012 |
| CR022 | Tencent coverage frames Botshare as a channel through which Agibot’s own robot products and capabilities can reach more use cases and customers. | Medium | SR023 |
| CR023 | Botshare publicly claims to be open to multiple robot brands and external service providers rather than limited to Agibot hardware. | Medium | SR012, SR013 |
| CR024 | Because Botshare’s origin, chairmanship, and ecosystem messaging are tightly linked to Agibot, neutrality risk remains material even if the platform is marketed as open. | Medium | SR012, SR013, SR023 |
| CR025 | Botshare’s dependency stack extends beyond Agibot to local service partners, insurers, logistics providers, and policy channels. | Medium | SR016, SR017, SR021, SR022 |
| CR026 | An April 2026 adverse Tencent/Sing Tao feature says Botshare was being discussed at roughly RMB 3 billion valuation only a few months after launch while public order volume was just over 5,500. | Medium | SR024 |
| CR027 | Sina and other May 2026 reports say Botshare’s valuation then stepped up again to roughly RMB 7 billion after A and A+ financing. | Medium | SR006, SR029, SR030 |
| CR028 | Public Botshare sources still do not disclose revenue, gross margin, burn, payback, or retention metrics sufficient to validate those valuation jumps. | Medium | SR001, SR006, SR024, SR029 |
| CR029 | Botshare’s national rollout strategy depends on city partners and standardized fulfillment processes rather than app demand alone. | Medium | SR013, SR021, SR024 |
| CR030 | Public background material shows Botshare recruiting senior Alibaba and Ele.me operators, which suggests management recognized early that scaling the network would be execution-heavy. | Medium | SR024, SR006 |
| CR031 | Fast financing can amplify governance risk because public sources identify investors and headlines but not board rights, related-party rules, or detailed shareholder protections. | Medium | SR006, SR024, SR029 |
| CR032 | Tencent/Sing Tao coverage says Botshare was already describing a 13-country global service footprint in April 2026 without corresponding public disclosure of local compliance or unit economics. | Medium | SR024 |
| CR033 | Xinhua describes China’s robot-rental market as moving from gimmick to economic engine, indicating real interest but also acknowledging its novelty-driven origin. | Medium | SR009 |
| CR034 | China Daily says robot rentals are transitioning from niche novelty to mainstream service, which implies the transition is underway rather than complete. | Medium | SR010 |
| CR035 | Shanghai government reporting says Botshare’s holiday-period orders rose nearly 70 percent, but over half of those orders were tied to festive scenarios. | Medium | SR021 |
| CR036 | Tencent interviews with Botshare management say 2025 robot-rental demand was still largely trying or curiosity-driven rather than daily habitual use. | Medium | SR012, SR023 |
| CR037 | Sohu and Tencent reporting indicate that rental prices have already fallen materially as supply expands and more basic hardware becomes available. | Medium | SR008, SR023 |
| CR038 | Botshare still marketed premium daily rental packages in late 2025, which means price compression risk is about what happens next as supply broadens, not that the category is already cheap everywhere. | Medium | SR023, SR007 |
| CR039 | The April 2026 adverse feature warns that six-month payback stories can break quickly if mass production accelerates and rental supply surges. | Medium | SR024 |
| CR040 | MIIT’s 2026 action and Shanghai’s 2025 embodied-intelligence plan both highlight industrial, logistics, commercial, and service deployments as target scenarios for the next phase of commercialization. | High | SR019, SR022 |
| CR041 | Those same policy documents frame many industrial and logistics scenarios as validation, demonstration, or pilot-style tracks that still need safety, reliability, and economic proof before normal deployment. | High | SR019, SR022 |
| CR042 | IFR and IDC context supports the view that China’s robotics push is strong, but it does not prove that Botshare has already solved after-sales service or industrial integration at the platform level. | Medium | SR027, SR028 |
| CR043 | Botshare and Agibot interviews use 100-billion-yuan market language and broad adoption analogies that should be treated as aspirational demand framing rather than audited demand proof. | Medium | SR012, SR013 |
| CR044 | As robots move from demos into dense public and enterprise scenes, insurance and governance sources show that third-party injury, data leakage, and behavior-control risks become more consequential. | Medium | SR016, SR017, SR018 |
| CR045 | Botshare’s visible mitigations include published privacy terms, active insurance integration, supportive policy frameworks, and an expanding partner network. | Medium | SR014, SR016, SR019, SR022 |
| CR046 | A practical thesis-break trigger is failure to convert event-led demand into repeat enterprise workflows within the next 12 to 18 months. | Medium | SR009, SR010, SR021 |
| CR047 | Another thesis-break trigger is inability to standardize uptime, maintenance response, and incident handling across the city network as order volume expands. | Medium | SR013, SR017, SR021 |
| CR048 | A further thesis-break trigger is continued valuation inflation without corresponding public disclosure of revenue, margin, and repeat-usage proof. | Medium | SR024, SR029 |
| CR049 | Yicai reported that Chinese robot insurers now bundle robot-body damage, third-party liability, and cybersecurity-incident coverage, while industry participants also flagged data-compliance and cross-border-flow legal challenges as embodied robots enter public and private spaces. | Medium | SR031 |
| CV001 | Multiple May 2026 sources report that Botshare completed Series A and A+ financing totaling several hundred million yuan at a post-money valuation of RMB 7 billion. | Medium | SV002, SV003, SV004 |
| CV002 | The new financing was earmarked for building Botshare’s RaaS system and expanding into industrial manufacturing, park operations, warehousing, logistics, and commercial-service scenarios. | Medium | SV002, SV003 |
| CV003 | The financing narrative explicitly frames Botshare’s prior commercial mix as display-heavy and event-heavy, with the next phase aimed at higher-frequency industrial use cases. | Medium | SV002, SV003 |
| CV004 | By May 2026 Botshare publicly described more than 4,000 dispatchable robots and a team of more than 100 people supporting its rollout. | Medium | SV002, SV003 |
| CV005 | Crunchbase News separately rounded Botshare into the May 2026 new-unicorn cohort at roughly $1 billion, reinforcing that outside observers are treating the RMB 7 billion mark as unicorn-level. | Medium | SV004 |
| CV006 | Xinhua and China Daily both describe China’s robot-rental market as roughly RMB 1 billion in 2025 and at least RMB 10 billion in 2026. | High | SV005, SV006 |
| CV007 | Xinhua says more than 54% of Spring Festival robot-rental orders were still tied to greeting, temple-fair, and mall-style event scenarios, showing current demand is not yet predominantly industrial or deeply recurring. | Medium | SV005 |
| CV008 | Public 2026 coverage indicates rental pricing reset materially lower from early scarcity peaks above RMB 10,000 per day toward mainstream levels closer to the low-thousands of renminbi per day. | Medium | SV005, SV006, SV007 |
| CV009 | Sohu argues that the moat in robot rental is shifting away from simple listing arbitrage and toward logistics, maintenance, insurance, debugging, and uptime recovery. | Medium | SV007 |
| CV010 | Tencent-linked adverse commentary explicitly asks what capital is pricing into Botshare’s rapid valuation step-up, signaling that some observers already see proof-risk in the financing pace. | Medium | SV008 |
| CV011 | Jiemian reported that embodied-robot insurance claims had already been completed in live deployments, showing the category’s operational risk is real rather than hypothetical. | Medium | SV011 |
| CV012 | MIIT and IFR materials support a real industrial-policy tailwind for humanoid and embodied robotics, but they frame commercial rollout as a staged real-world validation effort rather than a solved deployment problem. | Medium | SV012, SV013 |
| CV013 | Across Botshare’s retained public source set, the disclosed operating proof centers on fleet, orders, scenarios, and expansion plans rather than revenue, ARR, gross margin, burn, runway, or cap-table terms. | Medium | SV001, SV002, SV003, SV004, SV007 |
| CV014 | Because round terms and current financial statements remain undisclosed, the May 2026 headline functions more like a strategic scarcity mark than a public-evidence-backed earnings mark. | Medium | SV002, SV003, SV008, SV013 |
| CV015 | Serve Robotics is a public, SEC-reporting robotics platform, making it a useful disclosed benchmark for a smaller-scale autonomy company with national rollout ambitions. | High | SV017, SV018 |
| CV016 | Serve reported 2025 revenue of $2.7 million and a net loss of $101.4 million. | Medium | SV018 |
| CV017 | Serve ended 2025 with $233.4 million of cash and short-term marketable securities. | Medium | SV018 |
| CV018 | Serve’s market capitalization was about $0.61 billion in mid-June 2026. | Medium | SV019 |
| CV019 | Symbotic is a public, SEC-reporting warehouse-automation company that represents a much more mature industrial-automation endpoint than Botshare’s current business model. | High | SV020, SV021 |
| CV020 | Symbotic reported $2.247 billion of fiscal 2025 revenue and $1.245 billion of cash and cash equivalents at the end of fiscal 2025. | Medium | SV021 |
| CV021 | Symbotic’s market capitalization was about $25.18 billion in mid-June 2026. | Medium | SV022 |
| CV022 | Richtech Robotics is a public robotics company that explicitly pitches a RaaS transition and therefore offers a more model-adjacent disclosed lens than a pure hardware OEM. | High | SV023, SV024, SV026 |
| CV023 | Richtech reported fiscal 2025 revenue of $5.045 million, said it secured 55 RaaS contracts during the year, and ended September 2025 with $193.6 million of cash and cash equivalents. | Medium | SV024, SV026 |
| CV024 | Richtech disclosed a material weakness in internal control over financial reporting tied to inventory accounting, revenue recognition, investments, intangible assets, and payroll-related processes. | Medium | SV024 |
| CV025 | Richtech’s market capitalization was about $0.47 billion in mid-June 2026. | Medium | SV025 |
| CV026 | Knightscope reported 2025 revenue of $11.3 million, service revenue of $8.0 million, and year-end cash of $20.6 million. | Medium | SV027 |
| CV027 | Knightscope’s market capitalization was about $35 million in mid-June 2026. | Medium | SV028 |
| CV028 | Bain says most humanoid deployments remain in pilot phases and still depend heavily on human input for navigation, dexterity, or task switching. | Medium | SV029, SV030 |
| CV029 | CNBC investor commentary warns that early humanoid robotics can still go to zero and that manufacturing discipline matters more than pipeline narratives. | Medium | SV029 |
| CV030 | Using mid-June 2026 public market caps, Botshare’s roughly $1 billion headline is about 1.6 times Serve’s market cap, about 2.1 times Richtech’s, and roughly 28 times Knightscope’s. | Medium | SV004, SV019, SV025, SV028 |
| CV031 | Botshare’s roughly $1 billion headline is only about 4% of Symbotic’s market capitalization, underscoring that Symbotic is a scale endpoint rather than a direct peer. | Medium | SV004, SV022 |
| CV032 | Simple market-cap-to-trailing-revenue lenses vary from about 3 times for Knightscope to about 11 times for Symbotic to roughly 93 times for Richtech and more than 200 times for Serve. | Medium | SV018, SV019, SV020, SV022, SV023, SV024, SV025, SV027, SV028 |
| CV033 | That dispersion means no single public multiple can credibly value Botshare today without first taking a view on which maturity bucket the company will eventually inhabit. | Medium | SV019, SV022, SV025, SV028, SV030 |
| CV034 | On disclosed evidence alone, Botshare currently looks closer to speculative orchestration optionality than to scaled industrial-automation economics. | Medium | SV013, SV018, SV023, SV029, SV030 |
| CV035 | At a $1 billion headline valuation, hypothetical annual revenue levels of $25 million, $50 million, $100 million, and $200 million would imply roughly 40x, 20x, 10x, and 5x revenue respectively. | Medium | SV004 |
| CV036 | Because Botshare does not publicly disclose revenue, investors cannot know where the company actually sits on that implied-multiple sensitivity curve. | Medium | SV001, SV002, SV003, SV004 |
| CV037 | The bull case requires Botshare to convert event-led demand into repeat industrial and enterprise workflows while keeping partner economics and uptime reliable enough for recurring spend. | Medium | SV002, SV003, SV012, SV013 |
| CV038 | The base case is that Botshare becomes a real national orchestration layer for robot deployment but still needs time to prove repeatability, margin structure, and capital efficiency. | Medium | SV002, SV003, SV007, SV013 |
| CV039 | The bear case is that price compression, human-heavy fulfillment, repair and insurance burden, and thin disclosure produce a flat or down-round outcome once novelty demand normalizes. | Medium | SV007, SV008, SV011, SV029, SV030 |
| CV040 | The current roughly $1 billion headline already asks investors to underwrite a meaningful portion of the bull case before public operating disclosure has caught up. | Medium | SV004, SV014, SV029, SV030 |
| CV041 | The most defensible recommendation on public evidence is research-more rather than buy, because strategic momentum is real but price support is still evidence-light. | Medium | SV002, SV003, SV013, SV019, SV022, SV025, SV028, SV030 |
| CV042 | Confidence in that recommendation should be medium because market direction and strategic demand look real even though monetization proof remains incomplete. | Medium | SV005, SV006, SV012, SV013, SV030 |
| CV043 | Risk rating is high because commercialization, service delivery, financing dependency, and disclosure all remain unresolved at the current mark. | Medium | SV007, SV008, SV011, SV023, SV024, SV029, SV030 |
| CV044 | Valuation stance is stretched rather than impossible, because the mark could work if industrial recurrence and monetization prove out quickly but already looks demanding on disclosed evidence. | Medium | SV002, SV003, SV013, SV029, SV030 |
| CV045 | Entry discipline should require either materially more disclosure or a lower effective price than the May 2026 headline before the risk-adjusted setup becomes attractive. | Medium | SV013, SV019, SV022, SV025, SV028, SV030 |
| CV046 | The most important remaining diligence asks are audited revenue recognition, take-rate and gross-margin disclosure, cohort retention, industrial renewal evidence, uptime and incident data, and owned-versus-managed fleet economics. | Medium | SV013, SV017, SV018, SV023, SV024, SV030 |
| CV047 | Thesis-break triggers include no industrial renewals by the next refresh, repeated service incidents, partner-concentration surprises, or another financing step-up without better operating disclosure. | Medium | SV007, SV008, SV011, SV013, SV029, SV030 |