The spreadsheet doesn't save you, the habit does.

The spreadsheet doesn't save you, the habit does.

Member since 2026 · 52 posts · 16 votes

Someone on here said something last week that's been sitting with me.

Talking about tracking chaos across a portfolio, he said: "the spreadsheet doesn't save you, the habit does."

Not what I expected. I figured the fix was better software. He's saying the fix is a behavior you do every single time, and the tool is just where you put it.

He also said something sharper: most tracking problems aren't actually tracking problems. They're "everything lives in my head" problems wearing a spreadsheet as a costume. You think the tenant's behind on rent but they paid cash and you forgot to log it. You think the repair wasn't done but it was, you just never got the confirmation.

That's not a software gap. That's a discipline gap that software can enforce, if you build the habit into the tool instead of hoping the human remembers to have the habit.

Where's your actual line? The door count, unit count, or vendor count where "I'll remember" stopped being true for you?

0Reply
269 views

2 Replies

Jump to latestLatest
  • Investor · Pacific Northwest · Member since 2026 · 538 posts · 309 votes
    3w

    I think the line shows up earlier than most people realize.

    It’s not really a door count. It’s the first time the business depends on somebody remembering that something happened.

    Tenant paid cash. Vendor finished the repair. Lease got renewed. Insurance changed. Someone said “I’ll handle it.” If the next step depends on a person remembering to update the system, you already have a structural problem — even at five units.

    The strongest operations I’ve seen treat every meaningful event like a state change: something happens, it gets captured, and the next action becomes obvious.

    The spreadsheet can be perfectly ugly. If that habit is reliable, the operation works.

    If the habit isn’t reliable, prettier software just gives you a nicer-looking version of missing information.

    This is actually one of the more interesting operational problems I’ve been working around lately.

    • Member since 2026 · 52 posts · 16 votes
      3w

      The state change framing is the clearest version of this I've seen anyone put into words on here. Most people describe the symptom, you just described the actual mechanism.

      When you say you've been working around this lately, what does that actually look like day to day? Curious if that's a process you built yourself, or something you're piecing together from existing tools.

Join the conversationCreate a free account to reply, vote on answers and follow this thread.