Approvals that outlive the phone call

Spending decisions lived in phone calls and memory. Now anything above an owner’s limit stops and waits, and the decision survives.

Written for illustration. This is a picture of how Heyno would fit a property management company. It is not an account of a current customer, and nobody quoted here is a real person.

“Every job spent an owner’s money, and the only record of who allowed it was me.”

Portfolio manager, property management company, illustrative

Every repair is a spending decision

A leak is never just a leak. Fixing it means sending a trade, and sending a trade means spending an owner’s money, and every owner has a different idea of how much of their money may be spent without asking. One is relaxed up to a point. Another wants a call about anything beyond a lightbulb.

Those limits live nowhere. They were agreed on a phone call when the property was signed, adjusted in passing at an inspection, and remembered, more or less, by the manager. A portfolio of two hundred units means two hundred versions of how much is fine.

The approvals themselves are just as fragile. An owner says yes in a hallway or between meetings, the work goes ahead, and the yes evaporates. When the invoice lands three months later, the only evidence of the decision is two people’s memory of a call.

A repair, a quote, a spending decision
Limits that lived in memory
A limit set for every owner
Above the limit, everything waits

Two ways to get it wrong

Commit an owner’s money without asking and the invoice becomes a surprise, and surprised owners are the ones who start taking calls from other agencies. Ask about everything and the owner drowns in questions about faucets while the tenant waits, which is its own way of losing them.

The manager walks that line from memory, dozens of times a week, and mostly gets it right. Mostly is the problem. It takes one spend the owner never agreed to, or one emergency stalled waiting for a yes nobody could reach, for the relationship to change.

And when it does go wrong, the argument is always the same argument: who approved this, and when. A verbal yes cannot be produced afterwards. Whoever kept better notes wins, and usually nobody kept notes at all.

“Above the limit, nothing moves until the owner decides. And the decision is written down where I can find it.”

Portfolio manager, property management company, illustrative

A limit for every owner, a trail for every yes

Approvals holds a spending limit for each owner, written down once and applied every time. Work below the limit proceeds the way the owner already agreed it should. Anything above it stops and waits for a decision from the person whose money it is, before a trade is committed.

The waiting is the feature. The request reaches the owner with the quote and the reason attached, the owner answers when they answer, and nothing is spent on their behalf in the meantime. The manager sees everything that is waiting instead of discovering it later in an invoice.

Every request, every decision and every date is kept. The approval trail survives the phone call, the staff change, and the three months it takes for a question to become a dispute. When an owner asks who agreed to a repair, the answer is a record, not a recollection.

A decision requested, not assumed
The owner answers in their own time
The trail, still there months later

What the month looks like now

Routine work proceeds inside limits every owner actually set, anything above a limit waits for a real decision, and the manager stops being the only record of who allowed what. Owners see what was spent at their property and can see that they agreed to it, tenants stop waiting on approvals stalled in somebody’s voicemail, and when the question comes up months later the trail answers it. The manager still decides what to recommend and which trade to send. What changed is that a yes, once given, no longer depends on anyone remembering it.

“When an owner asks who said yes to that, I can show them.”

Portfolio manager, property management company, illustrative

See where it would fit

Try HeynoGet Heyno