
A Task List Is Not a Plan Until You Add Time to It
Somebody on this week's call said the most useful thing they took from The One Thing was that no is usually not no. It is not now. That is the right read, and it leads straight to a question most operators never answer. If most things are not now, then when are they? A task list cannot tell you. A list of ideas stacked on top of each other looks like a plan and behaves like a pile. The rest of the call was about putting time, rules, and guardrails around the pile.
Write the Rule While You Still Remember Being Broke
Two years ago, a plumbing problem that should have cost about five thousand dollars cost us thirty thousand. We had money sitting in the account and a problem that felt big, so a national drain company got the call. They kept finding more work, and they only stopped when we ran out of money to give them. If the account had been deeper, they would have kept going.
Afterward we asked a simple question. If we had no money, how would we have handled this? We would have found a local plumber, gotten a second opinion, and scoped the job before anyone started. So that became the rule. That company is banned from our properties unless the invoice is two hundred dollars or less, which in practice means never.
The point is not one vendor. When a company gets bigger, the staff making calls were not there for the early hustle. They do not know the creative workarounds you used when every dollar mattered. A book on this came up on the call, The Power of Broke, and its argument fits: having too much money at the start can be more dangerous than having too little, because nothing forces you to think. You cannot hand your staff your old scarcity. You can hand them the rules it taught you. Write those down while you still remember why they exist.
A Gantt Chart Is a Task List With Time Added
Three people on the call defined a Gantt chart three ways. The shortest version was the best: a process flow with milestones, timelines, and delivery dates. The difference from a task list is that it shows lead time and sequence. This takes ninety days, that one cannot start until this one is done, and these two can run side by side. Instead of every idea sitting in parallel, you see the order your year actually has to happen in.
I have used one for acquisitions since 2011, and I did not buy anything in 2011. I bought my first house in 2008 and sold it in 2012. In between, working a corporate job, I spent my lunch breaks with a property evaluation spreadsheet. One day I asked what would happen if I bought a second property, then a third. Then my brain told me I could not buy them all at once. So I asked a different question: if I bought one, then another, then another, how long would each one really take before I could do the next? That turned the spreadsheet into a timeline, and the timeline into a five year plan.
My early estimates were conservative. I used to put six months against fixing up a three unit building. Since then we have turned ten and twenty unit buildings in six months, and last year we turned forty units in a single month. Your sense of what is possible changes once you have done it, which is exactly why you write the first plan anyway.
Two years ago I did it again on a wall of whiteboards. The goal was two hundred doors. Four blocks of ninety days: get something under agreement, close and start stabilizing while finding the next one, and repeat. We ended up managing close to twice the goal for a while, then handed the weakest buildings back and kept the ones we wanted. The portfolio I am part of now sits above four hundred doors.
What matters about that story is not the number. A lot of people keep telling me to go for a thousand doors. Maybe someday. But I set the plan on my timeline, at a pace I can actually run, and I only need to find the next right deal in the next ninety days. For some people the next right deal is a single family house. For some it is a multifamily building. Map when it happens, not just what it is. The same idea is behind treating complexity as a cost you never see on the statement.
Guardrails for the Manager You Do Not Control
A big part of the call turned into a debate between owners and the property managers in the room, which is the most useful kind of debate because both sides were there.
First, when does it make sense to bring management in house? My answer is that somewhere between eighty and one hundred twenty units, it starts to become fiscally logical, especially if it is only one or two sites that are easy to get to. At two hundred units, keeping it with someone else rarely makes sense unless you have found a very unusual manager. Below that range, a good outside manager is taking real work off your plate, and that is worth paying for.
Second, if you use an outside manager, set the guardrails in writing before the first work order. The owners in the room who were comfortable all had the same few things in place. A dollar threshold above which nothing gets done without owner approval. A full, line item scope of work on every unit turn. Everything agreed in writing, and photos after the work is done. One owner had also asked the manager to batch non emergency calls into one tech visit per week instead of paying a trip charge every time a doorknob wobbled.
Third, know what counts as an emergency. A manager in the room offered a clean standard: habitability, safety, and security. If a call touches one of those, someone goes, day or night, holidays included. Everything else can wait for the batch.
Fourth, understand how the manager makes money before you squeeze. Both managers on the call said the same thing plainly: most management companies do not make their margin on the management fee. They make it on maintenance. Push too hard there and you are asking them to rebuild their whole system for one owner. If they are good at the things that matter most, finding good residents, collecting, and keeping units rented, it can be worth giving a little on maintenance. One manager on the call runs the opposite model, charging a higher fee per door and taking no maintenance markup. Neither model is wrong. You just want to know which one you are buying.
We have kept outside management in place when it worked. On one acquisition, the manager told me she could get the property where we wanted it if we funded it. We did, and she did everything she said. That is rare, and it has always been the goal. Build the system first, then hire the person applies to managers just as much as staff.
Stop Paying Your AI to Rethink Solved Problems
The last stretch was about AI, and one lesson cost me a day of work this week. I hit my usage limit because I had been running routine automations through long conversations with the most expensive models. Every time, the model rereads the whole conversation and thinks the problem through again, even when the answer never changes.
So the rule I am putting in place is this. Anything that took heavy thinking the first time should be turned into a fixed routine the second time. Pulling reports and reorganizing them by the same numbers every week is not thinking, it is a procedure. Code it once and let it run cheaply.
Someone asked the right follow up: how do you keep the context if you strip the thinking out? You keep it in the knowledge base, not in the conversation. Store everything in one repository and organize the folders early around what you actually do, so the models can find it later. That is much easier if you already know your long term direction, which is why the planning conversation above and the AI conversation are really the same conversation.
Two housekeeping items that matter more than they sound. Export your data from any AI tool you rely on. We lost a large amount of work when we dropped one platform from a paid plan to the free tier and everything was wiped. And check your data controls in every tool so your information is not shared further than you intended. Before you connect bank accounts or anything sensitive, read what you are agreeing to.
The Takeaway
The call kept circling the same idea from four directions. Rules, timelines, written guardrails, and fixed routines are all ways of making a decision once so you do not have to keep making it under pressure.
If you do one thing this week, take your idea list and put time on it. Pick the next right move, give it a real lead time, and let everything else be not now.
The plan does not have to be big. It has to be yours, on your timeline, and written down where you can see it.
Further Reading
- The Number of Doors You Can Manage Is a Setting, Not a Fact Last week's Mastery call on why your capacity number is a decision, which is the ceiling this week's timeline is built to raise.
- REAP Principle 44: Systemize Your Business So It Works Without You How written procedures turn a portfolio that depends on you into one that runs without you, the same move as turning a solved problem into a routine.
- Three Stuck Problems, One Pattern: More Effort Was Never the Answer Why working harder was never the fix, and what shared root sits under problems that look unrelated.
Join the Alchemist Mastery Accountability Call
Alchemist Mastery meets weekly. It is a working room, not a lecture. Owners and operators bring what is actually stuck, the room pulls on it, and the pattern underneath usually turns out to be shared by everyone else on the call. Bring your idea list and the date you think the next move happens. We will put time on it together.
*Educational purposes only. Not an offer or solicitation.*
