Skip to content
Growth · 18 min read

Should You Hire Your First Helper? A Six-Question Decision Tree for Solo Makers

A solo-maker decision framework for the first hire. Six questions cover revenue floor, hours-per-week, the real bottleneck, contractor vs. W-2 reality, family-hire pitfalls, and whether you can give up control of the thing you are handing off.

A maker and a helper smiling as they examine a small device together at a workshop bench, with a pegboard wall of organized hand tools and parts shelving in the background

A year from now, you'll either be running the same business with the same helper, the same shoulder ache, and the same Sunday-night packing marathon — or you'll be doing one of two completely different things. You'll have hired someone, and you'll have spent six months figuring out what it actually changed. Or you'll have hired someone, decided it was the wrong call, and spent six months figuring out that. Both versions teach you something. The second one teaches it more expensively.

The decision to make a first hire is the most asymmetric one in a maker business. Get it right and you buy back twelve hours a week, ship orders before the customer asks where they are, and stop being the bottleneck on your own growth. Get it wrong and you've added a payroll line, a tax form, a difficult conversation, and a person who is now in your kitchen on Tuesday afternoons asking what the wifi password is. The asymmetry is what makes everyone agonize over it. The asymmetry is also what makes the decision deserve a real framework, not just a vibes check.

Most "should I hire?" advice is written for tech founders or restaurant owners. It assumes your business has things called "departments" and "roles" and a payroll service that arrived pre-installed. None of that applies to a person who finishes a custom order at 11pm and then wonders if they should hire someone to "help with the business." This is for that person.

The short version: Hire your first helper when (1) trailing-twelve revenue is at least ~$60K with consistent demand, (2) you are turning down work or compressing personal hours, (3) there's one specific 8+ hour/week task that someone else could do without your supervision, (4) you can clear ~$2-4K/month for a contractor without the math going red, (5) you've decided what "done well" looks like in writing, and (6) you genuinely believe you can let go of the thing you're handing off. Six yeses means hire. Anything less means there's a different problem to solve first.

Why "I need help" isn't the same as "I should hire someone"

Almost every maker who tells me they need to hire is actually saying one of three things, only one of which is solved by hiring.

The first is I have too much demand. This one's the easiest to diagnose because it shows up as a calendar with no gaps and a backlog you keep apologizing for. Hiring genuinely helps, assuming the demand is durable and not the December spike you mistook for the new normal.

The second is I am doing the wrong tasks. This one looks the same from the outside — overwhelmed, behind schedule, working past dinner — but the fix isn't a hire. The fix is killing or automating tasks that shouldn't exist in the first place. The Etsy seller who manually copies order details into a spreadsheet for ninety minutes a day doesn't need a helper. They need the spreadsheet to die.

The third is I want company. Working alone in a garage workshop is genuinely lonely, and the impulse to hire someone is sometimes the impulse to have a coworker. This is a real problem and a hire might solve it, but you should be honest with yourself about what you're buying. A 12-hour-a-week contractor isn't a coworker. They're a contractor. The loneliness will still be there at 2pm on Wednesday.

Rule of thumb: Before you make a hire, spend two weeks writing down every task you do and how long it took. If 30%+ of your week is tasks that shouldn't exist, fix that first. Hiring someone to do unnecessary work is just paying to scale the unnecessary work.

The decision tree below assumes you've ruled out the second and third versions. If after reading the next section you realize you're actually in one of those buckets — congratulations, you just saved $1,800 a month and a difficult conversation.

Question 1: Is your trailing-twelve revenue at least ~$60K with consistent demand?

Pick a number. Any number. The number people pick for "when should I hire" is almost always wrong, because it's based on a feeling, not on what a contractor actually costs.

Here's the math. A part-time contractor at 10-15 hours a week, paid $22/hour, costs you roughly $1,000-1,400 a month. Add 10-15% for tools, supplies they'll consume during ramp-up, and the small amount of administrative overhead that comes with a 1099. Round to $1,500/month, or $18,000/year, for a modest first hire.

If your trailing-twelve revenue is $40,000, that helper just consumed 45% of revenue. Your COGS, fees, and material costs already eat 50-65% of revenue in most maker businesses. The math doesn't work — not even close.

