How to Hire Your First Employee for a 3D Print Shop
Most print shops hire too early, for the wrong role, and underestimate what it actually costs. This guide covers the decision framework: whether a hire is the right move at all, what role actually makes sense, what you're legally getting into, and what the full cost looks like before you post a listing.
For operators approaching or past the $100K revenue mark who are feeling capacity pressure. The guide addresses the decision, not just the mechanics. If you've already decided to hire and need process guidance, skip to What You're Actually Buying.
The Capacity Problem You're Actually Solving
Operators think about hiring when they are feeling capacity pressure. But running out of hours is a symptom, not a diagnosis. The actual problem might be a utilization ceiling that a second machine would break faster and cheaper than a person would. It might be a process bottleneck that's consuming hours on tasks that could be eliminated or automated. It might be a job mix problem, where low-margin orders are diverting time from higher-margin work. The operation leak diagnostic maps where your hours are actually going.
Hiring into an undiagnosed capacity problem doesn't solve the problem. It adds a fixed cost to it.
The equipment-versus-hire decision is a full topic on its own, covered separately in this series. Before you move forward here, spend 20 minutes mapping where your hours are actually going. If the answer is "printer management and post-processing," a hire makes sense. If the answer is "quoting, customer back-and-forth, and file prep," the bottleneck is operational, not physical, and the solution set looks different.
When Hiring Actually Makes Sense
Annual revenue is an imprecise threshold. $100K gets cited frequently because it's the point where most solo operators are generating enough margin to absorb a part-time labor cost without destroying cash flow. But two shops at $100K can have entirely different needs depending on job mix, fleet size, and how the owner spends their time.
A more useful threshold test has three parts.
Part 1: Utilization
Your printers should be running at or near capacity consistently before you hire anyone. If machines are idle because you're the bottleneck on setup, removal, and QC, a hire addresses the right problem. If machines are idle because demand isn't there, adding labor increases your fixed cost without adding revenue potential.
Part 2: Owner time allocation
Track your hours for two weeks. Categorize every task as either production work (things a trained shop hand could do) or owner-level work (customer relationships, quoting decisions, equipment decisions, finding and closing new accounts). If more than 60% of your time is production work, you're functioning as your own employee. That's the time a hire recovers. If owner-level work is the bottleneck, a production hire won't free up the hours you need.
Part 3: Revenue per owner-hour
Divide your monthly revenue by the hours you work in the shop per month. If that number is $40 or higher, a part-time hire at $18–22/hour has a plausible ROI: you recover time worth more than the labor cost. If the number is below $30, the math gets harder to justify, and you should focus on raising revenue per hour before adding cost.
If you pass all three parts, the hire is probably the right move. If you fail one, identify which one and address it first.
What You're Actually Buying
You're not hiring "an employee." You're purchasing a defined number of hours applied to a defined category of tasks. The clearer that definition is before you post the listing, the better the hire will go.
Most first hires at a 3D print shop fall into one of three role categories. They look similar on a job posting but they're different jobs with different skill requirements and different failure modes.
The shop hand
Handles physical production tasks: bed leveling, print removal, support removal, light post-processing, packaging. Requires attention to detail and reliability, not technical depth. This is the most common first hire and the easiest to train. It also has the narrowest coverage: if your bottleneck includes file prep or printer troubleshooting, a shop hand doesn't solve it.
The production technician
Handles setup, slicing, print monitoring, basic troubleshooting, and quality control. Requires prior 3D printing experience or a steep learning curve you'll have to manage. Covers more of the production workflow, but the candidate pool is smaller and the wage floor is higher. Miscast shop hands in this role are the most common source of early hire failures.
The operations generalist
Handles a mix of production and administrative tasks: order intake, customer communication, job tracking, shipping. An experienced person in this role can help build processes, not just follow them, but only if you're present enough to shape what gets built. If you hand a disorganized operation to a generalist and step back, you get their system, not yours. This role works as a first hire when you have enough operational clarity to recognize good work. It fails when you're hoping the hire will provide that clarity for you.
List the 10 tasks you want this person to own. Assign each one to a category: physical production, technical production, or coordination. The category with the most tasks tells you which role you're actually hiring. If the coordination category dominates, re-read the operations generalist description before you post. That role has a prerequisite the other two don't. If the list spans all three, you're trying to hire two roles at once, and the hire will fail.
Contractor vs. Employee: The Actual Test
The contractor classification matters because misclassifying an employee as a contractor creates liability: back taxes, penalties, and potential state labor violations. It's not a technicality. The IRS and most state labor boards actively audit this, and small operators are not too small to be found.
The IRS uses a three-category test: behavioral control, financial control, and the type of relationship. In practice, for a 3D print shop, the questions that matter most are these:
| Question | Points to employee | Points to contractor |
|---|---|---|
| Do you control when and where they work? | Yes — set hours, your location | No — they set schedule, can work elsewhere |
| Do you control how they do the work? | Yes — you direct the method | No — you specify the result only |
| Do they work exclusively for you? | Yes, or primarily | No — multiple clients |
| Do you provide the tools and equipment? | Yes | No — they bring their own |
| Is the work ongoing vs. project-based? | Ongoing, recurring | Defined project or deliverable |
A shop hand working set hours at your location, using your equipment, doing ongoing production work is an employee. Calling them a contractor doesn't make them one. If every question in that table points to employee, you're hiring an employee.
There are legitimate contractor engagements in this business: a graphic designer handling customer file cleanup on a project basis, a bookkeeper working remotely for multiple clients, a part-time delivery driver with their own vehicle. Those arrangements can hold up. A recurring shop hand cannot.
The administrative consequence of hiring an employee is real but manageable: you need an EIN if you don't have one, a payroll provider, and a handle on your state's new hire reporting requirements. Services like Gusto, Rippling, and Patriot Payroll handle most of the compliance mechanics for under $50/month. That cost belongs in your burden rate calculation, covered in the next section.
What It Actually Costs
Operators consistently underestimate the cost of a hire because they anchor on the hourly wage. The wage is the floor, not the number.
The real cost is the wage plus employer-side taxes and required contributions, plus any benefits or allowances, plus the administrative overhead of payroll management, plus the productivity drag during the onboarding period. The combined number is called the burden rate, and for a part-time shop hire, it typically runs 20–30% above the base wage.
Most states require workers' comp coverage for any employee. Manufacturing and production classifications carry higher rates than office work. Budget $1.50–$4.00 per $100 of payroll depending on your state and classification code. For a $1,733/month wage, that's $26–$69/month. Get a quote before you finalize your cost estimate; rates vary significantly by state.
Onboarding drag is the cost that doesn't show up on any invoice. For the first four to six weeks, a new hire is absorbing your time, not freeing it. You're slower because you're training. Mistakes add rework. You're doing two jobs while trying to hand one off. Budget for this mentally: the break-even point on a hire is rarely before week six, and often closer to week ten for a production technician role.
Divide the total monthly burden cost by your revenue per owner-hour. That gives you the number of owner-hours per month the hire needs to free up for you to break even. At $1,973/month burden and $50/hr owner value, you need to recover roughly 40 hours per month — about 10 hours per week — to justify the cost. If the role you're describing doesn't free up that much time, the math doesn't work.
The First 90 Days as a Diagnostic
The standard framing for a new hire's first 90 days is onboarding: getting someone up to speed, building habits, and establishing expectations. That framing is fine for corporate roles. For a first hire at a small shop, it misses the more important function of the period.
The first 90 days are a test of whether the role you defined actually exists as you defined it. You will discover tasks you forgot to include. You will discover tasks you included that the person can't do. You will discover that some problems you thought were labor problems are actually process problems that a new hire exposes rather than solves.
Run the first 90 days as a structured diagnostic, not an orientation program.
-
01
Document every task you hand off in the first two weeks. Write the procedure before you teach it. If you can't write it down, you don't know it well enough to delegate it, and training will take twice as long.
-
02
Track your own hours weekly throughout the period. The point of the hire is to change how you spend your time. If your hours look the same at week eight as they did before the hire, something is wrong: the role is miscast, the handoff isn't happening, or the process you're handing off doesn't exist yet.
-
03
Set a 30-day and 60-day checkpoint, not just a 90-day review. The 30-day checkpoint is process quality: can they execute the core tasks without supervision? The 60-day checkpoint is reliability: are they executing consistently, or are you still catching errors? The 90-day review is a capacity question: has the time you expected to recover actually been recovered?
-
04
If the 60-day checkpoint fails, diagnose before you decide. Persistent errors at 60 days usually indicate one of three things: wrong person for the role, wrong role definition, or missing process documentation that makes the task undoable consistently. The first is a personnel issue. The second and third are on you.
A hire that makes it to 90 days with clean checkpoints is a hire that worked. One that does not tells you something specific and fixable, either about the person or about the operation they were hired into.
The Software Implication
Going from solo operator to a two-person shop changes your operational software requirements in a specific way: everything that lived in your head needs to live somewhere else.
When you're the only person in the shop, you can carry job status, material inventory, print queues, QC checkpoints, and packaging instructions in working memory. The moment someone else needs to act on that information without asking you first, it needs to exist in a system.
Before the hire starts, audit your processes against one question: can a trained person follow this without asking me? If the answer is no for any core workflow, fix it before day one. Adding a person to a process that isn't documented isn't delegation. It's a more expensive version of the same problem.
The same applies to your tools. A tool that works for one person often breaks the moment a second person needs to act on its outputs without asking you what something means. The stack builder on this site includes a filter for team-size scenarios if you're evaluating whether your current stack supports the transition.