How do you implement the Sandler Rules by David Mattson in your first 30 days as a new sales manager in 2027?

The Monday you inherit a pipeline nobody believes

You take over a seven-rep team in January 2027. The forecast says $2.4M for the quarter. The VP tells you privately that the last two quarters came in at 61% and 68% of forecast, which means the number on the board is decoration. You open the CRM and find forty-one opportunities in "Proposal Sent," and when you sort by last activity date, nineteen of them have gone dark for more than 45 days. Three of them have close dates that have been pushed four times. Nobody has told a single one of those buyers no, and no buyer has told a rep no. The deals are simply floating.

This is the exact condition David Mattson's *The Sandler Rules* was written against. The book is 49 short chapters, each one a compressed rule with a page or two of explanation, and the temptation for a new sales manager is to hand every rep a copy and announce that the team "runs Sandler now." That fails for a mechanical reason: 49 behavioral rules introduced simultaneously produce zero behavior change, because a rep under quota pressure will default to whatever they already know how to do the moment a call gets uncomfortable. You are not competing with the reps' willingness. You are competing with their reflexes.

So the first 30 days is not an implementation of Sandler. It is a diagnosis, a selection of two or three rules that map onto the specific leak you find, and the installation of one inspection mechanism that makes those rules visible in the CRM. Everything else in the book waits for month two, three, and six.

The leak in the scenario above is diagnosable in about four hours of reading call notes. Nineteen dark opportunities in Proposal Sent means reps are sending pricing before they have confirmed that the prospect has a problem worth solving, money allocated to solve it, and a defined path to a yes. Mattson's Rule 7 — "you never have to like prospecting, you just have to do it" — is not your problem. Your problem is the cluster around Rule 4 ("a prospect who is listening to you is no prospect at all"), Rule 15 ("the best presentation you will ever give, the prospect will never see"), and the up-front contract rules that keep a meeting from ending in "send me something and I'll circulate it internally."

A note on scope before you touch anything. You have roughly 22 working days. Realistically you get one behavior change to stick per 30-day window, and it sticks only if you inspect it weekly. A new manager who tries to install a methodology, rewrite the comp plan, restructure territories, and fix the CRM in the same month ends the month with seven confused reps and no methodology. Pick the leak. Pick the three rules. Install the inspection. Leave the rest alone.

What the first 30 days actually looks like, day by day

Here is the structure that survives contact with a real team. It is four one-week phases, and the sequencing matters more than the content — reversing weeks one and two is the single most common way a new manager burns credibility in month one.

Days 1–5: observe, and change nothing. Sit on a minimum of two live calls per rep — for a seven-person team that is 14 calls, roughly 10 hours. Say nothing on the calls. Do not correct, do not rescue a rep who is drowning, do not take over when the prospect asks a pricing question the rep fumbles. You are building a baseline and, more importantly, you are earning the right to change something later. Take notes against a fixed template: did the rep set an up-front contract at the top? Did the prospect state a problem in their own words, or did the rep state it for them? Was money discussed? Was the next step scheduled on a calendar during the call, or promised by email?

Run the same week on the CRM. Pull every open opportunity, sort by stage and last-activity, and build a one-page picture: stage distribution, median days in stage, percentage of pipeline with no scheduled next meeting. That last number is your headline. In a team with the pathology described above it will land somewhere between 40% and 60%, and it is the number you will put on a slide in week two.

Also do seven 45-minute one-on-ones, but as intake interviews rather than coaching. Three questions: what's working, what's broken that I can fix, and what would you change if you had my job. Write it down verbatim. Half your month-two roadmap comes out of these.

Days 6–10: name the leak and teach three rules. Bring the team together for 90 minutes. Show the pipeline picture from week one — no names, no blame, just the aggregate. Then introduce exactly three rules from Mattson and connect each one to a specific number on the slide. This is the whole trick: a rule that arrives attached to a number the team already agrees is bad gets adopted; a rule that arrives as philosophy gets nodded at and ignored.

The three-rule set for a "deals go dark after proposal" leak is typically: the up-front contract (agree on purpose, agenda, time, and outcome before the meeting starts, including the right for either side to say no), no mutual mystification (never leave a meeting with an ambiguous next step — "I'll follow up next week" is mystification), and don't spill your candy in the lobby (stop presenting before the prospect has articulated pain, budget, and a decision process). Mattson's phrasing for these is short enough that reps can recall them mid-call under pressure, which is precisely why the book is written in one-line rules rather than paragraphs.

