For a humanoid- and service-robotics company, the most consequential pages of a Form 10-K are not the product photos in the business section but the revenue-recognition policy in the notes. The product description tells you what the company builds; the accounting policy tells you how, and when, building it turns into reported revenue. That distinction matters acutely in robotics because the industry has been migrating from selling a robot as a one-time hardware transaction toward leasing capability under a Robots-as-a-Service (RaaS) model, and the two are recognized very differently on the income statement.

Richtech Robotics Inc. (RR) lays out both halves clearly. On products, the company describes a portfolio organized into strategic pillars and introduces, among them, a humanoid robot built for light industrial use. The business section names the hardware lines, delivery robots, autonomous mobile robots (AMRs), cleaning robots, and the newly introduced humanoid, grounding the strategy in specific products rather than abstractions. That product-level disclosure is what lets a reader tie the company's autonomy ambitions to actual machines, and it is the kind of concrete description Regulation S-K's business-narrative requirements are meant to elicit.

Dex humanoid robot designed for light industrial applications. Products in the Industrial category are purpose-built for production and manufacturing environments, with an emphasis on durability, reliability, and heavy-duty operation.— Richtech Robotics Inc. (RR), Form 10-K, source

Why RaaS revenue is recognized over time

The accounting half is where the business model shows. Richtech discloses that it generates revenue through Robots-as-a-Service (RaaS) offerings that provide customers ongoing access to its robotic solutions under long-term contracts, and that revenue from those arrangements is recognized over time, on a monthly basis, as the customer simultaneously receives and consumes the benefits of the company's continuous provision of robotic functionality, maintenance, and technical support. Under the applicable revenue-recognition standard, a performance obligation is satisfied over time, rather than at a point in time, when the customer receives and consumes the benefit as the company performs, which is exactly the condition a continuous-service robotics subscription meets. The company applies a straight-line method over the service period.

That choice reshapes how the financials read. In a one-time hardware sale, revenue is recognized at a point in time, at delivery, producing a lumpy top line tied to shipment timing. Under RaaS recognized over time, the same deployment produces a smoother, recurring revenue stream spread across the contract term, with the trade-off that a new deployment contributes less revenue in its first period than an outright sale would. For an analyst, the recognition policy is therefore essential context: a RaaS-heavy robotics company will show lower upfront revenue per unit but a building base of recurring revenue, and comparing it to a hardware-sale peer without adjusting for that difference would misread both. The policy also implies a backlog of contracted, not-yet-recognized revenue that the disclosures around remaining performance obligations can illuminate.

The over-time test under the revenue standard turns on a specific question: does the customer simultaneously receive and consume the benefit of the company’s performance as the company performs? For a discrete hardware sale, the answer is no, the benefit transfers at a single moment, delivery, so revenue is recognized at that point in time. For a Robots-as-a-Service arrangement bundling a robot with continuous functionality, maintenance, and support under a long-term contract, the answer is yes, because the customer consumes the service continuously, and that condition routes the revenue to over-time recognition. Richtech’s disclosure that revenue is recognized monthly as the customer benefits from the ongoing provision of robotic functionality is the textual marker of that conclusion, and the straight-line method is the mechanic that spreads the contract’s transaction price across the service term. The same arrangement also tends to push hardware cost ahead of revenue, since the company often builds and retains ownership of units it leases rather than sells, which is why the capital intensity of a RaaS model belongs in the same reading as its revenue policy.

What to read in a robotics 10-K

Three sections carry the weight. First, the business narrative, for the product lines, including whether a humanoid is a shipped product, a pilot, or a roadmap item. Second, the revenue-recognition policy in the significant-accounting-policies note, which tells you whether revenue is point-in-time (hardware sale) or over-time (RaaS), and therefore how to interpret the revenue trajectory. Third, the risk factors and liquidity discussion, where a hardware-and-service robotics company discloses the capital intensity of building units it leases rather than sells, an upfront cost that a RaaS model pushes ahead of the revenue it generates. Reading those together lets the autonomy story reconcile to filed numbers: what the company makes, how it earns from it, and what that timing does to the income statement.

Comparability is the practical payoff of getting this right. Two robotics companies with similar deployments can show very different revenue if one sells hardware and the other leases it as a service, and the difference is an accounting-model difference, not a demand difference. Reading the recognition policy first, then the revenue trend, keeps an analyst from mistaking the smoother, slower-building curve of a Robots-as-a-Service model for weaker traction, or the lumpier curve of hardware sales for stronger momentum.

The durable point is that a humanoid-robotics 10-K is two documents in one, a product catalog and an accounting policy, and the second governs how the first appears financially. When revenue is recognized over time under a Robots-as-a-Service model, the company is telling you its economics are recurring-service economics, not hardware-sale economics, and that single policy choice frames everything about how its growth will print.