What an underwriter looks for in a deployed fleet

Before a financing partner looks seriously at a deployed robot fleet, it is running through the same handful of questions. None of them are secret, and a manufacturer can answer most on its own before ever picking up the phone. What follows is that list, in roughly the order it comes up, along with why each one matters to an underwriter and not just what it is.

Installed and formally accepted

The equipment needs to be installed, commissioned and formally accepted by the customer. Acceptance is the specific event, usually defined in the contract, where the customer confirms the equipment works as promised and the payment obligation becomes unconditional.

This matters because everything before acceptance is still the manufacturer's risk to carry. Manufacturing delays, shipping damage, integration problems, a customer who changes its mind mid-installation: all of that sits with the manufacturer, not with a financing partner, until acceptance happens. Financing a deployment before acceptance means financing the manufacturer's execution risk rather than the customer's payment obligation, which is a different and much harder thing to underwrite. Acceptance is the event that turns a promise into an obligation.

A fixed minimum payment

There needs to be a fixed minimum amount the customer owes each period, rather than a fee that depends entirely on how much the customer chooses to use the equipment.

The distinction matters because an underwriter is trying to put a value on what a payment stream is worth today. A contractual minimum gives the underwriter something concrete to work from: a known floor of cash flow over a known period. A usage-only structure, where the customer pays per unit of work performed and could in principle owe close to nothing in a slow period, gives the underwriter nothing solid to hold onto. A contract can combine both, a fixed minimum plus a usage-based amount above it, and still be financeable on the fixed portion. What does not work is a fee that is entirely variable, with no floor at all.

A creditworthy enterprise obligor

The obligor, meaning the party legally responsible for making the payments, needs to be a business that would pass an ordinary credit review on its own.

This is worth sitting with, because it tends to read as a hurdle when it is closer to good news. The credit being underwritten is the customer's, not the manufacturer's. A fleet financing does not generally depend on the manufacturer's own balance sheet or borrowing history; it depends on whether the enterprise using the equipment is likely to keep paying for it. A thinly capitalized manufacturer with strong, creditworthy customers is often an easier financing than a well-capitalized one with weak customers.

Standardized, redeployable, serviceable hardware

The equipment should be a standardized model that can be removed, refurbished and placed with a different customer if it ever needs to be.

Underwriting a hardware financing means underwriting what happens if a deployment does not work out, and that depends on what the equipment is worth if it has to be recovered. A standard mobile robot or autonomous forklift that exists in meaningful numbers can be pulled, serviced and redeployed elsewhere. A one-off, bespoke installation built for a single customer's specific facility generally cannot. Recovery value on the second kind of equipment is close to nothing, and that changes what can be financed against it.

Assignable payment rights and clear title

The customer contract needs to permit the payment rights to be assigned to a financing party, and the manufacturer needs to be able to deliver clear title to the equipment or the payment stream being financed.

Many standard subscription contracts are not written with this in mind and quietly bar assignment without the customer's consent, which is worth checking well before a financing conversation starts. Clear title raises a related but separate question: whether an existing lender already has a claim over the hardware. Blanket liens and fleet financing covers that side of the problem in detail.

Separable hardware and service economics

The contract, or at least the underlying pricing model, needs to distinguish what portion of the customer's payment relates to the hardware and what portion relates to software, maintenance and service.

If a contract bundles the robot and the service into one undifferentiated fee with no way to allocate between them, there is no discrete hardware payment stream to buy. It is all one thing, and carving a financeable slice out of it after the fact is difficult. The reason this split works well for manufacturers is that it lets service and software obligations, along with the revenue and the customer relationship that come with them, stay entirely with the manufacturer, while only the hardware payment right moves to the financing party.

Concentration

A single customer accounting for a large share of the pool being financed is a problem, even when that customer's credit is excellent.

The reasoning is about diversification, not doubt in the customer. A financing built around a handful of contracts is exposed to whatever happens to those specific customers: a facility closure, a change in strategy, a dispute unrelated to the equipment itself. A pool spread across many obligors is exposed to the average, which behaves far more predictably than any single relationship does. Concentration does not disqualify a deployment on its own, but it does change how much of a given pool can be financed at once.

What does not fit yet

Some deployments are not financeable today, though that can change as they mature:

• Pilots and demos, where there is no accepted, revenue-generating deployment yet
• Cancel-anytime contracts, where the customer can walk away without a minimum commitment or a make-whole
• Deployments that depend on a revocable permit or a similarly uncertain right to operate
• Systems with no practical recovery route if a deployment does not work out

None of these are permanent disqualifications. They describe a deployment's current state, not the equipment or the customer relationship itself, and each can change as a program matures.

The bottom line

Most of this a manufacturer can work through on its own, well before ever speaking with a financing partner: whether contracts carry a fixed minimum, whether they permit assignment, how concentrated the customer base is. Doing that work early is what makes the first real financing conversation short instead of long.

This note is part of a short series of notes on fleet financing. For what to do if an existing lender already has a claim over the hardware, see Blanket liens and fleet financing. For the broader case for financing hardware payment streams at all rather than carrying them yourself, see Why robotics-as-a-service turns manufacturers into lenders. Terms used above are defined in the glossary.

Spotlight underwrites against criteria like these. To see how your own fleet measures up, discuss a financing program.