How to hire your first technician without sinking your margin

You have been the business. Every quote, every job, every invoice has run through your own two hands, and for a while that was the appeal — full control, no payroll, all the margin. Then the calendar filled. Now you are booking three weeks out, letting Saturday calls go to voicemail, and quietly passing on work you used to take without a second thought. The first technician is how you buy that capacity back. It is also the first hire whose pay lands whether or not next week books, which is why capable operators stall on it long past the point their own numbers said go.

A word on the relationship behind this page before the playbook: we make these tools free, and Fieldwynn — the field-service app we’re building for small crews — is ours too, with a funnel attached. Fieldwynn isn’t out yet; the intent is one coherent system that takes the coordination drag off you the moment a second person and a shared schedule enter the picture, and the day you add that person is where the funnel lives. Read every step below as operator process first, weigh the tool against your own setup, and if it’s what you’d want, join the early-access list — there’s nothing to buy, only a list to be first on.

The signal that says hire — and the one that fools you

The wrong reason to hire is a good month. The right reason is a pattern. Before you write a job post, confirm the demand is structural by reading three numbers you already generate. Your technician utilization — the share of your paid working hours that lands on revenue jobs rather than driving, quoting, and admin — should have been sitting near its ceiling for weeks, not days. You should be out of billable hours to sell: the calendar is full and the only way to take the next job is to drop one you already booked. And the overflow has to cluster tightly enough that a second truck stays busy, because a tech who spends half the day driving between thin, scattered stops never earns their seat. That is a route density question, and it is the one solo operators skip.

The signal that fools people is the seasonal peak. A wall of work in your eight busy weeks is not the same as year-round demand, and a permanent salary is a poor hedge against a spike that empties out by November. When the overflow is seasonal, bridge it with overtime, a temporary helper, or a subcontractor, and reserve the permanent hire for demand you can watch holding across your slow stretch too. Hire against the floor of your year, not its ceiling.

Price the role before you write the post

Here is the part most first-time employers get backwards: they pick a wage that “sounds fair,” post it, and only discover months later whether the math works. Run it the other way. The wage is an output of your numbers, not an input you borrow off a forum, and the only defensible figure is the one your own jobs can carry.

Start with the true cost of the seat, which is never just the hourly rate. On top of every paid hour sits the labor burden — payroll taxes, insurance, workers’ compensation, paid time off, plus the truck, fuel, phone, and tools the role consumes. The labor-burden calculator below turns a candidate wage into the loaded hourly cost you will actually carry, so you are comparing the real number against the revenue the seat can produce.

With the loaded cost in hand, the question becomes whether the seat pays for itself. Take the billable hours a realistic first-year tech can turn in a week — not the optimistic ones — and check, against your overhead-recovery rate, that those hours cover the loaded cost, the role’s share of overhead recovery , and a margin worth the risk you are taking. Read backward from that and you get a wage band the work can defend rather than a number you hope clears. It also sharpens what each billed hour has to return: the seat’s effective hourly rate is the floor your pricing has to clear once a second person is on the books, and if it does not, the fix is your rates, not the hire. Once the band is set, sanity-check it against public local wage data for the trade in your metro — the U.S. Bureau of Labor Statistics publishes free occupational wage tables you can search — so the offer is honest from the candidate’s side as well as yours. The point of the band, not a single figure, is that you can move within it for the right person without the seat going underwater.

Write a job description an actual technician will answer

A good technician reads twenty postings and answers three. Yours wins by being concrete where the others are vague. Describe the actual day — the kind of jobs, the trucks, the radius you cover, who they report to (you) — instead of a paragraph of “fast-paced team” filler. Post the pay range you worked out above; a real range pulls more serious applicants than “competitive pay,” which good techs read as code for low. Separate the few true requirements (a valid license, a clean enough driving record to insure, whatever certification the trade legally demands) from the nice-to-haves you can train, because a wall of requirements scares off the trainable people who would have grown into the role. And name what you offer back: steady year-round hours, a truck that works, paid time off, a path to lead tech. The first hire is choosing you as much as you are choosing them.

