For most of its history, the ERP had a humble and slightly thankless job. It was where the business wrote things down. A lease was signed, so it went into the system. Rent was collected, an invoice was paid, a work order was closed - each event, after it happened, was recorded, validated, and stored so that later, someone could trust the number. The ERP was the organization's memory. Reliable, authoritative, and fundamentally backward-looking. It told you, with great precision, what had already occurred. That job is not going away. But it is being quietly demoted from the whole point of the system to merely its foundation, because something is being built on top of it that changes what the ERP is for. The same platform that spent forty years recording the past is now being asked to interpret the present and act on the future - to notice that a building is trending toward a bad quarter, to propose the renewal price, to flag the vendor invoice that does not match the contract, and ...

The invoice is the last thing that determines what a repair costs. The first is the payment model. Long before a technician picks up a wrench, your contract has already decided whether speed, efficiency, extra hours, or additional materials will be rewarded. The repair simply follows those incentives. A garbage disposal fails. It is a common, well-understood repair, the kind a competent technician finishes in under an hour with a part that costs very little. Yet the invoice comes back at three times what you expected. There was a diagnostic visit, then a return visit for the part, followed by time spent checking adjacent fittings while they were already there. Nothing on the bill is obviously unreasonable. The total is simply far higher than it feels like it should be. The easy explanation is that the vendor is padding the bill. Maybe they are. But look across a hundred invoices from a dozen vendors and a different pattern emerges. The cost of a repair often correlates less with what ...

Quick Reference: Ohio Eviction Timeline Step Requirement Statute Notice to leave premises 3 or more days, exact statutory language required R.C. 1923.04 Notice to cure a material violation 30-day notice for certain material (health and safety) violations; tenant may remedy before the termination date R.C. 5321.11 Month-to-month termination 30 days before the next rental period R.C. 5321.17(B) Complaint filed In municipal or county court where property is located R.C. 1923.05 Possession hearing (first cause) Cannot be set sooner than 7 days after service is complete R.C. 1923.06 Answer deadline for money damages (second cause) 28 days after service is complete R.C. 1923.06 Judgment Writ of restitution issued if landlord prevails R.C. 1923.13 Execution of writ Sheriff/bailiff must execute within 10 days of receiving it R.C. 1923.14 Appeal Requires a stay of execution and a bond to pause removal R.C. 1923.14 Self-help by landlord Prohibited - no lockouts, utility shutoffs, or seizing ...

Minnesota is one of the most tenant-protective states in the country for repairs, and the mechanism that makes it that way surprises a lot of out-of-state owners: your tenant can legally stop paying rent to you and start paying it to the court instead. It's called rent escrow, and unlike the informal "I'm withholding rent" threat that gets tenants in trouble in most states, this one is a formal statutory remedy that a Minnesota judge can use to order repairs, abate rent, or in serious cases hand your building to a court-appointed administrator. If you own rentals in Minnesota, understanding how that remedy is triggered is the difference between a manageable repair request and a courtroom. This guide covers the covenants of habitability you owe under Minnesota law, what "reasonable repair" actually requires (including the specific heat rule), how the rent escrow process works step by step, and the emergency remedy that moves far faster than escrow. Quick answer: Under Minn. Stat. § ...

Almost every voice a CEO hears on this subject, the vendors, the consultants, the conference speakers, and yes, most of the pieces written by people who sell modern platforms, points the same direction: your systems are holding you back, modernize now, the cost of waiting is enormous. Some of that is true some of the time. But it is worth hearing the other side clearly, precisely because so few of the people talking have any incentive to say it: for a great many companies, at a great many moments, ripping out your systems is the wrong move, and doing it prematurely is one of the more expensive mistakes a leadership team can make. This is an uncomfortable argument for anyone adjacent to the software industry to make, which is exactly why it is worth making honestly. The default is not neutral. It is sold. And a leadership team that mistakes "everyone says to modernize" for "we should modernize now" is outsourcing one of its most consequential and least reversible decisions to people ...

