Nobody Owns Day 5

On the 6th of every month, a big chunk of our units are past due. Not a crisis, just the calendar. Day 5 came and went, and the balance is now delinquent whether the tenant meant to pay or not.

Then something predictable happens. Over the next week, most of those balances clear themselves. Late fees hit, texts go out, and people pay. By month end we're down to a handful of units that need real collections attention, and maybe one or two headed for auction.

That's not because I'm good at collections. The system has a name: nobody owns day 5 in most businesses.

In storage, day 5 is owned. Not by me, not by a manager making a judgment call about whether to call or wait another week. The lien law owns day 5. The sequence has no memory, no discretion, and no mercy for a balance that looks like it might pay itself.

The rest of small business isn't that lucky.

Storage has the best accounts receivable system in small business, and we didn't design it. The lien law designed it.

Part of the appeal of self-storage (the whole pitch when you're evaluating it as a business) is that there are no tenants in the traditional sense. No leases to enforce in housing court. No eviction proceedings, no judges, no six-month ordeal to get someone out of a unit they stopped paying for. The lien law is the collections process. It is self-contained and it costs you nothing but patience and certified mail.

The thing you don't fully clock until you're running the business is that this same feature is quietly the most powerful AR system in small business. Every state has a version of the same sequence: a late fee fires automatically on day X, a lien notice goes out on day Y, and if the balance doesn't clear by day Z, the unit goes to auction. The specific timing varies by state, but the structure is identical everywhere: fixed triggers, fixed actions, no discretion. An operator can't decide to skip the lien notice because the tenant seemed like they were going to pay. The law doesn't care.

That forced sequence is a dunning system most businesses would pay a consultant to build.

Here is what it does: it removes the question. In most businesses, somebody has to decide to follow up on a past-due balance. That decision has friction. The owner doesn't want to make the client uncomfortable. The call gets pushed to tomorrow, then next week, then "let me see if it clears." Day 5 passes. Day 15 passes. Hoping is not a strategy.

In our portfolio right now, 33 of 56 delinquent units are more than 60 days past due. The average age of a past-due balance at Edgefield is 218 days. At University, 153 days. These are not new problems. They are old problems that survived a system designed specifically to prevent them.

Some of those balances aged because we acquired a facility that inherited them. Some aged because a card failed on an autopay-enabled unit and never got updated. All of them passed through a 5-day window, a 15-day window, and a 30-day window without anything automatic happening.

That is what day 5 looks like when it has no owner.

The lien process gets framed as a legal compliance obligation, not a collections mechanism. You run it because you have to, not because you recognized it as the forcing function that keeps receivables from aging into irrelevance. That reframe matters. The operators who treat the lien sequence as a compliance step run it and move on. The operators who treat it as a model build the same discipline into everything else they touch.

The fix for any business isn't a collections person. It isn't a softer payment reminder or a more aggressive one. The fix is what the lien law gave us: a fixed sequence with prescribed actions at fixed intervals that fires whether you remembered or not.

Any business can build this. Call it an artificial lien timeline.

Most Excel users waste hours on tasks that take experts minutes. The difference is not talent. It is knowing the right shortcuts.

These 50 Excel hacks from Kenji Explains cover the functions, formulas, and workflows that make spreadsheets work for you instead of against you.

Each one comes with step-by-step instructions and ready-to-use templates. Subscribe to Marketing Against the Grain and get all 50 free.

Here's what you'll get:

The people who are fast in Excel are not smarter. They just stopped fighting the tool.

Get 50 Excel Hacks free when you subscribe to Marketing Against the Grain today.

Get The Guide

Invoice sent is your move-in. Your terms, net 15 or net 30, are your grace period. The sequence starts the day the invoice goes past due, not the day you send it. Day 1 past due: an automated message goes out, no customization, no "I'll reach out when it feels right." Day 10 past due: a second touchpoint with a clear consequence attached (a late fee, a pause on service, a defined next step). Day 30 past due is escalation: a direct call, a defined decision point. Continue the relationship or write it off. Every stage has a prescribed action, and no one decides whether to skip it.

The reason most businesses don't have this is that discretion feels kinder. Owners don't want to automate the relationship. The problem is that "when the time seems right" is a calendar that fills up with work and empties out of collection calls.

There's a second reason, and it's less flattering. Most businesses can't run this sequence even if they wanted to, because they can't answer the questions it depends on. Which invoices went past due this week? What's the total aged over 30 days? Who got the first touchpoint and who fell through? The data exists. It's just scattered across an invoicing tool, a bank feed, and a spreadsheet somebody updates when they remember. You can't automate a sequence you can't see.

My facilities answer those questions in one report because the management software forces every balance into one ledger. Most businesses have the opposite: three systems, three versions of the truth, and no single view of who owes what as of today.

Autopay is the other half of the equation. Whatever percentage of your revenue is on autopay is the percentage that never becomes AR at all. In our portfolio, University runs at 42% autopay adoption and Edgefield at 53%. Roughly half our revenue never enters the collections conversation.

The best collection call is the one that never happens.

For service businesses, autopay isn't always the right name for it. The structure underneath is what matters: ACH authorization on contract signing, a retainer billed monthly to a card on file, a deposit-on-signing that covers the first invoice. Any mechanism that moves the balance from "you'll pay when you decide to" to "the system takes it before either of us thinks about it."

Collections feels like a people problem because the people are visible. You know the client. You know they're slow. You know they'll pay eventually. What you cannot see is the aggregate cost of every balance that aged one more billing cycle because you decided to wait. And if your data is spread across three tools, you can't see it even when you go looking.

Build the timeline. Fix the triggers. Remove the decision.

The problem was never the tenant. It was the system that forgot to ask.

If your AR is aging, the problem is not the client. Nothing fired on day 5.

Here is the build: a Google Sheet that ages every invoice and assigns it a stage automatically, plus a Make.com scenario that sends you one digest every morning listing exactly who crossed a threshold and what the prescribed action is. Not fourteen separate pings. One message, every morning, with your collection calls already decided.

Set up the sheet first. Columns A through I: Client, Invoice Number, Invoice Date, Amount, Due Date, Amount Paid, Balance, Days Past Due, Stage. The last three do the work.

Balance: =D2-F2

Days Past Due: =IF(G2<=0,0,MAX(0,TODAY()-E2))

Stage: =IFS(G2<=0,"PAID",H2=0,"CURRENT",H2<=9,"FIRST NOTICE",H2<=29,"FOLLOW UP",TRUE,"ESCALATE")

The stage column is your lien law. An invoice at 6 days past due is FIRST NOTICE whether or not the client is a nice person. Recording a partial payment in Amount Paid recalculates everything downstream, so a client who paid half doesn't sit in ESCALATE by mistake.

Add three cells at the top of the sheet: =SUMIFS(G:G,I:I,"FIRST NOTICE"), same for FOLLOW UP, same for ESCALATE. That's your aging summary. Most businesses pay their bookkeeper to produce this quarterly. Yours updates every time you open the sheet.

Then the automation. Paste this into ChatGPT or Claude:

The templates matter as much as the alert. The digest tells you who to contact. The templates remove the "what do I even say" friction that turns a two-minute task into a skipped one. Save all three in your email drafts and the entire morning routine becomes copy, paste, send.

Run it as alerts-to-yourself for the first month. Once you trust the stages, you can have Make.com send the FIRST NOTICE email directly to the client and reserve your personal attention for FOLLOW UP and ESCALATE. That's the same progression storage software uses: the early touchpoints are automated because they don't need judgment, and you enter the sequence only where judgment pays.

Make.com's free tier covers this entirely. For non-storage readers: invoice sent equals move-in, due date equals rent date, and every trigger maps the same way.

The lien law handles collections. You didn't build that system. You just inherited it.

What else in your business has no day 5? The thing that ages quietly because nobody owns the follow-up, nobody owns the escalation, and you find out months later when the number finally looks wrong.

Hit reply and tell me what it is.

While we wait for life, life passes.

— Seneca, Epistulae Morales I.1