The first customer success hire checklist, before you post the job

You don't need a customer success hire checklist because hiring is hard. You need one because most founders skip straight to writing a job post before deciding what the role is actually supposed to fix. That order is backwards, and it explains why so many first customer success hires end up with the wrong scope, the wrong background, or both, three months after their start date.

Before you post anything, there are six questions worth answering in order. Each one changes what the job description says, who you should interview, and how you'll know if the hire worked. Skip them and you'll spend a quarter, and one expensive mis-hire, learning what an afternoon of planning would have told you.

Why this hire usually happens too late

Most startups don't decide to hire a CSM. They get forced into it. A founder answers the same onboarding question for the fifth time this month. A renewal slips because nobody owned the relationship. Usage on a mid-size account quietly drops for six weeks and nobody notices until the cancellation email arrives.

By the time any of that happens, you're hiring to put out a fire, not to build a function, and fire hires make weak decisions under time pressure. If you're not sure whether you're early or already overdue for this hire, run the three-question timing test first.

Jason Lemkin's well-known rule of thumb is one CSM for every $2 million in annual recurring revenue. At a median $21,000 annual contract value, that works out to roughly 95 accounts per rep, a ratio built for a company well past the first-hire stage. The better trigger for hire number one is qualitative, not a revenue threshold: at least one account whose loss would meaningfully hurt the business, or a founder spending several hours a week on account babysitting that isn't sales or product work.

The checklist to run before you write the job post

Work through these six questions in order. Each one changes what the job post should actually say.

1. Name the specific fire you're hiring to put out. Churn risk, an onboarding backlog, missed renewals, and stalled expansion revenue each point to a different job description and a different first 90 days.
2. Identify who owns these tasks today and what breaks if they stop doing them. If the honest answer is nothing breaks, the hire can wait another quarter.
3. Solve for an accounts-to-rep ratio, not a job title. Eight enterprise accounts and 150 self-serve accounts are two different jobs wearing the same customer success manager title.
4. Decide the background you actually need. Roughly a quarter of people working in customer success came up through customer success itself; most come from sales or account management. Hire for the underlying skill, not the resume label.
5. Rule out a VP or head of CS for this hire. A leader with ten-plus years of experience wants to build a team and a process, not personally run renewals and onboarding calls, and that mismatch shows up by month two.
6. Write the 90-day outcome you'll measure the hire against before you interview anyone. If you can't state it in one sentence, you're not ready to post the job yet.

If you want the exact interview questions to run against candidate five, SaaStr's founder checklist and HubSpot's broader interview list are both solid starting points.

The mistake that costs the most: hiring the title, not the job

The single most expensive version of this hire is bringing in someone senior before there's a team, a defined process, or even a settled account list for them to manage. Drift's David Cancel has made a version of this point about early hiring generally: too much structure too early slows a small team down instead of helping it move faster.

A first customer success hire needs to be comfortable running onboarding calls, chasing renewals, triaging support tickets, and feeding product issues back to the team, often all in the same week. That's an individual contributor's job, regardless of how senior the person doing it eventually becomes.

What this hire actually costs beyond salary

Base salary is the number founders budget for, and it's rarely the number that lands. Benefits, a CS or support tool, recruiting cost, and the ramp time before the hire is fully productive all add to the real total, often by a wide enough margin to change the hiring timeline. We broke down the full math here if you want actual dollar ranges instead of a rule of thumb.

The 30-day move

Before you write the job post, spend one week logging every customer-facing task a founder or salesperson does that isn't selling: onboarding calls, renewal check-ins, support escalations, usage reviews. That log becomes the real job description. It will look nothing like a generic customer success manager template, and it will tell you whether you're hiring to fix retention, expansion, or plain support triage first.

Frequently asked questions

What ARR should trigger a first customer success hire?

There's no fixed revenue number. The stronger signal is qualitative: at least one account whose loss would meaningfully hurt the business, or a founder spending several hours a week on account work that isn't sales or product.

Should a first customer success hire be a manager or an individual contributor?

An individual contributor. A VP or head of CS wants to build a team and a process, not personally run onboarding and renewals, which is exactly what a first hire needs to do day to day.

What background should a first customer success hire have?

Most people in customer success come from sales or account management, not CS itself. Prioritize product fluency and account instincts over a customer success title on the resume.

How much does a first customer success hire actually cost?

More than the salary line suggests. Benefits, tooling, recruiting, and ramp time typically add a meaningful percentage on top of base pay, see the cost breakdown above for exact ranges.

Is a customer success manager the same as an account manager?

Not quite. Account managers are usually tied to renewals and upsells. A first CS hire at a startup also owns onboarding, support triage, and product feedback, a broader scope than either title implies alone.

This checklist works because it forces the scope decision before the interview process starts, not during it. Run the week-long task log first. Everything else here follows from what it tells you.

If it turns out the real gap is upstream of hiring, retention or expansion revenue not showing up no matter who owns the account, that's a conversation worth having before you write a job post at all.