Going From Solo to a Two-Person Operation: What Your Admin Process Needs to Handle First

The moment the wheels come off

Talk to any contractor who's made the jump from solo to a small team and they'll describe a specific moment: the first week where something fell through the cracks.

An estimate went out with the wrong price because the other person used last year's material costs. A deposit was collected but not noted anywhere, and you almost charged the customer twice. A job was confirmed verbally by your subcontractor but never put in writing, and there's a dispute about scope. A customer called about a change order and you had no record of the original conversation.

These are not failures of character or work ethic. They're failures of system. When you're solo, the entire system is your memory. When you have two people, memory is not a system — it's a liability.

---

What "the system" actually needs to do

Before you bring on help, your admin process needs to handle four things reliably:

1. Consistent estimate presentation

When you send estimates, they look and read the same every time — your logo, your deposit percentage, your terms, your scope format. This matters because your estimates are your brand. They also matter because inconsistency creates liability: a signed estimate is a contract, and contracts need to be consistent.

2. A clear record of every commitment

Every estimate sent, every approval received, every change order agreed to, every deposit collected — these need to exist as documents that you and anyone else can look up. "I thought we agreed to..." is a conversation you never want to have with a customer. The written record is your protection.

3. Deposits collected before work begins

When you're solo, you know which jobs have deposits and which don't. When you have someone else sending estimates and scheduling jobs, you need the system to enforce deposit collection — not rely on someone remembering.

4. A follow-up process that doesn't depend on any one person's memory

If your follow-up cadence lives in your head, it disappears when you're on a job. Automated reminders ensure that every estimate gets followed up consistently regardless of who sent it or how busy the week has been.

---

The record-keeping gap

The most common thing that breaks first when contractors add headcount is record-keeping.

Solo contractors often have minimal documentation because they can hold everything in their head. They know which customers have signed, which have deposits, which jobs are pending change orders. This works — until it doesn't.

The standard to aim for: any job-related question should be answerable in under 60 seconds by looking at the record, by anyone with access to the system.

• "Has the customer approved the change order?" — Yes or no, with a timestamp.
• "When was the deposit collected and how much was it?" — There, in the payment record.
• "What exactly was in scope?" — Right there in the signed estimate.

If those questions can't be answered in 60 seconds from your system, your system isn't good enough for a two-person operation. Fix it before you grow.

---

Change orders: the biggest source of disputes

The fastest way to destroy a customer relationship on a growing team is a change order that both sides remember differently.

A verbal agreement on a change order is fine for the moment. The follow-up written record — sent to the customer, approved by the customer — is what you need when a dispute arises.

When it's just you, you usually remember verbal agreements accurately. When you have someone else running jobs and you're coordinating from the truck, you can't. The change order process needs to be automatic: every scope change generates a written change order, every written change order gets customer approval before work proceeds.

This protects you. It also protects your customer, which is why most professional customers actually prefer it.

---

The process to build now

Here is the minimum viable process for a two-person contracting operation:

Estimates:

• Template library so both people start from the same base
• Consistent branding and terms on every estimate
• Approval link (not PDF) so signatures are always timestamped and recorded

Deposits:

• Deposit required before any job is scheduled, no exceptions
• Payment record tied to the job so anyone can verify

Change orders:

• Every scope change above $X (set your threshold) requires a written change order
• Change order is sent via approval link, not verbal or text
• Work does not begin until approval is received

Follow-up:

• Automated reminders at day 3 and day 7 on every open estimate
• No one has to manually track or remember this

Audit trail:

• Every approval, payment, and change order creates a timestamped record
• If a dispute arises, you have documentation

---

Build the process before you need it

The mistake most solo contractors make is waiting until a problem forces the issue. They bring on help, something goes wrong, and then they build the process.

Building after the fact is expensive. The dispute you're now having with a customer is costing you relationship capital and possibly real money.

Build it before. It takes a few hours to set up a consistent estimating process, a template library, and automated follow-up reminders. The ROI on those few hours is every dispute you don't have for the next ten years of your business.

The contractors who grow smoothly from solo to small team are almost always the ones who ran a tight process when it was just them. Tight process at one person scales. Informal memory doesn't.