Mintlify powers documentation for 20,000+ companies reaching 100M+ people a year. Backed by a16z and Salesforce Ventures. Your docs deserve the same infrastructure.

Get Started for Free Today

The first real hire I made in my business was a disaster.

On paper, she was perfect. Eight years of experience in the exact industry I was serving. Strong references. Articulate in the interview. Came recommended by someone I trusted. I hired her as a client success manager, thinking I was finally going to get some of my time back.

Three months later I was working more hours than before, constantly re-doing her work, and the client renewals she was supposed to be managing had started to slip. I let her go on a rainy Tuesday and spent the rest of the month cleaning up what had unraveled. The total cost of that hire, including salary, onboarding time, and client churn, was north of 40,000 dollars.

The problem was not her. She was qualified. She had done this work before. The problem was that I hired a resume instead of hiring a role. I thought I knew what I needed, and I used her background to confirm the story I had already written in my head. I never actually mapped out what the role was supposed to do, what a good outcome looked like, or what specific outputs I was trying to buy.

Every founder I talk to who has made bad hires made the same mistake. They hired a title, not a function. They hired a skill set, not a deliverable. They hired a person, not a position.

The Difference Between A Resume And A Role

A resume is a list of things a person has done before. A role is a list of things you need to happen going forward. These are not the same thing, and conflating them is the single most expensive mistake in small-business hiring.

When you hire a resume, you read through the candidate’s background, find patterns that match what you think you need, and hope the experience transfers. The problem is that past performance in one environment rarely predicts future performance in yours. A marketing manager who crushed it at a 50-person SaaS company may be completely lost in a 3-person service business with no marketing infrastructure in place.

When you hire a role, you start with the function you need the role to perform. You write out the specific outputs the role must produce in its first 90 days. You describe the environment the person will work in. You define what success looks like in measurable terms. Then you evaluate candidates against that definition, not against their prior job titles.

The shift sounds subtle but the effect is massive. Hiring for a role forces you to design the role before you start looking for the person. That design process alone will save you tens of thousands of dollars in mis-hires, because half the time you realize the role you thought you were hiring for does not actually need to exist.

The Role Scorecard

Before I start any hiring process now, I build a role scorecard. It is a one-page document that lives before the job description, and it is the most valuable piece of paper in the entire hiring pipeline.

The scorecard has four sections.

Mission. One sentence that describes why this role exists in your business. Not what the person does. Why the role is needed. Something like: this role exists to ensure every client who signs with us completes their onboarding within seven days, fully configured and ready to run. That is a mission. It is clear, specific, and measurable.

Outcomes. Three to five specific results the role must produce in the first 90 days. Each outcome is written as a completed result, not as an activity. Not manage the onboarding process but deliver at least 95 percent of new client onboardings within seven business days with zero configuration errors. The difference between an activity and an outcome is huge. Activities can be performed badly. Outcomes are either achieved or not.

Competencies. The specific skills, behaviors, and traits a person must demonstrate to produce those outcomes. Not generic stuff like team player or detail oriented. Specific things like: can build and maintain a Make.com scenario without supervision, or can resolve a confused client over email in fewer than three exchanges, or can operate with minimal structure and does not need daily check-ins to stay productive.

Non-negotiables. The dealbreakers. What must be true about this person or this role. Not in a nice-to-have sense, but in a the-hire-will-fail-without-this sense. This is the section most people skip, and it is the one that prevents bad hires more than any other.

Writing The Job Description From The Scorecard

Once the scorecard is built, the job description writes itself. You are no longer starting from a blank page trying to describe a role you have not yet fully defined. You are translating a specific, validated set of outcomes into a language that will attract the right candidates and repel the wrong ones.

A job description written from a scorecard looks dramatically different from a typical corporate listing. It names specific outcomes. It states measurable expectations. It names the tools the person will use. It says explicitly what the role is not. That last part is critical.

I had a marketing role open last year, and the first line of the job description after the role name was: this role is not a generalist marketing position, and you will not be running paid ads. We are hiring someone to own lifecycle email and nothing else. That single sentence cut my application volume in half and tripled the quality of the remaining applicants. The people who self-selected out were people who would have wasted my time and theirs by applying for something they did not actually want to do.

The Interview That Actually Predicts Performance

Most interviews are conversations about the past. Where did you work. What did you do there. What are your strengths. What is your biggest weakness. These questions feel important but they are astonishingly bad at predicting future performance.

The interview that actually predicts performance puts the candidate in a situation that looks like the work they will actually do. Not a puzzle. Not a personality test. A work sample.

For a marketing role, I send candidates a brief. A real brief, usually a lightly redacted version of something I would have sent an existing team member. Here is the situation, here is the goal, here is what you have to work with. Send me back what you would do. I pay them for their time because their time is worth money.

What I learn from that one exercise is more than I learn from five hours of interviewing. I see how they think. I see how they structure ambiguity. I see whether they ask clarifying questions before diving in. I see whether their writing is crisp. I see whether they have opinions or just regurgitate best practices.

For an operations role, the test looks different. I might share a messy scenario in my CRM and ask them to diagnose what is wrong and what they would do to fix it. For a client-facing role, I might send them a real customer email that is frustrated and ambiguous and ask them to draft a response. The medium changes. The principle does not. Watch them do the work.

The Hire-Slow, Fire-Fast Rule Is Lying To You

You have heard the cliche. Hire slow, fire fast. It sounds wise. It is half right.

You should hire carefully. But slow is not the same as careful. A careful hiring process that takes three weeks is not better than a careful hiring process that takes three months. The extra time does not add rigor. It adds inertia, second-guessing, and opportunity cost.

