The platform holds the money, not the work

1. The split nobody designed

Start with the concession, because it matters. Your property management platform is good at the thing it was built for. It holds the lease, the ledger, the receipting and the trust account, and it holds them under rules that exist for a reason. Nothing in this paper suggests replacing it. You should not, and in the case of trust accounting you must not.

Now look at what actually goes wrong in a rent roll. It is almost never the ledger. It is a maintenance job the owner never approved, a routine inspection that slipped a month, an arrears follow-up that nobody made on the day it mattered, a smoke alarm service booked and never confirmed, a lease expiring in six weeks that nobody has started. Every one of those is an open loop, and not one of them is a number in the ledger.

So the office fills the gap the only way it can. The inbox becomes the record of what was agreed. An app holds the inspection photos. A spreadsheet holds the compliance dates. A second spreadsheet holds the arrears the platform reports differently to how you work them. And the property manager holds the rest, which is the real problem, because a portfolio has more open loops than any person can carry and still sleep.

Nobody designed this split. It happened because the platform holds the money and nothing was ever put in charge of the work.

2. Why another integration never finishes it

The instinct is to join them better. An integration between the platform and the maintenance app, a connector to the inspection tool, somebody technical for a fortnight. Sometimes that helps. It never finishes, and the reason is structural rather than a matter of effort.

You own neither end of any connection you buy. Both ends belong to vendors solving their own problems on their own timetable, so a field that is not in their interface is not available to you at any price, a change on their side is a change to your office made without asking, and a connection can be repriced or retired by somebody who has never heard of your agency.

And each of those systems keeps its own copy of the truth. Its own version of who the owner is, which contact to use, what the property is called, what was agreed. When you integrate you are not resolving that. You are agreeing to keep several copies in step forever, and that agreement is paid in somebody’s afternoons, every week, with no end date.

A floor inverts it. One place holds the state of the work, the platform stays the record of the money, and everything else reads rather than remembers. At that point you are not integrating at all.

3. What a floor actually is

Four things, and every one of them is boring, which is the point.

• A record. One place where a property is a property, a tenancy is a tenancy and an owner is an owner, each with a key issued by you, and the platform’s own reference sitting on the row as a column.
• A gate. Something that can refuse. A spreadsheet lets anybody type anything, which is why the compliance spreadsheet is always a bit wrong and everybody knows it. A gate says no: this inspection cannot be marked done without the report attached, this notice step cannot be reached before the date that earns it.
• An argument. A report that reads the record directly and refreshes without anybody preparing it. If a portfolio review needs a person to build the numbers first, the review is about the numbers rather than the roll.
• An identity. Who can see and do what, taken from the accounts the agency already administers. One property manager should not be able to close another’s arrears step by accident.

Record, gate, argument, identity. Every tool you have ever bought is those four things wrapped around one job, sold monthly, with its own login. Hold the four yourself and you stop needing a fresh set every time a new part of the job needs organising.

4. Why the gate matters more here than anywhere

In most businesses a gate saves you from mess. In property management it saves you from something worse, because nearly every loop on the roll has a statutory clock attached to it.

Arrears run on the paid-to date, and the paid-to date is a fact rather than an opinion. Entry needs notice, and the notice needs to have been given rather than intended. Minimum standards and safety obligations run on dates that do not move because the office was busy. Renewal has a runway. In each case the difference between a valid step and a void one is a date and a piece of evidence.

Which is why the single most useful rule to encode is this: a date that was typed is not a date that was served. A field somebody filled in is a claim. A date written by the step that produced it, with the document attached, is a record. Those look identical in a spreadsheet and they are not remotely the same thing six months later in front of a tribunal.

So the gates here earn their keep immediately. A step that cannot be reached early. A stop check re-read before every message rather than once at the start of the run. An escalation that cannot be closed without the reason. None of that is sophisticated. It is just the difference between a register and a defence.

5. The stack already under your feet

If the agency runs Microsoft 365, you are paying for all four already.

SharePoint lists are the record. Power Automate is the gate, and it is the good kind, because a person cannot type past a flow. Power BI is the argument. Entra is the identity, already administered by whoever set up the email. The document libraries holding your condition reports and certificates are already there, already backed up, already inside the security posture your owners and your insurer would ask about.

You do not have to like Microsoft for this to be the practical answer. The floor is already poured, already paid for, and already survives a property manager leaving, which is the part that has cost you before.

Two honest notes. Some of this steps up in cost once you need the premium tier of connectors, or Dataverse instead of lists, and that is worth pricing before you design around it rather than after. The arrears build plan and the compliance calendar build plan carry that question with the lists and flows spelled out.

On Google Workspace the same four pieces exist under different names, and if you are on neither there is a page for free tiers. The argument is about the shape, not the brand.

6. What you build, and what you never build

Build the loops. Arrears as a worked queue rather than a report. Maintenance from request through owner approval to attendance to close, with the approval as a record rather than a sentence in a thread. Inspections with the report as the thing that closes the row. The compliance calendar, every obligation with its date and its evidence. Renewals with a runway. Owner communication logged against the property rather than living in one person’s sent items. These are the parts where every agency is different, and where off-the-shelf has always felt like wearing somebody else’s boots.

Never build the regulated speciality. Trust accounting stays in the platform, full stop. Receipting, disbursements, owner statements and the audit trail on money are not hard because of the software. They are hard because being wrong has consequences that attach to a licence, and that is not something you generate on a Thursday.

Never hold the tenant’s or owner’s money twice. The floor reads balances and paid-to dates. It never becomes a second opinion on what is owed. One source for money, always, and it is not you.

One rule settles most arguments about where a thing belongs: organise by the question, not by the software. Not “what does the platform hold”, but “what do I need to answer at nine on Monday”. A register per question. The platform becomes a source, not a location.

