Training · RevOps
The Salecopy Method for RevOps: build it into the CRM
This is a four-week program for RevOps (revenue operations, the people who run the systems and reports behind sales), built on The Salecopy Method. It is for whoever owns the CRM (customer relationship management system, the place your deals are kept). You do not negotiate deals in this program. You build what makes the method stick after the sales training ends: the fields, the rules for moving a deal between stages, the forecast rule, the manager review and the AI checks, with a person deciding at every point.
Who it is for
- RevOps leads who are asked to make a new sales method show up in the pipeline (the list of open deals and the stage each one is in).
- CRM admins who build the fields, required-field rules and reports in HubSpot, Salesforce or a similar system.
- Sales operations managers who run the forecast call and the weekly pipeline review.
- A founder or operations manager at a smaller company who owns the CRM because nobody else does.
How it runs
Four weeks. Live sessions with your team, on your own open deals. Between sessions, each person practises against an AI buyer and brings the transcript back. At the end, the eight moves are fields in your CRM, so the habits outlast the training.
Quoted per team as a custom fixed quote.
Why deals stall
Four ways revops deals get stuck.
Fields nobody fills
The method gets a set of new fields, all optional and all on one long form. Reps skip them, managers never open them, and soon the fields are empty on every deal that matters.
Stages that mean nothing
A deal moves forward because the rep feels good about it, not because something is written down. Two reps with the same deal put it in two different stages, so the pipeline cannot be compared or coached.
A forecast built on optimism
The forecast (the list of deals you expect to close this period) counts whatever the rep says will close. No rule removes a deal that has no dated next step, so the number is a hope and the misses are a surprise.
AI bolted on with no owner and no cost
Someone switches on an AI summary or score. Nobody is named to review what it says, nobody knows what it costs to run, and reps cannot tell whether to trust it, so they ignore it.
The Salecopy Method, in revops
The eight moves, in your sector's words.
| Move | What it means here | A line to say | On the record |
|---|---|---|---|
| S Signal | Build the two Signal fields and make them the price of leaving discovery. The rep writes what changed for the buyer and the date on the buyer's side, and the deal cannot move forward until both are there. | If a deal has no reason to close and no buyer date, do we agree it stays in discovery, even when the rep is sure about it? | Why now (text) and Buyer's deadline (date). A required-field rule blocks the move out of discovery while either is empty. Report: open deals past discovery with no Buyer's deadline. |
| A Anchor | Build one number field for the Anchor and one link to the buyer contact who confirmed it. Keep the inputs in a note, so a manager can see how the number was reached. | Before a rep sends a price, do you want to see the monthly cost of the problem in the buyer's own figures, and the name of the person who agreed it? | Cost of doing nothing (currency, per month) and Whose numbers (link to a buyer contact). Both required before a quote or proposal stage. The second field must point to a contact, not free text. |
| L List | Build buying roles as labels on the contacts attached to a deal, so each role is either filled by a real person or visibly empty. Add a last-contacted date for each, taken from logged activity where your CRM allows it. | Which roles must have a named person attached before you will let a deal into negotiation: decision maker, budget holder, user, legal or procurement? | Buying role on each deal contact (Decision maker, Budget holder, User, Legal or procurement) with Last contacted (date). Rule: no move into negotiation without the roles sales leadership named. Report: deals in negotiation with an empty Budget holder. |
| E Evidence | Build the Evidence list as rows attached to the deal, one row per objection, each with a status. A single notes box cannot be counted or reported on. Rows can. | When a manager reviews a deal, do you want to see how many objections are still open and what was sent to answer each one? | Open objections (list on the deal): objection, raised by, evidence sent, status open or closed. A count of open objections shown on the deal and on the manager review view. |
| C Concessions | Build the Concessions table and the approval that goes with it. Sales leadership sets the limits once, and the CRM routes anything over the limit to the right person before the rep offers it. | What can a rep trade without asking, what needs a manager, and what needs you? I need the limits in writing to build the approval. | Give and get list (table on the deal): what we can give, what it costs us, what we ask for in return, approved by. An approval step that fires when a give is above the agreed limit. |
| O Options | Build the Options fields and require them before negotiation. Limit who can see the walk-away to the rep, their manager and leadership, so it is safe to write down. | Should a deal be allowed into negotiation when the walk-away is blank, and who is allowed to see that number? | Walk-away (currency and terms), Our alternative (text) and Buyer's alternative (text). Required to enter negotiation. Field-level permissions on Walk-away. |
| P Paper | Build the Paper step as a checklist on the deal with a template of your usual steps, so the rep edits a plan instead of starting from a blank page. Add a flag for any step past its date. | What steps sit between a verbal yes and a start date in our deals, so I can put them in the template: legal review, security review, signature, kickoff? | Mutual plan (checklist on the deal): step, owner on our side, owner on their side, due date, done. A calculated Overdue steps count. Report: deals in contract with one or more overdue steps. |
| Y Yes | Build the three Yes fields and wire them into the forecast. This is the one rule that turns the method from a form into a number leadership relies on. | Do you agree that a deal in negotiation with no dated next step owned by the buyer comes out of the forecast, with no exceptions made on the call? | Next step (text), Next step owner (buyer contact) and Next step date. Forecast rule: a deal in negotiation with no next step date, or a date in the past, drops out of the forecast. Shown as its own list in the manager review. |
The four weeks
What your team does each week.
- 1Data model and fieldsThe fields for all eight moves exist in your CRM with the right types, each one tied to a decision it enables, and you know which are empty on today's open deals.
- From move to field: turning each of the eight moves into a field, a list or a checklist, with the type that makes it reportable
- One field, one decision: writing down who uses each field and for what, and dropping any field that has no answer
- Where the fields live: grouping them on the deal record by stage, so a rep sees only what the current stage asks for
AI practice drillExport 20 open deals and give the export to an AI assistant with the eight moves. Ask it to list, deal by deal, which of the eight have nothing written down. You review the list against the records and correct anything it got wrong before you show it to anyone.
- 2Stages and exit criteriaEach pipeline stage has written exit criteria (what must be true before a deal can leave it), agreed by sales leadership and enforced by a rule in the CRM.
- Stages as facts: rewriting each stage so that it describes what is on the record, not how the rep feels
- Required at stage: building the rules that ask for Signal at discovery, Options before negotiation and Yes in the forecast
- Moving deals back: making it normal and easy for a deal to return to an earlier stage when a field goes stale
AI practice drillPaste your stage names and draft exit criteria into an AI assistant and ask it to find every criterion that two people could read differently. You rewrite those lines, then take the final list to sales leadership to agree.
- 3Forecast and manager reviewThe forecast follows one written rule, and each manager has a review view that shows the eight moves for every deal on one screen.
- The forecast rule: building the dated-next-step rule and showing leadership which deals it removes today
- The manager review view: one dashboard with empty buying roles, open objections, missing walk-aways and overdue plan steps
- Data quality checks: weekly reports for stale dates, deals with a single contact and required fields filled with placeholder text
AI practice drillGive an AI assistant last week's forecast list and the deal fields, and ask which deals would drop out under the new rule and why. You check each one against the record and bring the confirmed list to the forecast call. The manager decides what happens to each deal.
- 4AI checks, costs and handoverEach AI check has a named owner, a person who reviews its output and a known running cost, and the whole build is documented so someone else can maintain it.
- AI checks that only check: flagging missing fields and proposing a why-now for the rep to confirm, with no sending and no stage changes by the AI
- Owners and costs: writing down for each check who owns it, who reviews it, what it reads, and what it costs to run
- Handover: the field dictionary, the rule list and the change process, so the next admin can pick it up
AI practice drillHave an AI assistant draft the field dictionary from your field export: name, type, the move it belongs to and the decision it enables. You correct every line, add the owner, and publish it where reps and managers can find it.
Try it now
Practise it with AI
The role-play prompt
Copy the prompt into an AI assistant and fill in the square brackets with your own CRM and team. The AI plays a VP of Sales who does not want more required fields, and scores you at the end. It is practice only: you still have the real conversation with your own sales leader.
You are going to help me practice a conversation I need to have at work. Play a skeptical VP of Sales. Stay in role until I type END. About the situation: - My role: [for example, RevOps lead, CRM admin, sales operations manager] - Our CRM: [for example, HubSpot or Salesforce] - The sales team: [number of reps and managers, what they sell] - What I want to build: fields and stage rules for the eight moves of The Salecopy Method (Signal, Anchor, List, Evidence, Concessions, Options, Paper, Yes) - What the team does today: [for example, free-text notes, stages moved by feel, forecast by rep opinion] - What has gone wrong before: [for example, a past field rollout that reps ignored] How to play the VP of Sales: - You are responsible for the number and you protect your reps' selling time. You have seen required fields before and you think they produce junk data. - Open by saying you do not want more required fields. Make me earn each one. - For every field or rule I propose, ask what decision it lets you or your managers make that you cannot make today. If I cannot name a decision, refuse the field. - Push back in at least three different ways, such as: reps will type anything to get past the rule, top performers will not do it, it slows deals down, the forecast already works well enough. - Be hardest on the forecast rule that removes a deal from the forecast when it has no dated next step. Ask who gets to make exceptions. - Ask what the AI checks cost to run and who is accountable when one is wrong. - If I answer with a clear decision the field enables, concede that field and move to the next objection. If I answer with process language or say it is best practice, push harder. - If I offer to remove or simplify a field in return for your backing on another, respond as a reasonable leader would. - Keep each reply to a few sentences, as a real person would in a meeting. Do not coach me while in role. If any detail above is still in square brackets or missing, list what is missing and ask me for it before we start. When I type END, leave the role and score me from 0 to 2 on each of the eight steps, with one sentence of evidence from the conversation for each score. The test for every step is the same: did I tie the field or rule to a decision it enables? S Signal: Why now and Buyer's deadline, tied to the decision to let a deal leave discovery. A Anchor: Cost of doing nothing and Whose numbers, tied to the decision to send a price. L List: Buying roles, tied to the decision to let a deal into negotiation. E Evidence: Open objections, tied to what a manager coaches before the next call. C Concessions: Give and get list, tied to who approves a trade. O Options: Walk-away and alternatives, tied to whether a pricing call goes ahead. P Paper: Mutual plan, tied to whether the close date can be believed. Y Yes: Dated next step, tied to whether the deal counts in the forecast. Then give me the total out of 16, the field I defended worst, and the exact sentence I could have said instead. Also list any field I proposed that I never tied to a decision, so I can cut it or rethink it. Do not draft or send any message to a real person. This is practice only.
The buttons open a new chat with the prompt already typed in. Fill in the square brackets before you send it, or copy it into the AI assistant you already use. It is for practice and preparation. A person still decides, speaks and sends.
The CRM behind it
A pipeline where each stage means something.
What must be true before a deal moves on, and the fields that hold the method. We set this up in the CRM you already run.
- 1DiscoverySignal: Why now and Buyer's deadline are filled in. The CRM blocks the move while either is empty.
- 2Problem sizedAnchor: Cost of doing nothing is a number, and Whose numbers points to the buyer contact who confirmed it.
- 3Stakeholders and proofList and Evidence: every buying role sales leadership named has a contact attached, and each open objection has evidence sent or a note of what is still owed.
- 4NegotiationConcessions, Options and Yes: the give and get list is approved, the walk-away and both alternatives are written, and there is a dated next step owned by a buyer contact. Without that date the deal is out of the forecast.
- 5ContractPaper: the mutual plan has an owner on each side and a date for every step, and the overdue steps count is zero.
- 6Closed wonThe agreement is signed, a start date is set, and the terms that were traded are recorded on the account for whoever manages the customer next.
| Field | Why it exists |
|---|---|
| Why now and Buyer's deadline | Decides whether a deal can leave discovery. A deal with no buyer date has no reason to close this period. |
| Cost of doing nothing (per month) and Whose numbers | Decides whether a price can be sent. The manager can see the anchor and who on the buyer's side agreed it. |
| Buying role on each deal contact | Decides whether a deal can enter negotiation, and powers the report of deals with no budget holder attached. |
| Open objections (list with status) | Gives the manager something specific to coach before the next call, and a count that can be reported. |
| Give and get list with Approved by | Decides who signs off a trade, and leaves a record of what was given and what came back. |
| Walk-away, Our alternative and Buyer's alternative | Decides whether a pricing call goes ahead. Visible only to the rep, the manager and leadership. |
| Next step, Next step owner and Next step date | Decides whether the deal counts in the forecast. This is the field the forecast rule reads. |
An invented example
A worked rollout
This is an invented example to show the four weeks in order. The company, the people and every number are made up.
- 1
The setup
A made-up company sells packaging equipment to food producers. It has 8 reps, 2 sales managers and one operations manager who owns the CRM. The reps finished negotiation training last quarter, and the owner cannot see any sign of it in the pipeline.
- 2
Week 1: the audit
The operations manager exports 20 open deals and asks an AI assistant to list which of the eight moves have nothing written down on each one. She checks the list against the records herself. In this example, 6 of the 20 have a buyer deadline, so 14 have no Signal, and 3 have a cost of doing nothing, so 17 have no Anchor. She builds the fields and shows the two counts to the owner.
- 3
Week 2: the stage rules
She asks the sales managers one question per stage and writes the answers as exit criteria. Discovery now needs the Signal fields. Negotiation needs the buying roles from List and the walk-away from Options. Of the 20 deals, 9 are sitting in negotiation, and 5 of those have no budget holder attached. The managers decide those 5 go back a stage until the role is filled.
- 4
Week 3: the forecast rule
That leaves 4 deals in negotiation. She builds the Yes rule: no dated next step owned by the buyer, no place in the forecast. One of the 4 has a next step date in the past, so the forecast shows 3. The owner dislikes the smaller number and accepts it, because each of the 3 has a named person and a day beside it.
- 5
Week 4: AI checks and handover
She sets up one AI check that reads each deal in negotiation every week and lists what is missing, including any Paper step past its date. The list goes to the two managers, who decide what to raise with each rep. She writes down who owns the check, who reviews it and what it costs to run, then publishes the field dictionary so a future admin can maintain it.
Sources
- Salesforce (2022). New Research Reveals Sales Reps Need a Productivity Overhaul – Spend Less than 30% Of Their Time Actually Selling. Salesforce.
- Validity (2024). The State of CRM Data Management in 2024. Validity.
- Loewenstein, J., Thompson, L., & Gentner, D. (1999). Analogical encoding facilitates knowledge transfer in negotiation. Psychonomic Bulletin & Review, 6(4), 586-597.
- Paul J. Taylor, Darlene F. Russ-Eft, Daniel W. L. Chan (2005). A Meta-Analytic Review of Behavior Modeling Training. Journal of Applied Psychology (American Psychological Association).
- Salecopy.io. The booked revenue that was counted twice. Salecopy.io case study.
Every outside figure on this site was opened at its original publisher and checked twice before it was published. See all the research and how we check it.
Questions about this program
Which CRMs does this work in?
HubSpot, Salesforce and similar systems. The program is built on the CRM you already own, using its standard fields, required-field rules, lists and reports, and everything built is yours to keep. If the records need work first, see [CRM cleanup](/services/crm-cleanup/).
Will reps actually fill the fields in?
Nobody can promise that, and the program is designed around the risk. Each field is asked for only at the stage where it is needed, each one is tied to a decision the manager makes in the weekly review, and the forecast rule reads the next step date. A field that a manager asks about every week gets filled in. A field nobody looks at does not, so the program cuts those.
Does the AI change deals or message buyers?
No. The AI checks read the record, flag what is missing and propose text for a person to confirm. A person decides, speaks and sends, and a person moves every deal between stages.
How long is it and how do we start?
It runs for four weeks and is quoted per team. The first step is a free 30-minute audit at [/contact/](/contact/) to look at your fields, stages and forecast as they are today. The sales team's side of the method is covered in the sector programs at [/training/](/training/).
Keep reading
The Salecopy Method · 5 min read
The Salecopy Method: eight moves for negotiating a deal
The eight moves of The Salecopy Method in one line each, why each one is written on the deal record, and how to start this week.
Read itFour-week program
Tech
A four-week program that teaches software and tech sales teams to negotiate in eight written moves, with AI practice drills and the CRM fields to match.
See the programAsk about this program
Tell us about your team.
How many people sell, what you sell, and where deals get stuck. We reply with a written outline and a fixed quote for your team.