The most convincing proof that your fix worked is often the least trustworthy evidence you have. And the moment you are most likely to be fooled is the moment you feel most sure. Here is how it happens. Your weakest property has an ugly quarter. Occupancy slides, collections slip, complaints climb, and it lands at the bottom of every list you keep. So you step in. You move a stronger manager onto it, tighten up the process, and spend a few weeks paying close attention to a building that normally gets none. The next quarter, the numbers come back up. Not all the way, but clearly better. The lesson writes itself. You made a change at the worst-performing property and the property turned around, so the change is what did it. You remember that intervention as something that works and reach for it again the next time another property struggles. There is another explanation, and statistically it is often the more likely one. The improvement may not have been caused by your intervention at ...

A make-ready that used to take three weeks now takes three weeks. Your team is larger than it was, everyone is busier than they were, the calendars are full from morning to night, and somehow the unit still sits empty for the same number of days it always did. So you do the reasonable thing. You add another person, or you push the team to move faster, and you brace for the number to finally drop. It barely moves. And the next turn is the same, and the one after that, and at some point the pattern stops looking like bad luck and starts looking like a wall you cannot get past by pushing on it. This is not a work-ethic problem, and it is not solved by finding harder-working people. It is a queue problem, and queues follow a rule most operations never name out loud, even though it governs everything they do. The Slowest Step Sets The Speed, And The Rest Does Not Matter The rule comes from Eliyahu Goldratt, who laid it out in a 1984 business novel called The Goal and built it into a method ...

A property company will tell you, without hesitation, what business it is in. Buildings. Units. Square footage. Leases. The physical asset is the thing you can stand in front of, insure, depreciate, refinance, and sell. It sits on the balance sheet, in a line item, valued to the dollar. That is the business. That has always been the business. And yet almost every asset-heavy industry that arrived at this question before property was eventually forced to answer a more uncomfortable version of it. Not "what do we own?" but "where does our advantage actually come from now?" When those industries looked closely, the answer had quietly moved. It had migrated off the physical asset and onto the data about it - how the asset behaves, what it costs, who uses it, and what happens next. The machine, the aircraft, the store, the account: each became a somewhat interchangeable input. The accumulated knowledge about it became the moat. Property is now walking toward that same line, and the purpose ...

Tennessee is one of the trickier states to get right, and the reason catches a lot of owners off guard. The rules that govern your rental depend on which county it sits in. A duplex in Nashville and a duplex two hours away in a rural county are held to genuinely different legal standards, and if you assume the same playbook covers both, you can end up out of compliance without realizing it. Layer on the new Landlord Transparency Act that took effect in 2025, and the compliance bar for Tennessee landlords moved in a way that's easy to miss. This guide covers what you actually owe tenants on habitability and repairs, the exact notice-and-cure timelines, the remedies a tenant can reach for when you don't respond, and what HB 1814 now requires before a lease is signed. Quick answer: In Tennessee counties with more than 75,000 residents, landlords are bound by the Uniform Residential Landlord and Tenant Act (URLTA), which requires them to keep rentals fit and habitable under T.C.A. § ...

A unit comes back and the manager gives it a look. Straightforward turn, nothing structural, two weeks. It takes five. Not because anything catastrophic happened. The painter started a day late, one fixture was back-ordered, the cleaning slipped a day, and inspection turned up one final thing that needed a second visit. Nothing unusual. Everything normal. And the estimate was wrong by more than double, just as it was on the last turn, and the one before that. The surprising part is not that the estimate was wrong. It is that it keeps being wrong in exactly the same direction, and every new estimate still starts from scratch. The Estimate You Build Is The Estimate That Runs Long This is one of the most reliable findings in the study of how people plan. Daniel Kahneman and Amos Tversky named it the planning fallacy: the systematic tendency to underestimate how long a task will take and how much it will cost, and to do so even when you have watched similar tasks run long many times ...