Your customer chose a subscription so they would not have to buy the machine

When a customer picks a subscription over a purchase, they are making a specific choice: they do not want to tie up their own capital in your hardware. That capital requirement does not disappear because the customer declined it. It moves. Absent a financing partner, it moves onto your balance sheet, and you are now funding the equipment yourself, whether or not that was ever the plan.

The mechanic

Someone has to pay for the robot before the customer has paid enough in monthly fees to cover it. If your company built the machine, shipped it, installed it and is now collecting payments over a period of years, you already know this. The cash to build that unit left your account well before the corresponding revenue arrived, and it keeps happening with every new deployment.

A customer's decision to subscribe rather than buy is, from a balance sheet perspective, a decision to make someone else the lender. If there is no financing partner in the transaction, that someone is you.

This is easy to miss because nothing about it looks like lending from the inside. Sales calls it a deal won. Finance calls it a deployment funded. Nobody signs a document that says the company is now in the lending business. But the economics are the same regardless of what it is called: capital goes out today against a promise to be repaid over time, and the company bears the risk that the promise is kept.

What that makes you

Put plainly: a robotics company that finances its own RaaS deployments is running a small, undiversified, unlevered lending book, without the systems, pricing discipline or funding structure an actual lender would have.

That is not a criticism of the business. It is a description of what has happened to the balance sheet, often without anyone deciding it on purpose. A company built to design, manufacture and sell robots ends up also carrying long-dated receivables against enterprise customers, priced, if priced at all, more like a sales decision than a credit decision, and funded with whatever capital happens to be on hand rather than capital raised for that specific purpose.

The compounding problem

Cash goes out at deployment and comes back slowly, over the life of the contract. Every new fleet adds to the amount of capital tied up before it has been recovered, while the earlier fleets have not finished paying themselves back yet.

Growth then becomes limited by balance sheet capacity rather than by customer demand, which is close to the worst constraint a company with real product-market fit can face. The problem is not that customers do not want the product. It is that saying yes to another deployment means finding more capital before you can say yes.

Left alone, this tends to resolve itself in one of two unattractive ways: growth slows to match what the balance sheet can carry, or the company raises equity specifically to fund hardware it did not need to own in the first place. Neither is a reason to stop offering subscriptions. Customers are asking for them for good reasons. It is a reason to separate the decision to sell a subscription from the decision to fund it.

The capital mismatch

Equity is generally the most expensive capital a company raises, because it is priced for the risk that the entire business succeeds or fails, not for the risk of one specific, contracted payment stream from one specific customer.

Using that capital to fund equipment that is already installed, accepted and generating a fixed payment obligation from a creditworthy enterprise customer is a mismatch. The underlying risk being funded, whether one enterprise customer keeps paying a fixed amount each month, is narrower and more specific than the risk equity investors are actually pricing when they invest in the company as a whole. Funding a narrow, contracted risk with capital priced for a much broader one means the equity is doing more work than the situation calls for.

The honest trade-off

Carrying the payment stream yourself, rather than financing it, does collect more in total. You keep the finance income that would otherwise go to a financing partner. That is real, and worth saying plainly rather than glossing over: financing a deployment means sharing some of that economics with someone else.

What you give up in exchange is time. Carried yourself, that income arrives in installments across the full length of the contract. Financed, the corresponding cash arrives close to when the equipment is accepted. What that earlier cash lets you do is fund the next fleet, hire the next engineer, or simply avoid raising another round of equity to cover a customer commitment you have already won. The trade-off is real, and which side of it makes sense depends on how much you value cash now against cash later.

What good looks like

The alternative to financing each fleet as a one-off is capital that scales with how much you deploy rather than with how often you raise a funding round: a framework agreed once, with eligibility criteria set in advance, so qualifying deployments can be financed as they come in rather than each becoming its own negotiation.

That matters because deployment volume and fundraising timing rarely move together. A program agreed once decouples the two, so the pace of financing can track the pace of what customers are actually signing, rather than lagging behind the next round.

The bottom line

This note is part of a short series of notes on fleet financing. For the specific criteria that make a deployed fleet financeable, see What makes a robot fleet financeable. If an existing lender already has a claim over the hardware you would be financing, Blanket liens and fleet financing covers what that means and how it is usually resolved. Terms used above are defined in the glossary.

Spotlight exists to be that financing partner. To talk through a program built around your own deployment pace, discuss a financing program.