Chapter 2: Who Owns the Balance Sheet?¶
Scott's Core Question¶
"The key is who has the robot on the balance sheet. In a true HaaS model I believe it is the OEM themselves. If we ask KLC to do this the key will be 'who backstops this?' — i.e., who owns it if the customer doesn't like it or goes belly up."
This is the right question. Everything else — pricing, go-to-market, customer value — flows from the answer.
The Three Balance Sheet Scenarios¶
Scenario 1: OEM Owns the Asset¶
OEM builds robot → OEM deploys at customer site → Customer pays monthly subscription
OEM retains ownership throughout
| Factor | Implication |
|---|---|
| Asset on | OEM's balance sheet |
| Depreciation | OEM depreciates the asset |
| Default risk | OEM recovers the hardware |
| Residual risk | OEM must redeploy or resell |
| Capital required | OEM needs significant working capital or credit facilities |
| Customer accounting | Operating expense (OpEx) — no asset or liability on customer books |
Who backstops it? The OEM. If the customer cancels or defaults, the OEM gets the hardware back and must find another customer or take the loss.
Example from the blog: Rivelin Robotics — 12-month subscription, OEM retains ownership.
The Finance Opportunity
This is where equipment finance companies provide the most value. The OEM rarely wants to tie up $5M+ in deployed assets. A finance partner can purchase the hardware fleet and lease it back to the OEM (sale-leaseback), or fund the HaaS program directly, turning the OEM's balance sheet problem into a structured finance product.
Scenario 2: Customer Owns the Hardware, Subscribes to Software¶
OEM sells robot → Customer buys (CapEx or financed) → Customer subscribes to software/AI
Customer owns the hardware OEM provides ongoing SaaS
| Factor | Implication |
|---|---|
| Asset on | Customer's balance sheet |
| Depreciation | Customer depreciates |
| Default risk | Finance company (if financed) recovers hardware; OEM loses SaaS revenue |
| Residual risk | Traditional equipment residual — the hardware has standalone value |
| Capital required | Customer or their lender funds the hardware |
| Customer accounting | CapEx (hardware) + OpEx (software subscription) |
Who backstops it? The lender backstops the hardware (traditional equipment finance). The OEM absorbs the software churn.
Example from the blog: Vention — hardware purchase + software subscription (MachineAnalytics). Plus One Robotics — CapEx cells + SaaS vision/autonomy.
This Is Familiar Territory
This model is essentially equipment finance + software licensing — a structure KLC already understands. The new wrinkle is that the hardware may have limited value without the software subscription, which affects residual risk calculations.
Scenario 3: Finance Company Owns the Asset (Managed Service)¶
OEM builds → Finance company buys → Customer uses via managed service agreement
Finance co. owns asset OEM operates/maintains under contract
| Factor | Implication |
|---|---|
| Asset on | Finance company's balance sheet |
| Depreciation | Finance company depreciates |
| Default risk | Finance company recovers; OEM may lose service contract |
| Residual risk | Finance company — must remarket or redeploy |
| Capital required | Finance company funds the fleet |
| Customer accounting | Pure OpEx |
Who backstops it? The finance company owns the asset and takes the residual risk. The OEM is a service provider, not an asset owner.
This is the most capital-intensive model for the finance partner but offers the highest margin if utilization stays strong.
The Rental Model Comparison¶
As Scott noted: "The rental model is more familiar in this situation."
He's right. Traditional equipment rental (United Rentals, Sunbelt, etc.) is the closest analog to OEM-owned HaaS:
| Factor | Equipment Rental | OEM-Owned HaaS |
|---|---|---|
| Asset ownership | Rental company | OEM |
| Maintenance | Rental company | OEM |
| Technology/software | None (dumb iron) | Included (AI, analytics, updates) |
| Customer commitment | Short-term (days/weeks) | Medium-term (12+ months) |
| Pricing | Daily/weekly rate | Monthly subscription |
| Value proposition | Access to equipment | Access to outcomes/capability |
| Residual management | Rental company remarkets | OEM redeploys or remarkets |
The difference is that HaaS adds a technology layer that creates stickiness and justifies premium pricing. A rental forklift is commodity equipment. A subscription robot with AI-powered vision and analytics is a differentiated platform.
Decision Framework: Which Model to Recommend¶
Does the OEM want to own the asset?
├── YES → OEM-owned HaaS
│ └── Does the OEM have the balance sheet for it?
│ ├── YES → Pure OEM subscription
│ └── NO → OEM needs a finance partner (sale-leaseback, SPV, credit facility)
│
└── NO → Customer buys hardware
└── Does the customer need financing?
├── YES → Traditional equipment finance + software subscription
└── NO → Cash purchase + software subscription
The Backstop Question for KLC¶
If KLC is asked to finance a HaaS program, the diligence checklist:
- Who is the obligor? — Is the customer paying KLC, or is the OEM paying KLC?
- What's the collateral? — Is the robot worth anything without the OEM's software? Can it be redeployed?
- What's the remarketing path? — If default occurs, who buys a used specialized robot?
- What's the OEM's financial health? — If the OEM goes under, does the software still work?
- What are the unit economics? — Does the per-unit subscription cover the cost of capital + risk premium?
- What's the contract term? — Shorter terms = higher re-contracting risk
- Is there usage data? — IoT data can validate utilization and inform residual values