7. The smallest version that is still a system

A first version here is not an app. It is one key, one loop that runs on it, and one gate that can say no.

• The key. Two lists, properties and parties, where the property key is issued by you and the platform’s reference is a column on the row. That is the entire long game, and it costs an afternoon now or a migration later.
• One loop. Take the one that already lives in a spreadsheet. For most offices that is the compliance calendar, because the dates are external, the evidence is a document, and a missed one is the kind of miss that gets discussed with a lawyer.
• One gate. An obligation cannot be marked done without the certificate attached. It has to block, not warn.
• Money in one direction only. A nightly read of paid-to dates and balances from the platform into a list, read-only, never written back. Two-way sync is where these projects die and you do not need it to get the screen.
• One report. It reads the lists, and the test is that it refreshes without anybody touching a file.

Deliberately not in it: no tenant portal, no app for the field, no two-way writeback, no inspection capture yet, no document migration, and no agent. The field app is what everyone starts with and what kills the project, because you end up with a lovely form writing into nothing.

8. Where this goes, once agents have a floor

This is why the idea is worth acting on now rather than five years ago, when the same four pieces already existed.

An agent with five logins is a worse assistant than a person. It has to guess which system is right, it cannot see the whole tenancy, and every answer needs checking against the others. That is why so many attempts at this feel like a party trick. The problem was never the model. There was nothing coherent to point it at.

An agent with one floor can do real work. Which tenancies are in arrears past the point where a person should have rung, and has anybody rung. Which inspections are overdue against the agreement rather than against a habit. Which leases end inside the runway with no conversation started. Those are answerable because owner and clock are columns rather than conventions.

Three stages, and the first is already true.

• It builds the thing. Your department head describes the register they have always wanted and has a working list, a form and a gate the same afternoon. This is not a forecast. It is what changed, and it is the reason to pour the floor now.
• It maintains the thing. The agent reads the floor and notices where reality has drifted from the design. A register nobody has touched in six weeks. A gate people have found a way around. A field that is always blank, which means the process it described is not the process being run.
• The portfolio gets managed by exception. This is the one to aim at, and property management is the clearest case for it of any industry, because the work is thousands of small obligations with dates. When every loop has an owner and a clock on one floor, the question stops being “what have I forgotten” and becomes “show me only what is off track”. That is the difference between a property manager carrying a roll and a property manager running one.

That end state is not a product anybody sells. It is a consequence of having a floor.

9. The discipline that has to arrive with it

Here is the trap, and it is the mirror image of the opportunity.

If an agent can regenerate the whole thing from a prompt, you do not have a system. You have a slot machine. Ask again and it comes back different, and every check you did last month has to be done again from scratch, because nothing is the same shape any more. People are finding this out the expensive way with self-built tools: the second version is not an improvement on the first, it is a replacement, and it has to be reviewed like a stranger.

Yes, you can just ask an assistant to do all of this, in the same way you can run a rent roll out of a spreadsheet and a good memory. Both work until the day they do not, and in this industry that day is usually the day somebody has to prove what was served and when. The build, buy or have it built paper works through that decision properly.

So the floor carries the parts that do not regenerate.

• The objects and their keys. A property is a property, with one key, forever. Agents can write the screens, propose the flows and draft the reports. They do not get to rename the property.
• Gates that refuse rather than warn. A warning is a suggestion, and on a busy Friday half the team will read past it, correctly, because it was only a suggestion.
• A log. Who did what, when, and what the state was before. Not for suspicion. For the day an owner or a tribunal asks, and the answer needs to be a record rather than a recollection.
• A named owner on every queue, and a clock. The fastest way to tell a real system from a demo: point at any open loop and ask whose it is and when it goes overdue. If the answer is in somebody’s head, it is not a system yet.

Get those four right and the agents can be as creative as they like above them, because they cannot break the shape. Get them wrong and the more capable the agent, the faster the mess arrives.

10. The first step, and what stays with a person

One spreadsheet, moved.

Pick the file that would cause a problem tomorrow if it were deleted tonight. Everyone in the office knows which one within two seconds, and in a property management office it is usually the compliance dates or the arrears working list. Put it on the floor with the same columns and the same person maintaining it, add the property key to every row, and give it one rule it can enforce that the file could not.

It pays the same day. Two people can work in it at once, nobody asks who has it open, and nothing gets overwritten while somebody is on leave. And the first time the list refuses a row somebody wanted to close, you will have felt the difference between a file and a system, which is worth more than being told about it.

Then stop. Do not build a second register until people have stopped emailing the old file around. The failure here is never technical, it is two registers running in parallel for three months. Two weeks later the measure is simple: nobody has asked for the spreadsheet back, and at least one row got refused.

What stays with a person. The trust account. Serving a notice, and deciding to serve one. Entry. Anything legal, and any advice to an owner about their money or their property. A decision that affects somebody’s home is not a workflow step.

And the one thing no floor can give you: the live phone call. A register can tell you that a tenancy has been in arrears for days and nobody has spoken to anyone. It cannot make the call. That needs a number, a carrier, calling hours, the disclosure spoken at the top, a Do Not Call check before the dial, and a recording and transcript kept where somebody can read them later. That is not a feature you generate. It is the one row in the whole build that never goes to zero, and it is the part we run where a product exists: workmylist works the landlords and contacts an agency already owns by voice, SMS and WhatsApp. The arrears call is not one of them yet. No product reads a rent roll today, so that call is a scoped build to the arrears standard.

Everything else on this page you can build yourself, and now you can build it in an afternoon. That is the honest shape of it, and it is why the standards on this site are published rather than sold.