At $60K trailing-twelve, $18K helper = 30% of revenue. Still tight, but feasible if your gross margins are healthy. At $90K, helper = 20%. Now we're talking.

Rule of thumb: Your first hire should cost no more than ~25% of trailing-twelve revenue. If they cost more, your problem isn't lack of help. It's that the business hasn't grown into a hire yet, and you'd be hiring on hope.

A baker who does $80K but earns 60% of it in November and December has a different problem than one who does $80K spread evenly. The seasonal baker can't really hire year-round help on $80K — they need a temporary holiday hire, which is a different decision (and a much easier one). Look at your slowest three consecutive months. Could you afford a helper at that revenue level? If the answer is "only if I dip into savings," you're not ready.

Question 2: Are you turning down work or compressing personal hours?

This is the demand test. The reason you hire someone is to remove a constraint, and a constraint only deserves to be removed if it's actually costing you something measurable.

Two things qualify as evidence:

You are turning down work you would have taken. Custom orders you said no to. Wholesale inquiries you didn't reply to because you couldn't fulfill them. Markets you didn't apply to because you couldn't prep enough stock. Write the list. If it's empty, you don't have a demand constraint — you have a workflow problem, which is Question 1's other version.

You are compressing personal hours below sustainable. Working past 9pm three nights a week. Skipping the gym for two months. Canceling on people. Your spouse using the phrase "you're never around." This is real, and it's the more common reason for a first hire — but it's also the one most likely to trick you, because the answer might still not be hiring. The answer might be charging more, doing fewer SKUs, or stopping the side gig that's eating your evenings.

Rule of thumb: If you can name three specific opportunities you turned down in the last 90 days because you couldn't fulfill them, that's a demand constraint worth solving. If you can't name three, you might just be tired.

Before you hire, ask if a 15% price increase would solve it. Higher prices reduce demand to a level you can actually fulfill, raise margin per unit, and make the eventual hire cheaper-as-a-percentage. A maker who raises prices 15% and loses 10% of customers usually ends up with the same revenue, less work, and a healthier margin. Sometimes the right "first hire" is a price tag.

Question 3: Is there one specific 8+ hour/week task that someone else could do without your supervision?

This is the one most people get wrong. They imagine "having help" as a vague improvement to their life. But hiring isn't help-in-general. Hiring is a specific person doing a specific task on a specific schedule.

Run the time-and-energy audit:

For two weeks, log every task that takes more than 30 minutes. At the end, rate each one on two axes — 1 to 5 — and find the cells that light up:

Enjoy doing it Don't enjoy doing it
Requires you specifically Keep doing it. This is the work. Find a way to make it tolerable, or restructure the business so it happens less often.
Doesn't require you specifically Optional delegation — but you'll miss it. Be honest. First delegation candidate. Hire here.

The bottom-right is your hire. For most solo makers, the recurring inhabitants of that quadrant are: order packing and shipping, market booth setup and teardown, basic bookkeeping reconciliation, ingredient or material restocking errands, and photo editing for new listings. None of these are glamorous. All of them eat 6-15 hours a week.

Rule of thumb: A delegate-able task is one you could write down in a one-page SOP. If you can't write the SOP — because the task is "checking on things" or "noticing what needs doing" — it's not delegate-able. That's still you.

A surprising number of first hires fail because the maker delegated the wrong task — usually because they hired for "the obvious bottleneck" without admitting which task was their actual joy. Soap maker hires a packer to free up time, then realizes packing was the meditative part of her week and she now hates her own business. Talk to yourself honestly about which tasks fill the well versus drain it. Delegate from the drain side.

Question 4: Have you decided whether it's a contractor or an employee — and do you know why?

For 95% of first hires, the answer is contractor. A 1099 contractor is dramatically simpler from a tax and compliance standpoint — no payroll taxes withheld, no workers comp in most states, no unemployment insurance, no W-2 to file. You write a check or send a transfer; they handle their own taxes; you issue a 1099-NEC at year end if you paid them more than $600.

But "contractor" isn't a label you can just stick on someone. The IRS has a multi-factor test, and the consequences of getting it wrong — having a "contractor" reclassified as an employee — include back payroll taxes, penalties, and (in some states) substantially more pain. The relevant short version:

  • Contractors set their own hours, work location, and methods. Employees follow yours.
  • Contractors typically have other clients. Employees usually don't.
  • Contractors provide their own tools when feasible. Employees use yours.
  • Contractors are paid per project or per hour with no benefits. Employees get withholding and (often) benefits.

