It's 11pm and you're catching up on invoices again, because every daylight hour went to clients and putting out fires.
You've known for months that you need help.
But figuring out how to hire your first employee feels like a second job. Payroll, paperwork, interviews, and the terrifying math of committing to someone's salary before you're sure the work will keep coming.
Here's the thing you may not realize: the paperwork is one afternoon.
The part that actually determines whether this new hire actually works is the part that most guides, articles, and playbooks skip.
It’s making sure the role you’re hiring for is the actual right role, and then building a way to evaluate strangers when you've never hired anyone in your entire life.
I've made 100+ hires over 20+ years at The Motley Fool, The Hustle, HubSpot, and Hampton.
And this is the sequence I've been using for two decades, and still the same one I’d run if I were making hire #1 tomorrow.
The short version: hiring your first employee takes seven steps. Define the problem, handle the legal setup (EIN, state registration, workers' comp, payroll, I-9 and W-4), write a job description that filters, require a 3-minute video, interview with a scorecard, check references, and make the offer with a 90-day bar. Budget three to six weeks.
Are you actually ready to hire?
Three tests. You need all three:
The overflow test. You're turning away work or letting quality slip. Consistently, for 2 or 3 months, not one busy stretch.
The runway test. You can cover this new hires salary for six months even if revenue stays flat. If a slow month means you can't make payroll, you'll resent the hire by week six. I've watched founders hit that wall, and the resentment lands on the employee who did nothing wrong.
The definition test. You can name the specific work you'd hand over. "I need help" is not a role. A list of tasks currently eating 25 hours of your week is.
And one piece of honesty before you start: nobody will ever care about your business the way you do. That's not a reason to stay solo. It's the reason you need a process instead of a feeling, because employees don't need your obsession.
They need a well-defined job.
Step 1: Define the problem before the role
Before you write a word of the job description, answer five questions:
What specific problems am I trying to solve? Not "I need help." What's falling through the cracks? Write it down.
What does success look like in 90 days? What metrics move? What pain goes away?
What level of seniority does this actually require? Most first-time hirers overshoot. You probably need a strong executor, not a "manager."
Is this a full-time role, or could it be solved another way? A contractor for 90 days? An agency for one function? Sometimes the honest answer to "how do I hire?" is "not yet."
Can I explain this role to someone in 30 seconds? If not, you're not ready to post it.
If you can't answer all five, the job description (JD) will be vague.
And if the JD is vague, the hire will be wrong. Everything downstream inherits from this step.
(These five questions are Step 1 of Start the Hire, a free fillable workbook. Answer them in there before you go further.)
Step 2: Handle the legal setup in one afternoon
This is the part that stops most owners for months.
But it shouldn't. In most states it's genuinely an afternoon:
Get an EIN. Free, from the IRS, takes minutes online.
Register with your state's labor department for unemployment insurance and new-hire reporting.
Get workers' compensation insurance. Required in nearly every state once you have one employee.
Pick a payroll provider. Gusto, OnPay, QuickBooks, doesn't matter much at one employee. It calculates withholding and files the forms so you never think about them.
Have the new-hire forms ready. I-9 and W-4, both completed on day one.
File the new-hire report with your state. Your payroll provider usually does this.
That's the whole compliance side.
The SBA's hiring guide covers state-level specifics. Do this in parallel with your search, not as a reason to delay it.
Step 3: Write a job description that really filters
A JD is not a wish list. It's a filter.
Lead with the problems this person will own and what success looks like at 90 days. Make sure it details outcomes, not just a laundry list of duties.
Publish the pay range. So many founders don’t include the pay range because they’re hoping to find someone amazing for very little pay.
Trust me, it doesn’t happen.
You'll lose candidates at the offer stage anyway if the number you’re willing to pay was never viable, so lose them at hour zero instead of week three.
And write like a human. "Fast-growing company seeks rockstar" attracts exactly nobody good.
And remember, a great JD shouldn’t just attract candidates; it should also deter other candidates.
Be as specific as possible!
Step 4: Add the Mandatory Video ask
This is the highest-signal move available to a first-time hirer, because it requires zero hiring experience to use.
Add one line to your application: "Record a 3-minute video introducing yourself. Tell us why you're excited about this role, and a few things we should know about you, professionally and personally."
Three minutes of a video shows you communication, initiative, energy, and whether they bothered to learn what your company does. And most weak applicants, the ones who applied to 200 jobs this week, simply won't do it.
Your applicant pile will shrink by more than half.
Everything left is someone who actually wants this job. When you have no screening infrastructure, this is your screening infrastructure.
Step 5: Interview with a scorecard
You don't yet have pattern recognition from hundreds of interviews, which is fine — a structured scorecard substitutes for it.
Pick the three competencies that decide this role. Score every candidate on each, minus-2 to plus-2, and require evidence for every score. Something the candidate said or did, not something you felt.
Ask evidence questions. "Walk me through the last time you did the actual work" beats "how would you handle it," because the past tense is much harder to fake.
70% of the questions should be the exact same across every candidate, and 30% can be customized to their specific experience.
Step 6: Check references like you mean it
Fifteen minutes per finalist. Three questions minimum:
Would you hire this person again?
What kind of environment do they struggle in?
Where do they rank against others you've managed in similar roles?
Then listen for temperature. References almost never say negative things outright. They go quiet, or generic, or polite. Tepid is a warning.
Step 7: Make the offer and set the 90-day bar
Move fast. Days, not weeks.
Send a written offer: title, pay, start date, hours, at-will status (in the US), and any contingencies.
Then, before day one, write down what a successful first 30, 60, and 90 days looks like, and share it with them in week one. You already defined 90-day success back in Step 1. Now it becomes their operating map, and your early-warning system if the hire is going sideways.
What your first hire actually costs
Rule of thumb: budget roughly 1.25 to 1.4 times the salary for the true cost. BLS data puts the mandatory piece (Social Security, Medicare, unemployment, workers' comp) at about 10% of wages on its own. Tools, software, and whatever benefits you offer are what push it toward the top of that range.
But the number that should actually concern you is the cost of the wrong first hire. Months of wages producing rework, your time managing someone who isn't working out, severance, and starting over. At any meaningful salary, a failed first hire is a five-to-six-figure mistake for a small company.
That's why the process above is worth an afternoon of setup.
Before your first hire, fill this out: Start the Hire (free)
You don’t have hiring reps yet. This replaces them with structure: define the role, lock your non-negotiables, write a JD that sells, and the 10 Red Flags to check every candidate against. Three steps, one sitting, free.
FAQ: hiring your first employee
What paperwork do I need to hire my first employee? EIN, state employer registration, workers' comp policy, a payroll setup, and completed I-9 and W-4 forms on day one. Your payroll provider handles ongoing filings.
Should my first hire be an employee or a contractor? If the work is ongoing, done your way, on your schedule, that's an employee. Misclassifying carries real penalties. If it's a defined project or a specialty function, start with a contractor. Revisit Step 1, question 4: sometimes the right first "hire" isn't a hire.
How long does it take to hire a first employee? With this process: 3-6 weeks from posting to start date. Industry benchmarks run longer. SHRM puts the median near 39 days just to an accepted offer, and Greenhouse's data has time-to-fill approaching 60 days and climbing. Those are companies that already have a process.
What if I hire the wrong person? Act on evidence, early. That's what the 30/60/90 map from Step 7 is for. If the 30-day bar is missed and the 60-day bar is trending the same way, have the direct conversation then, not at month six. A wrong first hire corrected in 60 days is a bruise. One carried for a year is the $100K mistake.
Do I need an employment contract? In most US states, employment is at-will, and a signed offer letter plus a simple handbook acknowledgment covers hire #1. Add an IP-assignment and confidentiality agreement if the role touches anything proprietary. When in doubt, one hour of an employment attorney's time now is the cheapest insurance you'll ever buy.
Jordan DiPietro has spent 20+ years hiring for The Motley Fool, The Hustle, HubSpot, and Hampton, and is the creator of Hiring OS, the opinionated hiring system for growth-stage founders.
Related reading:
Looking For More?
—> Here are 3 ways I can help you:
