The Week You Realize You Can't Do This Alone
It usually shows up as a specific, ugly moment: you're answering customer emails at 11 p.m. because you spent the day on a client call, then invoicing, then packaging orders, and somewhere in there you missed a payment deadline that cost you a small late fee you can't stop thinking about. That's the week most founders start Googling "when to hire your first employee" — not because a business book told them to, but because the math on their own hours stopped working. If you're circling that same question, the honest answer is: you should have hired six weeks ago, and the delay is costing you more than the hire would.
Hiring is where a lot of women-led businesses stall, and not because of ambition — plenty of founders will tell you they're more comfortable pitching a $50,000 client than posting a job listing. Part of it is real: a bad hire is expensive, both in dollars and in the emotional tax of managing someone who isn't working out. But waiting too long is its own cost, and it's a quieter one — it shows up as missed deadlines, as the client you didn't have bandwidth to pursue, as burnout that eventually forces the decision anyway, just later and under worse conditions.
Employee or Contractor? Get This Wrong and the IRS Notices
Before you write a job post, decide whether you're hiring an employee or a contractor — this isn't a style preference, it's a legal classification with real consequences. The IRS uses a behavioral-control test: if you set the person's hours, tell them how to do the work, provide their equipment, and expect them exclusively for you, that's an employee, regardless of what the contract says. Misclassify someone and you're looking at back payroll taxes, penalties, and in some states — California's AB5 is the strictest example — a much narrower path to calling anyone a 1099 contractor at all.
Choose the contractor route only if the work is genuinely project-based and the person has other clients. A freelance graphic designer who does your logo and three brochures over two months is a contractor. The person answering your customer service inbox forty hours a week on your schedule is an employee, and treating her as a 1099 to dodge payroll taxes is the single most common — and most audited — mistake first-time employers make.
The Paperwork Nobody Warns You About
Before your first hire's start date, you need an Employer Identification Number from the IRS (free, takes about ten minutes online), state and federal payroll tax registration, and workers' compensation insurance — mandatory in every state except Texas, and even there most employers carry it anyway. You'll also need to register for unemployment insurance in your state, which usually happens automatically once you register as an employer.
- Form W-4 (federal withholding) — collected before day one
- Form I-9 (employment eligibility) — must be completed within three business days of the start date, and the penalty for late or missing I-9s runs into thousands of dollars per violation
- State new-hire reporting — most states require this within 20 days of the hire date
- A payroll system that actually withholds and remits taxes on schedule, because doing it manually in a spreadsheet is how founders end up owing the IRS with interest
Gusto and QuickBooks Payroll both run about $40–$80 a month for a one-person payroll and handle the tax filings automatically — pay for one of these. Don't try to run payroll by hand out of a sense of frugality; the IRS penalty for a missed deposit deadline starts at 2% and climbs to 15% the longer it goes unpaid, and that's before you've paid a cent toward the actual tax owed.
Where to Actually Find Your First Hire
Skip the big job boards for your first hire — Indeed and LinkedIn work fine for role number five, but for role number one, your network will outperform a stranger's resume almost every time. Post in founder communities specific to your industry, ask your accountant or your first clients if they know anyone, and be explicit about what you need rather than posting a generic "virtual assistant wanted" ad that will pull in two hundred low-effort applications. A founder we'd point to as doing this right posted in a regional women's business Slack with the exact task list — "12 hours a week managing Etsy order fulfillment and customer messages, $22/hour" — and had three qualified applicants within two days.
If you do go broader, write the job post around the actual work, not a title. "Handles 15–20 customer emails a day, updates our inventory spreadsheet every Friday, ships orders by 3 p.m." tells an applicant far more than "Customer Success Associate" ever will, and it filters out people who can't picture themselves doing the specific thing you need done.
What to Pay, and How to Talk About Money
Undervaluing the first hire is nearly as common a mistake as skipping payroll taxes, and it's the one that costs you the good candidates. Check your state and city minimum wage before you post anything — several states, including California, Washington, and New York, sit well above the federal $7.25 floor, some above $16 an hour, and local minimum wage ordinances in cities like Seattle and San Francisco go higher still. Price the role against what similar work actually pays in your metro area (Glassdoor and Payscale both give reasonable local ranges), not against what you wish you could afford.
Here's the part nobody says out loud: pay a little above market for your very first hire, even if it stretches the budget. The person willing to join a one-person operation with no track record is taking a real risk on you, and underpaying that risk-taking almost guarantees turnover within six months — which then costs you the recruiting time all over again, plus the disruption of retraining.
Interview Questions That Actually Predict Something
Skip "tell me about your greatest weakness" — it tells you nothing and everyone has a rehearsed answer. Ask instead about a real situation close to the job: "A customer emails angry about a late shipment that genuinely was our fault. Walk me through exactly what you'd write back." You're not grading for the perfect answer; you're watching for whether the candidate takes ownership, stays calm, and thinks about the customer relationship rather than just closing the ticket.
A second question worth asking every candidate: "What's something at your last job you disagreed with and did anyway?" The answer tells you whether this person can follow direction without becoming either a pushover or someone who quietly undermines decisions they don't like — both are landmines in a two-person company where there's no HR department to mediate later.
Making the Offer and the First 90 Days
Put the offer in writing, even for an hourly role — pay rate, hours, start date, and whether the position is at-will (it almost certainly is, unless you're in Montana, the one state without at-will employment as the default). Verbal agreements about "we'll figure out the details" are how founders end up in disputes over unpaid overtime, because the Fair Labor Standards Act still applies to a business with one employee, and nonexempt hourly workers are entitled to overtime pay past 40 hours a week regardless of company size.
The first 90 days matter more than the interview did. Set a real first-week plan instead of throwing your new hire straight into the deep end and hoping instinct fills the gaps — write down the three things you most need them to own by day 30, and check in weekly, not just when something goes wrong. Most first-hire relationships that fail don't fail because the person was wrong for the job; they fail because nobody defined what success looked like, so six months in, both sides are frustrated by expectations neither ever said out loud.
If It's Not Working, Don't Wait Three Months to Say So
Most states default to at-will employment, which means you can end the relationship without a formal disciplinary process — but that legal freedom doesn't mean you should skip having the conversation early. If the fit is wrong, you'll usually know inside the first three or four weeks: missed deadlines that don't improve after one clear correction, customer complaints that repeat, or a gap between what was promised in the interview and what shows up on the job. Waiting it out because letting someone go feels harsh only compounds the cost — you're paying wages for work you're redoing yourself anyway, and the eventual conversation gets harder, not easier, the longer you postpone it.
Document the specific issue and the correction you asked for, even in an informal note to yourself — not because you expect a lawsuit, but because clear documentation protects you if a wrongful-termination claim ever does surface, and because it forces you to be precise about what actually went wrong rather than acting on a vague feeling. Then act. A founder who lets a bad fit run three extra months isn't being kind; she's usually just avoiding an uncomfortable ten-minute conversation, and her business pays the difference.