How to Hire A Players in a Vertical SaaS Company

Define the role on a weighted scorecard before you meet anyone, set the budget before you fall in love with a candidate, and score every competency against evidence a dispassionate third party would accept—so a new hire adds leverage instead of subtracting it.

Maintained in the open at github.com/Golden-Section-Tx/playbook · CC BY-SA 4.0

PlayersFounder, COO, Hiring Manager
Initial Effort21 SP
Ongoing13 SP
FrequencyPer Hire
StageEarly Traction

Founders scaling past their own capacity tend to hire the people they already trust. Trust is the easiest thing to verify and the least useful thing to verify, because the person you trust most is rarely the person who holds the specific knowledge the role is missing. That is the whole reason you are hiring.

The cost of getting it wrong is not one salary. On a ten-person team, one wrong hire in a functional leadership seat pulls the founder back into the function, forces the rest of the team to route around the gap, and quietly slows execution everywhere. A hire is meant to be leverage. A wrong hire is negative leverage, and it stays negative for as long as it takes to admit it.

What a founder is actually buying is not a resume. It is the ability to hand off a functional area and the responsibility that comes with it, and still get reliable execution without supervising it. That is a high bar, and you cannot assess it in a friendly hour-long conversation.

Topgrading is the framework Golden Section uses for this. Companies that run it well report hiring success rates far above the roughly one-in-four most companies achieve, and the method is worth reading in full — Bradford Smart's Topgrading is the source. The steps below are the working distillation: what to do, in what order, before you meet anyone.

The goal: Know precisely what you are hiring for before you meet a candidate, and hire only against documented evidence that they have done it.

How can Golden Section Assist? Golden Section's recruiting arm can run sourcing and the first screens, and a venture partner can sit the tandem interview as the second interviewer.

Steps

  1. Build the scorecard before you talk to anyone. Write down the functional areas the role will own, the measurable accountabilities attached to each, and the competencies required to deliver them. This is not a job description with adjectives; it is the definition of the job done well. If you cannot write it, you are not ready to hire — you are still deciding what you want.
  2. Set the budget before you meet candidates. Two numbers: what the company can actually afford, and what the market pays for this role in your geography. If those two numbers do not overlap, the answer is to change the role, not to start interviewing and hope.
  3. Weight each competency 1–5 for importance. Five is crucial — the role fails without it. One is nice to have. Weighting turns the enriched job description into a scorecard you can track against, and it forces the hiring manager to say out loud which two or three things actually matter.
  4. Recruit, preferably from your network, then screen. Have candidates complete a career history form covering every job, and run a phone screen against the top-weighted competencies before anyone's calendar gets expensive.
  5. Interview in tandem, and interview long. Two interviewers, one leading and one taking notes. Budget the time honestly: roughly 45 minutes for entry level, two hours for an individual contributor, four hours for a management hire. Walk the resume chronologically from the first full-time job forward and, for each role, ask why they took it, what they accomplished and how, what they got wrong, what they liked least, who their supervisor was and what that supervisor would say about them, and why they left.
  6. Hold the evidence standard. A claim is not evidence. For each competency, you are looking for a specific story with a specific outcome that a dispassionate third party would find convincing. "I built the pipeline process" is a claim; "here is what conversion was when I arrived, here is what I changed, here is what it was eighteen months later, and here is who can confirm it" is evidence. Press on strengths until the real weaker points appear.
  7. Use the threat of reference check (TORC), and say it up front. Before the candidate tells you their stories, tell them you will be arranging calls with their former managers and peers, and name them: "You mentioned Tom ran supply chain at GE — we'll want to speak with him. And while we're at it, give us your reference on Tom: what was he like as a manager, where was he strong, where was he weak?" Asking the candidate to grade their manager, out loud, changes what they are willing to claim about themselves. Applied early and repeated at each step, it does more for the truthfulness of the process than the reference call itself.
  8. Score every competency 1–5 against documented proof. One is no evidence, five is demonstrated expertise. Write the note that backs each score while the interview is fresh. Roll the weighted scores into a single fit number, and do it before the debrief so the loudest voice in the room is not the deciding one. Weight the negatives more heavily than the positives.
  9. Conduct the candidate-arranged reference calls, then decide inside the budget. The scorecard and honest market-rate framing should attract the right person at the posted number. If the finalist only works at a stretch beyond the budget, you have learned something about the scorecard or about the finalist — not about what you can afford.
  10. Hand the scorecard to the new hire on day one. It is the clearest onboarding document you will ever write, it sets the standard for the first ninety days, and it gives both sides an honest basis for the first performance conversation.

Concerns

  1. Topgrading is long, structured, and document-heavy. It takes several times the hours of a normal hiring process, and that is the trade: you are spending days now to avoid spending quarters later. Do not start it and then abandon the documentation halfway — a half-run process gives you the cost without the benefit.
  2. Recent past behaviour is the best predictor of near-future behaviour. Look for patterns across jobs rather than one impressive story, and do not bet on the candidate changing a pattern that has held for a decade because they told you they will.
  3. Strengths presented as weaknesses are the most common evasion in the room. "I care too much" is not a weaker point. Keep asking until you get one you recognise as real, and treat the refusal to produce one as data.
  4. Do not let an impressive candidate rewrite the scorecard. If the finalist is excellent at something the role does not need, you have found a good person for a different job. Changing the scorecard after meeting the candidate is how founders talk themselves into the hire they already wanted to make.
  5. Vetting technical talent without technical judgement in the room does not work, whatever the process. Borrow the competence — a fractional CTO, a venture partner, a trusted engineer — and have them sit the tandem interview.
Mistakes this play prevents: #1 #3 #14 #28 #32 #33 #140 #146 #154

Questions this play answers

How do I hire a senior leader without guessing?

Define the role on a weighted scorecard before you meet anyone, set the budget before you fall in love with a candidate, and score every competency against evidence a dispassionate third party would accept—so a new hire adds leverage instead of subtracting it.

What should be on a hiring scorecard?

Weight each competency 1–5 for importance. Five is crucial — the role fails without it. One is nice to have.

How do I know what to pay before I start interviewing?

Set the budget before you meet candidates. Two numbers: what the company can actually afford, and what the market pays for this role in your geography. If those two numbers do not overlap, the answer is to change the role, not to start interviewing and hope.

What is the threat of reference check (TORC)?

Use the threat of reference check (TORC), and say it up front. Before the candidate tells you their stories, tell them you will be arranging calls with their former managers and peers, and name them: "You mentioned Tom ran supply chain at GE — we'll want to speak with him. " Asking the candidate to grade their manager, out loud, changes what they are willing to claim about themselves.

How long should a serious interview be?

Interview in tandem, and interview long. Two interviewers, one leading and one taking notes. Budget the time honestly: roughly 45 minutes for entry level, two hours for an individual contributor, four hours for a management hire.

Why is a bad hire worse than no hire on a small team?

The cost of getting it wrong is not one salary. On a ten-person team, one wrong hire in a functional leadership seat pulls the founder back into the function, forces the rest of the team to route around the gap, and quietly slows execution everywhere. A hire is meant to be leverage.