At ISS World Expo 2026, 250+ exhibiting companies competed for operator attention. The AI chat launches got the headlines - Alita, Lumio, and a half-dozen others. A separate piece covers that race. This one is about a different kind of claim, and it’s worth separating the two.
Tenant Inc.’s SuperLease makes a specific and testable argument: moving ID verification and lease compliance steps to after payment - rather than before - produces a measurable improvement in completed online rentals for the same traffic volume. Tenant Inc. states the improvement is greater than 30%. That figure has no independent operator-side verification in the public record. But the methodology question it raises is useful regardless of whether the number holds up.
What Deferred Compliance Actually Means
The standard online leasing flow looks roughly like this: a prospective tenant visits the site, selects a unit, then completes compliance steps - ID verification, lease disclosures, access code delivery - before making payment.
SuperLease reverses the sequence. The prospective tenant visits, selects a unit, and makes payment. Compliance steps - ID verification, lease execution, disclosures - happen after the payment is secured.
The logic is intuitive enough. Every step between “I want this unit” and “take my money” is a potential dropout point. Standard flows put several compliance steps in that gap. Deferred compliance removes them. The tenant pays at peak intent, then completes the paperwork.
The Conversion Claim and What It Actually Tells Us
Tenant Inc. publishes sample math: 400 monthly site visitors at a 6% baseline conversion rate produces roughly 24 rentals. A 30% improvement on that baseline yields approximately seven additional rentals per month. At illustrative lifetime values, that’s meaningful revenue per facility per month.
Those are Tenant Inc.’s published sample figures, clearly labelled as such - not a statistical benchmark.
The question this raises is the interesting one: is the improvement from the compliance sequencing specifically, or from other platform variables? A new leasing interface, better mobile design, faster page loads, clearer pricing display - any of these could contribute to conversion improvements independently of when compliance steps appear in the flow.
Without operator-side A/B test data isolating the compliance sequencing variable from other platform improvements, the claim is plausible but unverified. And that’s an unusual thing for a vendor claim, because it’s independently falsifiable. Any operator with sufficient monthly transaction volume can run the comparison themselves.
Four Questions to Ask Any Online Leasing Vendor
The methodology question applies to every platform, not just SuperLease. Operators evaluating online leasing tools in the post-ISS window are typically comparing feature lists - AI chat capabilities, mobile responsiveness, integration depth. Those matter. But conversion methodology is the structural variable that most determines rental yield per site visitor, and it rarely makes the comparison spreadsheet.
The right questions for any vendor:
- Where do renters drop off? What specific step in your rental flow do you identify as the primary dropout point, and what evidence supports that identification?
- How do you sequence compliance? Does the flow handle ID verification, lease disclosures, and payment as pre-payment steps, post-payment steps, or an integrated sequence? Why that choice?
- Can you isolate the conversion variable? Do you have operator-side A/B test data that separates conversion improvement from compliance sequencing versus other platform improvements? If not, what’s the path to getting it?
- What’s your state-specific compliance coverage? A deferred compliance model requires that payment-first flows comply with each state’s requirements on lease execution before access delivery. Requirements vary by state. Which states does your platform cover?
These aren’t gotcha questions. They’re methodology questions. The vendors who can answer them precisely are the ones whose conversion claims are worth evaluating.
The Payment Architecture Risk Worth Flagging
There’s a practical implication to collecting payment before lease completion that deserves attention.
A rental flow that captures payment before the lease is fully executed needs to structure that payment as an authorization hold, not an immediate capture. If the customer doesn’t complete the lease, an immediate capture creates a charge-back situation - money taken for a rental that was never finalized.
This matters more than it did a month ago. Mastercard’s new Force Post Transaction Fee ($0.09 per transaction, effective 1 April, first billing 26 April) applies to clearing submissions without a prior authorization record. Operators evaluating any deferred compliance platform should confirm specifically: how is the authorization and capture sequence structured, and does it establish prior authorization that avoids Force Post exposure? For context on that fee and two other card network fee changes hitting self-storage operations this April, see our earlier analysis.
Operators on embedded payment platforms like Storable’s may have limited ability to modify the authorization and capture sequence even if they find the deferred compliance methodology compelling. That’s a question for the processor, not a reason to dismiss the methodology - but it belongs in the evaluation. Operators weighing which vendor architecture decisions carry the most risk will recognise this as another instance where integration depth constrains operational flexibility.
The Regulatory Caveat
Some states require lease execution before a tenant receives access to a unit. Deferred compliance models - where compliance happens after payment - need to be assessed against the specific access-delivery timing in each implementation.
This is a category of legal risk requiring verification against an operator’s specific state portfolio. It’s not an argument against the model. Tenant Inc.’s SB 709 compliance integration for California, effective January 2026, demonstrates that deferred compliance can be built to incorporate state-specific requirements. The question is whether the specific implementation an operator adopts covers their states.
The claim is independently falsifiable by any operator with a large enough monthly volume - which is, itself, an unusual thing for a vendor to say. That’s probably the most useful thing to take away from ISS this year.
