I grew up working there
Weekends and summers, from the time I was a kid until I was twenty-one, I was a laborer at Village San Juan for my father's company. The community sits in San Juan Capistrano, California: condominiums and single-family homes around lakes, with three pools, walking trails, dog parks and play structures, and a portion of the condominium exteriors under the same contract, fascia and painting among it. I knew which trades showed up and which did not, what a pool costs to keep against what a trail costs, and where the maintenance load actually sat as opposed to where it looked like it sat, years before I had any commercial reason to see it one way or another.
When my father passed, this was the last contract his company held. It needed a company to carry it, and the only one that could was mine. That is the whole reason this engagement exists, and I am not going to dress it up as a sales win. In my own words at the time, I saved the business and the contract after my father passed away, and I did it as an homage to him.
The client was a homeowners association run by a third-party management company. The people in it were a board of owners who volunteer their evenings and vote on their vendors, a community manager employed by the management company who is the board's day-to-day eyes, and the residents, who do not care who holds the contract until something floods. On our side there was one full-time employee, no technology to speak of, a habit of doing the work without telling the board what had been done, and a contract file that had not been repriced in years and sat well under market. None of that was neglect in the ordinary sense. It was what a small, trusted operation looks like after a long time with the same client: the relationship carried what the systems should have.
What the board was actually deciding. A vendor whose principal has just died is the easiest vendor in the world to replace, and a board that does it is not being unkind. It is doing its job. So the question in front of them was not whether to keep the name on the contract. It was whether the son could give them the three things the relationship had been quietly providing: someone who shows up in person, an answer to who comes at two in the morning, and a way to know what they were paying for.
That is the diagnosis. What the community needed was not a lower price and not a bigger company. It needed the operation behind the contract rebuilt so that the things a person had been carrying, the property knowledge, the presence, the judgment about what is urgent, lived in a structure a board could see.
What I brought the board was not a lower number
There were three ways this could go. I could let the contract end with my father's company, which is what a board expects and what most sons would have done, since I had a design-build firm to run and this was a maintenance account. I could ask the board for the contract on continuity alone, the same crew and the same knowledge under a new name, and take the vote as it fell. Or I could go to the board with an operating design that answered the worry they would not say out loud, and put my name on a set of promises they could measure.
| The branches, and what each one costs | |
|---|---|
| Let the contract end | No risk to me. The community re-bids to a stranger who has never walked the property; the crew's knowledge of it leaves with the name. |
| Ask for continuity, take the vote | Honest and thin. Continuity is what they had lost, and it is the one thing the son cannot promise, because the person who provided it is gone. |
| Pitch an operating design and a reporting rhythm | Slower, and it commits me to run the account myself for years. The board gets promises it can hold me to. Chosen. |
I pitched the board, and then I pitched it again with the plan that follows. What changed between the two was not the price. It was that the second time I brought something a board could vote for: routine maintenance on one queue with a calendar, a separate crew for emergencies sized to how fast a truck can physically arrive, severity windows written down, and a report on the board's desk on a schedule instead of when something went wrong.
The reasoning underneath the design is simple and it is worth stating plainly, because it is the same reasoning I have used since in businesses that have nothing to do with maintenance. Routine work and emergency work are not the same kind of problem. Routine work is a scheduling problem: predictable wear, predictable seasons, get ahead of it. Emergency work is a capacity problem with a physical floor: a truck has to arrive, and no staffing decision makes the drive shorter. When both run through one crew, the emergency inherits the wait of whatever the crew was already doing, and the board finds out about the design flaw on the night it matters. A price does not fix that. A second queue does.
How I came at this one
The first question was what the board was actually voting on, and the answer was not price. Finding the real decision point mattered because a homeowners association board is owners voting on who they trust to show up, and the price was already in the file. The second question, once we had the contract, was what physically bounds how fast a truck can reach a unit, because the whole operating design is sized to that floor.