Device-as-a-Service contracts are sold on simplicity. One monthly rate per seat. The vendor takes care of procurement, deployment, support, refresh, and end-of-life. Procurement signs the deal because the operational picture is clean. Finance signs the deal because the cash flow is predictable. Sustainability signs the deal because the vendor's slide deck says circular twelve times.
And then, somewhere around year three, someone asks what the residual value assumption was. And nobody knows.
This applies whether the contract covers laptops, desktops, iPhones, monitors, or a mix. The mechanic is the same: a vendor calculating monthly rates against an undisclosed residual value at end-of-term, with the customer carrying the cost and the vendor capturing the upside. Apple Business Manager-led iPhone leases, Cisco refresh programmes, HPE GreenLake racks, fleet laptop DaaS — different shapes, same financial geometry.
This is not a small detail. In every DaaS, Hardware-as-a-Service, GreenLake-style, TruScale-style, or APEX-style contract I have reviewed, the monthly rate is calculated from three inputs: hardware cost, service cost, and an assumed residual value at end-of-term. That residual value is almost never disclosed. It is almost never auditable. And it is almost always set by the vendor in a way that quietly captures the upside of the secondary market for themselves.
End-of-life — what most of the industry calls ITAD — is not a small operational footnote in these contracts. It is the financial mechanic that determines whether the customer is getting a fair deal or quietly subsidising the vendor's resale business. Here is what to look for before signing.
/01The residual value assumption is a number, and you should know it
Lease-based DaaS pricing works like car leasing. The monthly payment reflects depreciation between purchase price and assumed residual at term-end, plus interest, plus service overlay. If the vendor assumes a low residual, your monthly rate goes up. If the vendor assumes a high residual but then under-recognises the actual resale value at end-of-term, the vendor captures the difference.
In a transparent leasing model, the residual value assumption is disclosed in the contract. The customer sees the number, can challenge it, and can model how the monthly rate would change if the residual were assumed at 18% instead of 12%.
In most DaaS contracts, the number is not in the document.
"We use industry-standard residual value assumptions" is not a disclosure. It is a redirect.
Ask the question. Ask in writing. Get the assumed residual value at end-of-term, by device category, in the contract. If the vendor will not disclose it, that is the answer. They are not selling you a transparent financial product — they are selling you a margin structure that depends on the asymmetry of information.
What to clarify
- Residual value assumption disclosed per device category, in writing, as a contract appendix
- A defined methodology for how residual will be recognised at end-of-term — not "vendor's assessment"
- An audit right on actual resale outcomes, exercisable at least once during the contract term
/02"Decommissioning" is not the same as ITAD
Read the end-of-life clauses in a typical DaaS contract and you will find language like "the Supplier shall arrange for the secure decommissioning and environmentally responsible disposal of equipment at end-of-term." This is the sentence procurement teams accept because it sounds responsible. It is also the sentence that does almost nothing.
"Decommissioning and disposal" can technically be satisfied by a vendor who collects the equipment, wipes the drives at an unspecified standard, sells the resaleable units through their own channel at whatever price they choose, and recycles the rest. The customer receives no asset-level report. No erasure certificate per device. No view of what was reused versus shredded. No share of the resale proceeds.
It is compliant with the contract because the contract asked for almost nothing. It is also a quiet transfer of value from the customer to the vendor's secondary-market business.
The fix is to specify the ITAD process inside the lifecycle contract with the same precision you would use in a standalone ITAD agreement. The standard is well-established — it just rarely makes it into DaaS contracts because nobody on the customer side is reviewing the back end.
What to clarify
- Certified data sanitisation explicitly named — NIST 800-88 Rev. 1, or equivalent — not "industry standard"
- Per-device erasure certificates as a standard contractual deliverable, not on request
- Serialised asset-level reporting at return: what was reused, what was harvested, what was recycled, with the resale outcome where applicable
- A reuse-before-recycle commitment, with the recycling fallback only for devices that fail functional grading
- Named downstream vendor certifications — R2v3, ISO 14001, e-Stewards — and the right to be notified if those certifications lapse
/03The gap between expected value and real cost is where decisions go wrong
Here is the question that quietly determines whether a lifecycle contract is commercially understood: what should this specific asset pool realistically return after collection, erasure, processing, reporting, resale, redeployment, and recycling costs?
In a transparent contract, there is at least a clear explanation of how the financial outcome is calculated. What was collected, what was reusable, what was recycled, what costs were deducted, and what net value remained. Without that bridge, the customer cannot tell whether a low return is caused by weak market value, high logistics cost, poor grading, missing data, or commercial margin hidden in the process.
In an opaque contract, the answer is usually unclear. That uncertainty is the issue: it prevents procurement, IT, finance, and sustainability from knowing whether the lifecycle model is performing as expected.
There is no universal answer because the asset pool matters. Device type, specification, age, geography, collection route, erasure standard, local labour cost, and resale demand all change the outcome. That is the gap I help close: translating the actual estate into a realistic expectation of gross value, associated costs, and net return.
What to clarify
- A defined calculation bridge from gross resale value to net customer return
- Evidence of resale outcomes and cost deductions, so the achieved result is explainable
- An annual statement of resale outcomes per cohort, even if the customer's share is zero — visibility is what disciplines the vendor's number
- A buyout or redeployment option where continued internal use may outperform disposal economics
The point
None of this means DaaS is a bad commercial model. For organisations with the right operational profile, lifecycle contracts genuinely simplify IT management and shift capex to opex in useful ways. The model is not the problem.
The problem is that the standard market template for these contracts treats end-of-life as an afterthought, and that asymmetry consistently moves value from customer to vendor. The five extra paragraphs that would close the gap — residual assumptions, ITAD scope, erasure standards, serialised reporting, and the bridge from gross value to net return — are not commercially controversial. They are just rarely asked for.
Ask for them. Before you sign.