Teach them by role-play, not by lecture. Sixty of the 90 minutes should be reps practicing an up-front contract on each other while you interrupt and reset. A rule that has never been said out loud in a low-stakes room will not appear in a high-stakes call.

Days 11–15: install the inspection. Add three required fields to the opportunity record — Pain (the prospect's stated problem, in their words, with a quote), Budget (a number or a stated range the prospect has confirmed, not your estimate), and Decision (named people, named steps, named date). Gate stage advancement on them: an opportunity cannot enter Proposal without all three populated. In most CRMs this is a validation rule and takes an admin under an hour.

Then re-qualify the existing pipeline against it. This is the painful part of the month and it must happen inside it, because if you let the old pipeline live under the new rules you have two systems and reps will hide in the old one. Sit with each rep for 60–90 minutes and walk their deals. Anything that cannot fill the three fields goes back to an earlier stage or gets closed out. Expect to remove 25–45% of open pipeline dollars. Tell your VP this is coming before you do it, framed as forecast accuracy, not as a write-down — a manager who surprises their boss with a 35% pipeline cut in week three does not get a month four.

Days 16–22: coach the rules in one-on-ones and hold the line. Weekly 30-minute one-on-ones move from intake to call review. Pull one recorded call per rep per week, listen to the first four minutes together, and score only the up-front contract. Not the whole call — one behavior. When a rep asks for an exception to the gate ("this one's different, the champion loves us"), the answer is no, and the reason you give is the nineteen dark deals from week one. Consistency in the first month is worth more than correctness; a gate that bends twice is not a gate.

The numbers that tell you whether it worked

Thirty days is too short to move revenue, and any new manager who promises their VP a revenue lift in month one has set a trap for themselves. Bookings in month one reflect pipeline built by the previous manager under the previous rules. What you can move in 30 days is a small set of leading indicators, and those are what you report on day 30.

Percentage of open opportunities with a scheduled next meeting. This is the single cleanest proxy for the no-mutual-mystification rule and it moves fast, because it requires one behavior at the end of one call. Baseline it in week one. A team with a dark-pipeline problem commonly starts between 40% and 60%. By day 30 it should be north of 85%, and if it isn't, the rule didn't land and you re-teach rather than adding rules. This metric is also unfakeable in a useful way: reps can't book a meeting the prospect won't take.

Up-front contract set at the top of the call. Score from recordings, not from self-report. Baseline is frequently near zero on a team that has never run a methodology. A realistic 30-day target is 60–70% of first meetings, not 100% — reps will use it on discovery calls before they use it on a call with a prospect they're afraid of losing. Track it per rep, because the distribution matters more than the mean; two enthusiastic adopters and five holdouts averages to something that looks like progress and isn't.

Pipeline dollars removed during re-qualification. Report the number, don't bury it. If you removed less than 15%, you were too soft in the deal reviews and the gate is theater. If you removed more than 55%, either the previous pipeline was fiction or you over-corrected and pulled deals that had real next steps. The 25–45% band is where honest re-qualification usually lands on a team with a proposal-stage graveyard.

Stage-to-stage conversion after the gate. You will not have enough deals through the new gate in 30 days to call this statistically meaningful — with seven reps you might have 20 to 40 qualified opportunities, and conversion rates on samples that size swing wildly. Record it as a baseline and set the expectation with your VP that the read comes at day 90. What you *can* say at day 30 is that the deals in Proposal now all have a named economic buyer, a confirmed budget range, and a decision date, which the previous 41 did not.

Forecast variance. Your predecessor came in at 61% and 68%. You will not fix that in a month, but you should commit to a number on day 30 and hit it, because the fastest way for a new manager to buy room for a methodology rollout is to be the first person in two quarters whose forecast was true. Under-commit deliberately in your first quarter. A forecast that lands at 103% buys you month four; one that lands at 88% costs you the mandate regardless of how good the coaching was.

Time cost, so you can plan the month. Ride-alongs 10 hours, CRM audit 4, intake one-on-ones 6, training session prep and delivery 5, pipeline re-qualification 8–11, weekly call reviews 4, reporting 3. That is roughly 40–45 hours across the month, on top of the deal escalations and interviewing and internal meetings that a manager cannot avoid. It fits in 22 working days only if you are ruthless about not also launching a new comp plan.

What you give up by choosing this sequence

Every implementation strategy in month one trades something away, and being explicit about the trade makes it easier to defend when someone senior asks why you aren't moving faster.

Choosing three rules over the full 49. You give up coherence — reps who read the book will notice you're teaching a fragment, and a rep who was trained at a Sandler shop previously may push back that you're skipping the fundamentals of the submarine (the seven-compartment Sandler Selling System). The gain is adoption. Three rules taught with role-play and inspected weekly change behavior; forty-nine rules distributed as a book change nothing. Hand out the book anyway — reps who want more should have it — but be explicit that you're inspecting three things, and name them.

Choosing behavior metrics over revenue metrics in month one. You give up the ability to claim an early win in dollars. Some VPs will be uncomfortable with a day-30 report full of leading indicators. The counter is that you can show them a pipeline that is 35% smaller and 100% inspectable, and offer a forecast you'll actually hit. If your VP genuinely needs bookings in month one, you have a different job than the one described here — you go sell the three biggest deals yourself and postpone the methodology to month two. That is a legitimate choice, but do it knowingly rather than drifting into it.

Choosing to re-qualify the inherited pipeline immediately. The alternative is to grandfather existing deals and apply the gate only to new opportunities. That is gentler on rep morale and it avoids the awkward conversation with your boss. The cost is that you carry a fictional forecast for another full quarter and the reps learn that the gate is negotiable. On balance the immediate cut is right, with one exception: if you inherit a quarter that is already 80% through, cut after the quarter closes rather than mid-flight, because a rep whose commission is riding on a deal you just closed out is a rep who will fight the whole methodology for a year.

Choosing Sandler at all. Mattson's rules are strongest on the psychology of the sales conversation — the up-front contract, the discipline against free consulting, the willingness to hear no early. They are weaker as a pipeline-generation system and weaker again in complex multi-stakeholder enterprise deals where a rule like "no mutual mystification" is necessary but nowhere near sufficient. If your team's leak is top-of-funnel volume rather than mid-funnel discipline, a Sandler rollout is the wrong first move and an activity-and-targeting fix is the right one. If your deals involve eight stakeholders and a security review, you'll want to layer something with explicit multi-threading mechanics on top by month three. Diagnose first; the method follows the leak, not the manager's preference.

Choosing to teach rather than replace. Some new managers conclude in week one that two of the seven reps will never adopt anything. Possibly true. Do not act on it in month one. You have not seen enough, your read on who is coachable is unreliable from 14 calls, and a termination in your first 30 days makes every remaining rep spend month two managing their own risk instead of learning the rules. Gather evidence, document, and act in month two or three if the evidence holds.

Where new managers break this in the first month

Announcing the methodology on day one. The most common failure and the most expensive. A manager who walks in and declares that the team runs Sandler now has spent their entire credibility budget before they've watched a single call, and they've told seven people that their existing skill is worthless without knowing whether it is. Observe first. The week of silence is not passivity; it is what makes week two's training land as a response to a real problem rather than a preference imported from your last job.

Teaching all 49 rules. Covered above, but it bears repeating because the book's format actively invites it — 49 short chapters feel coverable in a two-hour session. They aren't. Reps retain roughly what you inspect, and you cannot inspect 49 behaviors with seven direct reports.

Setting the gate and then approving exceptions. The first exception request will come from your best rep, on your biggest deal, in week three, with a plausible reason. If you approve it, the gate is dead and everyone will know by Friday. Say no and offer to spend an hour with them getting the missing field filled instead — which is usually possible, and which teaches the rule better than any training session.

Confusing the up-front contract with an agenda. Reps who half-adopt it will open calls with "so today I'll walk you through our platform and then we can talk next steps," call that a contract, and check the box. It isn't. The contract has to include the prospect's agenda alongside yours, an agreed time box, and — the part everyone drops — an explicit outcome, including permission for the prospect to say no at the end. Without the mutual-no clause it's a meeting agenda and it does nothing for the dark-pipeline problem.

Coaching everything at once in one-on-ones. Listening to a full 45-minute call with a rep and giving them nine pieces of feedback produces zero changes. One behavior, four minutes of tape, every week, until it's automatic. It feels absurdly slow. It's the only thing that works.

Reporting activity as if it were progress. A day-30 report that says "delivered training, added CRM fields, held 21 one-on-ones" is a report about you. The report should say: pipeline went from $2.4M to $1.6M and every dollar of it has a named buyer, a budget, and a decision date; next-meeting-scheduled went from 47% to 88%; here is the forecast I'll hit. That is a report about the business.

Skipping the boss conversation before the pipeline cut. Non-negotiable. Brief your VP in week two, before you re-qualify, with the expected range and the reasoning. A leader who hears about a 35% cut from a dashboard rather than from you will read it as a problem you caused rather than one you found.

Treating month one as the implementation. It isn't. Thirty days gets you a diagnosis, three rules, one gate, and a coaching rhythm. Months two through six are where the rest of Mattson's material gets layered in — pain funnel depth, negotiation rules, the discipline around dummy curves and reversing — and where the strategy stops being a rollout and starts being how the team sells.

Related questions

Should I hand every rep a copy of The Sandler Rules in week one?

Hand it out, but decouple it from your inspection. Say clearly: read it if you want, I'm inspecting three rules, here they are. Distributing a book and inspecting nothing teaches the team that your initiatives are optional.

What if the team already claims to run Sandler?

Verify against recordings before believing it. Teams that were trained years ago usually retain the vocabulary and not the behavior. If up-front contracts appear on under 30% of calls, treat it as a fresh implementation regardless of what the training history says.

Do I need certified Sandler training to implement this?

No, for a three-rule start built on call review. Formal training becomes worth the cost around month three, when you're layering the full selling system rather than a handful of rules, and when you have evidence the team will actually apply what they're taught.

How do I handle a rep who outsells everyone and refuses the gate?

Enforce the gate and separate the two conversations. Their results are not in question; their forecastability is. In practice, top reps often have the cleanest Pain/Budget/Decision answers already and object to the data entry rather than the discipline — fix the data entry.

What does month two look like if month one worked?

Add two rules, not ten — typically around pain depth and closing without discounting. Keep the same weekly call-review rhythm, add a monthly pipeline inspection, and start reading stage-to-stage conversion once you have 60+ deals through the gate.

FAQ

Which of the 49 Sandler Rules should a new manager start with?

Start with the ones that match your diagnosed leak, not the ones you like best. For a pipeline that stalls after proposal, the up-front contract, no mutual mystification, and the prohibition on free consulting cover most of it. For a team that presents too early, add the rule about not spilling your candy in the lobby. Three is the ceiling for month one.

How long before Sandler adoption shows up in revenue?

Longer than 30 days. Leading indicators — next meeting scheduled, up-front contracts on tape — move in three to four weeks. Conversion and forecast accuracy need a full sales cycle plus a quarter of data, so if your average cycle is 60 days, expect a credible read around month four or five, not month two.

Should I cut inherited pipeline in my first month or wait?

Cut in month one, unless the current quarter is nearly closed and reps have commissions riding on deals you'd remove. Waiting means carrying a forecast you don't believe and teaching the team that the new gate is negotiable. Brief your manager on the expected range before you do it, never after.

What if my VP wants bookings, not behavior change, in month one?

Then sell the top deals yourself and postpone the rollout to month two. That's a real constraint, not an excuse to skip diagnosis. Do the call observation anyway — it costs ten hours and it's the input to everything you do next — but hold the training and the gate until you've bought the room.

Is Sandler the right method for enterprise deals?

It's the right layer for the conversation and an incomplete one for the account. Mattson's rules govern how a rep behaves on a call — qualifying, refusing to present early, insisting on a clear next step. Deals with eight stakeholders and a procurement gauntlet need explicit multi-threading and stakeholder mapping layered on top by month three.

How do I inspect up-front contracts without listening to every call?

Sample. One recorded call per rep per week, first four minutes only. That's about 30 minutes of listening for a seven-person team, and it's enough to see the distribution. Reps quickly learn that any call might be sampled, which does more for consistency than exhaustive review ever would.

Sources

• https://www.sandler.com/
• https://www.sandler.com/resources/sandler-books/sandler-rules/
• https://www.mheducation.com/
• https://hbr.org/2015/05/the-new-sales-imperative
• https://www.salesforce.com/resources/articles/sales-pipeline/
• https://hbr.org/2017/03/how-to-set-up-a-sales-process-that-works
• https://www.gartner.com/en/sales
• https://www.rainsalestraining.com/blog
• https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights

Related on PULSE

• How do you run a pipeline review that actually removes deals instead of rescheduling them?
• What should a new sales manager's first 30-60-90 day plan cover?
• How do you gate CRM stage advancement on qualification criteria without reps working around it?
• What's the difference between MEDDIC, Sandler, and Challenger for a mid-market team?
• How do you rebuild forecast accuracy after two quarters of missed calls?
• How do you coach one behavior per week in sales one-on-ones?