The real rule is: hire carefully, validate quickly, and act on what you see. Once someone is in the seat, the first 60 days should include clear checkpoints where you are actively asking the question: is this role being performed the way the scorecard said it needed to be performed. If the answer is yes, you move forward with confidence. If the answer is no, you do not wait six more months hoping things turn around. You address it immediately.

Most bad hires do not become bad slowly. They are recognizably mismatched within the first month. Founders talk themselves out of believing what they are seeing because firing someone feels worse than watching the role underperform. That calculus is backwards. The pain of firing a mismatch in month two is a fraction of the pain of firing them in month eight.

The Tools That Make Role-Based Hiring Work

The administrative side of hiring is where most founders lose steam. Writing the role. Posting the role. Reviewing applications. Scheduling interviews. Sending work samples. Collecting feedback. It is a lot of moving parts for someone who is already running a business. I run my whole hiring pipeline through Go High Level with a dedicated pipeline for candidates, stages for each step of the process, and automated communication that moves candidates through the funnel without my direct involvement. Application received. Work sample sent. Work sample reviewed. Interview scheduled. Decision made. Offer delivered. Each stage has its own automation, which means the only thing I am doing manually is the substantive evaluation itself.

For the work sample review, Fathom comes into play again when candidates do a live interview. I can go back to the recording and compare what they said to what they delivered in their written work sample. Are they congruent. Do they answer questions the same way verbally and in writing. Inconsistencies between the two are almost always a signal of someone who is performing for the interview rather than being themselves.

What Happens When You Hire Roles Consistently

The compounding benefit of hiring for roles instead of resumes shows up about a year in. Your team functions more predictably because every position is designed around outcomes. Handoffs between roles are cleaner because each role’s outputs are documented. New hires ramp faster because the scorecard gives them a crystal clear target from day one.

But the biggest shift is in how you think about your own time. Once you have designed a few roles well, you start seeing your own workload differently. You notice which of your hours are being spent producing a scorecard-level outcome and which are being spent on activity without a corresponding result. That awareness is the first step toward being able to hand off your own work thoughtfully instead of dumping tasks on a team that does not have a clear target.

This is the part where founder-led businesses become operator-led businesses. Not when you add bodies, but when you start designing what the bodies are supposed to produce.

The First 90 Days Matter More Than The Hire Itself

Every good hire I have ever made was obvious by day 60. Every bad hire I have ever made was also obvious by day 60, and I ignored it until day 150, and by then the damage was significantly worse.

The first 90 days of a hire is not orientation. It is validation. You are actively testing whether the role you designed on paper is being performed the way you intended, by the person you selected to perform it. This requires structure, and most founders treat the first 90 days as a kind of honeymoon period where they do not want to be too critical or demanding.

That instinct is wrong. The kindest thing you can do for a new hire is be ruthlessly clear about whether they are meeting the bar. Not in a punitive way. In a collaborative way. Every two weeks for the first 90 days, you sit with them and walk through the scorecard. Are we on track for each outcome. What is blocking progress. What do we need to adjust.

This level of structure does two things at once. It gives you enough signal to catch a mis-hire early, when the cost is contained. It also gives the new hire enough feedback to either course-correct if they are drifting or feel validated if they are on track. Both outcomes are better than the default, which is usually a vague sense that things are either working or not, and no clear data to act on.

By day 90, you should be able to say one of two things with confidence. Either this person is executing the scorecard as designed, and we can now ease off the structured review cadence. Or this person is not executing the scorecard as designed, and we need to decide whether to invest in a coaching plan or part ways. The answer should not be: I am not sure yet. If you are not sure by day 90, your review process was not rigorous enough.

What Role-Based Hiring Does For Your Own Role

There is a secondary benefit to this approach that nobody tells you about when you start. When you get good at designing roles for other people to fill, you start seeing your own role through the same lens. And that changes everything.

You notice that your own role, the one you are currently playing in your business, is almost certainly not designed. It is just the collection of everything that has fallen to you over time. Some of it is high leverage. Some of it is not. Some of it requires your specific judgment. Some of it really does not.

Once you have hired for two or three real roles using the scorecard method, you will naturally find yourself sitting down and writing a scorecard for your own position. What are the three to five outcomes you, as founder, must produce this year that no one else can. What is the mission of your role. What are the competencies the role requires. What are the non-negotiables.

This exercise usually reveals two uncomfortable truths. First, most of your current day is spent on things that are not on the scorecard. Second, many of those things could be handed off to someone operating against their own scorecard. Not all at once, but systematically, over time, as you design and fill additional roles.

Want the shortcut?

If you want the exact role scorecard template I use for every hire, along with three sample scorecards for common service business roles, Just reply to this email with the word SCORECARD and I will send it straight to your inbox.

Talk Soon,

Dan

Dan Kaufman, Founder, Dead Simple Growth and Pinnacle Masters

Webinars can be one of the most effective ways to generate leads, build trust, and drive real engagement. But only if they're built to perform.

The Wistia Webinar Guidebook walks through exactly how to do it. From planning and promotion to delivery and follow-up, it covers the full webinar lifecycle so you're not just showing up live, but turning every event into a scalable growth channel.

Inside, you'll find how to attract the right audience, keep viewers engaged from start to finish, and repurpose content long after the event ends. Because the best webinars don't stop when the stream does. They keep working across landing pages, campaigns, and on-demand experiences.

If you're looking to create webinars that actually convert and keep delivering value over time, this guide covers everything you need.

Get the Free Guidebook