A RevOps guide to building a sales method into your CRM

Why a method fades after the training ends

Your sales team learns a method. For a few weeks people use the words. Then the quarter gets busy, and the method goes back to living in a slide deck.

The usual cause is not the reps. It is that nothing in the CRM (customer relationship management system, the place your deals are kept) asks for the method or uses it. If a manager cannot see a step on the record, they cannot coach it. If the forecast does not read it, nobody misses it when it is blank.

If you own the CRM, whether your title is RevOps (revenue operations), sales operations or just the person who knows how it works, this part is your job. This post shows how to do it with The Salecopy Method, which has eight moves: Signal, Anchor, List, Evidence, Concessions, Options, Paper, Yes. The same approach works for any method that has clear steps.

Start with the decision, then build the field

Before you add a field, write one sentence: who uses it, and what do they decide with it. If you cannot finish the sentence, do not build the field.

Take the walk-away, the point at which your side says no. The decision it enables is whether a pricing call goes ahead. A manager looks at it before the call and either agrees it or changes it. That is a field worth having.

Compare that with a field like Deal confidence, filled in by the rep. Nobody decides anything with it that they would not decide from the next step date. It adds a click and no information.

This test also gives you your answer when a sales leader says they do not want more required fields. You are not asking for data. You are asking which decisions they want to make from the record instead of from memory.

The eight moves as fields

Each move in the method already names what to keep. Your job is to pick a type that can be reported on. A notes box cannot be counted. A date, a number, a linked contact or a row in a list can.

• Signal: Why now (text) and Buyer's deadline (date).
• Anchor: Cost of doing nothing (currency, per month) and Whose numbers (a link to the buyer contact who confirmed it).
• List: a buying role on each contact attached to the deal, so an empty role is visible.
• Evidence: Open objections as rows on the deal, each with a status of open or closed.
• Concessions: a give and get table with an Approved by column.
• Options: Walk-away, Our alternative and Buyer's alternative, visible only to the rep, the manager and leadership.
• Paper: a mutual plan checklist with an owner on each side and a due date for every step.
• Yes: Next step, Next step owner and Next step date.

Ask for each field at its stage, not all at once

The fastest way to lose reps is to make everything required when the deal is created. They type a full stop in each box and move on, and you now have junk that looks like data.

Tie each field to the stage where the decision happens instead. Most CRMs, including HubSpot and Salesforce, let you require a field before a deal can move to a given stage.

A simple version: Why now and Buyer's deadline to leave discovery. Cost of doing nothing before a price is sent. Buying roles and the walk-away before negotiation. The mutual plan before contract. A rep on a new deal sees two fields, not fifteen.

Write the rule for each stage as a fact about the record, so two people cannot read it differently. There is more on this in pipeline stages with exit criteria. Make it easy to move a deal back a stage, too. A deal that returns to discovery because the buyer's date fell through is the system working.

One forecast rule

The forecast is the list of deals you expect to close this period. In many teams it is built from what each rep believes. You can replace part of that belief with one rule from the method: a deal in negotiation with no dated next step owned by the buyer drops out of the forecast.

Build it as a filter on the forecast report. If Next step date is empty or in the past, the deal is not counted. Show those deals in their own list in the manager review, so the conversation is about getting a date and not about arguing over the number.

Agree this with sales leadership before you switch it on, and agree who can make an exception. The first week the forecast will look smaller. Show them which deals moved and why, one by one.

Let AI check the record, and let a person decide

Once the fields exist, an AI assistant is good at one dull job: reading a set of deals and listing what is missing. A deal in negotiation with no budget holder. An objection with no evidence sent. A plan step past its date.

Keep its role narrow. AI prepares and checks. A person decides, speaks and sends. The AI does not move deals between stages, change the forecast or write to a buyer.

Give every AI check an owner, a named person who reviews what it produces, and a written note of what it costs to run. A check with no owner gets ignored the first time it is wrong.

What to do before Friday

Export 20 open deals. For each one, mark which of the eight moves has something written down. You can do this by hand or with the prompt below, then check the result yourself.

Take the count to your sales leader and ask which gap they most want closed. Build that field and its stage rule first. For the full field list, see CRM fields that make negotiation coachable.

If you want the whole build in order, the RevOps training program covers it in four weeks: fields, stages, forecast, then AI checks and handover. If you would like someone to build it with you, that is what RevOps and analytics is for.

What to add to your CRM

A prompt to try

You are helping me audit my CRM against a sales method. I own the CRM. I am not asking you to change anything or contact anyone.

The method has eight moves, and each should leave something written on the deal:
S Signal: why now, and the buyer's deadline
A Anchor: the monthly cost of doing nothing, and the buyer contact who confirmed it
L List: the decision maker, budget holder, user, and legal or procurement contact
E Evidence: open objections and the evidence sent for each
C Concessions: a give and get list with who approved it
O Options: our walk-away, our alternative and the buyer's alternative
P Paper: a mutual plan with steps, owners and dates
Y Yes: a next step, the buyer contact who owns it, and its date

Here is an export of my open deals, one row per deal, with the stage and the fields I have today:
[paste your export]

Here are my pipeline stages in order:
[list your stages]

Do three things:
1. For each deal, list which of the eight moves have nothing written down. If a field contains placeholder text such as a full stop or TBD, count it as missing and say so.
2. Give me a count for each move: how many deals are missing it.
3. List every deal in a late stage that is missing something an earlier stage should have asked for, and name the field.

If a column you need is not in the export, list what is missing and ask me for it. Do not guess or fill in values. Do not suggest messages to buyers. I will review your list against the records before I show it to anyone.