If you want someone in your workshop on Tuesday at 2pm, using your packing materials, doing tasks exactly the way you specify, with no other clients — congratulations, the IRS thinks that's an employee, regardless of what your contract says. If you can give the person a list of "ship these 40 orders by Friday" and not care when or where they work, that's a contractor.

Rule of thumb: Start with a contractor. Move to W-2 only when you need to control the work in ways the IRS contractor test would no longer allow. Most maker businesses can stay contractor-only for years — sometimes forever.

The version of this most makers actually live is: a friend or neighbor offers to "help out for a few hours a week" in exchange for cash, and there's no contract, no clear hours, and no written scope. This works fine right up until the moment it doesn't — when the friend gets injured in your workshop, or when their spouse loses a job and "casual help" is suddenly their only income, or when you need to end the arrangement and can't because you've never had a clear conversation about what it was. Even informal first hires deserve a one-page written agreement. Especially informal first hires.

Question 5: If you're hiring family, have you written a one-page agreement?

Your spouse, your sibling, your mother-in-law, your 17-year-old kid — at some point most maker businesses end up paying a family member to help. Sometimes it works beautifully. Often it doesn't, and the failure mode is uniquely awful: you can't fire them without ruining a relationship, you can't give honest feedback without dinner getting weird, and the work quality slides because the consequences of poor work aren't real.

If you're hiring family, the one-page agreement isn't optional. It needs:

  1. Scope — exactly what tasks they're doing, exactly what they're not.
  2. Hours — how many, when, and what happens if they need to flex.
  3. Pay — the rate, the schedule, and what counts as billable. (Yes, the 14-year-old neighbor doing $12/hour packing on Saturdays needs this too.)
  4. A trial period — usually 30 days or 4-8 weeks of part-time work, after which both of you have an explicit "is this still working?" conversation.
  5. An exit clause — how either of you can end the arrangement with 2 weeks notice and no hard feelings, in writing, signed before the work starts.

The agreement is not for the times when things go well. It's for the moment six months in when you realize your sister-in-law has been doing the cake decorating tasks "her way" instead of yours and you don't know how to bring it up. The written agreement is the thing you point at instead of the conversation you've been avoiding.

Rule of thumb: The kindest thing you can do for a family member you're hiring is to make the relationship slightly more formal than it would be with a stranger, not less. The formality protects the friendship.

Question 6: Can you actually let go of the thing you're handing off?

The last question is the one that fails the most first hires, and it has nothing to do with money or law. It's about whether you can hand a task to another human and not micromanage it back into your own column.

Three honest tests:

The "good enough" test. If your contractor packs an order 90% as well as you would, and the customer doesn't complain, can you live with that? If your honest answer is "no, I'd repack it after they leave," you're not ready to delegate. You're ready to hire a coworker who does it your way, which is a different and much harder hire.

The "wrong way" test. Your helper is going to do things differently than you do. Some of their ways will be worse. Some will be better. Some will be neither — just different. Can you let "different" be okay? The packer who folds tissue paper the wrong direction is not actually costing you anything. Pick the battles you actually care about and let the rest go.

The "I would do it myself faster" test. This is the trap that kills the most hires. For the first 30-60 days, the contractor is slower than you are. They're learning your products, your process, your customers. If you take the work back every time they're slower than you'd be, they will never get faster, and you'll have paid them to learn things you then refused to let them apply. The whole point of a hire is to let them be slower than you for a while so they can be as fast as you later.

Rule of thumb: If you imagine handing off a task and your gut says "but they won't do it right," the issue isn't the contractor you haven't hired yet. It's that you haven't decided what "right" actually means — and until you do, no hire will satisfy you.

The single best preparation for a first hire is writing the SOP for the task you'll delegate, before you hire anyone. Not a vague "this is how I do it" — a step-by-step document a stranger could follow. If you can write the SOP, the task is delegate-able and you've already done the hardest part of training. If you sit down to write it and realize you can't — because every order is different, because "you just know" how much fragrance to add, because the steps depend on context only you have — that's diagnostic. The task isn't ready to be handed off, and neither are you.

What "yes" looks like — and what to do next

