Hiring an office manager won't fix chaos. It'll give chaos a salary.
Most contractors figure this out after they've already signed the offer letter, trained someone for two months, and watched them leave. Then they call it a bad hire. It wasn't a bad hire. It was an unprepared employer.
I know a builder — residential, good volume, growing fast — who hired an office manager to fix his intake problem. Leads were falling through, follow-ups were inconsistent, he was answering the same questions twenty times a week. The solution seemed obvious: hire someone to handle it.
She was sharp. Organized. Showed up on time, caught things quickly, asked good questions. Five months later, she was gone.
His conclusion: bad hire.
The real conclusion: he handed her a pile of problems and called it a role. There was no defined scope. No metrics. No way to measure whether she was succeeding. No 30-day benchmark, no 60-day check-in, no 90-day review with criteria anyone had written down. She was bright enough to recognize that the job was impossible to win — and she left for somewhere she could.
Good people recognize chaos quickly. That's what makes them good people.
"If those answers aren't clearly defined, don't hire that role yet."
That's the rule. And the answers are to three questions every contractor should be able to answer before they write a job post, let alone extend an offer.
Question one: Can you describe the role in measurable terms?
Not "handles intake and follows up with leads." That's a description of tasks, not a role. A role has scope — what decisions this person owns, what they don't, where their authority starts and ends. If you can't describe the role in a way that tells someone exactly what winning looks like, you haven't designed a role yet. You've described a list of things you're tired of doing.
Question two: What does success look like at 30, 60, and 90 days?
This isn't performance review language. It's the foundation of every hiring decision that doesn't blow up in your face. At 30 days: what does a new hire need to know and have done? At 60 days: what should they own independently? At 90 days: what metrics will they be accountable for? If those three milestones aren't written down before day one, the hire is guessing — and so are you.
Question three: What metrics will they own?
Not observe. Own. "Leads responded to within five minutes" is a metric. "Leads followed up on" is not — it's vague enough to be meaningless in a performance conversation. Owned metrics make accountability concrete. They also make the role survivable for a good hire — because a good hire wants to know if they're succeeding.
Here's what most builders miss: before you hire, automate the repetitive work first. Not because automation replaces the hire — it doesn't — but because it clarifies what the hire is actually for. If lead response is automated, the office manager's job becomes judgment work — handling escalations, managing relationships, making decisions a system can't make. That's a job someone can succeed at. A salary attached to "catch everything that falls through the cracks" is a job description for someone who will burn out and leave.
The average cost of a bad hire runs about 30% of first-year salary. For a $55,000 office manager, that's $16,500 — recruiting fees, training time, the productivity crater while you backfill, and whatever fell through the cracks during the five months before she quit. That number doesn't count the leads you lost while the chaos was running unmanaged.
Hiring is the move. Just not the first move.
Here's the assignment: before you post the job, sit down and answer the three questions. Measurable role description. 30/60/90 success milestones. Owned metrics. Give yourself 30 minutes. If you can't answer them in 30 minutes, you're not ready to hire yet — and that's good information to have before you hand someone a salary and a chaos pile.
The contractor who answered these questions hired six months later. Same problems, better scope. That hire is still there.