Black Lake Technologies
Industrial AI and cloud manufacturing software diligence report
Black Lake appears to have real product-market fit in China's cloud manufacturing software niche and a credible industrial-AI upsell story, but the company still discloses too little about revenue quality, retention, and cap-table terms to justify an invest-now call at its April 2026 private-market valuation.
Cover facts
Company profile
Black Lake Technologies is a Shanghai-based industrial software company founded in 2016 that has evolved from cloud manufacturing collaboration into what it now calls an AI-native manufacturing operating system. Its core product stack spans Black Lake Intelligent Manufacturing for larger, multi-plant factories; Black Lake Small Work Order for smaller, higher-mix manufacturers; supply-chain collaboration workflows; and a newer layer of industrial AI agents for quoting, order splitting, scheduling, production, and quality decisions. Public sources strongly support real customer adoption, fast-deployment cloud positioning, and a meaningful April 2026 Series D, but still leave investors with material disclosure gaps on financial quality, governance detail, and reconciled operating metrics.
- Website
- blacklake.cn
- Founded
- 2016-01-01
- Founders
- Zhou Yuxiang
- Founding location
- Shanghai, China
- Headquarters
- Shanghai, China
- Product
- Cloud-native MES and manufacturing collaboration software, led by Black Lake Intelligent Manufacturing and Black Lake Small Work Order, plus industrial AI agents that automate workflow decisions across production, quality, warehousing, scheduling, and supply-chain collaboration.
- Customers
- Chinese and increasingly overseas manufacturers ranging from SME workshops to complex multi-plant enterprises across food and beverage, auto parts, industrial equipment, electronics, chemicals, pharma, and other manufacturing verticals.
- Business model
- Annual subscription software with modular cloud deployment, fast implementation, and an upmarket path from lightweight shopfloor tools toward broader enterprise manufacturing operating workflows and AI add-ons.
- Stage
- Series D
- Funding status
- Near-RMB1 billion Series D announced in April 2026 at a post-money valuation above RMB7 billion; public sources indicate strong investor appetite but do not fully reconcile lifetime capital raised or post-round ownership terms.
Executive summary
Top strengths
- Cloud-native MES and collaboration stack with evidence of fast deployment, lower-cost implementation, and multi-tier product packaging from SMEs to larger factories
- Repeated 2025-2026 evidence of broad market adoption, including near-40,000 reported factories/customers and large named manufacturers across multiple sectors
- April 2026 Series D, unicorn valuation, and profitability claims indicate capital access and commercial momentum rather than a speculative pre-revenue story
- Industrial AI workflow narrative is tied to specific manufacturing decision surfaces such as quoting, scheduling, order splitting, production, and quality management
Top risks
- Current revenue, ARR, gross margin, retention, and customer concentration remain undisclosed, making the April 2026 valuation hard to underwrite
- Public operating metrics conflict across sources, especially customer count, market-share framing, headcount, and cumulative capital raised
- Governance and cap-table visibility are limited for a late-stage private company, with no public post-Series-D ownership, board-control, or preference-stack detail
- International expansion and AI monetization are strategically attractive but still thinly evidenced in public sources relative to the valuation premium
Open gaps
- Current ARR or revenue base, gross margin, and cash-generation quality after the April 2026 Series D
- NRR, logo churn, customer concentration, and AI attach-rate or upsell evidence by cohort
- Post-Series-D cap table, investor rights, board seats, and any preference or downside-protection terms
- Reconciled definitions for factories, customers, supply-chain participants, and geographic footprint
- Independent validation of the 52.7% market-share claim and enterprise deployment depth versus large-factory peers
Contents
01Company Overview
1.1 Identity, products, and operating model
Black Lake Technologies presents itself as a Shanghai-founded industrial software company built around cloud-based manufacturing collaboration. Across official materials, the company consistently anchors its identity in 2016, even though entity-level registration records for one known operating company begin in 2017. That difference does not negate the operating narrative, but it does mean later diligence should distinguish between brand history and legal-entity history rather than treating them as interchangeable facts. The product stack is now broad enough to support a two-tier go-to-market story. Black Lake Intelligent Manufacturing is aimed at larger factories that need cross-workshop and cross-plant coordination, while Black Lake Small Work Order is framed as a lighter entry product for smaller, more variable manufacturers. Both are marketed as cloud-native, fast to deploy, and materially cheaper than traditional MES rollouts. That positioning matters because it explains how Black Lake can claim both large named customers and a very wide long-tail factory footprint. The same source set also shows a key diligence caveat: Black Lake's public scale claims are directionally strong but numerically inconsistent. Depending on the page, the company describes itself as serving 4,000+, 32,000+, 34,000+, or nearly 40,000 factories or customers. The right takeaway is not to average those numbers, but to treat Black Lake as clearly scaled while requiring a reconciled KPI pack before using any single customer-count figure in valuation work.[CO001, CO002, CO003, CO004, CO005, CO006]
| Metric | Value / status | As of | Confidence | Gap / note |
|---|---|---|---|---|
| Founded | 2016 brand founding | 2016 | High | Entity registration for one known Shanghai operating company starts in 2017 |
| Headquarters | Shanghai | 2026 | High | Supported by China Daily and Baidu profile pages |
| Stage | Private; Series D | 2026-04 | High | No public listing timeline disclosed |
| Latest financing | Near RMB1bn Series D | 2026-04 | High | Crunchbase translates the round to $146M |
| Latest valuation | >RMB7bn post-money / ~$1.3B on Crunchbase | 2026-04 | Medium | Cross-currency comparison requires exact FX basis |
| Profitability | Company says fully profitable; >60% YoY revenue growth | 2026-04 | Medium | No audited revenue or margin disclosure |
| Customer / factory scale | 4,000+ to near 40,000 depending source | 2021-2026 | Low | Definition likely varies across homepage, customers, factories, and supply chain |
| Headcount evidence | 230 social-insurance (2023); 500+ (Aug 2023); 600+ (Mar 2024) | 2023-2024 | Low | No current audited headcount disclosed |
| Geographic footprint | Singapore, Indonesia, Vietnam named; 12-country claim in Baidu profile | 2025-2026 | Medium | Need reconciled country-by-country revenue mix |
| Revenue / ARR | Not publicly disclosed with current precision | 2026 | Low | Historical profile says revenue >RMB100m in Mar 2024 only |
Snapshot values mix official claims and third-party reporting; scale, headcount, and total-capital fields remain unreconciled across public sources.
[CO001, CO002, CO013, CO014, CO019, CO022]| Product / layer | Target customer | Core workflow | Public evidence | Diligence note |
|---|---|---|---|---|
| Black Lake Intelligent Manufacturing | Large or multi-plant manufacturers | Production collaboration, quality, warehousing, scheduling, cross-factory coordination | Official product page; deep-dive profile | Confirm module attach rates and average contract value |
| Black Lake Small Work Order | Small and medium manufacturers with high-mix, small-batch orders | Order fulfillment, shopfloor coordination, inventory, supplier/customer collaboration | Official Small Work Order page | Need paid-seat, paid-factory, and churn definitions |
| Black Lake Supply Chain | Manufacturing groups and supply networks | Upstream/downstream coordination and data sharing | Named in founder and company profiles | No standalone pricing or customer count disclosed |
| Industrial AI agents | Factories already using Black Lake data and workflows | Quoting, order splitting, scheduling, production, quality decisions | 2026 news profiles and official narrative | Need attach rate, pricing, and verified outcome metrics |
This table summarizes the public product stack; the company does not disclose product-level revenue mix or attach rates.
[CO003, CO004, CO020, CO021, CO032, CO033]| Source | Date | Customer / factory count | Market-share claim | Headcount signal | Interpretation |
|---|---|---|---|---|---|
| Black Lake homepage | Undated | 4,000+ manufacturing enterprises | None on page | None on page | Most conservative live marketing number in the set |
| Digital China speech | 2021-04 | 2,000+ factories | None cited | None cited | Useful historical waypoint, not current scale |
| Official company deep dive | 2025-era content | 32,000+ enterprises; ~30,000 China + Southeast Asia factories | 42.7% SaaS MES share; overall MES No.2 | None cited | Broader company-authored positioning deck |
| China Daily | 2025-10 | 34,000+ enterprises and supply chains | 42.7% cloud-based production-management share | None cited | Independent restatement of older company metrics |
| White paper / QQ / 163 | 2026-04 | Near 40,000 customers or factories | 52.7% cloud production-management share | None cited | Latest and most aggressive growth narrative |
| Baidu English company profile | 2025 context | 32,000+ factories | No share figure | 230 social-insurance employees (2023) | Database-style profile with some risk notes |
| Baidu founder profile / Sina founder profile | 2023-08 / 2024-03 | 32,000+ factories by 2025 context | 52.7% cited in founder-era narrative | 500+ then 600+ employees; revenue >RMB100m | Founder-biography sources help bracket growth but not current metrics |
Black Lake is clearly large by Chinese industrial-software standards, but public scale, share, and headcount figures are not definitionally reconciled across sources.
[CO022, CO023, CO024, CO025, CO026, CO027]Black Lake's public narrative links lightweight collaboration software, named customer proof, industrial AI agents, and early overseas expansion into one operating logic.
Flow figure is conceptual; it maps public narrative links rather than quantified causal coefficients.
[CO001, CO003, CO004, CO020, CO021, CO030]1.2 Founders, leadership, and governance visibility
Founder-CEO Zhou Yuxiang is the single most legible public face of Black Lake. Multiple biographical profiles say he studied computer science at Dartmouth, worked in investment banking on industrial transactions, failed in an earlier data-heavy manufacturing startup, and then rebuilt Black Lake after spending time on factory floors. That sequence is strategically important: Black Lake's current product philosophy explicitly rejects abstract industrial-software copying in favor of narrow, workflow-level pain points that were discovered in live manufacturing environments. Governance visibility beyond Zhou is thinner. Aiqicha surfaces a named director roster for Shanghai Black Lake Technology Co., Ltd., which is enough to prove the company is no longer a one-founder shell, but not enough to underwrite actual control. Public materials do not explain board committees, investor seats, veto rights, or founder economics after the 2026 Series D. That leaves a meaningful diligence gap between what the market can observe and what an investor would need to judge governance quality. The leadership story is therefore strong on founder-market fit and weak on formal governance transparency. That is common for a private late-stage Chinese software company, but it should still be treated as a real underwriting gap rather than assumed away.[CO008, CO009, CO010, CO011, CO012, CO034]
| Person / group | Role disclosed publicly | Background or function | Why it matters | Key-person / diligence note |
|---|---|---|---|---|
| Zhou Yuxiang | Founder, CEO, legal representative, chairman/manager of named entity | Dartmouth-trained; ex-investment banker; founder with direct shopfloor immersion story | Combines founder narrative, product conviction, and public-market storytelling | High key-person dependence on founder vision and investor relationships |
| Li Xiang | Financial head and director of named entity | Finance role disclosed by Aiqicha | Signals at least some finance/governance layering beyond founder-only control | Need full CFO scope and tenure |
| Yu Yan | Director of named entity | Director name disclosed only | Shows broader formal governance perimeter exists | Need operating function and shareholding |
| Du Dikang | Director of named entity | Director name disclosed only | Potential investor or management representative | Need affiliation and board rights |
| Ren Yongqiang | Director of named entity | Director name disclosed only | Potential investor or management representative | Need affiliation and board rights |
| Dennis Cong | Director of named entity | Director name disclosed only | Suggests internationalized governance or investor representation | Need legal name details, affiliation, and control implications |
Aiqicha gives a useful named director roster, but public sources do not explain board committees, voting control, or observer rights.
[CO008, CO009, CO010, CO011, CO012, CO041]| Item | Public disclosure | Source basis | Implication | Diligence note |
|---|---|---|---|---|
| Brand founding date | 2016 | Founder/company profiles | Supports long operating-history narrative before current AI push | Need first-contract and first-revenue dates |
| Shanghai Black Lake Technology Co., Ltd. | Established 2017-03-28; active; director roster on Aiqicha | Aiqicha company detail | Likely one key operating or holding entity | Need exact role in contracts, IP, and employment |
| Shanghai Black Lake Network Technology Co., Ltd. | Named in Baidu English company profile with detailed business summary | Baidu English profile | Suggests more than one relevant Shanghai legal entity in public record | Need legal relationship to the Aiqicha-listed company |
| Named overseas markets | Singapore, Indonesia, Vietnam | Official company deep dive | Shows at least marketed Southeast Asia footprint | Need local entities, customers, and revenue split |
| Broader global claim | 12 countries and 30+ projects | Baidu English profile | Suggests early international execution beyond narrative only | Need dated country list and active-project count |
| Recent overseas push | More frequent travel and opportunities in Southeast Asia, Europe, and the US after 2025 | Jiemian + China Daily | Indicates active global go-to-market buildout | Need proof of recurring overseas revenue |
Entity and footprint rows combine company-authored and database-style profiles because Black Lake does not publish a clean legal-structure chart.
[CO028, CO029, CO030, CO031, CO034]1.3 Funding history and capital structure
Black Lake's April 2026 Series D is well supported by multiple independent news sources: the company raised nearly RMB1 billion at a post-money valuation above RMB7 billion, which also pushed it into unicorn framing on Crunchbase's April list. Caixin adds the most concrete investor disclosure, naming five participants and noting that the round was the company's sixth financing event. The capital narrative attached to the round is consistent as well: management says the money will accelerate industrial-AI rollout and global expansion. What is not consistent is cumulative capital history. Older official materials described the company as having already raised nearly RMB1 billion by the C round, while CB Insights still showed only $108.53 million total raised at fetch time. Those numbers might be reconciled through stale databases, FX translation, or different treatment of undisclosed intermediates, but the public record does not do that reconciliation for the reader. For diligence purposes, the right interpretation is that Black Lake has no visible fundraising access problem, but its public financing ledger is not clean enough to plug directly into ownership or dilution modeling. A post-Series-D cap table remains a must-have request.[CO013, CO014, CO015, CO016, CO017, CO018]
| Stakeholder | Role / round | Economic importance | Public evidence | Diligence ask |
|---|---|---|---|---|
| Guoxiang Capital | Series D investor | Named participant in near-RMB1bn round | Caixin Apr 2026 | Confirm check size and rights |
| Shanghai State-owned Capital Leading Fund | Series D investor | Signals local-state backing in latest round | Caixin Apr 2026 | Confirm strategic terms or policy expectations |
| Zhiying Investment (Fosun-linked) | Series D investor | Adds diversified private-capital participation | Caixin Apr 2026 | Confirm affiliation and follow-on reserve |
| National AI Industry Investment Fund | Series D investor | Strategic signal for industrial-AI positioning | Caixin Apr 2026 | Clarify whether investment carries ecosystem or procurement implications |
| Huaxia Zhiqing Venture Capital | Series D investor | Named new-round participant | Caixin Apr 2026 | Confirm ownership and board rights |
| Temasek / CITIC Industrial Fund / GSR Ventures / Jiyuan Capital / Lightspeed China | Earlier named investors | Evidence of prior institutional support before Series D | Official company deep dive | Reconcile who remains on cap table post-Series D |
| Zhou Yuxiang / management | Founder-management influence | Public face and likely major governance center despite opaque economics | Founder profiles + entity records | Request fully diluted founder ownership and voting rights |
Public investor disclosure is strongest for the 2026 round and much weaker for earlier rounds; no public cap table reconciles dilution across cycles.
[CO013, CO015, CO016, CO017, CO018]1.4 Milestones, footprint, and early risk signals
The strongest strategic through-line in the record is Black Lake's shift from collaboration SaaS into industrial AI. The origin story begins with factory-floor workflow coordination, evolves through rapid-deployment products such as Small Work Order, and by 2023-2026 becomes explicitly framed as an AI-native manufacturing operating system with industrial agents for quoting, order splitting, scheduling, production, and quality. That transition is not purely marketing language: independent 2026 reporting describes concrete agent categories, task volume at scale, and a management thesis that Chinese manufacturing may leap directly from low-software penetration into agent-led decision support. Geographic ambition is also visible, though still more narrative than audited fact. Public sources reference Singapore, Indonesia, and Vietnam; Baidu's English profile goes further to claim operations in 12 countries; and China Daily plus Jiemian describe rising overseas interest and travel. The company is therefore best described as early international rather than domestically confined. Risk signals exist, but they are summary-level. Aiqicha and Baidu profile pages show hearing notices, litigation relationships, and equity-freeze references, yet no public source in hand demonstrates a sanction, insolvency process, or product-recall event. The adverse conclusion is therefore nuanced: there is enough smoke to warrant docket-level follow-up, but not enough disclosed substance to make legal overhang a chapter-one red flag on its own.[CO020, CO021, CO028, CO029, CO030, CO031]
| Date | Event | Type | Amount / status | Participants | Implication |
|---|---|---|---|---|---|
| 2015 | Mada Data founded as Zhou Yuxiang's first industrial-data startup | founding | Later failed | Zhou Yuxiang and partners | Explains why Black Lake later emphasized workflow fit over abstract analytics |
| 2016 | Black Lake founded in Shanghai | founding | Operating brand established | Zhou Yuxiang and founding team | Start of current company narrative |
| 2018 | Black Lake Intelligent Manufacturing launched as early flagship product | product | Cloud manufacturing-collaboration product | Black Lake | Anchors original large-factory SaaS motion |
| 2020 | Black Lake Small Work Order launched for smaller factories | product | Lightweight mobile-first collaboration tool | Black Lake | Expanded TAM toward smaller manufacturers |
| 2021-04 | Zhou spoke at the Digital China Summit and cited 2,000+ served factories | scale | Public stage presence | Black Lake / Digital China Summit | Shows national-level visibility before AI narrative |
| 2024-03 | Sina founder profile described 600+ employees and revenue above RMB100m | scale | Historical operating marker | Sina Finance | Useful waypoint for pre-Series-D scale |
| 2025-10 | China Daily profiled Zhou after economic-situation symposium participation | governance | Policy visibility increased | China Daily / Zhou Yuxiang | Signals founder visibility beyond pure startup media |
| 2026-04 | Black Lake announced near-RMB1bn Series D at >RMB7bn valuation | financing | Latest disclosed round | Black Lake and Series D investors | Confirms continued capital access and unicorn status |
| 2026-04 | Independent profiles described 6 categories and 11 industrial AI agents already in use | product | AI program at scale | ITHome / IPO早知道 | Moves narrative from collaboration SaaS to AI operating system |
| 2026-04 | Management framed 2026 as the first year of industrial-AI productization and targeted >80% AI-agent penetration within served factories over 3-5 years | strategy | Forward-looking target | Black Lake / IPO早知道 | Creates upside case but also execution risk if attach rates lag |
| 2025 public-risk context | Aiqicha and Baidu profiles surfaced hearing notices, litigation relationships, and equity-freeze references | adverse | Summary-level risk signals only | Aiqicha / Baidu | Merits follow-up but is not yet a disclosed existential issue |
Milestones combine founding, product, financing, policy visibility, and adverse-signal events so later chapters have one chronology of record.
[CO010, CO013, CO019, CO020, CO021, CO029]02Market Analysis
2.1 Market boundary and substitute logic
Black Lake's relevant market is not the entire automation stack. The product evidence shows a software wedge centered on manufacturing execution, collaboration, and data visibility for factories that need faster planning, better traceability, and tighter coordination across plants or across the supply chain. That means the directly relevant spend pool includes MES software, cloud manufacturing collaboration, and adjacent workflow software for quality, warehousing, equipment, and supplier coordination; it does not include automation hardware, robotics capex, or generic ERP accounting modules, even though those systems touch the same factory workflows. The substitute set matters because Black Lake wins by framing itself against traditional on-premise MES and ERP-heavy implementation models rather than against no software at all. Its official materials repeatedly stress cloud deployment, rapid rollout, lower upfront cost, and mobile usability. The large-enterprise product promises multi-plant standardization and API-led integration, while Small Work Order is pitched as a lighter, faster, lower-cost route for SMEs that still live with spreadsheets, messaging apps, delayed reporting, or rigid legacy software. That boundary logic is the key to reading the market correctly: Black Lake is competing for a narrower but more actionable software budget than the full smart-factory stack, while still benefiting from broader digitization and industrial-AI tailwinds.[CM001, CM002, CM003, CM004, CM005, CM006]
| Segment / category | Included spend | Excluded spend | Buyer / payer | Relevance |
|---|---|---|---|---|
| Public-cloud SaaS MES | Recurring software for production execution, quality, warehousing, traceability, and cross-factory collaboration | Automation hardware, implementation hardware, and unrelated ERP modules | Plant operations, digital-transformation, or manufacturing IT budgets | Direct current monetization wedge for Black Lake |
| Cloud-native manufacturing collaboration | Workflow software connecting workshops, factories, and supplier-facing production processes | Pure office SaaS and non-manufacturing collaboration tools | Operations leaders and plant-management sponsors | Explains why Black Lake markets itself beyond narrow shop-floor control |
| SME order-fulfillment manufacturing SaaS | Order, scheduling, inventory, and lightweight execution software for small and mid-sized factories | Full-suite enterprise ERP replacement projects | Owners, factory managers, or SME operations leads | Captures the Small Work Order expansion path |
| Large-enterprise multi-plant execution layer | MES plus shared data standards, dashboards, quality, equipment, and inter-factory coordination | Heavy automation capex and bespoke systems-integration hardware | Plant groups, operations transformation, and IT co-sponsors | Matches the Heihu Zhizao and case-study motion |
| Industrial-AI overlays on factory data | Scheduling, maintenance, analytics, and workflow agents built on manufacturing data | Foundation-model infrastructure spending that is not application-specific | Innovation, operations excellence, and digital leaders | Important growth adjacency, but not the whole market boundary today |
The actionable market is software and workflow spend around execution and collaboration; hardware automation and generic enterprise software are adjacent but should not be counted as Black Lake addressable revenue.
[CM001, CM002, CM003, CM004, CM005, CM006]Black Lake sits inside nested layers that narrow from broad manufacturing digitization into the specific cloud-MES software wedge it monetizes today.
The pyramid mixes adoption breadth with revenue layers to show category narrowing; only the middle three layers are direct market-size numbers.
[CM005, CM007, CM008, CM009, CM013]2.2 China sizing lenses and demand backdrop
The most decision-useful sizing lens is the public China MES market rather than a hand-wavy "industrial software" TAM. IDC's 2024 market read puts China MES solutions at RMB15.91 billion, with RMB6.29 billion in software and RMB1.005 billion in public-cloud SaaS MES. Those layers matter because they show both opportunity and constraint: Black Lake is competing inside a real and growing software category, but the public-cloud slice remains much smaller than the full services-plus-software pool. The company's underwriting case therefore depends less on claiming a massive theoretical market and more on taking share as deployment preferences migrate toward cloud-native, cross-factory coordination and AI-enriched workflows. China's macro adoption backdrop is strong enough to support that migration. CAICT says 89.6% of above-scale industrial enterprises had undertaken digital transformation by end-2025, while equipment digitization reached 57.7%. Digitization is deepest in automotive, shipbuilding, and electronics, and national infrastructure keeps widening: more than 30,000 basic smart factories, more than 1,200 advanced smart factories, more than 230 excellence-level smart factories, and nationwide 5G-plus-industrial-internet coverage across all 41 industrial categories. NBS data on connected devices, industrial robots, and additive manufacturing reinforce the same point: Chinese manufacturing is no longer debating whether digitization matters, but which software layers, delivery models, and AI features deliver the fastest operational payoff.[CM007, CM008, CM009, CM010, CM011, CM012]
| Publisher | Year | Geography | Value | CAGR / growth | Methodology | Confidence | Limitation |
|---|---|---|---|---|---|---|---|
| IDC via Tencent News | 2024 | China MES solutions market | RMB15.91bn | +11.4% YoY | Solutions market including software and services, excluding hardware | Medium | Public summary cites IDC output but full report tables are not open |
| IDC via Tencent News | 2024 | China MES software market | RMB6.29bn | +16.3% YoY | Software-only slice inside the broader MES market | Medium | Does not itself reveal contract mix between cloud and on-prem |
| IDC via Tencent News | 2024 | China public-cloud SaaS MES | RMB1.005bn | +15.2% YoY | Public-cloud SaaS MES as a subset of MES software | Medium | Category is narrower than the company's broader collaboration narrative |
| CAICT / State Council | 2025 | China manufacturing digitization coverage | 89.6% of above-scale industrial enterprises | n/a | Enterprise digitization coverage, not revenue | High | Adoption breadth is not the same as software spend depth |
| ABI Research | 2028 | Southeast Asia Industry 4.0 investment | US$301.6bn | 32.9% CAGR | Regional Industry 4.0 investment forecast | Medium | Regional forecast spans more than MES or SaaS alone |
| Source of Asia | 2029 | ASEAN manufacturing market | US$2.3tn | From US$1.7tn in 2018 | Regional manufacturing output / market trajectory | Medium | Manufacturing output is a demand backdrop, not software TAM |
These are evidence-constrained sizing lenses rather than a single harmonized TAM; they intentionally mix category revenue and adoption/output proxies to show what can and cannot be defended from public data.
[CM007, CM008, CM009, CM013, CM038, CM040]Public China MES numbers are most useful when shown as comparable layers rather than forced into one synthetic TAM estimate.
The fourth bar is a simple subtraction of public-cloud SaaS MES from the total MES software market and is included to show how much of the category still sits outside the public-cloud slice.
[CM007, CM008, CM009]2.3 Buyer segments, budget owners, and adoption path
Black Lake is effectively selling into two buyer motions. The first is the larger-factory or group-factory motion served by Black Lake Intelligent Manufacturing. Here the economic problem is cross-plant standardization, multi-role workflow control, and the ability to connect production, warehousing, quality, equipment, and supplier data without a long custom project. The case studies with Liby, Mengniu, and Yada all fit that logic: the buyer is trying to connect multiple systems or multiple sites and cares about transparency, traceability, and coordinated execution more than a simple digital checklist. The likely budget owner is therefore shared between plant or operations leadership and IT or digital-transformation teams, because rollout success depends on both workflow ownership and system integration. The second motion is the SME and high-mix manufacturing wedge served by Small Work Order. That product is explicitly designed for smaller factories facing order volatility, non-standard work, inventory lag, and weak process transparency. Its faster deployment and subscription pricing lower the adoption threshold, and its open APIs create an upgrade path into heavier MES needs rather than a hard product cliff. This matters strategically because it lets Black Lake serve both the top-down buyer that wants multi-factory control and the bottom-up buyer that first wants faster order fulfillment. In market terms, the company is not selling one undifferentiated MES product; it is segmenting by organizational maturity, workflow complexity, and time-to-value expectations.[CM021, CM022, CM023, CM024, CM025, CM026]
| Segment | Buyer | User | Payer | Workflow | Budget owner | Adoption trigger |
|---|---|---|---|---|---|---|
| Multi-plant CPG / food groups | Group manufacturing leadership | Plant managers, quality, warehousing, planners | Corporate operations budget | Cross-factory visibility, quality, delivery, and supply coordination | Operations plus IT / digital | Need to standardize processes and shorten rollout across sites |
| Regulated process manufacturers | Operations and compliance leadership | Workshop supervisors, QA, document owners | Manufacturing operations / compliance spend | Traceability, SOP digitization, auditability, and batch visibility | Operations plus quality / IT | Need for compliant digital records and multi-site control |
| Discrete industrial groups | Plant operations and production leadership | Schedulers, production teams, warehouse, maintenance | Factory-transformation budget | Planning, execution, equipment, materials, and OEE visibility | Operations plus plant IT | Need to connect SCADA, ERP, and shop-floor data |
| High-mix SME manufacturers | Owner or factory general manager | Sales, purchasing, production, inventory, finance | Owner-managed operating budget | Order fulfillment, scheduling, inventory, and light execution | Owner / operations | Need faster delivery and less manual coordination with low IT overhead |
| Supplier / contract manufacturing networks | Lead factory or brand supply-chain team | Supplier coordinators and workshop leads | Lead manufacturer or supply-chain program budget | Order progress, exception handling, and upstream / downstream collaboration | Supply-chain operations | Need real-time coordination beyond one factory boundary |
| ASEAN greenfield or regional expansion targets | Regional manufacturing leadership | Country operations teams and implementation partners | Expansion / digital-transformation budget | Replication of China-proven operating model into new plants or vendor ecosystems | Regional operations plus partner ecosystem | Need lower-cost, cloud-first tooling with partner-assisted rollout |
Budget ownership is inferred from the product architecture and case studies; public sources show operational pain points clearly but do not disclose formal procurement authority or ACV by buyer type.
[CM021, CM022, CM023, CM024, CM025, CM028]Black Lake addresses different buyers through a large-enterprise coordination product and a faster-moving SME order-fulfillment product, while regional expansion readiness differs across ASEAN country profiles.
The matrix expresses buyer logic qualitatively because public sources do not disclose ACV, buyer titles, or formal procurement org charts by segment.
[CM021, CM022, CM023, CM024, CM025, CM028]2.4 Growth drivers, constraints, and Southeast Asia option value
The growth case is straightforward: policy, infrastructure, and AI are now reinforcing one another. China's official and quasi-official sources describe a manufacturing base that is already broadly digitized, still adding smart-factory capacity, and increasingly open to AI agents, predictive maintenance, and cross-factory data layers. That is exactly the environment where a cloud-native MES vendor can argue for shorter deployment cycles, lower integration friction, and a clean path from operational data into industrial-AI features. If IDC is right that SaaS MES is shifting from simple low-cost replication toward multi-factory and cross-organization coordination, Black Lake's positioning is directionally aligned with where the category is moving. The constraint case is just as important. SASAC still highlights SME hesitation, standards gaps, and weak security awareness. Deloitte shows that industrial-AI adoption is slowed by cost, use-case ambiguity, skills shortages, and data readiness. WEF and ASEAN/OECD add a similar warning: infrastructure, talent, and interoperability are uneven, and that unevenness is exactly what complicates regional rollout. Southeast Asia still matters as option value, not as a proven core. ABI, Source of Asia, Eurogroup, ASEAN/OECD, KAS, and BCG all support the idea that ASEAN manufacturing digitization will expand and that countries such as Singapore, Thailand, Malaysia, Vietnam, and Indonesia offer plausible landing zones. But they also imply that Black Lake's regional upside depends on country selection, partner strategy, and proof that its China-born operating model can travel across heterogeneous digital-maturity tiers.[CM031, CM032, CM033, CM034, CM035, CM036]
| Driver / constraint | Direction | Timing | Implication | Diligence ask |
|---|---|---|---|---|
| China manufacturing digitization at 89.6% coverage and 57.7% equipment penetration | Positive | Current | Broadens the installed base that can adopt execution software rather than just basic digitization | Request Black Lake's mix of first-time digitizers vs replacement deals |
| Smart-factory and 5G industrial infrastructure buildout | Positive | Current | Makes multi-site data visibility and connected workflows more realistic at scale | Test how much of Black Lake demand comes from 5G / IIoT-enabled projects |
| Rapid growth in industrial AI and agent use | Positive | Current to near-term | Raises value of structured production data and can expand software wallet share | Request attach rates and paid pricing for AI modules |
| Cloud delivery and lower rollout cost | Positive | Current | Supports Black Lake's wedge against long-cycle on-prem deployments | Validate actual time-to-live and services burden on recent projects |
| SME reluctance and capability gaps | Negative | Current | Can slow conversion even where digitization pain is obvious | Measure win rates and churn in the SME segment by industry and owner sophistication |
| Cost, use-case clarity, and data readiness barriers for industrial AI | Negative | Current | Can delay AI upsell even after core MES adoption | Separate paid AI usage from pilot or marketing-stage usage |
| Standards, security, and trust gaps | Negative | Current | Raises friction in regulated or security-sensitive factories | Confirm security certifications, audit history, and regulated-industry references |
| Uneven ASEAN digital maturity | Negative | Near-term | Makes regional expansion country-selective rather than one-size-fits-all | Prioritize country sequencing, partner model, and local implementation economics |
The same macro environment that helps demand also makes execution uneven; underwriting should distinguish between category momentum and Black Lake's ability to convert that momentum into repeatable, profitable deployments.
[CM011, CM013, CM014, CM017, CM031, CM033]The expansion logic runs from macro digitization to pilot deployment, then to multi-plant replication, supply-chain coordination, and finally AI overlays or ASEAN replication.
This flow is conceptual and maps the adoption path implied by the evidence set; it is not a quantified conversion funnel.
[CM011, CM017, CM021, CM024, CM031, CM038]2.5 Exhibits
03Competitors
3.1 Landscape segmentation and Black Lake's positioning niche
The public source set supports a clear competitive segmentation rather than one undifferentiated "MES market." At the heavyweight end, Siemens Opcenter, SAP Digital Manufacturing, and Rockwell's Plex all present manufacturing execution as one layer inside broader manufacturing operations stacks that tie planning, quality, analytics, automation, and enterprise systems together. Those vendors are relevant whenever the buyer already lives inside Siemens automation, SAP ERP, or Rockwell/Plex quality and plant systems, because execution software then becomes part of a larger systems-of-record decision rather than a stand-alone workflow purchase. At the lighter end, Odoo, Katana, and MRPeasy package manufacturing around inventory, orders, procurement, and shop-floor reporting with transparent online pricing and easier onboarding. Tulip sits between those worlds: it is much more MES-specific than a general SMB MRP tool, but it still sells cloud-native, composable, app-based operations software with explicit packaging and partner-led deployment. Black Lake's own two-product split matches that market shape. Intelligent Manufacturing is aimed at larger or multi-plant factories that need planning, quality, warehousing, and cross-factory coordination, while Small Work Order is designed for high-mix Chinese SMEs that care more about fast go-live, low learning cost, and order-centric coordination. Domestic Chinese rivals matter as much as global brands. Digiwin and Saiyi both market broad manufacturing-software suites with MES, planning, quality, and industry implementation depth, which makes them strategically closer to Black Lake's China-core opportunity than their English-language branding might first suggest. The implication is that Black Lake is not defending a monopoly category. It is defending a middle position: more factory-native than generic ERP/MRP tools, more agile and local-fit than classic heavyweight incumbents, and under pressure from domestic suites that can attack with stronger channel history and enterprise trust inside China.[CP001, CP002, CP004, CP005, CP006, CP007]
| Competitor | Category | Scale / funding signal | Target segment | Differentiation | Limitation |
|---|---|---|---|---|---|
| Black Lake | Cloud-native China MES + SME work-order stack | 4,000+ to ~40,000 factories/customers claimed across company materials | Chinese manufacturers from SMEs to multi-plant groups | Fast deployment, China-local workflows, supplier/factory collaboration, AI-native messaging | Public pricing is qualitative rather than explicit list pricing |
| Siemens Opcenter | Global incumbent MOM/MES | Siemens public-company industrial-software incumbent | Large regulated, process, and discrete manufacturers | PLM-to-automation linkage, digital twin framing, quality and traceability depth | No public list pricing on reviewed pages; heavier enterprise motion |
| SAP Digital Manufacturing | Global incumbent cloud MOM/MES | SAP public-company manufacturing cloud suite | Enterprises already standardized on SAP stack | Planning-logistics-workforce-quality integration in one SAP BTP layer | No public list pricing on reviewed pages; enterprise quote-led packaging |
| Tulip | Composable cloud MES | MIT spinout; 60+ implementation partners in 20 countries | Regulated and discrete manufacturers wanting app-based execution | No-code/app-based MES, open API, validation pack, explicit packaging | 10-interface minimum and add-on structure can be less SMB-like than per-user tools |
| Plex | Cloud MES/QMS/APM suite | Rockwell platform with 96% disclosed gross renewal rate | Plants wanting unified quality and execution with ERP linkage | Single UI across MES, QMS, monitoring, and asset workflows | Custom pricing and enterprise sales motion |
| Digiwin | Regional ERP + MES + WMS + AIoT suite | 44 years manufacturing focus; 50,000+ factories served; Shenzhen-listed | Asia-Pacific manufacturers and implementation partners | Local manufacturing depth, broad operational stack, sector templates | Public pricing unavailable; implementation-heavy motion likely |
| Saiyi | China industrial software + AI suite | Listed industrial-software vendor with broad case footprint | Large manufacturing groups plus SMEs | iMOM for big groups and 43 lightweight apps for SMEs | Public pricing unavailable; much public proof is company-selected |
| Odoo | Horizontal ERP with manufacturing app | 15 million users across Odoo ecosystem | SMBs wanting low-cost integrated ERP/MRP plus shop floor | Low public price, offline shop-floor app, broad app ecosystem | Less manufacturing-specialist positioning than dedicated MES vendors |
| Katana | Inventory-led production software | 1,500+ businesses cited on homepage | Product businesses selling across multiple channels | Fast onboarding, integrations, traceability, strong inventory/order fit | More inventory-centric than deep plant-execution suite |
| MRPeasy | Small-manufacturer MRP/MES substitute | 2,000+ manufacturers trust the software; 10-200 employee target | Small manufacturers needing planning, inventory, and shop-floor reporting | Transparent per-user pricing and clear SMB fit | Less suited to large multi-plant, enterprise-quality-heavy deployments |
Representative competitor set mixes heavy incumbents, cloud-native peers, domestic China suites, and lightweight substitutes; scale signals are not normalized because sources mix factories, customers, users, and company-level reach.
[CP001, CP004, CP005, CP006, CP007, CP008]Ordinal positioning of ten competitors on two public-evidence-backed axes: execution breadth (x-axis, 1-10, from lightweight inventory/MRP tooling to full MOM suites) and deployment approachability (y-axis, 1-10, from heavy custom enterprise motion to fast, low-friction cloud rollout). Black Lake sits in the middle-high zone: broader and more factory-specific than Odoo, Katana, and MRPeasy, but lighter and more approachable than Siemens, SAP, and Plex.
Scores are ordinal analyst estimates synthesized from public deployment language, disclosed pricing transparency, and product-breadth descriptions on the reviewed pages as of 2026-06-16. They are not vendor-published benchmark positions and should be read as comparative synthesis rather than audited measurements.
[CP004, CP005, CP006, CP008, CP009, CP010]3.2 Capability breadth, packaging, and where buyer overlap is real
Black Lake's overlap with competitors is real, but it is not symmetric. Against Siemens, SAP, and Plex, the overlap is strongest in traceability, plant execution, scheduling, quality, and multi-system integration. The difference is packaging: those incumbents describe execution as part of broad MOM or smart-manufacturing control planes, with stronger public language around standards, workforce orchestration, enterprise analytics, digital twins, and regulated workflows. Black Lake's public pages instead lean into prebuilt apps, cloud-native delivery, API connectivity, and practical multi-factory or supplier collaboration for Chinese manufacturers. That makes Black Lake look operationally lighter and more adaptable, but also less publicly explicit on compliance and enterprise-governance detail. Against Tulip, the contest is much closer on architecture and buyer psychology. Both vendors market cloud-native, configurable, API-connected manufacturing software with AI or no-code angles and faster implementation than legacy MES. Tulip, however, is notably more transparent in public packaging: it publishes interface-based pricing, regulated-industry add-ons, and partner/distribution signals through AWS and Microsoft. Black Lake still discloses economics mostly through relative claims such as lower cost versus traditional MES and fast deployment windows. That is enough to support a value story, but not enough to let an outsider benchmark list economics with the same precision available for Tulip, Odoo, Katana, or MRPeasy. The lowest end of the competitive stack is also strategically important because it shapes buyer expectations. Odoo, Katana, and MRPeasy all tell manufacturers they can replace spreadsheets, manual order tracking, and fragmented inventory workflows without accepting a classic year-long MES project. For small and mid-sized factories, those tools anchor a real outside option. Black Lake's Small Work Order remains more manufacturing-specific in Chinese workflow language and upstream-downstream collaboration, but the public evidence says procurement pressure will still come from explicit monthly software prices and quick-start promises, not just from global industrial incumbents.[CP011, CP012, CP013, CP014, CP015, CP017]
| Capability / buying criterion | Black Lake | Siemens | SAP | Tulip | Digiwin | Saiyi | Odoo | MRPeasy |
|---|---|---|---|---|---|---|---|---|
| Multi-plant execution and group coordination | Full | Full | Full | Partial | Partial | Full | Partial | Partial |
| Shop-floor traceability and quality workflows | Full | Full | Full | Full | Full | Full | Full | Partial |
| Supplier / upstream-downstream collaboration | Full | Unknown | Partial | Partial | Partial | Partial | Partial | Partial |
| Open API / system integration messaging | Full | Partial | Full | Full | Partial | Partial | Partial | Partial |
| AI / no-code / configurable workflow angle | Full | Partial | Partial | Full | Partial | Partial | Partial | Partial |
| Explicit public list pricing | No | No | No | Yes | No | No | Yes | Yes |
| China-local manufacturing delivery orientation | Full | Partial | Partial | Partial | Full | Full | Unknown | Unknown |
Full/Partial/Unknown values are analyst synthesis of the reviewed public source set as of 2026-06-16; Unknown means the reviewed pages did not confirm the capability, not that the vendor definitively lacks it.
[CP017, CP018, CP019, CP020, CP021, CP022]| Vendor | Public packaging signal | Public price signal | Unit / commitment | Included capability signal | Implication |
|---|---|---|---|---|---|
| Black Lake Intelligent Manufacturing | Annual-fee SaaS / subscription framing | Relative claim: ~1/10 of traditional MES cost | Per year; implementation in 6-12 weeks | 50+ apps, APIs, planning/production/warehouse/quality/equipment | Compelling value story, but weak public quote comparability |
| Black Lake Small Work Order | Subscription software | Qualitative low-cost claim only | Fastest 2-3 day go-live | Order-centric collaboration across sales, purchasing, production, inventory, suppliers | Designed to lower SME adoption friction without public list pricing |
| Tulip | Essentials / Professional / Enterprise / Regulated Industries | $100 or $250 per interface per month; higher tiers custom | 10 interface minimum; billed annually | Apps, analytics, connectors, API, compliance add-ons | Transparent for buyer benchmarking but less self-serve than per-user SMB tools |
| Odoo | One App Free / Standard / Custom | $0 one app; about $31.10 or $61.00 per user per month annually | Per user per month | All apps, hosting, support, API on Custom | Aggressive transparent price anchor for SMB and mid-market buyers |
| Katana | Free plus usage-based paid plans | Free plan; higher tiers usage-based with pricing page anchor | SKU/location capacity plus add-ons | Inventory, production, API, integrations, onboarding support | Pricing is public and onboarding is fast, but manufacturing depth is narrower than MES suites |
| MRPeasy | Starter / Professional / Enterprise / Unlimited | $49 / $69 / $99 / $149 per user per month | Per user per month; no module-based pricing | Planning, inventory, shop-floor interfaces, quality, integrations | Strong price transparency for small manufacturers |
| Plex | Private offer / custom contract | Custom pricing only | Quote-led enterprise contract | MES, QMS, monitoring, APM | Enterprise trust signal but no public budget anchor |
| SAP Digital Manufacturing | Product and features pages only | No public list price on reviewed pages | Quote-led enterprise motion | Cloud MOM/MES, analytics, workforce, orchestration | Likely bought inside broader SAP account strategy |
| Siemens Opcenter | Product overview only | No public list price on reviewed pages | Quote-led enterprise motion | MOM, digital twin, PLM-to-automation, quality | Heavyweight incumbent alternative rather than transparent SMB purchase |
Public price signals are list prices or qualitative claims only; they exclude services, implementation, hardware, and negotiated discounts, so realized total cost can differ materially from the public comparison.
[CP002, CP003, CP011, CP012, CP013, CP014]Capability and commercialization scorecard for the headline competitive set using Full / Partial / Unknown ratings from the reviewed public source set. This figure adds a go-to-market lens to the capability table by showing where public price transparency and China-local delivery sit alongside workflow breadth, making the competitive pressure on Black Lake's middle lane more visible.
Ratings reflect only what the reviewed source set explicitly documented. Full means the capability is prominent and repeated in the public materials; Partial means present but not central or not fully evidenced; Unknown means the reviewed pages did not provide enough proof to score with confidence.
[CP017, CP018, CP020, CP022, CP026, CP031]3.3 Moat durability, domestic pressure, and evidence that remains missing
The strongest public evidence for Black Lake's moat is still operational, not financial. Its product materials repeatedly emphasize fast deployment, lower up-front software cost, modular APIs, and a China-local factory workflow fit that spans both larger plants and smaller high-mix manufacturers. That is a real differentiator versus Siemens, SAP, and Plex, whose reviewed public pages read like enterprise control-tower suites. It is also why Black Lake can plausibly sit in a defendable middle lane between heavy global MOM software and generic SMB inventory tools. The problem is that middle lanes are only durable when buyers actually stay there. Public evidence suggests Black Lake faces two meaningful compression risks. First, Digiwin and Saiyi attack from inside China with broader local implementation histories, listed-company trust signals, and wide customer footprints. Second, Tulip, Odoo, Katana, and MRPeasy show buyers that modern manufacturing software can be purchased with much clearer public pricing and faster self-serve or guided onboarding. That means Black Lake's moat is likely stronger in workflows and localization than in public commercial transparency. The biggest evidence gap is neutral win-loss data. The chapter found many product and packaging signals, but almost no independent public proof showing Black Lake consistently beating or losing to Siemens, SAP, Tulip, Digiwin, Saiyi, or lighter MRP substitutes in named evaluations. As a result, the competitive verdict should stay disciplined: Black Lake has a credible and evidence-backed niche, but public sources do not yet prove that the niche is locked in through superior switching costs, renewal economics, or repeatable displacement of the best-funded alternatives.[CP025, CP026, CP027, CP028, CP031, CP032]
| Moat claim | Competing threat | Severity | Evidence-backed reason | Mitigation / diligence ask |
|---|---|---|---|---|
| Fast deployment and low-friction onboarding | Tulip, Odoo, Katana, and MRPeasy also market fast starts and lighter deployment | High | Multiple lightweight substitutes publish explicit quick-start packaging and pricing while Black Lake only discloses relative economics | Request recent bake-offs and actual time-to-value by segment |
| China-local factory workflow fit | Digiwin and Saiyi have longer local implementation histories and large customer footprints | High | Domestic suites pair broad manufacturing coverage with listed-company trust and named Chinese case libraries | Request vertical win-loss data in China by industry and factory size |
| Broader MES depth than generic SMB tools | Heavy incumbents retain stronger public compliance, workforce, and analytics detail | Medium | SAP, Siemens, and Plex disclose deeper enterprise-control and regulated-workflow language than Black Lake public pages do | Probe regulated deployments, validation artefacts, and quality/compliance references |
| AI-native positioning and modular apps | Tulip and Saiyi also frame AI/no-code/app-based operating models | Medium | Cloud-native configurability is no longer unique in public marketing across the competitor set | Request proof that AI modules improve conversion, renewal, or module expansion |
| Public commercial value story | Black Lake publishes less explicit list pricing than lighter substitutes | Medium | Tulip, Odoo, Katana, and MRPeasy provide stronger public budget anchors for procurement teams | Request anonymized quotes, services burden, and realized payback by customer cohort |
| Perceived execution credibility | No neutral public win-loss or churn dataset confirms Black Lake displacement versus named rivals | High | Public evidence proves overlap and niche fit, but not repeatable competitive win rates | Ask for top 20 recent evaluated deals, losses, renewal rates, and expansion cohorts |
Severity reflects analyst judgment from the public source set rather than disclosed pipeline-loss data; this table is designed to show where Black Lake's moat is evidenced, where it is only asserted, and what diligence item would close each gap.
[CP025, CP029, CP030, CP031, CP032, CP033]Compact public metrics that anchor competitive readiness and pricing pressure around Black Lake's niche. The pattern is mixed: Black Lake's deployment claims are strong, but transparent price anchors and disclosed installed-base metrics often sit with the alternatives rather than with Black Lake itself.
All KPI values are direct public claims from the reviewed pages and are not normalized for implementation services, hardware, negotiated discounts, or apples-to-apples user/factory counts. They are best read as proof of public market signaling rather than full TCO parity.
[CP002, CP011, CP012, CP013, CP025, CP030]3.4 Exhibits
04Financials
4.1 Revenue model and pricing architecture
Black Lake’s public revenue model is visible enough to prove real monetization, but not visible enough to model actual contract economics. Official product pages split the company into a heavier enterprise motion and a lighter SME motion: Black Lake Intelligent Manufacturing is framed for larger multi-plant and supply-chain-heavy factories, while Black Lake Small Work Order is designed for smaller, high-mix manufacturers that want faster deployment and lower upfront spend. That segment split matters financially because the public evidence points to meaningfully different delivery intensity and likely different average contract values across the two motions. For the SME layer, the company now gives unusually concrete list pricing. An official April 2026 pricing explainer says Small Work Order professional is priced at RMB10,800 per year with 50 included accounts and RMB140 per additional account per year, while the flagship package is priced at RMB18,800 per year and adds procurement, sales, quality, and PDA workflows. The same source also says the product is SaaS-only, charged annually, and not sold as a perpetual license. That is stronger evidence than a generic 'contact sales' page, but it is still list pricing rather than realized pricing. For the enterprise and AI layers, public visibility drops sharply. The official manufacturing page says Black Lake uses annual subscription pricing by user and module and positions first-year cost at roughly one-fifth of a traditional buyout system, but it does not publish enterprise rate cards. Jiemian adds an important monetization nuance: management says AI-agent fees are being priced against roughly one month of the relevant worker’s salary rather than against a simple seat count. That suggests Black Lake is trying to move from classic SaaS packaging toward a hybrid model of package fees, account expansion, module upsell, and labor-value-based AI pricing. What remains missing is the part investors actually need: realized contract value, discounting, attach rates, renewal terms, and software-versus-services mix.[CI001, CI002, CI003, CI004, CI005, CI006]
| stream | mechanism | unit | current value/status | quality | diligence ask |
|---|---|---|---|---|---|
| Black Lake Intelligent Manufacturing subscriptions | Annual enterprise SaaS subscription sold by user and module to larger factories and supply-chain-heavy groups | Contract year + user/module basis | Public model disclosed; enterprise list price undisclosed | Medium — official positioning is clear, realized enterprise ACV is not | Provide the last 12 months of enterprise bookings, average contract value, and renewal uplift by cohort. |
| Small Work Order professional package | Standardized SME SaaS package | RMB per year | RMB10,800 per year with 50 included accounts | High for list pricing; low for realized pricing | Disclose paid factory count, renewal rate, and discount frequency on the professional tier. |
| Small Work Order flagship package | Higher-feature SME package with procurement, sales, quality, and PDA workflows | RMB per year | RMB18,800 per year; included-account disclosure not clearly visible in fetched text | High for list pricing; medium for packaging detail | Disclose flagship attach rate, expansion path from professional, and gross margin by tier. |
| Account and module expansion | Additional users plus feature expansion beyond the base package | RMB per account per year and module upsell | RMB140 per extra account per year; module upsell is visible but enterprise catalog is not | Medium — direct list price exists for extra seats only | Provide actual ARPA uplift from added accounts, modules, and cross-sell motions. |
| AI agent monetization | Annual fee anchored to the monthly salary of the target role instead of only seat count | Agent / role / year | Pricing logic disclosed; no numeric public rate card | Medium — management commentary is specific, but commercial conversion is unquantified | Provide first 20 paid agent deployments, price realized, and pilot-to-paid conversion. |
| Implementation and ecosystem services | Onboarding, configuration, partner-led integration, and customer success labor around software rollout | Project / deployment effort | Publicly visible in deployment claims and ecosystem language; revenue contribution undisclosed | Low — visible as a delivery requirement, not as a disclosed revenue line | Break out services revenue, partner share, and contribution margin by product line. |
Revenue stream boundaries are evidence-backed, but only the SME package layer has public list pricing. Enterprise ACV, services mix, and AI-agent realized pricing remain undisclosed.
[CI001, CI003, CI005, CI006, CI007, CI009]| price / unit / contract | buyer | public evidence | list vs realized pricing | implication | source |
|---|---|---|---|---|---|
| Small Work Order professional — RMB10,800/year, 50 included accounts, RMB140 per extra account/year | SME factories | Official April 2026 pricing explainer | List pricing only | Provides a rare hard anchor for SME ACV but says nothing about discounting or renewal economics | Official pricing blog |
| Small Work Order flagship — RMB18,800/year | More process-complex SMEs | Official April 2026 pricing explainer | List pricing only | Shows clear upsell path from basic production control into broader operational workflows | Official pricing blog |
| Intelligent Manufacturing — annual subscription by user and module; first-year cost framed at ~1/5 of buyout software | Larger factories and groups | Official manufacturing page | Realized enterprise pricing undisclosed | Supports a recurring-software model but leaves enterprise ACV and gross margin unknown | Official manufacturing page |
| AI agents — annual fee tied to one month of the target role’s salary | Factories adopting quoting, split-order, scheduling, or quality agents | Founder / CEO interview with Jiemian | No public numerical catalog | Potentially expands value capture beyond classic seat pricing if conversion and retention are strong | Jiemian |
| Trial / demo terms — no online trial, free on-site demo in 35 cities | Primarily SME prospects | Official pricing explainer | Commercial access disclosed; self-serve pricing funnel absent | Implies a sales-assisted motion even for the lower-ticket product | Official pricing blog |
| Deployment architecture — SaaS only, no buyout / no local perpetual package for Small Work Order | SME buyers evaluating digitalization spend | Official pricing explainer and feature page | Commercial structure disclosed; hosting cost to vendor not disclosed | Reduces customer capex but may keep support and cloud-cost burden on Black Lake | Official pricing blog + feature page |
The public record reveals the list-price envelope and monetization logic, not realized contract terms. Enterprise discounting, multi-year commitments, and AI-agent renewal behavior remain unverified.
[CI002, CI005, CI006, CI007, CI008, CI009]Black Lake’s public monetization bridge runs from segment-specific product entry points into recurring subscription revenue, expansion levers, and an emerging AI-agent fee layer.
This figure maps the evidence-backed monetization logic, not actual revenue shares. Public sources disclose package pricing and pricing mechanics, but not realized mix or gross margin by node.
[CI001, CI005, CI006, CI007, CI009, CI024]4.2 Growth, profitability, and unit-economics proxies
The best-supported financial headline in the public record is that Black Lake says it has crossed an important commercialization threshold. Multiple April 2026 outlets repeat the same management line: revenue is growing more than 60% year over year, the company is fully profitable, and industrial AI is already scaling into real workflows such as quoting, split-ordering, scheduling, and quality. Repetition across Sina, CNFin/Xinhua, Tencent, Caixin, 36Kr, and other outlets makes the claim too widespread to ignore, but it is still a company-disclosed operating statement rather than an audited financial disclosure. No source in hand translates that profitability claim into operating margin, EBITDA, free cash flow, ARR, or revenue base size. That distinction is the central financial-quality issue. Public sources make it easy to believe Black Lake has customers and spendable pricing power, but they do not show whether profitability comes from mature software gross margins, unusually low sales and marketing spend, partner-assisted delivery, or simply a favorable mix of services and projects at a point in time. Even scale metrics drift by denominator: official and quasi-official surfaces cite roughly 30,000, 32,000, 34,000, or nearly 40,000 factories or manufacturing enterprises, and market-share references move between 42.7% and 52.7% depending on the year and category being quoted. The available unit-economics signals are therefore proxies rather than answers. The enterprise product’s four-to-six-week implementation language implies materially higher onboarding effort than the SME product’s two-to-five-day rollout. The recruiting page’s 500+ employee and 200+ technical-staff claim suggests a meaningful fixed-cost base, while Jiemian’s pricing-shift commentary implies Black Lake believes AI agents can capture value more directly than classic seat pricing. Those are credible directional signals, but they are not substitutes for gross margin, retention, CAC payback, or segment-level revenue mix.[CI011, CI018, CI019, CI020, CI021, CI022]
| metric | value / null | confidence | why it matters | diligence ask |
|---|---|---|---|---|
| Revenue growth | >60% YoY (company-disclosed) | Medium | Signals real commercial momentum, but the absolute revenue base is undisclosed so growth quality cannot be normalized | Provide monthly or quarterly revenue from 2024 through 2026 and identify recurring versus services mix. |
| Profitability status | Fully profitable (company-disclosed) | Medium | A critical quality marker, but without operating margin or cash-flow detail it does not prove durable software economics | Provide EBITDA, operating cash flow, and adjusted free cash flow for the last 12 months. |
| Gross margin % | Low | Core test of whether Black Lake behaves like a software platform or a labor-heavy implementation business | Provide consolidated gross margin and a split between software, services, partner-delivered work, and AI-agent usage. | |
| CAC payback months | Low | Needed to judge sales efficiency and how long new business takes to recover acquisition spend | Provide blended CAC, segment CAC, and payback by SME package, enterprise, and AI-agent upsell. | |
| NRR / churn | Low | Retention determines revenue quality far more than one-time fundraising headlines | Provide gross retention, net revenue retention, and logo churn for the last eight quarters. | |
| Deployment intensity proxy | 4–6 weeks enterprise vs 2–5 days SME | Medium | Implementation length is the best public proxy for support burden and likely services intensity by segment | Provide average implementation hours, partner utilization, and time-to-go-live by cohort. |
| Headcount proxy | 500+ employees, 200+ technical staff (recruiting-page claim) | Low | A rough indicator of cost base and R&D burden, but not a current audited headcount | Provide current FTE count, fully loaded payroll, and split across R&D, services, sales, and G&A. |
Most unit-economics fields remain null because Black Lake does not publicly disclose margin, retention, CAC, or cash-flow metrics. The non-null rows are company-claimed traction or operational proxies, not audited economics.
[CI018, CI019, CI025, CI030, CI032, CI039]Public evidence implies that value creation is real, but the conversion from growth and deployment into durable unit economics remains largely opaque.
Every step in the bridge is source-backed, but the economics on each link are not. The figure is qualitative because public sources stop before CAC, payback, or margin can be calculated.
[CI008, CI018, CI023, CI025, CI030, CI032]Only a few Black Lake financial parameters have source-backed numeric boundaries. Most operating metrics remain outside the public record.
This figure deliberately avoids invented revenue, burn, or runway estimates. It only visualizes numeric ranges that can be bounded directly from retained sources.
[CI006, CI007, CI011, CI012, CI039]4.3 Capital adequacy and financing dependency
Black Lake does not look capital-constrained in the narrow sense of market access. The April 2026 D round is heavily corroborated across independent outlets, and the reported post-money valuation above RMB7 billion signals that external capital still assigns strategic value to the company’s industrial-AI positioning. Sources are also consistent about the round’s intended use: accelerate AI deployment in real manufacturing workflows and fund global expansion. Those uses are logical for the business, but they also imply ongoing cash demands in R&D, implementation, partner enablement, and overseas commercial buildout. The harder question is whether the round makes Black Lake adequately capitalized, and public evidence cannot answer that. The company does not disclose cash on hand, monthly burn, runway, debt, leasing commitments, or covenant structure in any reviewed source. Even the lifetime capital ledger is messy: official and recruiting surfaces describe pre-D cumulative financing in different ways, while CB Insights still showed a much lower total-raised figure at fetch time. That may reflect stale databases, FX conversion, or partial round coverage, but the point for diligence is the same: the public capital stack cannot yet be plugged directly into dilution or runway modeling. There is also at least some adverse signal around contingent liabilities. Aiqicha surfaces one court notice, 15 hearing notices, and five litigation relationships, yet none of the reviewed sources quantify economic exposure, reserves, or insurance recovery. Combined with the absence of debt and cash disclosure, that means the D round proves financing access, not capital adequacy. Until management provides a current cash bridge and obligations schedule, Black Lake should be treated as financeable but still opaque on runway.[CI011, CI012, CI013, CI014, CI015, CI016]
| metric | public value / status | confidence | why it matters | diligence ask |
|---|---|---|---|---|
| Latest financing round | Near RMB1bn Series D in April 2026 | High | Confirms continued access to external capital and investor appetite for the industrial-AI thesis | Provide signed close memo, primary versus secondary split, and exact proceeds received by the company. |
| Latest valuation | >RMB7bn post-money / ~$1.3bn Crunchbase translation | Medium | Sets the dilution and valuation anchor for future rounds, but exact share count and FX basis are absent | Provide post-money share count, fully diluted capitalization, and valuation method used in investor materials. |
| Round chronology | Public sources say the D round was the sixth financing after angel, A, A+, B, and C | Medium | Supports the maturity of the financing history but not the exact cumulative cash-in number | Provide round-by-round cash raised, lead investor, security type, and ownership dilution. |
| Cumulative capital before D | Not reconciled: official / recruiting surfaces and database pages do not align cleanly | Low | A stale capital ledger distorts dilution, ownership, and runway modeling | Provide a reconciled lifetime capital table including FX basis and whether venture debt or other facilities are included. |
| Use of proceeds | Industrial AI rollout and global expansion | Medium | Useful because it points to likely future cash uses in R&D, deployment, and overseas GTM | Provide 24-month operating plan and budget split across R&D, commercial, services, and overseas expansion. |
| Cash on hand / monthly burn / runway | Low | This is the central capital-adequacy test and it is entirely absent from the public record | Provide month-end cash, net burn, gross burn, runway, and downside runway under slower growth. | |
| Debt / project-finance obligations / contingent liabilities | No debt schedule disclosed; Aiqicha surfaces litigation and hearing notices but not exposure values | Low | Hidden obligations can materially change effective runway and downside protection | Provide debt schedule, lease obligations, guarantees, litigation reserve, and insurance coverage. |
Public sources prove financing access and intended use of proceeds, but they do not prove runway. Cash, burn, debt, and contingent-liability disclosure are the critical missing pieces.
[CI011, CI012, CI013, CI014, CI015, CI016]| missing private metric | impact on underwriting | current public substitute | exact diligence path |
|---|---|---|---|
| Audited revenue, ARR, and bookings | Cannot test whether >60% growth is off a meaningful recurring base or a project-heavy base | Company-claimed growth and older recruiting-page milestones only | Request 24 months of monthly recurring revenue, services revenue, bookings, and audited annual statements. |
| Gross margin and services-delivery cost | Cannot judge scalability or whether profitability is software-like versus labor-assisted | Implementation-time proxies and SaaS positioning only | Request product-level and company-level gross margin with software/services/partner splits. |
| Cash on hand, burn, and runway | Cannot underwrite solvency, next-round timing, or downside buffer despite the D round | Funding round size and stated use of proceeds only | Request treasury report, monthly burn bridge, covenant summary, and downside runway cases. |
| Revenue mix by SME packages, enterprise subscriptions, services, and AI agents | Cannot see whether growth is driven by scalable recurring software or high-touch deployment work | Product segmentation and pricing logic only | Request segment P&L, ACV by segment, and attach rate of AI agents to legacy products. |
| Realized pricing, discounting, retention, and NRR | List pricing alone does not show revenue quality or expansion efficiency | Official list price for SME product and qualitative enterprise pricing model | Request top-50 contract extract with list price, net price, term, renewal status, and expansion history. |
| Customer concentration and receivables quality | A few large accounts or slow collections could materially change risk despite broad factory-count marketing | Named-case studies and broad factory counts only | Request top-20 customers by ARR, share of revenue, gross margin, renewal dates, and DSO by cohort. |
| Litigation economics and reserves | Potential legal cash leakage is unknowable even though registry pages show hearing notices and litigation relations | Aiqicha summary counts only | Request case list, claimed amounts, reserves, insurance, and management’s probability-weighted exposure view. |
This table intentionally emphasizes what public evidence does not disclose. The chapter’s core conclusion is that Black Lake has enough public traction to merit diligence, but not enough disclosure to complete financial underwriting.
[CI019, CI028, CI029, CI030, CI038, CI040]The public record points to where Black Lake is likely consuming capital, but visibility is strong only on funding access and weak on actual cash-flow burden.
Ratings are qualitative and evidence-backed. “Partial” means the cash-use bucket is named publicly without a budget, expense line, or runoff schedule.
[CI013, CI026, CI027, CI028, CI032]4.4 Financial verdict on revenue quality, margins, and blockers
Black Lake’s financial story is stronger than its formal disclosure standard. The public record proves that customers exist across both SME and larger-factory motions, that at least one product has explicit annual SaaS pricing, and that investors were still willing to fund the company at an above-RMB7 billion valuation in 2026. It also supports a credible thesis that AI agents could deepen monetization over time by tying price to customer labor savings instead of just seats and modules. Those are real positives for revenue quality. The problem is that nearly every underwriting question that sits beneath those positives remains unanswered in public. There is no audited topline, no ARR, no gross margin bridge, no churn or NRR, no CAC/payback, no segment mix between enterprise and SME, and no disclosed cash/burn/runway frame. The company’s profitability claim may be true, but public evidence does not yet show whether that profitability is durable, software-like, or dependent on implementation intensity that will rise again during global expansion and AI rollout. My financial conclusion is therefore cautious but not negative. Black Lake appears to have genuine commercial traction, concrete list pricing, and fundraising credibility. It does not yet have a public evidence set strong enough for clean underwriting on revenue quality, margin path, or capital sufficiency. The next diligence step should not be another narrative interview; it should be a data room pack with revenue by segment, gross margin by software versus services, cash runway, debt and contingent liabilities, and cohort retention by product line.[CI018, CI019, CI028, CI029, CI030, CI031]
4.5 Exhibits
05Product & Technology
5.1 Product surface in factory workflow terms
Black Lake's publicly visible product surface is built around two clearly differentiated operating systems for factories. Black Lake Intelligent Manufacturing targets larger organizations that need multi-role, multi-plant, and often supply-chain-connected execution, while Black Lake Small Work Order addresses smaller factories that need faster setup, lighter training, and order-driven execution. Across the two surfaces, the company consistently positions itself around planning, production management, warehousing, quality, equipment, and traceability instead of a narrow dashboard or analytics SKU. The product documentation and company profile repeatedly stress that the software is meant to turn live production data into workflow coordination, not just digitize paperwork. For large factories, the strongest public evidence is the Intelligent Manufacturing page and company deep dive: they describe more than 50 business apps, flexible module combination, and a browser-first SaaS surface with data reports, factory modeling, scheduling, and inventory management. For smaller factories, Small Work Order extends the workflow backward into quoting, order intake, procurement, and downstream fulfillment. It also keeps a visible upgrade path into the heavier Intelligent Manufacturing stack, which suggests product segmentation by organizational complexity rather than by a totally separate code base. The 2026 ranking-style white paper also introduces a third line, Black Lake Light Manufacturing, but that line is much less documented than the other two and remains a diligence item.[CE001, CE002, CE004, CE005, CE008, CE009]
| Module / product line | Primary user | Status / maturity | Differentiation | Diligence gap |
|---|---|---|---|---|
| Black Lake Intelligent Manufacturing | Large and upper-mid manufacturing plants; group operations | Commercially deployed; deepest public product surface | Cloud-native multi-role execution stack with multi-plant coordination and configurable modules | Public docs do not break out reference architecture by industry or deployment tier |
| Black Lake Small Work Order | SME factory owners, planners, workshop supervisors | Commercially deployed; fastest-start product | Order-fulfillment-centric workflow, low training burden, rapid go-live, mobile-first operations | Pricing model, support SLA, and data-migration tooling detail remain light |
| Black Lake Light Manufacturing | Likely mid-market / lighter-weight digitalization use cases | Mentioned in 2026 white paper only | Suggests a middle product tier between full MES and SME work-order tooling | Public feature-level documentation is sparse outside one ranking-style source |
| Data / analytics layer (reports + MI + big-data stack) | Plant managers, quality, operations analysts | Production use claimed in cases and product docs | Flink + StarRocks stack, second-level analytics, equipment and line alerts | No externally validated benchmark on throughput, latency, or ML governance |
| AI-agent suite | Planners, estimators, schedulers, QA leaders | Scaling; 2023 R&D start and 2026 commercialization push | Targets decision-heavy steps such as split order, quoting, scheduling, and quality | Independent audit of agent accuracy and exception handling is unavailable |
| Open platform / SDK surface | Customer IT, integrators, ecosystem partners | Public artifacts exist but full docs are gated | OpenAPI, Java SDK, and structured doc tree support systems integration | Anonymous inspection of the complete API catalog is not available |
Rows combine official product pages, public developer artifacts, and financing coverage; maturity labels distinguish clearly documented production surfaces from roadmap or partially documented assets.
[CE001, CE004, CE008, CE011, CE015, CE041]| User job | Current workflow / pain point | Black Lake solution | Measurable benefit | Limitation |
|---|---|---|---|---|
| Large-factory production planner | Multi-plant planning and live progress are fragmented across ERP, spreadsheets, chat, and manual reports | Intelligent Manufacturing links planning, production, warehouse, quality, and equipment data in one SaaS layer | Official materials claim multi-plant visibility, faster plan response, and real-time synchronization | No public benchmark decomposes planner productivity gains by module |
| SME owner or workshop lead | Orders, procurement, production, inventory, and finance are tracked separately and late | Small Work Order centers the workflow on order fulfillment and cross-department task visibility | Site examples claim much faster reporting and order-progress lookup | Public evidence is case-by-case and company-selected |
| Quality / traceability manager | Paper records and nonstandard forms make root-cause analysis slow | SOP-gated digital records and one-code traceability connect process, material, and finished goods data | Yada and other cases describe unified digital records and traceability improvements | Retention periods, audit logging, and regulated-record controls are not public |
| Operations leader at chain-owner or group manufacturer | Upstream suppliers and multiple plants must coordinate around fast-changing demand | Cloud-based collaboration extends from one factory into upstream and downstream partners | Nongfu and Liby case language points to faster response, fewer manual handoffs, and better resource use | Hard evidence on supplier onboarding time or partner churn is absent |
| Estimator / scheduler in AI-enabled factories | Experienced staff manually split orders, quote, and prioritize work | AI agents automate split order, quote generation, and scheduling decisions on top of the data platform | Third-party coverage reports minutes-level split-ordering and faster quotes with higher response rates | Independent verification of agent performance at fleet scale is not public |
Benefits are reported outcomes from public case studies and company-selected examples; they indicate directionality, not a controlled benchmark across the customer base.
[CE002, CE004, CE014, CE025, CE027, CE029]Publicly described operating flow from order or demand signal to execution, traceability, and multi-plant collaboration.
[CE002, CE004, CE025, CE027, CE030]5.2 Architecture, integration, and developer surface
The architecture signal is stronger than the average Chinese industrial-software homepage, though still not at the level of a fully open enterprise trust center. Black Lake repeatedly describes its platform as cloud-native, containerized, and built with Service Mesh, microservices, and low-code configuration. The Intelligent Manufacturing product brief adds a concrete data stack, naming Flink and StarRocks for large-scale storage and second-level analysis. Together, these sources support a view of Black Lake as a modern internet-style manufacturing stack rather than a traditional on-prem monolith. That matters because the company's differentiation thesis depends on fast implementation, modular rollout, and AI-native iteration speed. Integration is a material part of the product story. Black Lake's official pages mention standard openAPI interfaces, ERP/OA/data-capture connectivity, and one-stop sign-on. The developer evidence is imperfect but real: a public GitHub organization exists, the repository list was updated in 2026, the openapi-sdk README points to the Black Lake Open Platform, and the v3-ali-openapi landing page describes a structured documentation tree built from api-index.json plus per-interface Markdown pages. Directly fetched doc artifacts deepen that signal: the api-index.json catalog enumerates hundreds of endpoints, while standalone Markdown docs expose detailed quality-task and equipment-list interfaces rather than only a marketing splash page. At the same time, another fetched API route endpoint returned a login-required token error, so developers cannot fully inspect the API surface anonymously. That mix implies Black Lake has a meaningful integration layer and some external developer artifacts, but not the kind of open public API sandbox that would let a buyer independently evaluate integration breadth, auth model, or change-management discipline from the outside.[CE006, CE007, CE010, CE011, CE015, CE016]
| Layer / process | Role | Dependency | Risk |
|---|---|---|---|
| Cloud-native application layer | Runs production, planning, inventory, and workflow applications in SaaS form | Containerization, Service Mesh, microservices, mainstream cloud infrastructure | Public material does not detail region redundancy, uptime commitments, or tenant-isolation design |
| Configuration and low-code layer | Lets factories adapt forms, logic, permissions, and workflows without full custom code | Product configuration framework and customer implementation discipline | Highly flexible configuration can still create hidden complexity without strong governance |
| Data / analytics platform | Collects, stores, models, and analyzes high-volume production data | Flink, StarRocks, factory data collection, MI analytics layer | No independent scale, latency, or data-quality benchmark is public |
| Integration layer | Connects ERP, OA, logistics, sales, device data, and SSO surfaces | Standard openAPI, one-stop login, ecosystem partners, Java SDK | Full API breadth, auth model, and versioning policies are not anonymously inspectable |
| AI-agent layer | Automates split order, quoting, scheduling, and selected decision flows | Historical shopfloor data, domain rules, industrial AI agents | Accuracy, override logic, and hallucination/failure controls are still lightly documented publicly |
| Delivery / customer-success layer | Turns product modules into live multi-plant workflows on short timelines | Implementation experts, ecosystem partners, industry templates | Public evidence is strong on speed claims but light on renewal, support SLAs, or failed rollouts |
This table uses only publicly visible architecture references; where documentation is silent, risks are analyst interpretations rather than company admissions.
[CE006, CE007, CE009, CE010, CE017, CE018]Five-layer stack of Black Lake's manufacturing software, data, integration, and AI surfaces as described in public materials.
[CE006, CE007, CE010, CE011, CE019]Key technical and commercial dependencies needed for Black Lake to deliver AI-native manufacturing software at scale.
[CE007, CE018, CE019, CE025]5.3 Deployment maturity, customer proof, and roadmap direction
Black Lake has stronger public deployment proof than many industrial-AI startups because it can point to named factory rollouts instead of only AI demos. Official materials say Intelligent Manufacturing can go live in four to six weeks and that Small Work Order can be live in roughly two to five days, while cases such as Yada, Mengniu, Liby, and Nongfu Spring show the product touching planning, production, quality, equipment, and cross-factory coordination. The Yada case is especially useful for product diligence because it details SCADA and ERP integration, SOP-gated production steps, digital records, traceability, and device-quality analytics. Liby and Mengniu extend that proof into work-order-centric orchestration, packaging, warehousing, device connectivity, and quality-digitization narratives. Public outcome evidence is still mostly company-selected, but it is concrete enough to sketch maturity. Black Lake publishes workflow and outcome claims such as 7,000 man-hours saved, delivery-rate improvement from 50% to 90%, scrap below 1%, and large multi-factory efficiency gains at Nongfu Spring. Independent sources reinforce the sense that the company is no longer just a collaboration SaaS vendor: 2026 coverage centers on industrial AI agents, a near-RMB1 billion D round, profitability, and expansion into 12 countries. That indicates the roadmap is moving toward an AI-native manufacturing operating system layered on top of an already-deployed execution footprint. The main caution is that customer-count and market-share metrics drift across sources, so dated metric definitions still need direct diligence.[CE003, CE012, CE013, CE014, CE023, CE024]
| Date / stage | Feature / milestone | Status | Implication | Source |
|---|---|---|---|---|
| 2016-2021 | Cloud manufacturing-collaboration stack established and promoted through Digital China era messaging | Commercial foundation in place | Shows the company built the collaboration layer before the AI narrative accelerated | Baidu Baike; Digital China speech |
| 2023 onward | Industrial AI-agent R&D program starts | In active development and commercialization | Marks transition from data-recording software toward decision automation | NetEase; IT之家; Baidu Baike |
| 2024 | IDC-based 42.7% SaaS MES share appears in official and China Daily materials | Leadership claim established | Helps explain why Black Lake can test new features across a large installed base | Company deep dive; China Daily |
| 2025 | Independent media cite 52.7% cloud production-management share and WEF AI benchmark recognition | Leadership narrative strengthens | Suggests product maturity plus stronger external validation than a niche startup | IT之家 |
| 2026 | Near-RMB1 billion D round funds industrial AI rollout and global expansion | Active scaling stage | Capital is being aimed at AI-native operating-system ambitions rather than point-solution upkeep | Caixin; Tencent News; NetEase; Crunchbase |
| 2026 public developer signal | GitHub org updates AI-coder templates while openapi-sdk and open-platform docs remain visible | Live but partial external surface | Shows continuing ecosystem activity, though not yet a fully open developer platform | GitHub org repos; SDK README; Open Platform |
This roadmap blends public release evidence, funding milestones, and developer-surface activity to show product evolution; it is not a substitute for an internal release calendar.
[CE012, CE015, CE021, CE024, CE038, CE039]Relative maturity by product surface, based only on public documentation depth and proof of deployment.
[CE003, CE005, CE012, CE015, CE018, CE040]5.4 Trust, compliance, and technical diligence risks
Black Lake does show more trust surface than a pure marketing-only SaaS vendor. The Small Work Order site displays MLPS level 3, ISO27001, and national industrial-internet standard participation as public signals, while multiple product pages emphasize cloud security, disaster recovery, and standardized APIs. The company also appears to have accumulated a meaningful proprietary asset base through copyrights, trademarks, and an open-platform SDK presence. Those are constructive signs for an industrial buyer that wants a vendor with more than slideware. Still, the trust surface is materially thinner than the product ambition. Public pages do not expose an uptime SLA, a public status history, or a broad anonymous API explorer. AI-agent performance and ROI claims are still largely relayed through company-selected examples or financing coverage rather than independent audits. Even the product-matrix story is not fully settled: the heavily documented Intelligent Manufacturing and Small Work Order lines are clear, but the white-paper-only Light Manufacturing line lacks the same public operational detail. As a result, the product looks credible and commercially mature enough to warrant diligence, but technical underwriting should focus on integration depth, release/change governance, reliability history, and the reproducibility of AI-led workflow gains.[CE018, CE021, CE036, CE037, CE040, CE041]
| Control / signal | Status | Scope | Gap |
|---|---|---|---|
| MLPS level 3 | Displayed on Small Work Order public site | China network-security baseline signal for a manufacturing SaaS vendor | No certificate scope, validity date, or hosting-entity mapping is public on the fetched page |
| ISO27001 | Displayed on Small Work Order public site | Information-security management signal for customers evaluating governance maturity | Certificate number, audit scope, and recertification date are not visible in the fetched public surface |
| National industrial-internet standards participation | Displayed on Small Work Order public site | Signals policy alignment and product-standard engagement | Participation does not by itself prove runtime reliability or deep security controls |
| OpenAPI developer surface | Structured docs exist and a Java SDK is public | Supports partner and customer integration workflows | Anonymous access is gated; buyers still need hands-on sandbox diligence |
| IP / product asset accumulation | Baidu Baike reports 58 software copyrights and 109 trademarks | Suggests sustained productization beyond one-off projects | Public records do not reveal which assets matter most to current customers |
| Reliability / status transparency | No public uptime SLA or status page was found on fetched surfaces | Would matter for factories depending on live execution workflows | Needs direct diligence on incident history, disaster recovery, and change management |
Compliance rows reflect visible public signals only; absence of public detail is treated as a diligence gap rather than evidence that a control does not exist.
[CE018, CE036, CE037, CE040]5.5 Exhibits
06Customers
6.1 Segmentation and installed-base trajectory
Black Lake’s public customer story is really two businesses under one label. The heavier Smart Manufacturing product is aimed at multi-plant or otherwise operationally complex manufacturers that care about cross-site planning, traceability, quality, equipment, and supply-chain synchronization. The lighter Mini Worksheet motion is aimed at smaller factories that need fast deployment, work-order visibility, inventory discipline, and shop-floor reporting without a traditional MES project. That split matters because it implies different buyers, different sales motion, and likely very different ACV and retention behavior even if the company reports one aggregate customer total. Public scale metrics are directionally strong but analytically messy. Black Lake homepage copy still points to 4,000+ manufacturing enterprises, the longer company profile moves to 32,000+ enterprises and nearly 30,000 factories in China and Southeast Asia, the World Economic Forum profile says nearly 40,000 factories globally, and 2026 company-authored market pieces push the number to 40,000+ factories with 40% growth. Those figures are not useless; they do show that the company is far beyond a pilot-stage vendor. But they are not on one denominator, so the right underwriting move is to treat the trajectory as proof of breadth while explicitly refusing to treat any single public customer-count line as a clean KPI until management bridges enterprise, factory, site, and paying-customer definitions.[CU001, CU002, CU003, CU004, CU005, CU006]
| Segment | Buyer / sponsor | Primary users | Payer / budget owner | Use case | Evidence-backed note / gap |
|---|---|---|---|---|---|
| Large multi-plant FMCG / beverage groups | Group COO / CIO / supply-chain lead | Plant managers, planners, QA, warehouse leaders | HQ operations or digital-transformation budget | Cross-plant scheduling, traceability, inventory, quality, upstream coordination | Named proofs include Nongfu, Mengniu, Mixue, and Liby; ACV and renewal terms stay undisclosed |
| Large industrial / discrete manufacturers | Plant operations or group manufacturing leadership | Production, quality, equipment, engineering teams | Factory or group operations budget | SCADA / ERP-linked execution, traceability, group vertical management | Yada plus other case language shows workflow depth, but independent renewal proof is thin |
| SME discrete factories | Owner / general manager / workshop lead | Workshop supervisors, planners, frontline workers | Annual operating budget | Work orders, inventory, procurement, reporting, delivery control | Public proof is stronger on pricing and demo motion than on named SME logos |
| Chain-owner supply ecosystems | Supply-chain or manufacturing platform owner | Factory planners, upstream suppliers, warehouses, logistics teams | Anchor enterprise budget | Multi-factory collaboration across internal and external nodes | Mixue and Nongfu stories point here, but supplier-seat economics are not public |
Segments synthesize product positioning, named customer stories, and third-party company profiles; payer roles remain inferred because no contract disclosure is public.
[CU001, CU002, CU003, CU004, CU005, CU021]| Metric | Value | Date | Source | Confidence | Implication | Missing denominator |
|---|---|---|---|---|---|---|
| Homepage partner count | 4,000+ manufacturing enterprises | 2026 fetch | Black Lake homepage | Medium | Shows a clear minimum floor for public installed-base claims | Unclear whether enterprises are paying, active, or cumulative |
| Company-profile enterprise count | 32,000+ manufacturing enterprises and supply chains | 2026 fetch | Black Lake company profile | Medium | Signals a much broader footprint than the homepage floor | Enterprise count is not directly bridged to factory or site count |
| China / Southeast Asia factory count | Near 30,000 factories | 2026 fetch | Black Lake company profile | Medium | Shows region-specific site footprint rather than just enterprise logos | Geographic scope differs from global counts |
| Global factory count | Nearly 40,000 factories globally | 2026 fetch | World Economic Forum | High | Independent corroboration that Black Lake is operating at large regional scale | Still a factory count, not a paying-enterprise count |
| 2026 heat-article installed base | 40,000+ factories; +40% YoY | 2026 | Black Lake market-heat article | Medium | Suggests growth continued into 2026 | Self-authored claim and denominator is again factories |
| White-paper phrasing drift | Near 40,000 service customers and 35,000-customer heuristic | 2026 | Black Lake white paper | Medium | Shows breadth but also sloppy public KPI wording | Customer versus factory versus paying-customer labels are not reconciled |
This table preserves public count drift rather than forcing one canonical installed-base number; different rows refer to different denominators and scopes.
[CU006, CU007, CU008, CU009, CU010, CU011]6.2 Named customer proof and deployment depth
The strongest public evidence is not the logo wall but the handful of case narratives that show workflow depth. Mengniu is framed as a digital-factory program tied to device and system interconnection, process transparency, digital quality control, finer cost control, and faster product-development cycles. Yada is the best industrial-manufacturing proof because the case describes a live operating environment with six production bases, nearly forty lines, existing SCADA and ERP infrastructure, and Black Lake being used to connect production, quality, materials, and equipment into traceable, group-manageable workflows. Liby adds a different shape of proof: a FMCG smart-factory program centered on work orders, packaging, warehousing, and distribution, with explicit pilot-to-all-factory rollout language. Mixue and Nongfu are especially important because they show Black Lake attached to chain-owner supply systems rather than only to isolated factories. Black Lake’s own materials position Mixue as a beverage-supply-chain operator serving a huge franchise network, while Nongfu is described as a multi-water-source, multi-plant beverage operator where coordination, plan response, and traceability matter as much as raw throughput. The limitation is just as important as the proof: almost all of this evidence is company-selected. Public named deployments clearly exist, but outside the company’s own customer storytelling there is still very little independent detail on contract size, renewal timing, or module-by-module expansion.[CU013, CU014, CU015, CU016, CU017, CU018]
| Customer | Segment | Deployment / use case | Production vs pilot | Outcome | Limitation |
|---|---|---|---|---|---|
| Mengniu | Dairy / FMCG group | Digital factory and cloud-collaborative manufacturing tied to supply-chain online strategy | Production program rather than simple logo mention | Device and system interconnection, process transparency, digital quality control, cost-control and R&D-cycle claims | No public contract value, user count, or renewal timing |
| Yada Group | Industrial pipe manufacturing | SCADA + ERP + MES-linked execution, quality, equipment, and traceability across multi-base production | Production deployment with group-management depth | One-code traceability, data aggregation, vertical management, and resource-allocation visibility | No public commercial terms or post-rollout ROI series |
| Liby Group | Household FMCG | Integrated smart factory centered on work orders, supply, packaging, warehousing, and distribution | Pilot validated with stated path to all-factory rollout | Cross-system interconnection and flexible delivery narrative | Later rollout completion is not independently verified |
| Mixue Group | Beverage supply-chain / franchise platform | Manufacturing and supply-chain coordination for a large franchise network | Named usage with outcome claims but little module detail | Company-selected case claims +30% efficiency, +50% inventory turns, -15% production cost, +80% communication efficiency | Evidence is mostly company-authored rather than customer-hosted |
| Nongfu Spring | Bottled beverage group | Multi-plant planning, quality, equipment, and process coordination across water-source regions | Named multi-plant production-style deployment | 106 steps removed, 358 labor hours/day saved, and +50% plan response claimed | No public contract size, site list, or independent renewal proof |
Rows are limited to deployments where public material describes workflow, scope, or outcome rather than only showing a logo.
[CU013, CU014, CU015, CU016, CU017, CU018]| Motion stage | Enterprise path | SME path | Evidence | Diligence gap |
|---|---|---|---|---|
| Problem discovery | Cross-plant coordination, traceability, and supply-chain speed pain surfaces at group level | Order delay, inventory, cost visibility, and reporting pain at workshop level | Official cases plus Mini Worksheet positioning | Need win-rate data by use case |
| Proof stage | Named pilot or first factory is used to validate workflow fit | On-site demo and same-industry references replace generic online trial | Liby pilot language; 35-city demo coverage | Need demo-to-pilot conversion rate |
| Implementation | 4-6 week enterprise implementation claims with multi-system integration | 1-3 day / short-cycle deployment claims for Mini Worksheet | Homepage, marketplace, and 2026 articles | Need actual median time to value |
| Expansion | Customer stories emphasize more factories, more plants, or broader supply-chain nodes | Potential expansion is implied by more modules or more sites, but named proof is limited | Liby, Nongfu, Mixue, Yada narratives | Need attach-rate and expansion-ARR data |
| Renewal / reference loop | Public proof relies on case stories rather than disclosed renewals | Public proof relies on testimonials and reference visits | No public NRR or GRR; company-selected references dominate | Need renewal, referral, and referenceability metrics |
The motion is reconstructed from public cases and product-positioning materials rather than from a disclosed sales-ops deck.
[CU019, CU029, CU030, CU031, CU032, CU041]Compares public proof quality by customer, showing that deployment maturity is clearer than retention visibility.
Freshness and maturity are judged from public evidence recency and workflow specificity, not from private operational data.
[CU017, CU019, CU020, CU023, CU028, CU033]6.3 Expansion, retention visibility, and procurement motion
What public materials do show is expansion logic, not retention math. Liby’s pilot-to-all-factory language, Nongfu’s multi-plant coordination, Yada’s group-level management story, and Mixue’s one-factory to multi-factory to upstream-and-downstream collaboration narrative all point to a land-and-expand motion where Black Lake tries to become operational middleware across plants and supply nodes. Alibaba Marketplace testimonials also give a glimpse of a mid-market and SME motion: replace a rigid legacy MES or spreadsheets, get quick visibility wins, then expand usage after shorter proof periods. This is qualitatively helpful because it suggests that expansion, if it happens, is likely site-based and workflow-based rather than seat-based alone. The weak point is durability evidence. There is no public NRR, GRR, logo churn, average contract length, renewal rate, or customer-satisfaction series that would let an investor separate one-time lighthouse wins from a compounding base. The SME motion is also not self-serve in the software sense; Black Lake’s own 2026 materials say Mini Worksheet does not offer a generic online trial and instead relies on on-site demos, live-factory references, and same-industry case validation. That may fit manufacturing buying behavior, but it also implies a heavier field-sales and solutioning motion than the headline SaaS label might suggest.[CU026, CU027, CU028, CU029, CU030, CU031]
| Signal | Value / null | Segment | Confidence | Diligence ask |
|---|---|---|---|---|
| Net revenue retention | All segments | Low | Request NRR by enterprise versus Mini Worksheet cohorts for the last eight quarters | |
| Gross revenue retention / logo churn | All segments | Low | Request GRR, logo churn, and expansion contribution by product line | |
| Contract length / renewal cadence | Enterprise | Low | Request average initial term, renewal cycle, and % of ARR on annual versus multi-year contracts | |
| Public expansion proof | Pilot-to-all-factory at Liby; multi-plant coordination at Nongfu; group-scale Yada and Mixue narratives | Enterprise | Medium | Verify site-by-site rollout timelines and module attach rates |
| SME procurement motion | On-site demos, same-industry references, and live-factory visits instead of online trial | SME | Medium | Request demo-to-close conversion, CAC payback, and churn by first-year cohort |
| Independent satisfaction corpus | All segments | Low | Provide customer-hosted cases, referenceability rates, and CSAT / NPS by cohort |
Null means the metric was not found in reviewed public customer materials, not that the metric is zero or irrelevant.
[CU019, CU029, CU030, CU031, CU032, CU033]Maps how Black Lake appears to sell and expand across large-enterprise and SME manufacturing segments.
The map synthesizes repeated patterns from public product and case materials; it is not a disclosed internal sales funnel.
[CU003, CU019, CU029, CU030, CU032, CU041]Shows the public path from buyer pain to rollout and expansion for Black Lake customer programs.
[CU019, CU029, CU030, CU031, CU041]6.4 Concentration and diligence risks
The biggest customer risk is not that Black Lake lacks named proof; it is that the proof is unusually concentrated in the kinds of customers a fundraising narrative would naturally emphasize. Public references over-index to food, beverage, household FMCG, and other supply-chain-intensive operators where planning speed, traceability, and multi-plant coordination are visible and easy to market. That does not mean the business is actually concentrated there, but it does mean the public evidence set can overstate traction in adjacent verticals if investors do not ask for revenue by industry, product, and customer size. The same skew appears in customer size: the company can describe a very large installed base, but the named proof still comes mostly from lighthouse enterprises plus a thin layer of generic SME testimonials. There is also a procurement diligence angle. Public legal-surface records such as Aiqicha hearing notices do not prove customer harm or failed deployments, but they are the sort of thing an enterprise procurement team, especially at a regulated or listed customer, may still ask management to explain. Combined with the lack of public renewal metrics and the count-definition drift, that means customer quality cannot be underwritten from logos alone. The diligence path is straightforward: ask for a reconciled customer KPI bridge, top-customer concentration, cohort retention, and a reference pack split by enterprise and SME rather than accepting one aggregate customer count as proof of durable demand.[CU035, CU036, CU037, CU038, CU042]
| Risk / expansion driver | Evidence | Impact | Diligence path |
|---|---|---|---|
| Food and beverage / FMCG proof concentration | Mixue, Nongfu, Mengniu, and Liby dominate the most specific named public stories | Public proof may overstate traction in other verticals if revenue is concentrated in consumer supply chains | Request ARR and customer counts by vertical and top-10 logos |
| Lighthouse-account skew versus SME long tail | Public named proofs are mostly large enterprises while SME proof is mainly pricing plus generic testimonials | Aggregate customer-count claims may hide much weaker retention or lower ACV in the long tail | Request cohort analysis by ACV band, factory size, and product |
| Count-definition drift | 4,000+ enterprises, 32,000+ enterprises, near-30,000 regional factories, near-40,000 global factories, and 40,000+ factories all appear publicly | Weakens confidence in customer KPIs used for valuation or market-share claims | Request a dated bridge across enterprise, site, paying, and active definitions |
| Consultative SME sales motion | No online trial; field demos and case-based validation substitute for self-serve proof | Could lengthen CAC payback or make the SMB engine less software-like than headline SaaS framing suggests | Request funnel metrics from demo to paid account and first-year retention |
| Procurement diligence friction | Aiqicha hearing notices plus missing renewal metrics create extra diligence questions for enterprise buyers | Could slow procurement or security / vendor reviews even if no customer failure is proven publicly | Request litigation summary, closed-case status, and customer-procurement objection log |
This table focuses on revenue-quality and proof-quality risk rather than on general legal or product risk handled elsewhere in the report.
[CU012, CU033, CU034, CU035, CU036, CU037]6.5 Exhibits
07Risks
7.1 Regulatory, legal, and disclosure risks
Black Lake's most defensible public risk stack starts with what the company and third-party legal sources say in plain text. The Small Work Order privacy statement, user agreement, and legal declaration create a wide data-governance perimeter: personal and business data can be collected, OPENAPI-ingested business data can be used for model training and optimization, cross-border transfers are contemplated, and public materials disclaim timeliness and completeness while limiting liability. On top of that, Aiqicha shows live litigation and hearing-notice signals but not enough detail to judge severity from the outside. For an investor, the underwriting issue is less ‘is the company breaking rules today?’ than ‘how much compliance, liability, and disclosure uncertainty is being carried by a private company that is now marketing AI-native and overseas-expansion ambitions.’ The risk is amplified because the most bullish growth, profitability, valuation, and customer-count metrics in this run still come from media or company-linked disclosures rather than from filing-audited financials.[CR001, CR002, CR004, CR005, CR006, CR007]
| Risk / case | Jurisdiction / rule | Current public status | Likelihood | Severity | Mitigation maturity | Residual exposure | Diligence path |
|---|---|---|---|---|---|---|---|
| Open-court notices and litigation relationships | PRC company-level legal risk | Aiqicha shows 1 court announcement, 15 hearing notices, and 5 litigation relationships, but public summaries do not disclose merits or outcomes | Medium | High | Low | High | Obtain docket list, claim amounts, counterparties, and outcome history from counsel |
| Private-company disclosure gap | Company-level governance / financing | Growth, profitability, valuation, and customer-count claims are media-reported rather than filing-audited in this run | High | High | Low | High | Request audited financials, board KPIs, renewal data, and customer concentration |
| Customer-data and AI-training rights | PRC privacy / contract / product terms | Public terms allow business-data use for AI training and optimization under customer authorization and legal compliance language | Medium | High | Medium | Medium | Review opt-in flows, anonymization controls, and enterprise contract carve-outs |
| Cross-border data transfer and overseas deployment | PRC PIPL / CAC standard-contract regime plus destination-country rules | Public materials contemplate overseas rollout and cross-border compliance but do not show country-by-country transfer architecture | Medium | High | Low | High | Request transfer impact assessments, standard contracts, and local hosting maps by country |
| Generative-AI compliance and model reliability | PRC generative-AI regulation | Current rules require lawful data, transparency, user-input protection, accuracy, and reliability for public AI services | Medium | Medium | Medium | Medium | Confirm whether any public-facing agent flows trigger filing, safety assessment, or labeling obligations |
Rows are severity-ranked from a public-evidence investor lens; public legal and regulatory evidence is partial because Black Lake is private and detailed case files or transfer assessments are not publicly available.
[CR001, CR002, CR006, CR008, CR009, CR010]Public evidence places disclosure opacity, legal/proceeding visibility, AI governance, and SME demand cyclicality in the highest residual-risk quadrant.
Likelihood, impact, and mitigation maturity are analytical ratings derived from public evidence; they are not management-provided scores.
[CR001, CR006, CR009, CR023, CR025, CR031]7.2 Implementation, security, and AI-decision risks
Operationally, Black Lake is not a lightweight plugin; its value proposition depends on real factory-system connectivity, rollout discipline, and credible decision quality once AI agents move from assisting to deciding. Official materials show meaningful integration intent through openAPI documentation, SDK assets, cloud-native deployment claims, and case language around ERP or workflow connectivity. That is constructive, but it also means customer outcomes can fail at the seams: incomplete API visibility, weak versioning discipline, poor master data, brittle device connectivity, or rollout mistakes can all degrade the customer experience before a classic software outage becomes visible. The public security surface is also thinner than the product ambition. Black Lake highlights certifications and protections, yet public materials do not provide a public incident ledger, uptime history, or independent security assurance report. The AI layer adds another step-up in risk because public accuracy claims for split-ordering and quoting are impressive but still appear in financing or founder-story coverage, not in an independently validated operating benchmark.[CR014, CR015, CR016, CR017, CR018, CR019]
| Failure mode | Evidence | Likelihood | Severity | Mitigation maturity | Residual exposure | Unresolved gap |
|---|---|---|---|---|---|---|
| Integration failure across ERP / device / API layers | Official materials stress broad connectivity and external docs, so deployment success depends on data quality and interface stability | Medium | High | Medium | High | Need sandbox, versioning policy, and change-log discipline |
| AI-agent decision error or poor exception handling | Public metrics are strong, but they come from financing or founder-story coverage rather than independent audits | Medium | High | Low | High | Need override rates, rollback logic, and customer incident logs |
| Security incident without strong public transparency surface | Public trust signals exist, but no public incident history or external assurance report is visible in this run | Medium | High | Medium | Medium | Need pen-test, uptime, and incident-postmortem evidence |
| Service interruption during migration, expansion, or network instability | User agreement explicitly lists data-center changes and network issues as service-interruption risks | Medium | Medium | Medium | Medium | Need SLA terms, RTO/RPO, and status history |
| Implementation speed over-promised relative to factory complexity | Rapid-go-live claims are attractive, but cross-system and cross-country deployments can still become expert-heavy projects | Medium | Medium | Medium | Medium | Need cohort data on delayed or failed rollouts |
Residual ratings combine company disclosures with investor interpretation; the key uncertainty is not whether the product has real capabilities, but whether public evidence is enough to underwrite repeatable enterprise-quality execution.
[CR014, CR015, CR017, CR018, CR019, CR020]The main downside chain runs from soft factory demand or AI/integration failure into delayed rollout, weaker expansion, lower trust, and financing sensitivity.
Transmission links summarize the most plausible public-evidence paths rather than a quantified probabilistic model.
[CR023, CR024, CR031, CR040, CR042, CR044]7.3 Demand cyclicality, partner dependence, and macro transmission
The public macro evidence makes cyclical demand a real risk rather than a generic caution. Black Lake's fastest-growth public surface is the SME-focused Small Work Order product, while official May 2026 PMI data shows medium and small manufacturers below the expansion threshold and Reuters reports weak domestic demand plus rising cost pressure. That does not prove immediate churn, but it does create a credible path to slower logo adds, softer seat expansion, lower willingness to pay for AI upgrades, and delayed implementation projects among the exact cohort that values low-friction rollout. The dependency story is similarly structural. Black Lake relies on mainstream clouds, integration layers, external documentation gateways, and factory ecosystem connectivity across supply chain, logistics, planning, and production. Once the company follows customers overseas, those dependencies broaden further into local data-transfer mechanisms, legal advisers, visa logistics, and local operating partners. None of these are fatal on their own; together they create a multi-node failure chain that deserves explicit monitoring.[CR017, CR020, CR022, CR023, CR024, CR032]
| Dependency | Counterparty / surface | Role | Concentration signal | Failure scenario | Severity | Mitigation | Residual exposure |
|---|---|---|---|---|---|---|---|
| Mainstream cloud infrastructure | Cloud providers / hosting stack | Runs application, security, disaster recovery, and elasticity layers | Official materials say deployment is on mainstream cloud platforms | Cloud incident, price shock, or regional hosting issue slows customer operations | High | Multi-cloud or region design, contractual safeguards, DR planning | Medium |
| OpenAPI and systems integration | ERP, OA, device data, logistics, supply-chain systems | Makes the SaaS valuable inside customer workflows | Integration is core to product positioning and external SDK/docs exist | Broken integration reduces customer outcomes even when core app stays online | High | Implementation runbooks, versioning, sandbox access, SI governance | High |
| SME demand base | Growth-oriented small and mid-sized factories | Feeds logo growth for Small Work Order and entry-level expansion | 30,000+ customer claim plus sub-50 SME PMI show cohort sensitivity | Weak demand delays new logos, seat expansion, and paid AI upsell | High | Enterprise mix-upmarket strategy, ROI messaging, flexible pricing | High |
| Overseas enablement partners | Local legal, accounting, visa, export, and plant-mapping support | Helps replicate deployments abroad | Sina profile shows expansion depended on external support mechanisms | Cross-border rollout stalls or becomes costly in new jurisdictions | Medium | Repeatable country playbooks, local counsel roster, hosting templates | Medium |
| Founder-led ecosystem and selling motion | Zhou Yuxiang plus headquarters ecosystem in Shanghai/Yangtze Delta | Connects product, customers, and policy relationships | Public narrative is heavily founder-centered | Relationship or hiring disruption weakens enterprise selling and roadmap credibility | High | Broaden executive bench, local GM model, documented playbooks | High |
This register treats customers, clouds, integrators, and expansion enablers as dependencies because each can transmit failure into churn, delayed revenue, or costly remediation.
[CR020, CR022, CR023, CR024, CR034, CR035]Black Lake depends on cloud, integration layers, founder-led ecosystem trust, and cross-border enablers at the same time.
Dependencies are simplified to the nodes most likely to matter in diligence rather than every vendor or partner named publicly.
[CR017, CR020, CR036, CR041, CR042, CR043]7.4 People risk, expansion execution, and kill criteria
Founder and people risk matter here because Black Lake's public strategy, regulatory voice, and market narrative all route through Zhou Yuxiang while the product itself is moving into decision-heavy industrial AI. Aiqicha shows concentrated formal authority, China Daily shows Zhou as the visible policy-facing executive, and Jiemian positions the company's industrial-AI thesis largely through his interpretation of market structure and product evolution. At the same time, the underlying customer problem is partly a scarcity problem: experienced factory experts and middle-layer coordinators are hard to replace, which is exactly why Black Lake's agents are attractive and exactly why implementation mistakes could be expensive. The right underwriting response is therefore not a binary go/no-go on any single public signal. It is a monitored set of kill criteria around new legal proceedings, data-governance lapses, independent evidence of AI error, material slowdown in SME demand, and any sign that overseas rollouts require bespoke heroics rather than repeatable process. Until management proves repeatability, people risk and execution risk remain linked.[CR003, CR026, CR027, CR028, CR041]
| Role / function | Dependency or gap | Likelihood | Severity | Mitigation | Diligence path |
|---|---|---|---|---|---|
| Founder / CEO | Public strategy, financing narrative, and policy visibility concentrate around Zhou Yuxiang | Medium | High | Broaden external-facing leadership and product decision rights | Ask for succession coverage and second-line executive ownership |
| Industrial AI product team | Decision quality depends on scarce manufacturing know-how plus AI capability | Medium | High | Retain domain experts and formalize eval/rollback workflows | Request org chart, attrition, and model-governance process |
| Implementation / customer-success bench | Fast rollout claims can hide dependency on a small set of expert implementation leads | Medium | Medium | Codify deployment templates and partner certification | Request implementation cohort data and escalation model |
| Factory-domain experts / “masters” | Customer workflows often rely on aging experts that agents aim to replace or augment | High | Medium | Keep human override in loop and document exception handling | Request customer references on override design and training burden |
People risk matters because Black Lake sells into mission-critical workflows where product, rollout, and domain expertise are tightly coupled.
[CR003, CR026, CR027, CR028, CR029, CR041]| Risk | Monitorable trigger | Threshold / event | Action implication |
|---|---|---|---|
| Legal / regulatory overhang | New disclosed proceedings or regulator inquiry | Any material claim, injunction, or data-governance inquiry affecting production or cross-border processing | Pause underwriting until counsel quantifies liability and remediation |
| Private-company disclosure risk | Data room cannot reconcile revenue, profitability, customer counts, and retention with public narrative | If audited or board-level KPIs materially diverge from the media story | Move to research-more or re-cut price/risk terms |
| AI-agent accuracy risk | Evidence of frequent human overrides, customer complaints, or costly decision errors | Override rates or error losses materially above management narrative | Treat agent moat claims as unproven and haircut adoption assumptions |
| SME cyclical demand risk | PMI or customer data show sustained weakness in SMB manufacturing demand | Two or more quarters of worsening SMB conversion, churn, or seat compression | Reset base-case growth and payback expectations |
| Overseas expansion risk | Each new country requires bespoke legal or data-transfer work rather than repeatable process | Country launches repeatedly depend on emergency visas, custom hosting, or ad hoc legal fixes | Constrain expansion premium and require stronger local control framework |
| Implementation / integration risk | Delayed go-lives or failed integrations cluster in major customer rollouts | Repeat escalation on ERP/device/API integration in reference checks or deployment cohorts | Treat services capacity and partner governance as gating diligence items |
Kill criteria are designed for IC use: each trigger is something management should be able to measure or document during diligence rather than a vague sentiment test.
[CR001, CR009, CR023, CR031, CR040, CR041]7.5 Exhibits
08Valuation
8.1 Recommendation and price discipline
Black Lake looks investable as a business narrative but not yet as a price-cleared underwriting decision. The April 2026 round is real, the new-money amount is broadly corroborated, and the post-money mark above RMB7 billion is consistent with unicorn framing in both Tencent and Crunchbase coverage. The same cluster of sources also says the company is already profitable and growing revenue more than 60% year over year. Those are exactly the ingredients that can justify a premium private mark in industrial software. The problem is that the open-web record stops at the headline. Public sources do not disclose the current revenue base, gross margin, net retention, or cap-table terms that would let an investor translate the RMB7 billion price into an actual risk-adjusted return case. That gap is too large to wave away because public software multiples in June 2026 are not generous. The disciplined call is therefore research-more: Black Lake may deserve a strong valuation, but the current mark cannot be called attractive on evidence now in hand.[CV001, CV002, CV004, CV005, CV006, CV031]
| Dimension | Assessment | Rationale |
|---|---|---|
| Recommendation | Research-more | The company may be strong enough to deserve the price, but public evidence does not yet disclose the denominator behind the valuation. |
| Confidence | Medium | Funding, profitability, customer-scale, and niche-share anchors are real, but financial-quality evidence is still incomplete. |
| Risk rating | High | The main risk is paying a premium private price without revenue, retention, gross-margin, or preference-stack visibility. |
| Valuation stance | Stretched | Absent verified current revenue and margin disclosure, the >RMB7 billion mark leans expensive relative to June 2026 public comp bands. |
| Decision implication | Advance only after a KPI pack | Underwrite only if management discloses current revenue or ARR, gross margin, retention, AI monetization, and cap-table terms. |
This table is intentionally price-sensitive: it distinguishes company quality from willingness to pay the current private mark.
[CV001, CV002, CV006, CV032, CV036, CV042]The recommendation is blocked by valuation-opacity risk, not by a lack of evidence that Black Lake has built a real business.
Decision nodes summarize qualitative underwriting logic rather than numeric model outputs.
[CV002, CV006, CV031, CV032, CV036]8.2 Market proof and comparable context
Black Lake does have real operating proof behind the valuation story. Multiple April-to-June 2026 articles repeat the near-40,000-factory footprint, the 52.7% share claim in China's cloud production-management niche, and the pivot from cloud MES into industrial AI agents. Official product pages support the idea that the company has a multi-product stack rather than a single lightweight tool, and the AI narrative appears tied to live workflows such as quoting, scheduling, production, and quality rather than to a generic copiloting layer. Even so, the competitive context is mixed rather than one-sided. The strongest external comparison piece still ranks Black Lake behind Dingjie and Siemens overall, and specifically warns that Black Lake is strongest in faster SMB cloud deployments rather than the most complex large-factory environments. That matters for valuation because it may limit average contract value expansion unless management can show that AI and enterprise editions are pulling the company upmarket faster than the public comparison pieces suggest.[CV007, CV008, CV009, CV010, CV011, CV012]
| Argument | Evidence base | What would change the view |
|---|---|---|
| THESIS: Black Lake appears to lead a real cloud-MES niche | Near-40,000 factory scale, 52.7% niche-share claims, and multi-product manufacturing workflow coverage create genuine platform value. | Confidence rises if management reconciles customer-count definitions and shares independent IDC methodology plus audited financial detail. |
| THESIS: Industrial AI can expand value above the base MES story | Coverage on AI agents, global expansion, and workflow automation suggests the company is trying to monetize decision support, not just digitize records. | View strengthens if AI attach rate, pricing, and ROI are disclosed by cohort or customer segment. |
| ANTI-THESIS: Public proof is still weaker than the valuation headline | The open-web record repeats profitability and share claims but omits the current revenue base, margins, and retention needed to defend the mark. | View improves only when current ARR or revenue and gross-margin quality are disclosed. |
| ANTI-THESIS: Black Lake may still skew toward lighter deployments than premium enterprise software | External comparison coverage says the product is strongest in quicker SMB cloud deployments and weaker in highly complex large-factory contexts. | View improves if large-enterprise ACV, deployment depth, and expansion evidence contradict the lightweight-deployment framing. |
Arguments are framed around what would move the underwriting call, not around static company-quality slogans.
[CV008, CV009, CV011, CV012, CV013, CV037]| Comparable | Metric | Multiple / valuation / status | Relevance | Limitation |
|---|---|---|---|---|
| PTC | Q2'26 ARR $2.36bn; market cap $13.26bn | ~5.6x ARR | Mature industrial software benchmark with meaningful recurring revenue and profitability. | Broader product set and more mature installed base than Black Lake. |
| Autodesk | Apr-2026 revenue $1.93bn; market cap $41.93bn | ~5.4x annualized quarterly revenue | Large design-software anchor for software scarcity and recurring revenue quality. | Far larger and more global than Black Lake; not a factory-ops pure play. |
| Procore | Q1-2026 revenue $359m; market cap $6.39bn | ~4.4x annualized quarterly revenue | Useful vertical-workflow SaaS benchmark with strong RPO disclosure. | Construction workflow is adjacent, not direct manufacturing execution. |
| Plex / Rockwell transaction | Strategic sale to Rockwell | Acquired for $2.22bn cash | Direct manufacturing-software M&A precedent showing strategic value for cloud-native factory platforms. | Revenue base and transaction multiple were not fully disclosed. |
| Tulip | Series D private round; 1,000+ sites in 45 countries | $1.3bn valuation | AI-native manufacturing workflow private comp with clearer global scale disclosure. | Private round, not a public-clearing valuation; financial detail still limited. |
| Augury | Series E private round | >$1bn valuation on $180m raise | Adjacent industrial-AI comp proving investor appetite for industrial intelligence assets. | Machine-health category is adjacent rather than directly cloud-MES. |
Coverage is partial: the table mixes public, private, and strategic references because no single comp set cleanly matches Black Lake's stage, geography, and product scope.
[CV020, CV023, CV026, CV028, CV029, CV030]Black Lake scores well on category momentum and proof of activity, but much worse on valuation clarity and evidence completeness.
Scores are IC-style qualitative ratings on a 10-point scale derived from the evidence set rather than management-provided KPIs.
[CV006, CV008, CV015, CV027, CV040, CV042]8.3 Scenario range and multiple sensitivity
The comparable set argues for caution on entry price rather than skepticism on the category. PTC, Autodesk, and Procore all trade in roughly mid-single-digit revenue-equivalent bands in June 2026, and all three show meaningful market-cap compression versus 2025. Strategic and private references are richer than that—Rockwell paid $2.22 billion for Plex, while Tulip and Augury both sustained unicorn valuations in adjacent manufacturing and industrial-AI categories—but those cases came with clearer scale or strategic-asset framing than Black Lake has disclosed publicly. That is why a scenario model is more honest than a point estimate. At RMB7 billion post-money, the implied multiple is extremely sensitive to the hidden revenue denominator. If current revenue is only a few hundred million RMB, the price looks stretched relative to public comps; if revenue is already well into the upper hundreds of millions with credible profitability and retention, the same price can look fair. The evidence supports a wide band, not precision.[CV018, CV019, CV020, CV021, CV022, CV023]
| Scenario | Revenue proof assumption | Public-comp / private-comp lens | Indicative valuation range | Probability signal | Key risks |
|---|---|---|---|---|---|
| Bear | Current revenue remains in the low hundreds of millions RMB and retention or margins are mediocre. | Public comps dominate; market pays closer to compressed 2026 listed software bands than to private-unicorn scarcity. | RMB4.0bn-RMB5.5bn | Live risk if the hidden revenue denominator is too small or growth cools before the next financing. | Down round, slower enterprise expansion, or weak unit economics. |
| Base | Revenue is in the mid-hundreds of millions RMB, profitability is real, and AI monetization is emerging but not yet fully proven. | Blend of public mid-single-digit comp discipline plus a modest private-company premium for category position. | RMB6.0bn-RMB8.0bn | Most plausible public-only range, but still low-confidence without current KPI disclosure. | Customer-count definition drift, opaque cap table, and uncertain AI attach rates. |
| Bull | Revenue is in the upper hundreds of millions RMB, retention and gross margin are strong, and AI modules deepen ACV. | Private industrial-software scarcity and strategic value matter more than compressed public multiples. | RMB8.5bn-RMB10.5bn | Requires a data-room-quality disclosure package, not just more headline storytelling. | Execution on upmarket expansion and proof that AI contributes real commercial uplift. |
Ranges are scenario enterprise-value-style frames tied to evidence gaps and public comp bands, not precise equity-value forecasts.
[CV027, CV031, CV033, CV034, CV035, CV039]The current mark only moves into a public-comp-like range if the hidden revenue base is already much larger than public sources disclose.
Bars show implied revenue multiples at a fixed RMB7.0bn post-money valuation using illustrative revenue scenarios rather than asserted actual revenue.
[CV020, CV023, CV026, CV033, CV034, CV035]A wide scenario band is more honest than a point estimate because the hidden revenue base drives most of the valuation uncertainty.
Ranges are indicative post-money valuation scenarios in RMB billions, not promised exit outcomes or equity values after preferences.
[CV031, CV033, CV034, CV036, CV039]8.4 Final diligence and kill triggers
The final underwriting work is straightforward even if it is not easy. Investors need a current KPI pack, not more category storytelling: current ARR or revenue, gross margin, retention, AI attach rate, geography mix, and a post-Series-D cap table with any preference or downside-protection terms. Without those items, the recommendation cannot improve because the main uncertainty is valuation quality, not product awareness. The thesis also has clear break points. If retention or gross margin are weak, if revenue is far below what the headline valuation implies, or if the company remains better suited to smaller cloud-MES deployments than to high-ACV enterprise programs, then the current mark is too demanding. Conversely, a shift toward public-company-style transparency would materially upgrade confidence. Until then, Black Lake belongs on a high-priority diligence watchlist rather than in an invest-now queue.[CV039, CV040, CV041, CV042, CV043, CV044]
| Trigger | Threshold | Transmission to thesis | Action implication |
|---|---|---|---|
| Revenue proof | Current revenue turns out to be far below the level needed to support even the low end of base-case valuation | Would make the >RMB7bn mark look like a public-comp dislocation rather than justified scarcity pricing | Re-cut to bear case or walk away from the current process |
| Retention / gross margin quality | NRR, logo retention, or gross margin are materially below what premium software pricing assumes | Would show that reported profitability and scale do not translate into durable software economics | Require a much lower entry price or stop |
| Enterprise-fit ceiling | Large-factory ACV expansion is weak and the product remains concentrated in lighter deployments | Would cap upside and reduce the relevance of premium manufacturing-platform analogs | Shift from platform thesis to lightweight-tool thesis |
| Funding-window reset | Next financing is flat or down despite the 2026 AI narrative | Would validate public-multiple-compression risk and compress exit optionality | Treat the current valuation as too demanding |
| Disclosure behavior | Management still withholds KPI and cap-table detail in a serious process | Would confirm that the information asymmetry is structural, not temporary | Do not progress beyond watchlist status |
Kill triggers are designed to be monitorable and valuation-linked rather than generic operating risks.
[CV027, CV039, CV043, CV044]| Topic | Missing evidence | Why it matters | Owner or diligence path |
|---|---|---|---|
| Current revenue / ARR | Latest monthly ARR, LTM revenue, and bridge from 2025 to 2026 growth | Needed to convert the >RMB7bn mark into an actual revenue multiple rather than a headline. | Management finance pack; CFO or investor materials |
| Gross margin and services mix | Software gross margin, implementation burden, and contribution margin by product line | Separates true software leverage from services-heavy growth. | Finance data room plus cohort analysis |
| Retention quality | NRR, gross retention, logo retention, churn by customer segment | Determines whether public-comp multiples are even directionally relevant. | Board pack or sales-ops retention dashboard |
| AI monetization | Attach rate, pricing, renewal behavior, and ROI for agent modules | Tests whether the AI narrative increases ACV or is mostly positioning. | Product analytics plus customer reference calls |
| Cap table and preferences | Post-Series-D ownership, liquidation preferences, ratchets, and employee dilution | Without this, enterprise-value scenarios cannot be converted into equity outcomes. | Legal counsel and cap-table export |
| Geography and enterprise mix | Revenue by country, vertical, and ACV band; enterprise vs SMB concentration | Shows whether the company is really moving upmarket and global or mainly extending its domestic core. | Revops segmentation export and regional sales review |
Each ask is directly valuation-relevant and tied to a decision that would change the recommendation, confidence, or acceptable entry price.
[CV041, CV042, CV043]8.5 Exhibits
Disclaimer
This report relies on public and retrieved web sources as of the run date and should be used as a diligence starting point, not as a substitute for management materials, customer calls, financial statements, or legal review.
Evidence index
| ID | Statement | Confidence | Sources |
|---|---|---|---|
| CO001 | Black Lake says the business was founded in 2016 to deliver cloud-based manufacturing-collaboration software. | High | SO012, SO019 |
| CO002 | Public profiles place Black Lake's headquarters in Shanghai. | High | SO008, SO009 |
| CO003 | Black Lake's named product set includes Black Lake Intelligent Manufacturing, Black Lake Small Work Order, and Black Lake Supply Chain. | High | SO012, SO013, SO014, SO019 |
| CO004 | Official product materials position Black Lake Intelligent Manufacturing for larger complex factories and Small Work Order for smaller high-mix manufacturers. | Medium | SO013, SO014 |
| CO005 | Official materials describe Black Lake's commercial model as annual subscription software rather than one-time perpetual licensing. | High | SO012, SO014 |
| CO006 | Official marketing claims Black Lake Intelligent Manufacturing can be deployed in roughly four to six weeks. | High | SO002, SO018 |
| CO007 | Official marketing claims first-year software cost can be roughly one-fifth to one-tenth of traditional MES alternatives. | High | SO002, SO012, SO018 |
| CO008 | Zhou Yuxiang is publicly identified as Black Lake's founder, CEO, and legal representative of the named Shanghai operating entity. | High | SO008, SO019, SO020 |
| CO009 | Public profiles say Zhou Yuxiang studied at Dartmouth and worked in investment banking focused on industrial and manufacturing deals before founding Black Lake. | High | SO019, SO022, SO026 |
| CO010 | Zhou's first startup, Mada Data, failed because factories lacked enough structured data to support its original analytics-heavy product. | Medium | SO019, SO022, SO025 |
| CO011 | Aiqicha discloses a director roster for Shanghai Black Lake Technology Co., Ltd. that includes Zhou Yuxiang, Li Xiang, Yu Yan, Du Dikang, Ren Yongqiang, and Dennis Cong. | Medium | SO020 |
| CO012 | Public materials do not disclose the wider Black Lake group's full cap table or board-control structure beyond the named entity roster. | Medium | SO012, SO020 |
| CO013 | Black Lake announced a near-RMB1bn Series D in April 2026 at a post-money valuation above RMB7bn. | High | SO003, SO004, SO005, SO006 |
| CO014 | Crunchbase listed Black Lake among April 2026 new unicorns and reported the round as $146M at a $1.3B valuation. | Medium | SO001 |
| CO015 | Caixin named Guoxiang Capital, Shanghai State-owned Capital Leading Fund, Zhiying Investment, the National AI Industry Investment Fund, and Huaxia Zhiqing Venture Capital as Series D investors. | Medium | SO004 |
| CO016 | Older official company material described Black Lake as a C-round company backed by Temasek, CITIC Industrial Fund, GSR Ventures, Jiyuan Capital, and Lightspeed China. | Medium | SO012 |
| CO017 | CB Insights still showed Black Lake as Series D and listed total raised at $108.53M at fetch time. | Medium | SO010 |
| CO018 | Caixin said the April 2026 round was Black Lake's sixth financing round and exceeded all prior financing totals. | Medium | SO004 |
| CO019 | Multiple April 2026 reports say Black Lake is fully profitable and growing revenue by more than 60% year over year. | High | SO003, SO004, SO006, SO026 |
| CO020 | ITHome reported that Black Lake had built 6 categories and 11 industrial AI agents by 2026. | Medium | SO006, SO007 |
| CO021 | A 2026 profile said Black Lake aims to push AI-agent penetration above 80% of served factories within three to five years. | Medium | SO006 |
| CO022 | Official company material says Black Lake has won the trust of over 32,000 manufacturing enterprises and supply-chain participants. | Medium | SO012 |
| CO023 | China Daily said Black Lake was trusted by more than 34,000 manufacturing enterprises and their supply chains in October 2025. | Medium | SO008 |
| CO024 | The 2026 white paper and multiple April 2026 articles describe Black Lake as serving roughly 40,000 customers or factories. | Medium | SO003, SO011, SO024 |
| CO025 | The homepage still markets Black Lake as a digital partner for 4,000-plus manufacturing enterprises, well below the larger figures used elsewhere. | Medium | SO002 |
| CO026 | Official deep-dive material cites a 42.7% share in China's 2024 SaaS MES market and says Black Lake ranked second in the overall MES market. | Medium | SO012 |
| CO027 | April 2026 funding articles cite a 52.7% share in China's cloud-based production-management software market. | Medium | SO003, SO006, SO025 |
| CO028 | Baidu's English company profile says Black Lake operates in 12 countries and has delivered more than 30 overseas projects. | Medium | SO009 |
| CO029 | China Daily said overseas factories had shown interest in the Black Lake system and linked the company's growth to Shanghai's supportive environment. | Medium | SO008 |
| CO030 | Official company material says overseas coverage already includes Singapore, Indonesia, and Vietnam. | Medium | SO012 |
| CO031 | Jiemian reported that Black Lake stepped up overseas travel and began seeing opportunities in Southeast Asia and even Europe and the United States after 2025. | Medium | SO026 |
| CO032 | Public customer-proof materials confirm deployments or projects with Liby, Mengniu, Nongfu Spring, Mixue Bingcheng, and other large manufacturers. | High | SO012, SO015, SO017, SO018 |
| CO033 | Product materials position Small Work Order as the lightweight entry point and Black Lake Intelligent Manufacturing as the upgrade path for more complex plants. | Medium | SO013, SO014 |
| CO034 | Aiqicha dates Shanghai Black Lake Technology Co., Ltd. to 2017-03-28, while founder and brand materials date Black Lake's start to 2016, creating a disclosed brand-entity timing gap. | Medium | SO009, SO019, SO020 |
| CO035 | Baidu's English profile lists 230 social-insurance employees for 2023. | Medium | SO009 |
| CO036 | Baidu's founder profile said Black Lake had more than 500 employees by August 2023. | Medium | SO019 |
| CO037 | Sina's March 2024 founder profile said Black Lake had grown to more than 600 employees and revenue above RMB100m. | Medium | SO022 |
| CO038 | Aiqicha flags 1 court notice, 15 hearing notices, and 5 litigation relationships for Shanghai Black Lake Technology Co., Ltd. | Medium | SO020, SO021 |
| CO039 | Baidu's English profile adds a 2025 risk alert that mentions court-hearing announcements, judicial cases, and frozen shareholder-equity risk. | Medium | SO009 |
| CO040 | Aiqicha lists 14 patent records and 19 software copyrights for the named Shanghai entity. | Medium | SO020 |
| CO041 | The homepage says Black Lake's engineering organization includes more than 200 engineers from firms such as Google, Facebook, Alibaba, ByteDance, SAP, and Siemens. | Medium | SO002 |
| CO042 | Official speeches and profiles consistently frame Black Lake's differentiation as cloud-native manufacturing collaboration with fast rollout and lower complexity than traditional industrial software. | High | SO012, SO018, SO026 |
| CO043 | The adverse signals visible in public sources are summary legal notices and disclosure inconsistencies rather than disclosed sanctions, insolvency events, or product recalls. | Medium | SO009, SO020, SO021 |
| CM001 | Black Lake presents itself as a cloud-native manufacturing collaboration platform rather than a generic ERP suite. | High | SM001, SM003 |
| CM002 | Black Lake Intelligent Manufacturing targets larger factories that need planning, production, warehousing, quality, equipment, and supply-chain coordination. | Medium | SM003 |
| CM003 | Black Lake Small Work Order targets small and medium manufacturers that need order-fulfillment-centered production management. | Medium | SM004 |
| CM004 | Black Lake consistently positions cloud deployment, rapid implementation, and lower upfront cost as alternatives to traditional on-premise MES projects. | High | SM002, SM003, SM004, SM005 |
| CM005 | Black Lake's public framing places the monetizable core in manufacturing execution and collaboration software, while adjacent hardware automation spending sits outside its direct software revenue pool. | Medium | SM001, SM003, SM017 |
| CM006 | The company's market boundary extends from single-plant execution into cross-factory and supply-chain collaboration, which is broader than a narrow shop-floor-only MES definition. | High | SM002, SM003, SM008 |
| CM007 | IDC said the 2024 China MES solutions market, including software and services but excluding hardware, reached RMB15.91 billion. | Medium | SM017 |
| CM008 | IDC said the 2024 China MES software market reached RMB6.29 billion. | Medium | SM017 |
| CM009 | IDC said the 2024 China public-cloud SaaS MES software market reached RMB1.005 billion, equal to 16.0% of the overall MES software market. | Medium | SM017 |
| CM010 | IDC ranked Baoxin Software, Black Lake, and Siemens as the top three vendors in 2024 China MES software. | Medium | SM017 |
| CM011 | IDC said the competitive center of gravity in SaaS MES is shifting from low-cost replication toward multi-factory and cross-organization coordination. | Medium | SM017 |
| CM012 | IDC identified especially fast growth in 2024 MES demand from high-tech electronics, shipbuilding, auto parts, and equipment manufacturing relative to the overall market. | Medium | SM017 |
| CM013 | CAICT said 89.6% of above-scale industrial enterprises in China had carried out digital transformation by the end of 2025. | Medium | SM011 |
| CM014 | CAICT said digital equipment penetration in China's manufacturing base reached 57.7% by the end of 2025. | Medium | SM011 |
| CM015 | CAICT said automotive, shipbuilding, and electronics manufacturing had the highest digitization rates, at 94.4%, 94.2%, and 93.9% respectively. | Medium | SM011 |
| CM016 | China had built more than 30,000 basic smart factories, more than 1,200 advanced smart factories, and more than 230 excellence-level smart factories by the end of 2024. | High | SM015, SM013 |
| CM017 | Digital China 2024 said 5G plus industrial internet had covered all 41 industrial categories, with 700 high-level 5G factories and more than 17,000 projects. | Medium | SM015 |
| CM018 | The National Bureau of Statistics said China's key industrial-internet platforms had connected more than 100 million devices by 2025. | Medium | SM012 |
| CM019 | The National Bureau of Statistics said China's industrial robot output rose from 218,000 units in 2020 to 773,000 units in 2025. | Medium | SM012 |
| CM020 | The National Bureau of Statistics said China's 3D-printing equipment output reached 5.211 million units in 2025 after a 30.9% CAGR from 2021 to 2025. | Medium | SM012 |
| CM021 | Black Lake's large-enterprise pitch is built around multi-plant standardization, rapid replication, and cross-factory data visibility. | High | SM002, SM003 |
| CM022 | Black Lake cites pharma, chemicals, metals, plastics, food and beverage, appliances, and electronics as representative verticals for its larger-factory offering. | High | SM002, SM003 |
| CM023 | Black Lake Small Work Order explicitly targets high-mix, small-batch SME manufacturing in categories such as machinery, sheet metal, furniture, food processing, textiles, and plastics. | Medium | SM004 |
| CM024 | Black Lake says Small Work Order can go live in two to three days, which is a materially different adoption path from the six-to-twelve-week rollout of the larger MES product. | Medium | SM003, SM004 |
| CM025 | Because both product lines emphasize ERP, OA, data-capture, and API integration, real budget ownership likely spans plant operations and IT rather than a single pure software buyer. | Medium | SM003, SM004, SM010 |
| CM026 | Huawei Cloud said all of Black Lake's business runs on its container service and that operating costs were 70% lower than running a self-managed Kubernetes cluster. | Medium | SM010 |
| CM027 | Huawei Cloud said Black Lake used the cloud marketplace to reach more industry customers and generated annual marketplace sales in the tens of millions of RMB. | Medium | SM010 |
| CM028 | The Liby case shows the buyer problem for a large consumer-goods group is multi-system interconnection, agile supply, and flexible delivery across plants. | Medium | SM007 |
| CM029 | The Mengniu case shows the buyer problem for a large food manufacturer is supply-chain-online coordination, process transparency, and digital quality control. | Medium | SM008 |
| CM030 | The Yada case shows a multi-site industrial group buying Black Lake to combine SCADA, ERP, production, quality, and materials data into one traceable operating layer. | Medium | SM009 |
| CM031 | An NDRC-affiliated article citing IDC said the share of Chinese industrial enterprises using large models or intelligent agents rose from 9.6% in 2024 to 47.5% in 2025. | Medium | SM013 |
| CM032 | The same NDRC-affiliated article said smart factories covering more than 80% of manufacturing categories had shortened product R&D cycles by an average of 28.4%. | Medium | SM013 |
| CM033 | SASAC said many SMEs still face “do not dare to transform” and “do not know how to transform” barriers in industrial intelligence adoption. | Medium | SM014 |
| CM034 | SASAC said industrial-intelligence adoption is also constrained by weak standards and insufficient security awareness. | Medium | SM014 |
| CM035 | Deloitte said the main barriers to industrial physical-AI adoption are cost and resource requirements at 41%, identifying use cases at 36%, talent and skills gaps at 33%, and technology or data availability at 31%. | Medium | SM019 |
| CM036 | Deloitte said only 3% of firms have physical AI extensively integrated today, but 18% expect that within two years and 41% expect transformational impact within three years. | Medium | SM019 |
| CM037 | KAS said AI adoption among Southeast Asian SMEs is often constrained by skills shortages, inadequate digital infrastructure, and high financial costs, with talent gaps worse in Indonesia, the Philippines, and Vietnam than in Singapore. | Medium | SM021 |
| CM038 | ABI Research said Southeast Asian manufacturers' Industry 4.0 investment is expected to reach US$301.6 billion by 2028 at a 32.9% CAGR. | Medium | SM022 |
| CM039 | ABI Research said the share of Southeast Asian factories implementing smart solutions could rise from 6.3% to 32.8% by 2028. | Medium | SM022 |
| CM040 | Source of Asia said ASEAN manufacturing is forecast to grow from US$1.7 trillion in 2018 to US$2.3 trillion by 2029. | Medium | SM024 |
| CM041 | Source of Asia said Vietnam's average manufacturing wages are about half of China's, reinforcing ASEAN's cost-competitive pull for regional manufacturing expansion. | Medium | SM024 |
| CM042 | Eurogroup Consulting said Southeast Asia has more than 1,000 industrial parks and zones that support scalable production and Industry 4.0 deployment. | Medium | SM025 |
| CM043 | Eurogroup Consulting said Southeast Asia has recently surpassed China in greenfield manufacturing FDI trends. | Medium | SM025 |
| CM044 | The ASEAN Secretariat and OECD argue that higher digital maturity should help ASEAN members attract more manufacturing FDI, but the region still shows large maturity gaps between Singapore and lower-tier members. | Medium | SM023 |
| CM045 | The ASEAN Secretariat and OECD recommend stronger digital infrastructure, digital-worker skills, and targeted financial incentives to improve manufacturing FDI attraction. | Medium | SM023 |
| CM046 | The World Economic Forum said China's AI strategy depends on infrastructure, data interoperability, talent, and industry-specific applications rather than generic one-size-fits-all deployment. | Medium | SM026 |
| CM047 | The World Economic Forum also said fragmented data flows, uneven regional capabilities, and talent gaps remain obstacles to scalable industrial AI adoption in China. | Medium | SM026 |
| CM048 | Siemens' IDC MarketScape summary says modern MES competition is increasingly shaped by cloud computing, IIoT, AI, and adaptability to enterprise applications. | Medium | SM018 |
| CM049 | BCG said Southeast Asia's AI trajectory depends on cross-border collaboration and on closing talent and infrastructure gaps across ASEAN-6. | Medium | SM027 |
| CM050 | Accessible public evidence still does not independently verify Black Lake's exact share of China's public-cloud SaaS MES market because the underlying IDC tables are not publicly visible in full. | Medium | SM017, SM018 |
| CM051 | Accessible public evidence also does not disclose Black Lake's current Southeast Asia revenue, customer count, or local entity footprint with enough precision for underwriting. | Medium | SM024, SM025, SM027 |
| CP001 | Black Lake publicly segments its product line between Black Lake Intelligent Manufacturing for larger factories and Black Lake Small Work Order for SMEs. | Medium | SP002, SP003 |
| CP002 | Black Lake says Intelligent Manufacturing can be deployed in about 6-12 weeks while Small Work Order can go live in roughly 2-3 days. | Medium | SP002, SP003 |
| CP003 | Black Lake describes its products as subscription or annual-fee software and claims costs materially below traditional MES alternatives. | Medium | SP002, SP003, SP025 |
| CP004 | Siemens Opcenter is marketed as manufacturing operations management software that links PLM to automation and emphasizes quality, visibility, and digital-twin-enabled production control. | Medium | SP004 |
| CP005 | SAP Digital Manufacturing is marketed as a cloud MOM/MES layer on SAP Business Technology Platform that connects shop floor execution with planning, logistics, quality, maintenance, and workforce data. | Medium | SP005, SP006 |
| CP006 | Tulip markets a composable, app-based MES with open API, AI-native capabilities, and a three-month average implementation window. | Medium | SP007, SP009, SP010 |
| CP007 | Plex markets a unified cloud platform spanning MES, QMS, production monitoring, and asset performance rather than a narrow point execution tool. | Medium | SP011, SP012 |
| CP008 | Digiwin publicly presents a manufacturing stack spanning ERP, MES, WMS, and AIoT instead of only a stand-alone execution application. | Medium | SP020, SP021 |
| CP009 | Saiyi publicly presents a heavy iMOM manufacturing-operations suite for large groups plus a lighter SIE IDP app platform for SMEs. | Medium | SP022, SP023 |
| CP010 | Odoo, Katana, and MRPeasy all market manufacturing as part of broader inventory, orders, planning, and shop-floor software rather than as a classic heavyweight MES project. | Medium | SP013, SP015, SP017 |
| CP011 | Tulip's public pricing starts at $100 per interface per month with a 10-interface minimum, rises to $250 per interface per month for Professional, and uses custom pricing for higher tiers. | Medium | SP008 |
| CP012 | Odoo publicly offers a one-app free plan plus about US$31.10 and US$61.00 per-user-per-month annual plans for broader app access. | Medium | SP014 |
| CP013 | MRPeasy publicly prices its plans at $49, $69, $99, and $149 per user per month depending on tier. | Medium | SP018 |
| CP014 | Katana publicly offers a free plan and says guided onboarding can reach full inventory visibility in about six weeks, with some teams starting in one day. | Medium | SP015, SP016 |
| CP015 | The reviewed Siemens, SAP, and Plex pages do not publish list pricing and instead imply quote-led enterprise sales. | Medium | SP004, SP005, SP006, SP012 |
| CP016 | Plex's Microsoft Marketplace page says pricing is available only through a private offer or custom contract. | Medium | SP012 |
| CP017 | Tulip explicitly markets validation packs, regulated-industry add-ons, electronic signatures, auditable record history, and long-term support for compliance-heavy buyers. | Medium | SP007, SP008 |
| CP018 | SAP publicly emphasizes hybrid manufacturing, skills matrices, issue-resolution workflows, and bidirectional integration with logistics, maintenance, safety, and workforce systems. | Medium | SP005, SP006 |
| CP019 | Siemens and SAP both frame execution inside broader manufacturing-operations stacks, which favors buyers already standardized on their enterprise or automation ecosystems. | Medium | SP004, SP005, SP006 |
| CP020 | Black Lake Intelligent Manufacturing publicly emphasizes 50+ apps, APIs, low-code composition, and multi-factory or supplier coordination for Chinese manufacturers. | Medium | SP002, SP025 |
| CP021 | Black Lake Small Work Order publicly emphasizes order-centric coordination across sales, purchasing, production, inventory, and supplier collaboration for SMEs. | Medium | SP003 |
| CP022 | Odoo's manufacturing module includes a tablet shop-floor app, offline operation, traceability, and IoT integration. | Medium | SP013 |
| CP023 | MRPeasy targets manufacturers with 10-200 employees and says more than 2,000 manufacturers trust the software. | Medium | SP017 |
| CP024 | Katana positions itself against spreadsheets and legacy ERP with real-time inventory, production tracking, lot traceability, and fast implementation. | Medium | SP015 |
| CP025 | Digiwin's Thailand site says the company has 44 years of manufacturing focus, serves 50,000+ factories, and is Shenzhen-listed. | Medium | SP020 |
| CP026 | Digiwin sMES emphasizes machine data, task dispatch, traceability, quality control, and mobile factory management rather than purely financial ERP logic. | Medium | SP019 |
| CP027 | Saiyi's 2026 profile says its SME platform includes 43 lightweight apps across seven business domains. | Medium | SP022 |
| CP028 | Saiyi's public case library names many Chinese manufacturing customers across auto parts, electronics, appliances, feed, lighting, and elevators. | Medium | SP024 |
| CP029 | Black Lake occupies a middle position that is more factory-execution-specific than Odoo, Katana, and MRPeasy but lighter and more approachable than Siemens, SAP, and Plex. | Medium | SP002, SP003, SP004, SP005, SP011, SP013, SP015, SP017 |
| CP030 | Black Lake's public commercial disclosure is qualitative and relative, while Tulip, Odoo, Katana, and MRPeasy provide much clearer public price anchors. | Medium | SP003, SP008, SP014, SP016, SP018 |
| CP031 | Tulip discloses broader public ecosystem signals than Black Lake, including 60+ implementation partners in 20 countries plus AWS and Microsoft distribution proof. | Medium | SP007, SP009, SP010 |
| CP032 | Domestic incumbents Digiwin and Saiyi look more dangerous inside China than SAP or Siemens on channel and access grounds because they pair local manufacturing coverage with wider domestic trust signals. | Medium | SP020, SP022, SP024 |
| CP033 | Status-quo competition remains active because Digiwin, Katana, and MRPeasy all explicitly market against spreadsheets, ghost inventory, and manual production tracking. | Medium | SP015, SP017, SP020 |
| CP034 | SAP, Siemens, and Tulip all disclose more explicit regulated-workflow, validation, or compliance language than Black Lake's reviewed public pages do. | Medium | SP004, SP005, SP006, SP007, SP008 |
| CP035 | The reviewed public source set does not include a neutral win-loss dataset or churn disclosure showing Black Lake consistently beating or losing to named competitors. | Low | SP001, SP004, SP005, SP007, SP020, SP022 |
| CP036 | The strongest public evidence for Black Lake's moat is deployment speed and China-local workflow fit rather than disclosed renewal economics, lock-in metrics, or exclusive ecosystem control. | Medium | SP002, SP003, SP020, SP022 |
| CP037 | The strongest public enterprise-trust signals in the reviewed set sit with Siemens, SAP, and Plex through broader operations stacks, quality systems, or renewal/security disclosures. | Medium | SP004, SP005, SP006, SP011, SP012 |
| CP038 | Lightweight substitutes compress SMB procurement because they combine public list pricing, rapid onboarding claims, and broad inventory-order-production coverage without a classic MES project. | Medium | SP014, SP015, SP016, SP017, SP018 |
| CP039 | Tulip's pricing uses interfaces rather than users, which creates a different scaling model from the per-user economics disclosed by Odoo and MRPeasy. | Medium | SP008, SP014, SP018 |
| CP040 | Odoo says 15 million users run their businesses with Odoo, indicating large horizontal software scale even though manufacturing is only one module. | Medium | SP013 |
| CP041 | Plex publicly cites 8B+ transactions a day, an A security rating, and a 96% gross renewal rate. | Medium | SP011 |
| CP042 | Digiwin's sMES ROI statistics are framed as relevant industry statistics rather than customer-specific audited results, so they are directional rather than definitive proof of outcome superiority. | Low | SP019 |
| CI001 | Black Lake’s official manufacturing page describes a cloud-based, configurable collaboration system sold on an annual subscription model for factories. | Medium | SI001 |
| CI002 | The official manufacturing page says Black Lake charges annual subscriptions and frames first-year cost at about one-fifth of traditional buyout software. | Medium | SI001 |
| CI003 | Official materials position Black Lake Intelligent Manufacturing for larger and more complex factory environments that need multi-factory and supply-chain coordination. | Medium | SI001 |
| CI004 | Official Small Work Order materials position the product for SMEs and high-mix, small-batch manufacturing with much faster go-live expectations than the enterprise product. | Medium | SI004, SI025 |
| CI005 | An official April 2026 pricing explainer says Small Work Order is sold in professional and flagship editions as SaaS software charged annually and not sold as a buyout license. | Medium | SI003 |
| CI006 | The official pricing explainer lists the Small Work Order professional package at RMB10,800 per year with 50 included accounts and RMB140 per additional account per year. | Medium | SI003 |
| CI007 | The same official pricing explainer lists the Small Work Order flagship package at RMB18,800 per year and ties it to added procurement, sales, quality, and PDA workflows. | Medium | SI003 |
| CI008 | The official pricing explainer says Black Lake does not offer an online trial for Small Work Order and instead offers free on-site demos across 35 cities. | Medium | SI003 |
| CI009 | Jiemian reports that after AI agents were introduced, Black Lake began pricing annual agent fees against roughly one month of the relevant worker’s salary. | Medium | SI009 |
| CI010 | The AI-agent pricing language implies Black Lake is trying to monetize labor-value capture rather than only software seats or modules. | Medium | SI003, SI009 |
| CI011 | Multiple independent April 2026 outlets report that Black Lake completed a Series D financing of roughly RMB1 billion. | High | SI005, SI006, SI008, SI011, SI013, SI016, SI022 |
| CI012 | Independent 2026 coverage places Black Lake’s post-money valuation above RMB7 billion, while Crunchbase translated the round to roughly a $1.3 billion valuation. | High | SI011, SI013, SI016, SI022, SI023 |
| CI013 | The stated use of proceeds for the 2026 D round is to accelerate industrial-AI deployment and fund global expansion. | High | SI005, SI006, SI009, SI012, SI018 |
| CI014 | Public 2026 financing coverage says the D round was the company’s sixth financing after angel, A, A+, B, and C rounds. | Medium | SI005, SI008, SI013 |
| CI015 | Black Lake’s public cumulative-capital ledger is not reconciled cleanly across official, recruiting, and market-data sources. | Medium | SI001, SI017, SI021 |
| CI016 | CB Insights still showed Black Lake’s total raised at a much lower figure than the implied post-D capital stack, suggesting database lag or incomplete public round aggregation. | Low | SI016, SI017 |
| CI017 | A Zhaopin company profile said Black Lake had previously received more than RMB800 million of investment, which still does not fully reconcile the post-D public capital picture. | Low | SI021 |
| CI018 | Multiple 2026 outlets repeat Black Lake’s claim that revenue is growing more than 60% year over year and that the company is fully profitable. | Medium | SI005, SI006, SI007, SI008, SI009, SI010, SI012, SI013, SI014, SI022 |
| CI019 | No retained public source discloses Black Lake’s audited revenue, ARR, gross margin, or operating cash flow alongside the profitability claim. | Medium | SI005, SI009, SI013, SI017 |
| CI020 | A recruiting-page chronology claims Black Lake reached roughly RMB20 million revenue in 2018, more than RMB50 million in 2019, and more than RMB100 million in 2020. | Low | SI021 |
| CI021 | Public scale metrics drift across sources, with official and quasi-official pages citing roughly 30,000, 32,000, or nearly 40,000 factories or manufacturing enterprises served. | Medium | SI001, SI002, SI005, SI021, SI022, SI023 |
| CI022 | Market-share claims also vary by time period and category, with the official manufacturing page citing 42.7% in IDC’s 2024 SaaS MES view while 2026 articles cite 52.7% in a cloud production-management framing. | Medium | SI001, SI005, SI022 |
| CI023 | Jiemian says many of Black Lake’s target factories had never previously used industrial software, which implies a greenfield adoption motion rather than mainly replacement buying. | Medium | SI009 |
| CI024 | Black Lake’s official product surfaces show a dual-segment model: Intelligent Manufacturing for larger factories and Small Work Order for smaller manufacturers with lighter budgets and faster rollout needs. | High | SI001, SI004, SI025 |
| CI025 | A Zhaopin company page says Black Lake has more than 500 employees and more than 200 technical staff, providing a rough but unaudited cost-base signal. | Low | SI021 |
| CI026 | Jiemian and the Shanghai government both show Black Lake pursuing overseas expansion, especially in Southeast Asia, which implies incremental spending before overseas revenue is publicly proven. | Medium | SI009, SI018 |
| CI027 | Aiqicha surfaces one court notice, 15 hearing notices, and five litigation relationships for Shanghai Black Lake Technology Co., Ltd., but does not disclose the economic exposure. | Medium | SI019 |
| CI028 | No retained source discloses current cash on hand, monthly burn, runway, debt facilities, or covenant structure for Black Lake. | Medium | SI005, SI009, SI013, SI019 |
| CI029 | No retained source discloses how much revenue comes from enterprise subscriptions versus SME packages, services, or AI-agent upsells. | Medium | SI001, SI003, SI004, SI009 |
| CI030 | No retained public source discloses CAC, payback, churn, or net revenue retention for any Black Lake product line. | Medium | SI003, SI009, SI021 |
| CI031 | The public evidence supports at least four monetization levers: packaged SME subscriptions, enterprise annual subscriptions, seat or module expansion, and AI-agent fees. | Medium | SI001, SI003, SI009 |
| CI032 | Because the products are positioned as SaaS with fast rollout rather than local perpetual software, Black Lake likely carries ongoing cloud, onboarding, and support costs that are not publicly broken out. | Medium | SI001, SI003, SI004 |
| CI033 | Black Lake’s official ecosystem language indicates partner-assisted delivery rather than a purely direct-implementation model. | Medium | SI001, SI002 |
| CI034 | Jiemian’s founder interview argues that quote and split-order mistakes directly erode factory profit, which explains why Black Lake believes AI-agent pricing can map to customer labor economics. | Medium | SI009, SI020 |
| CI035 | 2026 coverage frames Black Lake’s industrial-AI productization as early but commercially ambitious, with a 3–5 year target of more than 80% AI-agent penetration across served factories. | Medium | SI008, SI014 |
| CI036 | The flagship Small Work Order tier broadens the SME product from core production control into procurement, sales, quality, and PDA workflows, creating an explicit wallet-share upsell path. | Medium | SI003 |
| CI037 | The Zhaopin company page uses a different denominator from the factory-count headlines, saying more than 3,000 manufacturing enterprises have partnered with Black Lake, including dozens of Fortune 500 groups. | Low | SI021 |
| CI038 | The public evidence supports a view that Black Lake has financing access and commercial traction, but not enough disclosure to prove revenue quality, margin durability, or capital sufficiency. | Medium | SI011, SI013, SI019 |
| CI039 | Official product surfaces imply materially different service intensity by segment, with enterprise deployment taking 4–6 weeks and the SME product going live in roughly 2–5 days. | High | SI004, SI025 |
| CI040 | Black Lake’s public pricing disclosures reveal list-price mechanics but do not reveal realized enterprise contract values, discounting, or renewal economics. | Medium | SI001, SI003 |
| CE001 | Black Lake's core public product portfolio centers on Black Lake Intelligent Manufacturing for larger multi-role factories and Black Lake Small Work Order for SME manufacturers. | High | SE001, SE003, SE024 |
| CE002 | Black Lake Intelligent Manufacturing presents a browser-based SaaS surface spanning data reports, factory modeling, production management, planning and scheduling, and inventory management. | Medium | SE001, SE002 |
| CE003 | Official materials claim Black Lake Intelligent Manufacturing can be implemented in roughly 4-6 weeks and priced at roughly one-tenth of traditional MES software. | Medium | SE001, SE002, SE003 |
| CE004 | Black Lake Small Work Order is positioned around order-fulfillment workflow, linking sales, procurement, production, inventory, and finance for smaller factories. | Medium | SE005, SE011 |
| CE005 | Black Lake Small Work Order claims a very short deployment cycle, with public materials citing two to five days to go live and low training overhead. | Medium | SE005, SE011 |
| CE006 | Black Lake publicly describes its architecture as cloud-native, containerized, and Service-Mesh-based rather than an on-prem monolith. | High | SE001, SE010, SE014 |
| CE007 | Black Lake exposes standard openAPI interfaces for ERP, OA, logistics, sales, and shopfloor-system integrations. | High | SE001, SE004, SE013 |
| CE008 | Black Lake Intelligent Manufacturing public documentation lists 50+ prebuilt business apps across planning, production, warehousing, quality, equipment, and production supply-chain management. | Medium | SE004 |
| CE009 | The company says those manufacturing modules are microservice-based and can be combined or configured per factory scenario. | Medium | SE004 |
| CE010 | The public product brief describes a big-data layer built on Flink and StarRocks that supports 100TB-scale storage plus second-level data collection and analytics. | Medium | SE004 |
| CE011 | Black Lake's MES-facing AI-native features include workflow-customization agents, system-integration agents, and code-generation capabilities. | Medium | SE004 |
| CE012 | Independent 2026 coverage says Black Lake has built six categories of 11 industrial AI agents spanning design, scheduling, production, and quality. | Medium | SE021, SE022 |
| CE013 | IT之家 reports those industrial AI agents had executed more than 160 million tasks by mid-2026, indicating deployment beyond proof-of-concept. | Medium | SE022 |
| CE014 | Dahecube reports Black Lake's split-order agent cuts manual split work from two to three hours to minutes at over 95% accuracy, while its quote agent reduces quoting from six hours to seconds with ±5% error. | Medium | SE020 |
| CE015 | Black Lake maintains a public GitHub organization with active 2026 repository updates, including AI-coder templates and a Java openapi-sdk repository. | Medium | SE015, SE016 |
| CE016 | The public openapi-sdk README directs developers to the Black Lake Open Platform at v3-ali-openapi.blacklake.cn. | Medium | SE017, SE013 |
| CE017 | The fetched Black Lake Open Platform landing page instructs users to consult api-index.json and per-interface Markdown files, indicating a structured documentation tree. | Medium | SE013 |
| CE018 | Another fetched API route endpoint returned TOKEN_NOT_FOUND / 请先登录, showing that at least some public-facing API documentation or route surfaces are login-gated. | Medium | SE012 |
| CE019 | Black Lake's official company brief says its open platform is complemented by more than 300 ecosystem partners and one-stop sign-on/data-interconnection capabilities. | Medium | SE003 |
| CE020 | Black Lake says its product team includes 200+ engineers with backgrounds at Google, Facebook, Alibaba, ByteDance, SAP, and Siemens. | Low | SE001 |
| CE021 | Official company materials describe Black Lake as a continuously iterated SaaS product with monthly release cadence. | Medium | SE003 |
| CE022 | Official surfaces place Black Lake's served-customer base at more than 32,000 manufacturing enterprises and supply chains. | Medium | SE003, SE024 |
| CE023 | Independent 2025-2026 sources place Black Lake's footprint higher, at over 34,000 manufacturing enterprises or nearly 40,000 factories, implying rapid growth but also metric-definition drift. | Medium | SE021, SE022, SE023 |
| CE024 | Public materials attribute category leadership to IDC-backed cloud MES share figures of 42.7% in 2024 and 52.7% in 2025/2026 media, supporting a leadership narrative but with differing measurement windows. | Medium | SE003, SE021, SE022, SE023 |
| CE025 | Black Lake positions its software around multi-plant and supply-chain collaboration rather than just digitizing a single shopfloor. | Medium | SE001, SE003, SE010 |
| CE026 | The Yada case shows Black Lake integrating SCADA and ERP with production, quality, material, and equipment modules to support factory and group-level monitoring. | Medium | SE008 |
| CE027 | The same Yada case shows SOP-gated operations, standardized digital records, and one-code traceability as core operating mechanisms. | Medium | SE008 |
| CE028 | Yada also used the MI analytics layer to build equipment- and line-level alerting from production data. | Medium | SE008 |
| CE029 | Official materials say Black Lake helped Nongfu Spring digitize plan, production, quality, and equipment management across 25+ factories, increasing single-factory efficiency 30%, cutting 358 labor-hours per day at group level, and raising plan response speed 50%. | Medium | SE003 |
| CE030 | The Liby case frames Black Lake as a work-order-centric, cloud-real-time platform that links material supply, production, packaging, and warehouse-distribution flows. | Medium | SE007 |
| CE031 | The Mengniu case describes Black Lake as enabling device connectivity, system interoperability, production transparency, digital quality control, and cost control in a dairy factory rollout. | Medium | SE009 |
| CE032 | The English homepage includes a customer quote claiming an old MES replacement saved 7,000 man-hours and improved traceability enough to win more orders. | Medium | SE002 |
| CE033 | The Small Work Order site says one machinery customer reduced report delays from over half a day to 10 minutes and cut order-progress lookup time from over 30 minutes to one minute. | Medium | SE011 |
| CE034 | The Small Work Order site says another customer raised delivery rate from 50% to 90% after rollout. | Medium | SE011 |
| CE035 | The Small Work Order site says another customer used process-level scrap tracking to keep defect rate below 1%. | Medium | SE011 |
| CE036 | Public Black Lake materials display MLPS level 3, ISO27001, and national-industrial-standards participation as trust and compliance signals. | Medium | SE011 |
| CE037 | Baidu Baike records 58 software copyrights and 109 registered trademarks, suggesting a meaningful accumulation of proprietary product assets. | Medium | SE024 |
| CE038 | 2026 funding coverage says Black Lake's near-RMB1 billion D round is earmarked for industrial-AI commercialization and global expansion rather than maintenance of a static MES stack. | Medium | SE018, SE019, SE021, SE026 |
| CE039 | Independent 2025-2026 sources say Black Lake has reached 12 countries and is exporting China-style flexible-manufacturing workflows to overseas factories. | Medium | SE022, SE024 |
| CE040 | Black Lake's public surface does not expose a public status page, uptime SLA, or open anonymous API explorer, so enterprise diligence still needs direct reliability and integration review. | Low | SE001, SE012, SE013 |
| CE041 | The 2026 white paper describes a three-line product matrix of Black Lake Intelligent Manufacturing, Black Lake Light Manufacturing, and Black Lake Small Work Order. | Medium | SE006 |
| CE042 | Black Lake Intelligent Manufacturing publicly supports cross-terminal use on PC, TV, Android, and iOS. | Medium | SE004 |
| CE043 | Small Work Order materials say the product can be extended with a few hundred lines of code and upgraded later into the fuller Black Lake Intelligent Manufacturing stack. | Medium | SE005 |
| CE044 | Across official cases and company summaries, Black Lake appears strongest in food and beverage, auto parts, plastics/chemicals, pharma, and equipment-heavy discrete manufacturing rather than highly regulated continuous-process niches. | Medium | SE003, SE008, SE009, SE010 |
| CE045 | The fetched api-index.json from Black Lake's open platform enumerates 787 APIs across categories including auth, organization permissions, modeling, production, warehousing, quality, traceability, equipment, and sales workflows. | Medium | SE027 |
| CE046 | The public 检验任务列表 API doc exposes a quality-task endpoint tied to inbound orders, outbound orders, work orders, production tasks, equipment IDs, and inspection schemes, indicating quality execution is modeled as an operational workflow rather than a standalone checklist. | Medium | SE027, SE028 |
| CE047 | The public 设备列表接口 doc exposes equipment metadata, lifecycle dates, supplier and location fields, storage links, and parameter read/write hooks, supporting the view that Black Lake models equipment as a structured production resource inside the platform. | Medium | SE027, SE029 |
| CU001 | Black Lake Smart Manufacturing is publicly positioned for large or multi-plant manufacturers with complex cross-department workflows. | Medium | SU018, SU019, SU020 |
| CU002 | Black Lake Mini Worksheet is publicly positioned for small and micro factories and priced as an annual SaaS tool rather than a perpetual-license MES. | Medium | SU004, SU005, SU007 |
| CU003 | The public buyer-user-payer split implies enterprise deals are sponsored by group operations or IT leadership, while SME deals are closer to owner or workshop-lead budgets and frontline usage. | Medium | SU002, SU004, SU005, SU007 |
| CU004 | Named public customer proof spans both consumer supply-chain groups and industrial manufacturers rather than a single narrow niche. | Medium | SU006, SU015, SU016, SU017, SU018 |
| CU005 | Most named proofs still come from large enterprise operators such as Mixue, Nongfu Spring, Mengniu, Liby, and Yada rather than from small factories. | Medium | SU006, SU015, SU016, SU017, SU018 |
| CU006 | Black Lake homepage copy publicly presents the company as a digital partner to 4,000+ manufacturing enterprises. | Medium | SU019 |
| CU007 | A longer Black Lake company profile says the company has won the trust of more than 32,000 manufacturing enterprises and their supply chains. | Medium | SU018 |
| CU008 | That same Black Lake company profile also describes near-30,000 factories covered across China and Southeast Asia. | Medium | SU018 |
| CU009 | The World Economic Forum profile says Black Lake has empowered nearly 40,000 factories globally. | High | SU006, SU021 |
| CU010 | A Black Lake-authored 2026 MES market article claims more than 40,000 factories served and 40% year-over-year growth. | Medium | SU002 |
| CU011 | A 2026 Black Lake white paper uses both “近4万家服务客户” and “3.5万家客户体量”, further showing that public installed-base metrics move across different labels and rounding conventions. | Medium | SU020 |
| CU012 | Public installed-base metrics are directionally positive but not reconciled because they alternate among enterprises, factories, geography-limited factories, and paying customers. | Medium | SU006, SU018, SU019, SU020, SU021, SU023 |
| CU013 | Black Lake publicly says it won a Mengniu digital-factory project to build a cloud-collaborative dairy plant. | Medium | SU015 |
| CU014 | The Mengniu case describes device interconnection, system interconnection, production transparency, digital quality control, finer cost control, and a shorter product-development cycle. | Medium | SU015 |
| CU015 | Before the Black Lake rollout, Yada was already operating six production bases and nearly forty automated lines. | Medium | SU016 |
| CU016 | The Yada case says Black Lake connected existing SCADA and ERP data with production, quality, material, and equipment modules. | Medium | SU016 |
| CU017 | Yada public proof goes beyond a pilot because it describes full-process control, one-code traceability, and group-level vertical management across multiple plants. | High | SU013, SU016 |
| CU018 | The Liby case frames Black Lake as the workflow core of an integrated smart factory spanning materials supply, production, packaging, warehousing, and distribution. | Medium | SU017 |
| CU019 | The Liby case says the initial project would be promoted to all factories after pilot validation, which is a direct public land-and-expand signal. | Medium | SU017 |
| CU020 | Mixue Group is named as a Black Lake customer by both the World Economic Forum profile and Black Lake's own 2026 customer materials. | High | SU001, SU006, SU018 |
| CU021 | Mixue context sources show it is a franchise-led beverage chain whose supply chain provides ingredients, packaging materials, and store equipment to franchisees across multiple Asian countries. | Medium | SU008, SU009, SU011 |
| CU022 | Black Lake's Mixue customer narrative says the system improved production operating efficiency by 30%, warehouse turns by 50%, same-capacity production cost by 15%, and cross-department communication efficiency by 80%. | Medium | SU018 |
| CU023 | Nongfu Spring is named as a Black Lake customer by both the World Economic Forum profile and Black Lake's own customer materials. | High | SU006, SU018 |
| CU024 | Black Lake customer materials describe Nongfu Spring as coordinating nearly thirty factories across five water-source regions. | Medium | SU018, SU019 |
| CU025 | Black Lake customer materials claim Nongfu Spring simplified more than one hundred process steps, saved 358 labor hours per day at group level, and lifted planning-response speed by 50%. | Medium | SU018 |
| CU026 | Alibaba Cloud Marketplace quotes a ChinaUST Group IT head saying Smart Manufacturing replaced a traditional MES, saved 7,000 man-hours, and helped win more customer orders. | Medium | SU007 |
| CU027 | Alibaba Cloud Marketplace quotes JYD Technology saying Mini Worksheet improved order-delivery rate by 5% after one month of use. | Medium | SU007 |
| CU028 | Public SME proof is materially thinner than enterprise proof because the company gives pricing, demo motion, and generic testimonials for Mini Worksheet but few named long-tail factory references. | Medium | SU004, SU005, SU007 |
| CU029 | Multi-plant collaboration is repeatedly central to Black Lake's enterprise value proposition across homepage copy, official customer cases, and 2026 market articles. | Medium | SU002, SU003, SU016, SU017, SU018, SU019 |
| CU030 | Black Lake publicly routes SME procurement through on-site demos, same-industry references, and visits to live factories instead of a self-serve online trial. | Medium | SU004, SU005 |
| CU031 | Black Lake public pricing put Mini Worksheet professional at RMB 10,800 per year and flagship at RMB 18,800 per year in April 2026. | Medium | SU004 |
| CU032 | Black Lake public materials describe Mini Worksheet as serving 20-150 person factories and more than fifty manufacturing subsectors. | Medium | SU004, SU005 |
| CU033 | No reviewed public customer material disclosed net revenue retention, gross retention, logo churn, or renewal rate by segment. | Medium | SU001, SU004, SU005, SU018, SU021 |
| CU034 | No reviewed public customer material disclosed average contract length, average contract value, or top-customer revenue share. | Medium | SU004, SU005, SU018, SU021, SU022 |
| CU035 | The named public proof set skews toward food and beverage, household FMCG, and supply-chain-intensive operators, so vertical concentration cannot be ruled out from public evidence alone. | Medium | SU001, SU006, SU015, SU017, SU018, SU020 |
| CU036 | The customer-size mix in public proof skews even more heavily toward large accounts than the aggregate customer count would suggest. | Medium | SU004, SU005, SU007, SU018 |
| CU037 | Aiqicha hearing-notice disclosures create a procurement diligence item for enterprise buyers even though they do not, by themselves, prove customer churn or deployment failure. | Low | SU025 |
| CU038 | Independent 2026 news coverage repeated near-40,000 customer or factory scale and >60% revenue-growth claims, which supports broad market traction but not retention quality. | Medium | SU021, SU022, SU023, SU026 |
| CU039 | Independent company-profile sources show Mixue and Mengniu are scaled consumer platforms, so winning them implies Black Lake can sell into demanding supply-chain-centric operators. | Medium | SU008, SU009, SU010, SU011 |
| CU040 | Yada and Bright Dairy official profiles describe sizeable plant or production footprints, reinforcing that Black Lake's public named references are not small-shop deployments. | Medium | SU013, SU014, SU016 |
| CU041 | The public expansion pattern most visible in Black Lake customer materials is pilot-to-rollout or single-site-to-multi-site progression rather than disclosed signed-term renewals. | Medium | SU002, SU016, SU017, SU018 |
| CU042 | Food-and-beverage customer stories emphasize planning response, traceability, inventory turns, and cross-factory coordination more than stand-alone automation throughput. | Medium | SU001, SU015, SU018, SU020 |
| CR001 | Aiqicha's public profile for Shanghai Black Lake Technology Co., Ltd. says the company has been involved in 1 court announcement, 15 hearing notices, and 5 litigation relationships. | High | SR001, SR003 |
| CR002 | Aiqicha lists Black Lake as a limited liability company with Hong Kong/Macau/Taiwan investment rather than a public issuer, reinforcing that investors should not expect listed-company disclosure depth. | High | SR001, SR002 |
| CR003 | The operating entity's public registry page shows Zhou Yuxiang as legal representative, chairman, and manager, concentrating formal authority around the founder. | Medium | SR001 |
| CR004 | Black Lake's privacy statement says the public product surface may collect names, email addresses, phone numbers, IP addresses, company information, and bank-card or account information in purchase flows. | Medium | SR005 |
| CR005 | The same privacy statement says user information may be transferred or stored outside the user's home jurisdiction while being processed in China. | Medium | SR005 |
| CR006 | Black Lake's user agreement says customer business data, including data ingested through OPENAPI, may be used for AI model training, algorithm optimization, product upgrades, and industry-trend analysis. | Medium | SR006 |
| CR007 | The user agreement says customers can revoke training authorization and that closing authorization should not impair core software functionality. | Medium | SR006 |
| CR008 | The user agreement says cross-border transfers will follow China's data-export security-assessment and standard-contract requirements. | High | SR006, SR022 |
| CR009 | China's generative AI rules require providers to improve transparency, accuracy, and reliability, protect user inputs, and can escalate to penalties or service suspension for non-compliance. | High | SR021, SR006 |
| CR010 | The PRC Personal Information Protection Law applies not only to domestic processing but also to offshore processing aimed at providing products or services to people in China or analyzing their behavior. | Medium | SR023 |
| CR011 | China's standard-contract rules require a personal-information impact assessment and provincial CAC filing within 10 working days after a standard contract takes effect. | Medium | SR022 |
| CR012 | Black Lake's legal declaration says the website materials are for reference only and disclaims guarantees on accuracy, validity, timeliness, and completeness. | Medium | SR007 |
| CR013 | The legal declaration caps website-related liability at RMB1,000 and routes disputes to the court with jurisdiction over Black Lake's domicile. | Medium | SR007 |
| CR014 | The user agreement says service disruptions can occur during data-center rectification, expansion, migration, updates, or because of unstable networks or bandwidth constraints. | Medium | SR006 |
| CR015 | Black Lake's English site publicly claims 4-6 week implementation for Intelligent Manufacturing and 2 days to get started. | Medium | SR008 |
| CR016 | The Small Work Order site says many factories can be trained in 1-2 hours, which supports rapid adoption but also signals that churn-sensitive SME users are a core audience. | Medium | SR004, SR018 |
| CR017 | Black Lake's English and Chinese official materials say the platform integrates supply chain, production, logistics, sales, ERP, OA, and other factory systems through standard openAPI interfaces. | Medium | SR008, SR028 |
| CR018 | The public open-platform documentation tells users to start from api-index.json and then open per-interface Markdown files, showing that implementation depends on a structured but company-curated API-documentation scheme. | Medium | SR009 |
| CR019 | The public Java SDK README points developers to a single Black Lake open-platform site for detailed documentation, indicating platform dependency on one documentation gateway. | Medium | SR011 |
| CR020 | Black Lake's public materials say the product is deployed on mainstream cloud platforms with security protection, disaster recovery, and elastic scaling, which implies cloud-provider dependency rather than self-owned infrastructure independence. | Medium | SR008, SR027 |
| CR021 | The Small Work Order public site displays MLPS level 3 and ISO27001 as trust signals. | Medium | SR004 |
| CR022 | The same Small Work Order site says 30,000+ growth-oriented factories choose the product, tying Black Lake materially to the health of smaller manufacturers. | Medium | SR004 |
| CR023 | China's official May 2026 PMI release shows headline manufacturing PMI at 50.0, with new orders at 49.9 and SME PMI readings at 48.6 and 48.5 for medium and small manufacturers. | High | SR018, SR019 |
| CR024 | Reuters' May 2026 PMI coverage says manufacturers remained under pressure from weak domestic demand and higher production costs. | Medium | SR019, SR020 |
| CR025 | Black Lake's public customer-count and market-share metrics drift materially across sources: over 2,000 manufacturers on the English site, 30,000+ factories on Small Work Order, 34,000+ enterprises in China Daily, and nearly 40,000 factories in funding coverage. | Medium | SR004, SR008, SR013, SR016 |
| CR026 | China Daily presents Zhou Yuxiang as founder and CEO speaking at government economic symposiums, making him the company's primary public policy and strategy voice. | Medium | SR013 |
| CR027 | Jiemian frames Black Lake's industrial-AI strategy, pricing logic, and market thesis almost entirely through founder commentary, reinforcing founder-centric external communication. | Medium | SR014 |
| CR028 | Jiemian says China's factory floor still suffers from scarce experienced masters and weak mid-level capability handoffs, which is exactly the labor bottleneck Black Lake's AI agents claim to solve. | Medium | SR014 |
| CR029 | Jiemian says Black Lake believes software alone does not solve factory decision bottlenecks, which makes the commercial thesis more dependent on AI decision quality than on workflow digitization alone. | Medium | SR014 |
| CR030 | Funding coverage from Tencent News and Forbes says the split-order agent cuts a 2-3 hour task to minutes with accuracy above 95%, while the quote agent reduces cycle time from six hours to seconds with quoted error within ±5%. | High | SR015, SR016 |
| CR031 | Those AI-performance metrics are appearing in financing and founder-story coverage rather than in an independent third-party audit, benchmark, or regulator-reviewed quality report. | Medium | SR015, SR016, SR018 |
| CR032 | The NBD interview says Black Lake believes 90% of Chinese factories may skip deep industrial-software adoption and jump directly to industrial agents, which is a large but execution-heavy market bet. | Medium | SR029 |
| CR033 | The same NBD interview says Black Lake will keep investing in flexible manufacturing upgrades because many factories care more about fast switching and high-margin small-batch orders than about classic standardization. | Medium | SR029 |
| CR034 | Sina's overseas-expansion profile says Black Lake has followed customers into Vietnam, Malaysia, Mexico, and Eastern Europe. | Medium | SR017 |
| CR035 | The Sina profile says overseas rollout requires remapping processes and material codes locally while headquarters keeps global order visibility through cloud dashboards. | Medium | SR017 |
| CR036 | The same profile says the Mexico project depended on local visa coordination, export-process guidance, and access to legal, accounting, IP, and consulting support, showing that expansion relies on external institutional partners. | Medium | SR017 |
| CR037 | Black Lake's public technical and marketing surfaces emphasize certifications, cloud security, and data-protection language more than they provide a public uptime history, incident log, or external assurance report. | Medium | SR004, SR005, SR006, SR008 |
| CR038 | The public Java SDK, GitHub organization, and documentation hub indicate the company has a real external integration surface, but the public materials do not independently validate change-management discipline, versioning quality, or support responsiveness. | Medium | SR009, SR010, SR011 |
| CR039 | Because implementation, data quality, and AI decisions are tightly coupled, the most likely public downside path is delayed go-lives, lower realized ROI, and slower expansion before a classic outage ever becomes visible. | Medium | SR006, SR008, SR014 |
| CR040 | The combination of 30,000+ SME-facing product exposure and sub-50 official SME PMI makes slower logo growth, weaker seat expansion, and higher churn a plausible downside channel even if large-enterprise demand stays healthier. | Medium | SR004, SR018, SR019 |
| CR041 | Because Zhou holds concentrated formal authority and remains the central public strategist, founder unavailability would affect fundraising narrative, product direction, and enterprise-selling credibility simultaneously. | Medium | SR001, SR013, SR014 |
| CR042 | Because product value depends on cross-system data flows, a failed ERP, device, or API integration can degrade customer outcomes even when the core SaaS application itself remains online. | Medium | SR008, SR009, SR012, SR028 |
| CR043 | Black Lake's expansion into overseas plants compounds both AI-governance risk and cross-border data-transfer risk because the product is meant to sit inside production, quality, and planning workflows rather than outside them. | Medium | SR006, SR017, SR021, SR022, SR023 |
| CR044 | Public evidence for growth, profitability, valuation, renewal quality, and customer concentration in this run is still media-reported or company-reported rather than filing-audited, so private-company disclosure risk remains a core underwriting issue. | Medium | SR002, SR016, SR024, SR026 |
| CV001 | Black Lake announced a near-RMB1 billion Series D on 2026-04-23. | Medium | SV003, SV004, SV005, SV010 |
| CV002 | Tencent coverage said the post-money valuation exceeded RMB7 billion, while Crunchbase translated the round to about $146 million at a $1.3 billion valuation. | Medium | SV003, SV014 |
| CV003 | Caixin named five Series D investors: Guoxiang Capital, Shanghai Guotou Pioneer Fund, Zhiying Investment, the National AI Industry Investment Fund, and Huaxia Zhiqing Venture Capital. | Medium | SV004 |
| CV004 | Caixin said the Series D was Black Lake's sixth financing event and larger than all prior financing combined. | Medium | SV004 |
| CV005 | April 2026 financing coverage consistently said the new capital will fund industrial-AI rollout and global expansion. | Medium | SV004, SV005, SV010, SV011 |
| CV006 | Multiple April 2026 outlets said Black Lake had become profitable and was growing revenue more than 60% year over year, but none disclosed audited revenue or margin bases. | Medium | SV004, SV005, SV006, SV010, SV011 |
| CV007 | Several 2026 outlets said Black Lake serves nearly 40,000 factories or industrial customers across more than 30 manufacturing subsectors. | Medium | SV003, SV005, SV006, SV009, SV010 |
| CV008 | Secondary 2026 sources repeated an IDC-based claim that Black Lake holds 52.7% share of China's cloud production-management or SaaS MES niche. | Medium | SV003, SV010, SV011, SV012, SV015 |
| CV009 | Official Black Lake materials show a tiered product stack spanning Small Work Order, Intelligent Manufacturing, and supply-chain collaboration rather than a single narrow MES SKU. | Medium | SV002, SV027, SV028, SV029 |
| CV010 | IT之家 ranked Black Lake third overall in a 2026 MES comparison behind Dingjie and Siemens, indicating real market presence but not category-wide dominance. | Medium | SV013 |
| CV011 | The same IT之家 comparison said Black Lake is best suited to faster SMB cloud deployments and warned about weaker field service and complex-scenario fit. | Medium | SV013 |
| CV012 | 2026 narrative coverage framed industrial AI as the next growth wedge for Black Lake, not just a continuation of base MES subscriptions. | Medium | SV007, SV008 |
| CV013 | IT之家 reported that Black Lake had built six categories of 11 industrial AI agents that had executed more than 160 million tasks. | Medium | SV007 |
| CV014 | Tencent global-expansion coverage and Baidu's English profile point to operations in 12 countries. | Medium | SV008, SV017 |
| CV015 | Baidu's English profile cited more than 32,000 factories in 12 countries, which conflicts with the near-40,000 figure repeated in April 2026 financing coverage. | Low | SV017, SV010 |
| CV016 | Xinhua-backed financing coverage listed angel, A, A+, B, and C rounds before the 2026 Series D, but still left post-Series-D ownership and dilution terms undisclosed. | Medium | SV010, SV011 |
| CV017 | Crunchbase News treated Black Lake as an April 2026 new unicorn, which corroborates the new-round valuation crossing the $1 billion threshold. | Medium | SV014 |
| CV018 | PTC's June 2026 market capitalization was $13.26 billion. | Medium | SV019 |
| CV019 | PTC reported Q2'26 ARR of $2.36 billion, Q2 revenue of $774 million, and non-GAAP operating margin of 53%. | Medium | SV018 |
| CV020 | PTC's public market cap equated to about 5.6x ARR and roughly 4.3x annualized quarterly revenue in June 2026. | Medium | SV018, SV019 |
| CV021 | Autodesk's June 2026 market capitalization was $41.93 billion. | Medium | SV021 |
| CV022 | Autodesk reported April 2026 quarterly revenue of $1.93 billion, 97% recurring revenue mix, and $7.81 billion of remaining performance obligations. | Medium | SV020 |
| CV023 | Autodesk's public market cap implied roughly 5.4x annualized quarterly revenue in June 2026. | Medium | SV020, SV021 |
| CV024 | Procore's June 2026 market capitalization was $6.39 billion. | Medium | SV023 |
| CV025 | Procore reported Q1 2026 revenue of $359.3 million, total RPO of $1.56 billion, and cRPO growth of 21% year over year. | Medium | SV022 |
| CV026 | Procore's public market cap implied roughly 4.4x annualized quarterly revenue in June 2026. | Medium | SV022, SV023 |
| CV027 | All three public software comparables show 2026 valuation compression versus 2025 market-cap history: PTC about -37%, Autodesk about -35%, and Procore about -45%. | Medium | SV019, SV021, SV023 |
| CV028 | Rockwell agreed to acquire Plex for $2.22 billion in cash and described Plex as a leading cloud-native smart-manufacturing SaaS platform with 700-plus customers and double-digit revenue growth. | Medium | SV024 |
| CV029 | Tulip raised $120 million at a $1.3 billion valuation and supported more than 1,000 sites in 45 countries in 2025. | Medium | SV025 |
| CV030 | Augury raised $180 million at a post-money valuation above $1 billion and had raised $286 million in total. | Medium | SV026 |
| CV031 | Black Lake's reported >RMB7 billion valuation sits inside the same broad private industrial-software unicorn band as Tulip and Augury rather than outside it. | Medium | SV003, SV025, SV026 |
| CV032 | The core valuation problem is not whether Black Lake can tell a compelling growth story, but whether public evidence reveals enough revenue-quality detail to justify paying a premium to public comps. | Medium | SV004, SV006, SV018, SV020, SV022 |
| CV033 | At a RMB7.0 billion post-money valuation, every RMB100 million of current revenue equals roughly 70x revenue. | Medium | SV003 |
| CV034 | If current revenue were roughly RMB250 million, RMB400 million, or RMB600 million, the implied valuation multiples would be about 28x, 17.5x, and 11.7x revenue respectively. | Medium | SV003 |
| CV035 | Those implied multiples would look stretched relative to June 2026 public comps unless Black Lake can prove much stronger growth durability, margin expansion, or scarcity value than the listed benchmarks. | Medium | SV018, SV019, SV020, SV021, SV022, SV023 |
| CV036 | Public evidence therefore supports a research-more posture at the current private mark rather than a clean buy recommendation. | Medium | SV003, SV004, SV020, SV022 |
| CV037 | The positive thesis is that Black Lake combines niche cloud-MES leadership, a large installed base, profitability claims, and AI workflow adoption into a platform that could still compound. | Medium | SV003, SV006, SV007, SV010 |
| CV038 | The anti-thesis is that customer-count definitions drift, market-share evidence is secondary and partly self-amplified, and key financial quality metrics remain private. | Medium | SV012, SV013, SV015, SV017 |
| CV039 | Downside risk is amplified because 2026 public software multiples are below 2025 levels, so a weaker funding window or slower growth could force a flat or down round. | Medium | SV019, SV021, SV023 |
| CV040 | No public IPO filing, audited financial pack, or disclosed cap-table terms make exit readiness and dilution overhang impossible to judge from the open web. | Low | SV010, SV014 |
| CV041 | Public sources show global-expansion ambition, but they do not reveal geography mix, sales efficiency, or whether AI modules monetize above the base software stack. | Low | SV008, SV016, SV025 |
| CV042 | A disciplined valuation case still requires a management KPI pack covering current ARR or revenue, gross margin, NRR or logo retention, AI attach rate, and post-Series-D cap table. | Medium | SV004, SV010, SV018 |
| CV043 | The best evidence-based upgrade trigger is not more storytelling but disclosure that moves Black Lake closer to the transparency standard of public software peers. | Medium | SV018, SV020, SV022 |
| CV044 | The best evidence-based kill trigger is confirmation that Black Lake's current revenue base or retention quality cannot support even the lower end of public-comp valuation bands. | Medium | SV018, SV019, SV020, SV021, SV022, SV023 |