Case studies
Co-living

PadSplit Cuts Utility Late Fee Cost to Zero Across Its Co-Living Portfolio

PadSplit pioneered co-living at scale: single family homes converted into affordable room by room housing, where every listing carries the same promise. Utilities included. That is not a pricing note. It is a commitment to residents. AirBills ran the operations behind it, caught leaks in the bill before they showed up on the floor, and kept the lights on.

Co-living, student housing, and utilities-included models · 6 min read

The stakes in co-living

A missed water bill is not a $205 problem. It is a disconnect notice on a house where eight people live, a same-day crisis for the host, and a trust problem for a marketplace whose entire brand rests on dependable affordable housing. The failure mode is not a late fee. It is residents.

5x
the bill density of a standard single family rental
~35
bills per house per month under management
0%
late fee cost, absorbed by AirBills
<0.05%
of bills resulted in a service disconnect

Why co-living is a different operational problem

A standard single family rental generates a handful of utility bills per month. Electric, maybe gas, maybe trash. A co-living house runs utilities like a small hotel: water for eight or ten people showering and doing laundry, electricity for every bedroom, gas heat, and internet, because for many members the house Wi-Fi is their only connection for work.

~35

utility bills per house per month, roughly five times a standard single family rental

$1,100+

in utility spend per house per month, before any late fees or disconnect costs

This means the operating load does not scale with doors. It scales with bills. And when every one of those bills is a promise already printed on the listing, the bar for bill pay moves from mostly on time to never wrong.

That is the bar AirBills was built for. Seven business days from contracts to live bill pay. Every statement fetched the day it drops. Every consumption curve checked before payment. Every disconnect notice treated the same way: stop everything, fix it today.

Seeing the leak in the bill before you see the water

A vacant co-living property posted an abnormal water reading. AirBills flagged it the day the statement arrived. The operator dispatched a leak detection crew. AirBills contacted the water authority in parallel to request a meter check. The leak was confirmed. It was fixed within days.

What did not happen: four weeks of a running leak until the next billing cycle. A five figure water bill absorbed quietly. Eight residents arriving to a problem that had been building for a month.

On one house, the bill that arrived carried an unpaid prior balance, a late fee on top of it, and a current cycle that was still high. Here is the protocol AirBills ran:

Leak response protocol
1
Flag and hold

Consumption spike detected against the property baseline. Payment held pending investigation. Operator notified same day.

2
Dispatch and verify

Operator sends physical inspection. AirBills requests a meter check from the water authority in parallel to establish whether the reading reflects actual consumption or a provider error.

3
Pay strategically

Once the leak is confirmed real: pay the minimum to stop further accrual and late fee accumulation while the repair is completed. Do not overpay before the credit negotiation.

4
Fight the fees

Call the biller with the plumbing report in hand. Request credit for the overage and waiver of late fees on a leak affected account. Document the outcome.

5
Recover and close

Credits and adjustments tracked bill by bill until the account is clean and the books close correctly. No outstanding charges left open.

An autopay setup would have wired the full balance on the statement date. The leak would have run through another billing cycle. The credits would have gone unclaimed.

Disconnect notices treated like fire alarms

No power. No water. No product.

In co-living, a service disconnection is not a billing incident. It is a resident incident. Every disconnection notice that arrives is escalated and cleared the same day. Not triaged. Not queued. The same day.

When a disconnect notice arrived on a member house, the bill was paid immediately. Service changes in the other direction operated on the same discipline: accounts were only ever closed on the operator's own explicit written request, never unilaterally on AirBills' initiative. Because in co-living, an unrequested disconnection does not affect a credit score or a late fee. It affects people.

Rate negotiation carries the same resident-first rule. No service is ever changed or downgraded without the operator's written approval. Within three months of onboarding, AirBills came back with negotiated savings on internet bills across the portfolio. Same service, lower price. The residents did not notice, because they were not supposed to.

When utilities are the product, the bar is 100%

Standard bill pay services are built around "mostly on time." Co-living needs different standards, and a different kind of contract to back them. Every AirBills engagement includes a performance exhibit with hard KPIs and pre agreed financial credits for any miss.

Late fees
Absorbed by AirBills, not passed to the operator or to residents
Disconnects
Under 0.05% of bills company wide, same day escalation when one occurs
Breach remedy
Published credit table, applied to the invoice without negotiation
Service changes
Only on written operator approval. Never unilateral. Never without notice.

For a model where residents pay for utilities as part of their rent, the vendor's SLA has to match the listing promise. Ask any utility management company what happens financially when they miss. If the answer is a conversation rather than a credit table, the SLA is not real.

The accounting the finance team could actually close on

Monthly bill payment files mapped to the operator's GL codes, per property detail for host billing, and reconciliation thresholds protecting every payment: per bill type minimum and maximum, and spike gates before auto approval. When credits and adjustments flowed, including leak credits and late fee waivers, they were tracked bill by bill until the books closed cleanly.

Finance involvement dropped to roughly 30 minutes of exception review per month. The reconciliation did not get easier because someone got better at it. It got easier because the rules were set once and the engine ran them.

The results

The promise held. Every day.

Zero late fee cost to the operator. Under 0.05% of bills resulting in a service disconnect. No residents coming home to a dark house or a dry tap because a utility bill slipped. That is what utilities included actually requires operationally, and it is what the engagement delivered.

Leaks caught in the bill, not on the floor

Consumption spike detection flagged abnormal usage the day statements dropped. For co-living houses with multiple residents and high baseline consumption, that is the difference between a same-week repair and a five figure bill absorbed quietly. The protocol worked every time it ran.

Finance down to 30 minutes of review per month

From carrying utility reconciliation as a standing workload to exception review only. GL coded, per property entries ready for host billing. Credits and adjustments tracked to closure. The accounting the finance team needed to actually close the month.

Resident-first escalation

Disconnect notices treated like fire alarms. Cleared the same day, every time.

No unilateral changes

Service only changes on written operator approval. Never downgraded without notice.

Financial credits for misses

Published rate table. Applied to the invoice without negotiation when we slip.

If utilities are part of your product, treat them like it.

Co-living, student housing, assisted living, build to rent. Anywhere utilities included sits on the lease, the bar moves from mostly on time to never wrong. AirBills is built for that bar, and the SLA backs it.

Contact us