A new sales leader's first 30 days: what to check first
The average CRO lasts 1.8 years. A 30-day sequence for a new sales leader: numbers, people, process, decisions, and the traps that shorten tenure.
By Semir Jahic
/ 8 min read
The average chief revenue officer lasts 1.8 years, level with chief marketing officers and well short of the 4.3 years a chief executive gets, according to Pave data on 14,000 executives reported by SaaStr. Part of that number is decided early. A new sales leader's first 30 days are the only window in which the forecast, the pipeline and the excuses still belong to somebody else. A leader who does not establish the facts in that window inherits all three, and by the second quarter is judged on them. This post is for the CEO who just made the hire and for the person who took it: a four-week sequence, the evidence for each week, and the traps that cut tenure short.
Why do the first 30 days decide a sales leader's tenure?
Because that is when the facts are still neutral. On day one, a weak forecast and a padded pipeline are the previous leader's record. By day 90 they are the new leader's, and the first missed quarter lands on the new name. The data behind GTM due diligence argues that each change of sales leader is a moment to re-check the engine.
The order below is deliberate: numbers before people, people before process, process before decisions. Reverse it and opinions harden before the data can correct them.
| Week | What to check | The one number or artefact that proves it |
|---|---|---|
| 1 | The numbers | Four quarters of forecast against actual, with bias |
| 2 | The people | One page per role with the same three answers |
| 3 | The process and systems | Stage definitions with exit criteria, as the CRM enforces them |
| 4 | The decisions | A one-page 100-day plan with five to eight owned actions |
Week 1: what do the numbers say?
Four figures: forecast accuracy and bias, clean coverage, win rate by segment and the attainment spread. The numbers come first because nobody can argue with them. Ask RevOps on day one for four pulls: forecast snapshots against closed revenue for four quarters, every open opportunity with stage history and last activity, closed won and lost by segment, and quota attainment by rep.
From those, compute four figures before any long conversation. Forecast accuracy and bias at the start, middle and end of each quarter: a team that is 15% optimistic every quarter has a definitions problem. Coverage after removing deals with no activity in 60 days and deals past their close date; in an illustrative case, 3.0 times reported becomes 1.8 after cleaning, and the one-week forecast test walks through the steps. Win rate by segment, by count and by value. The attainment spread: the share of ramped reps at quota, and the share of bookings the top three carry.
Then review every deal above a size threshold personally, by size, with the owning manager. Two days is enough, and you will see how managers react when a deal is questioned.
Week 2: what do the people say?
Ask each role the same three questions and look for answers that contradict the records. The people come second so that every conversation can be held against a number. Hold one conversation per role: front-line manager, account executive, development rep, customer success, marketing and RevOps. Ask three questions each. What is your biggest roadblock? What is the biggest opportunity we are missing? If you had my job, what would you do first?
Write one page per role with the answers side by side. What you are looking for is disagreement: between the records and the people, and between roles. A manager who describes a reliable forecast while the snapshots show 70% accuracy has told you how the business is run.
Ask managers one more question: who on your team would you hire for their role today? Record the answer and do nothing with it yet.
Week 3: how does the process actually run?
Either the CRM enforces a written process or there are only habits, and three checks show which. Process comes third because you now know where the numbers break and who thinks what. The test is whether a written process exists and whether the CRM enforces it. Pull the stage definitions and ask three reps to describe them unprompted. If the descriptions differ, there is no process, only habits.
Check the exit criteria: buyer actions (a named economic buyer, a signed evaluation plan) or seller activities (demo given, proposal sent)? Check qualification fields; blanks on more than 30% of opportunities mean the CRM records activity, not evidence. A forecast built in a spreadsheet beside the CRM is a red flag, and so is a number that moves most in the final fortnight.
Sit in the forecast call before you change it. Note who submits what, who changes the number before it reaches the CEO, and whether the call helps deals close or interrogates their owners.
Week 4: what gets decided?
Four decisions. What to stop: the reports, rituals and tools that produced nothing you used in weeks one to three. What to keep: the parts that work, named out loud, so the team does not hear that everything is broken. What goes into the plan: five to eight actions, each with an owner and a measure. What belongs in a 100-day go-to-market plan covers the shape.
The fourth is what to tell the board: the diagnosis in four lines (team, customers, process, deals in flight), the clean pipeline number beside the reported one, any change to the forecast, and what will wait until next year. A board that hears a lower number in week four, with the reason, trusts the leader more than one that hears it in month five.
Which traps shorten a sales leader's tenure?
Three traps are worth naming, and all three come from acting before the facts are in.
- Rebuilding the team before seeing the data. Repeated leader turnover at a founder-led company can be an engine problem: a team fed by inbound that never prospected, territories drawn on dirty data, no marketing owner. Judge the system first, then the people.
- Changing the CRM in month one. A migration consumes the quarter, erases the history you need for a baseline and hands everyone a reason for the next miss. Fix definitions and hygiene in the tool you have.
- Promising a forecast before the categories are defined. Until "commit" means one thing to every manager, any number given to the board rests on somebody else's definitions. Publish the definitions sheet, then forecast.
A quieter fourth trap is fixing everything at once. Install four basics (definitions, an operating calendar, pipeline hygiene, a talent read) and say openly what will wait.
Why get an outside baseline at day zero?
Because a scorecard the new leader did not write protects the leader and the CEO alike. A GTM Health Check costs CHF 8,000, takes five working days and needs 4 to 8 hours of the team's time. It scores all ten areas from a four-quarter CRM extract and three to five conversations, and records clean coverage, accuracy and attainment as an independent baseline, dated before the new leader changed anything.
The CEO sees what was inherited. The leader gets a 100-day plan built from evidence rather than the previous leader's slides. For a first read, score your own company in a few minutes. If you have just hired a sales leader, or just started as one, book 30 minutes with me and bring the number you trust least.
Key takeaways
- The average CRO lasts 1.8 years, and the first 30 days are when the inherited forecast and pipeline become the new leader's own.
- Order matters: numbers, then people, then process, then decisions.
- Four figures carry week one: forecast accuracy and bias, clean coverage, win rate by segment, attainment spread.
- The traps: rebuilding the team before the data, changing the CRM in month one, forecasting before definitions exist.
- An outside baseline at day zero gives the leader and the CEO a scorecard neither of them wrote.
Frequently asked questions
What should a new CRO do in the first 30 days?
Establish the facts before changing anything. Pull four quarters of forecast against actual, clean the pipeline, measure win rate by segment and attainment spread, hold one conversation per role, test whether the CRM enforces the process, then decide what to stop, keep and put in the 100-day plan.
Should a new sales leader change the CRM straight away?
No. A migration in month one consumes the quarter and erases the history needed for a baseline. Fix stage definitions, exit criteria and hygiene rules inside the existing tool first, and decide on a new system only once the process is written and the data is clean.
When should a new sales leader give the board a forecast?
After the forecast categories are defined and published, usually by the end of the first month. Until "commit" means one thing to every manager, any number rests on the previous leader's definitions. Give the board the clean pipeline and the diagnosis first, then the forecast.
How does a GTM Health Check help a new sales leader?
It gives the leader and the CEO an independent baseline at day zero: all ten areas scored from a four-quarter CRM extract and three to five conversations, in five working days for CHF 8,000. The scorecard records what was inherited, and the 100-day plan starts from evidence.