![]()
Greg manages fourteen rental units scattered across three buildings, mostly by himself, and for years the maintenance request process ran entirely through a phone number tenants were supposed to remember to call. What actually happened was messier: some tenants texted, some called and left voicemails he didn’t check until evening, one emailed an address he’d stopped using two landlords ago, and at least one leaky faucet went unreported for a month because the tenant simply didn’t know who to contact after a change in property management. The information was never really missing. It was scattered across four different channels, none of which tenants reliably used the same way twice.
Why a Sticker by the Fridge Beats a Welcome Packet
Every new tenant gets a welcome packet at move-in with Greg’s contact information printed clearly on page one, and every welcome packet ends up in a drawer within a week, unread again until something breaks eighteen months later and nobody remembers where it went. The information being correct on paper somewhere in the unit turns out to matter far less than the information being visible at the exact moment a tenant notices a problem, standing in the kitchen looking at a dripping pipe, not digging through a filing drawer for a folder from move-in day.
The fix Greg landed on was almost embarrassingly simple once he thought of it: a small laminated card taped inside a kitchen cabinet door, at eye level, right where a tenant naturally looks when something under the sink starts acting up. The location mattered as much as the content. A card in a drawer gets forgotten the same way a welcome packet does. A card taped where a leaking pipe or a jammed disposal is physically visible gets noticed at exactly the moment it becomes useful, which is the only moment that actually matters.
Turning a Notice into an Actual Workflow
A phone number on a sticker solves the visibility problem but not the channel problem, since a tenant seeing the number still has to decide whether to call, text, or email, and Greg still ends up managing four inconsistent inboxes. What he actually wanted was every tenant funneled into one specific request form, with a photo upload and a unit number attached automatically, so he wasn’t playing detective about which building a “the heat isn’t working” text came from at eleven at night.
Instead of a phone number, the card now carries a scannable code linking straight to a maintenance request form pre-filled with that unit’s address. A tenant with a broken disposal photographs it, scans the code taped inside the cabinet, and submits a structured request in under a minute, no phone call, no guessing which building they’re in, no message getting lost between three different channels Greg used to have to check separately throughout the day.
Setting It Up Across Multiple Units Without Repeating Work Fourteen Times
Setting this up for fourteen separate units could easily have meant building fourteen separate forms, which is exactly the kind of repetitive setup that makes landlords give up on a good idea halfway through. Greg needed each unit’s code to route to the same request form but auto-populate a different unit number, without hand-building a unique page for every single door. That requirement is precisely what led him to a resource built specifically around this use case, the kind of guidance found at busalab.com/dynamic-qr-code/qr-codes-for-real-estate, which walked through generating a batch of codes tied to individual unit identifiers from one template rather than building each one from scratch.
Once the template was set up, adding a fifteenth unit when he acquired another building later that year took about ten minutes rather than an afternoon. That scalability turned out to matter more than he expected going in, since his portfolio grew by four units within the following year, and redoing this process from scratch for each new acquisition would have quietly eaten a full day of admin work he didn’t have to spare.
What Actually Changed for a One-Person Landlord
The measurable difference wasn’t dramatic on any single day, but it added up over months. Requests arrived with photos attached from the start instead of a follow-up text asking “can you send a picture,” unit numbers were never ambiguous, and Greg stopped checking four different channels throughout the day for something that might or might not be urgent. The tenants noticed too, several mentioning unprompted that reporting a problem felt less like a favor they were asking for and more like a normal part of living there.
Greg still manages all fourteen units by himself, and nothing about the underlying work changed, faucets still leak, heaters still fail in February. What changed was the friction between a tenant noticing a problem and Greg actually receiving a usable, complete report of it, which turned out to be the difference between problems getting fixed in days rather than sitting unreported for weeks at a time.
