Should you improve processes before hiring?

Before hiring, measure whether work is delayed by a shortage of field hours or by estimating, scheduling and billing. Improve the process where jobs stall, then measure again to see whether another person is still needed.

Count last week before you count the crew

Split one real week into hours a customer pays for and hours nobody pays for. Not a typical week you remember — last week, off your calendar and your texts. The example below is a one-truck contractor, with invented numbers to show the method.

That is 32 billable hours out of 58, about 55%. The other 26 hours are the business running itself, and a second installer does not shrink them. He adds field hours and adds paperwork: another schedule to build, another set of hours to track, another person's questions mid-job.

Use your own hours and work mix as the baseline. If nearly all of your week is already on site and you are still turning work away, hands are the constraint. If a large share is office work, another installer may not address it; administrative help is a separate option.

Find where the jobs stall

Track a group of inquiries through each stage until the work and payments have had time to finish. This fictional example follows 25 inquiries received in one month; later stages may occur in subsequent months.

Eight inquiries did not reach an estimate, and eight estimates did not lead to approval. The counts show where to investigate, not why customers left: some may be unsuitable leads, declined quotes or still deciding. Track a cohort long enough to distinguish delay from loss.

The invoice and payment rows need their own investigation. Check agreed billing milestones, due dates, disputes and reminders before deciding that a delay is an administrative failure.

Run this on your own month. Investigate the largest avoidable delay or loss before choosing a fix.

What a hire actually commits you to

Wages and payroll setup are their own subject. What matters here is the shape of the commitment.

• The cost is not the wage. Add employer payroll taxes, required insurance, benefits and paid nonproductive time. Use the first-employee payroll guide to identify the accounts and current rates you need.
• Allow time for training. A capable installer still needs your material list, your standards and your callbacks explained, and those conversations come out of your billable hours.
• It does not switch off. Payroll runs in a slow February whether or not the phone rang, while a follow-up routine needs setup and continued attention.

Four processes to put in writing

None of these need software to start. They need a decision made once instead of every time.

A priced catalog. Your twenty most common line items with a unit and a price: linear foot of six-foot cedar privacy fence, post set in concrete, gate, mobilization, haul-away. These give you a starting point; the scope, quantities, access and exceptions still need a job-specific check. It also gets the pricing out of your head, which matters most later.

One estimate format. Use a reusable structure, then review exclusions, validity and terms for each job. Editing yesterday's document is not a template — it is how the last customer's exclusion ends up on this customer's job. If your state requires specific language on a residential contract, include the locally reviewed terms and required notices, then check that they apply to this project.

A follow-up cadence with dates on it. For example: day 2, confirm receipt; day 7, offer to answer a scope question; then one final check before the actual expiry date. Adjust to the customer's stated decision date and stop if they decline. Record the dates in your calendar. Eleven days of silence is not a customer saying no. It is nobody saying anything.

One list of what is owed and what is scheduled. A spreadsheet is fine. Two columns matter: jobs approved but not yet on the calendar, and invoices sent but not paid, with the date each went out. An overdue payment needs a check against its due date and any dispute; the list helps you notice it.

The catalog takes the longest, because you are writing down prices you have only carried in your head. Start with whichever system sits on your worst drop-off.

When the bottleneck really is hands

Sometimes it is. The signals are in the field, not the office.

• Your booked backlog — work already priced and won — keeps growing week over week instead of holding steady.
• You are declining jobs after the customer accepted, not before you responded.
• The work itself needs two people, so you are renting equipment or paying a sub to hold the other end on most jobs.
• Estimates go out fast and still convert, and the job still cannot be scheduled.

That is a capacity problem, and no template fixes it. Adding a person, or a sub for the overflow, is the right call.

Hire into a business that can run without you

An undocumented business does not delegate. If your prices live in your head, every estimate still routes back to you after the hire — now with payroll on top of the same evening paperwork.

Estimating took six of the twenty-six nonbillable hours in the example. DoneQuote can draft from your description or a forwarded customer email using your catalog prices. Review scope, quantities, prices, assumptions and terms before sending. If enabled, it can email one reminder before a quote expires, provided the customer has an email address; that is not the day-2/day-7 routine above. Schedule any other follow-ups yourself.

Run the count for 30 days

Log two things for a month: hours by category, and how many jobs entered and left each stage. Fix the biggest drop, then measure again. If billable share climbs and the drop-off shrinks, you bought capacity without payroll. If neither improves, investigate why the change failed before assuming a hire would solve it. Hire when the remaining work actually needs more capacity.