Six yeses on the questions above means hire. Here's the unromantic version of the next 30 days:

  1. Write the SOP for the task you're handing off. One page. A stranger could follow it.
  2. Define what "done well" looks like. Specific. Measurable. The kind of thing you could grade on a 1-5 scale.
  3. Write a one-page contractor agreement. Scope, hours, pay rate, trial period, exit clause.
  4. Set the trial period. Typically 30 days or 4-8 weeks of part-time work. Tell the candidate, in writing, that this is what it is.
  5. Find one candidate and hire them. Not three. One. You're testing whether having help solves your problem, not building a team.
  6. At the end of the trial, have an explicit conversation. Working? Continue. Not working? End it on the agreed terms. No hard feelings, both because the agreement protects everyone and because you both knew this was a trial.

The thing nobody tells you about your first hire is that the first month feels worse, not better. You're training someone, redoing things, explaining your business out loud for the first time. Then somewhere around week 5-8, you wake up on a Sunday morning and realize you didn't pack any orders the day before, and the orders shipped anyway. That's the moment. That's what you're paying for.

What "no" looks like (and that's also a real answer)

If you got fewer than six yeses, the right move is to figure out which question failed and address that — not to hire anyway and hope. The translations:

  • Failed Q1 (revenue): Grow the business another 6-12 months before hiring. Use the time to fix pricing and margins so the eventual hire fits comfortably.
  • Failed Q2 (demand): Either there isn't enough demand or you're tired-but-not-overloaded. Take a real week off, then re-evaluate. If you come back rested and still feel overwhelmed, it's a hire signal. If you come back rested and feel fine, the problem was rest, not staffing.
  • Failed Q3 (delegate-able task): Your bottleneck is something only you can do. Hiring won't fix that — restructuring will. What's the smallest change that makes the bottleneck task itself less central?
  • Failed Q4 (contractor vs. W-2 confusion): Read up before you hire. Misclassifying a worker is one of the genuinely expensive mistakes a small business can make.
  • Failed Q5 (family agreement): Write the agreement, then proceed. Don't skip this one.
  • Failed Q6 (control): Most common failure. Spend 60 days learning to delegate to yourself — write SOPs, define "done," let yourself ship work that's 90% as good as the platonic ideal. If you can't do that for yourself, you definitely can't do it for someone else.

Where the right tools cut the decision in half

A surprising amount of the "should I hire" anxiety dissolves when the operational backbone of the business is good. If your inventory is tracked accurately, your orders flow through one system, your COGS are real numbers and not vibes, and a new helper can sit down and see the state of the business — the hire is easy. They have a map. They know what's done and what isn't.

If your operational backbone is six spreadsheets, a Notion page from 2023, and a notebook on your workbench, even the perfect hire will struggle, because half of what you need to delegate is knowledge that lives in your head. They'll spend their first month asking you questions that are technically just lookups in systems you don't have.

This is where Ardent Seller earns its place — it gives a small maker business a single backbone for inventory, recipes, transactions, and reporting, so a new helper can actually see what's going on without translating from your spreadsheet dialect. The features list walks through what a helper would actually be looking at on day one. If you're heading into a first hire and your systems are a patchwork, the cleanest order of operations is: tighten the systems first, then hire. The hire will go better and the trial period will tell you the truth faster.

  • Spreadsheet Breakup — Most "should I hire" conversations are actually "should I leave my spreadsheet" conversations in disguise. Read this first if your operational backbone is a patchwork.
  • Scaling a Handmade Business: What Breaks at Each Stage — Stage-by-stage map of what breaks when you grow from 10 to 100 orders/week. The first-hire decision is one entry on a longer list.
  • Cash Flow for Seasonal Sellers — Before you commit to a recurring monthly contractor cost, make sure your slowest three months can carry it.

Free resources

A few free downloads from the Ardent Workshop library that pair well with this post:

This article is provided for educational purposes only and does not constitute legal, tax, or accounting advice. Worker classification rules (contractor vs. employee), payroll tax obligations, and state-level employment law vary by jurisdiction and change frequently. The IRS contractor test, state-specific worker classification standards (such as California's ABC test), and family-employment rules can have significant tax and legal consequences if applied incorrectly. Consult a qualified CPA, employment attorney, or small-business advisor before making hiring decisions for your business.