Why we built StoreKeep around the lien engine

If you demo enough facility-management software, you notice every product opens the same way: the move-in wizard. It's the easy, photogenic workflow — pick a unit, take a card, print a lease. Ours has one too. But it's not where we started, and the reason says more about StoreKeep than any feature tour.

We started with the delinquent tenant in unit 214.

The legal pad problem

Every management system on the market can tell you who's past due. Then, at exactly the moment the stakes get real, most of them hand you back to a legal pad.

Because what happens next isn't a reminder email. It's a statutory sequence that differs by state: when the late fee can post and what it's capped at, when you may overlock, when the lien notice may be sent and precisely what it must say, which delivery method the statute requires, how many consecutive weeks the auction ad must run and where, and the earliest date you may legally sell a stranger's belongings to recover what they owe you.

Get it right and you recover revenue that was walking out the door. Get one step wrong — a notice worded loosely, a certified letter you can't prove was attempted, an auction a week early — and you're exposed to a wrongful-sale claim that can cost more than the tenant ever owed. Independents run this gauntlet with a legal pad, a calendar, and nerve. The big REITs run it with a legal department.

That asymmetry is the product. So we built the lien engine first:

• A deadline computer. Given the trigger date and your state's interval rules, every downstream earliest-legal date is computed. "What's my earliest legal auction date for 214?" is a query, not a guess.
• Template-locked notices. The statutory text is attorney-reviewed, versioned, and frozen. The AI fills variables and drafts the humane cover language — it is architecturally barred from writing statutory language. We think "the AI wrote my lien notice" is a sentence that should never be true, in ours or anyone's product.
• Evidence by default. Every step writes an append-only record — the frozen document, the certified-mail tracking, the overlock photo, the address as of the mailing date. One click bundles the case file for your attorney.
• Automatic mercy. Pay in full at any point and the workflow cancels itself and restores gate access, transactionally. Firmness and fairness are both just correctness.

The second bet: the remote owner is the real user

The archetypal independent we build for owns a 220-unit facility two states away, runs it from a phone, and pays someone part-time to walk the lot. So StoreKeep is mobile-first in the literal sense: the whole operating loop — approve a rate increase, watch a lien timeline advance, dispatch an overlock with photo-proof required, answer a tenant — is designed to be completable one-handed from elsewhere.

The same logic drove the AI tenant desk. Remote operators don't fear the hard tenant conversations; they fear the two hundred easy ones — gate codes, hours, "what do I owe." The desk answers those from the tenant's actual account state, escalates anything that smells like hardship or dispute, and reports recovered revenue against real payments rather than estimating its own usefulness. When it doesn't know, it hands off. A tool that guesses about someone's balance is worse than no tool.

The third bet: alignment is a feature

We've written elsewhere about the roll-up that owns most of this industry's software, its bundled processing, and the marketplace that sells operators their own tenant demand. Our structural answers are simple and deliberately boring:

• Flat tiers — $99, $179, $349 — by facility size. No per-unit fees, so your bill doesn't climb as you fill units.
• Opt-in processing at disclosed interchange-plus. Turn it off; everything still works.
• No marketplace. Not now, not as a "growth initiative" later. Your demand is not our inventory.
• An importer that commoditizes switching — in both directions. Point it at a SiteLink or storEDGE export and get a verification report, with balance reconciliation, that you sign off on before anything commits. We made leaving-them easy, which obligates us to make staying-with-us worth it.

Where it points

The near-term roadmap is depth on the same bets: more state coverage in the legal library run through the same attorney-review pipeline, more gate vendors behind the same adapter, sharper anomaly summaries from the gate logs, and a weekly owner briefing that keeps earning its place in your inbox.

What won't change is the order of priorities that unit 214 set for us on day one: correctness where the legal risk lives, leverage for the operator who isn't on site, and a vendor structure you don't have to squint at. If that matches how you run your facility, the demo is two clicks — the delinquent units in it are already mid-sequence, so you can watch the legal pad workflow execute itself properly.