· The Maintly team
My Dad Managed Six Properties With a Notebook. I Tried to Do the Same.
The system that worked for one generation, and why it stopped working for ours.
My dad is the kind of person who never loses track of anything.
He built a construction company from scratch. He managed crews, timelines, budgets, and clients, all at once, for decades. When he added rental properties to the mix, he handled those the same way he handled everything else: with a notebook, a phone, and a memory that never seemed to fail him.
Six properties. Multiple contractors at each one. Maintenance schedules, service histories, contractor relationships: all of it lived in his head and on paper. And for a long time, it worked.
I watched him do it growing up. It looked effortless. It looked like something I'd be able to do too.
I was wrong.
What I inherited wasn't the system. It was the assumption.
When my brother and I started working alongside my dad (first in the construction company, then managing properties of our own), we assumed the notebook approach would carry over. It's what we'd seen. It's what made sense.
What we didn't account for was scale.
My dad built his system over decades. He knew every contractor personally. He remembered every repair because he'd been there for most of them. The knowledge lived in him, accumulated slowly, one property at a time.
When we started managing properties at the pace the business demanded, there was no time to build that kind of accumulated knowledge. We were coordinating maintenance across multiple properties, working with contractors we hadn't known for twenty years, and trying to track everything the way he did: manually, from memory, through texts and calls and handwritten notes.
It became almost impossible to follow up on everything.
A contractor said he came. Did he? We weren't there to check. A service was scheduled for last Tuesday. Did it happen? Nobody logged it.
The notebook system assumes one thing above everything else: that the person running it is always present, always tracking, always remembering. My dad was. We weren't. And the business didn't allow us to be.
The problem with memory as infrastructure.
Here's what nobody tells you about managing properties the old way: it works until the person it lives inside isn't available.
My dad could tell you the service history of every unit he'd ever owned. He could tell you which plumber to call, what that plumber charged last time, and what he'd found when he came out in 2019. That information was valuable. It protected his properties and his investments.
But it lived in one place: him.
When we started scaling (more properties, more contractors, more moving parts), we realized that system wasn't transferable. You can't hand someone a notebook and expect them to have the same context my dad built over thirty years. And you can't run a growing property portfolio on institutional memory that belongs to one person.
What we needed wasn't a better notebook. We needed the knowledge to live somewhere permanent: attached to the property, not the person managing it.
What home maintenance tracking actually requires.
Managing maintenance across multiple properties isn't just about remembering things. It's about visibility.
Knowing what's scheduled. Knowing what actually happened. Knowing which contractor came, what they did, what they charged, and whether the work held up. Having a record that survives personnel changes, memory lapses, and the general chaos of running a business that involves real property in the real world.
My dad had that visibility because he built it manually over a lifetime. Most property owners don't have thirty years and an extraordinary memory. They have jobs, families, and more properties than one person can track in their head.
The generation before us managed properties with relationships and notebooks because that was the infrastructure available. It worked. For them, in their context, at their scale.
That context is gone. The properties are more complex. The contractor relationships are harder to maintain. The pace is faster. The scale is bigger. And the old tools weren't built for any of it.
This is what Maintly came from.
My brother and I didn't set out to build a software company. We set out to solve a problem we were living inside every day.
We watched what happened when maintenance coordination lived in someone's head. We experienced what it felt like to not know if a contractor had shown up, to lose track of a service history, to realize we'd been paying for work we couldn't verify.
Maintly is the system we needed and didn't have, built for the way property ownership actually works today.
Every service logged. Every contractor tracked. Every property coordinated from one dashboard. A verifiable care record that lives with the home, not with whoever happens to be managing it this year.
My dad's notebook was a solution to a real problem. It just wasn't built for what came next.