Where service operators actually find a first technician

Your first tech rarely comes off a single job board, and the channels are not interchangeable. Each trades reach against quality and effort differently, so work two or three at once rather than betting the hire on one.

A structured interview beats a gut read

Likability is not competence, and the operators who hire on a good conversation are the ones who get burned. Decide the questions before you meet anyone, ask the same ones in the same order, and write down the answers, so you are comparing candidates against each other instead of against your mood that afternoon. Cover four things: why they left the last job and what they would change about how it ran, a time a job went sideways and what they did, how they would handle a customer who is angry before they have said a word, and a couple of plain competence checks for the trade. Listen for ownership over blame, and for whether they talk about the customer at all. Keep the questions about the work itself — your attorney’s guidance on which topics are off-limits in an interview is worth ten minutes before you sit down, because the line is narrower than most owners assume.

The paid ride-along is the real interview

No answer in a chair predicts a workday like a workday does. Bring your top candidate along for a real shift, or run a short working interview on an actual job, and pay them for the time — an unpaid “tryout” on billable work invites a wage claim, and a good tech reads the offer to pay as a sign you run a real shop. Then watch the things that decide whether customers keep calling you: do they show up on time, do they treat the customer’s home and the customer’s questions with respect, do they listen before they reach for a tool, do they leave the site clean. Speed you can coach. The instinct to protect your name with a stranger’s property you mostly cannot. This is the day your first-time-fix rate and your review average are on the line, because the moment an untrained second person starts closing jobs is the moment both can slip, and the ride-along is your cheapest chance to catch a mismatch before it is permanent.

The first week: an onboarding checklist that protects the work

A technician you hire well and onboard badly still becomes a bad hire. The first week is where you convert a good candidate into someone who represents you without you in the truck, so run it as a sequence, not a stack of paperwork shoved across the desk on Monday.

• Settle the paperwork and the classification first. Employment eligibility (I-9), tax withholding (W-4), and your payroll setup come before the first paid hour, and the W-2-versus-1099 decision is settled now, on the test rather than on convenience (next section). A misstep here is the expensive kind to unwind.
• Hand over the gear and the systems. Truck, tools, uniform, and logins to whatever runs your schedule and jobs. This is the natural moment the second person meets your dispatch and scheduling setup; a shared calendar that two people can both trust is the difference between a crew and two solo operators colliding.
• Shadow, then be shadowed. Day one they ride with you and watch how you run a job and talk to a customer. By mid-week you watch them run one while you say nothing, then debrief. Telling is not training; supervised reps are.
• Define “done” out loud. What a finished job looks like — the photos, the customer sign-off, the site left clean, the notes written up — is obvious to you and invisible to them until you say it. Write it down once and it stops being a guess.
• Close the loop on getting paid. A productive tech only helps cash flow if the work they finish converts to an invoice the same day and gets collected fast; fold them into your billing rhythm in week one, and lean on the playbook for getting paid faster so their completed jobs do not pile up as uninvoiced work in your truck.

Employee or contractor: settle it before week one

You will be tempted to pay the first hire on a 1099 because it looks cheaper on the day you do it. Resist deciding it by convenience. If you set their schedule, train them in your method, and supply the tools and the van, they are almost certainly a W-2 employee whatever form you file — the IRS and the Department of Labor each apply their own test, and the working reality decides the answer, not the label. Because that is a tax and legal question with real penalties for getting it wrong, settle it against the actual tests rather than re-derive employment law here: work through the full 1099-vs-W-2 classification guide, and bring a borderline call to your accountant before a single payment goes out.

Make the first hire the one that makes the second easier

The first technician is not a hole you are plugging; it is a system you are building. Every step you do deliberately the first time — the readiness signal you measured, the wage you derived from your own labor-burden math, the structured interview, the ride-along rubric, the week-one checklist — is a step you will not have to invent again for hire number two or five. Write down what you did and why, keep the version that worked, and the next hire stops feeling like a leap and starts feeling like a process you trust. That is the real return on getting the first one right: not just a second pair of hands this season, but a business that can add the third pair without you white-knuckling the decision every time.