Wholesaling SOPs that live inside your CRM: shown at the moment of the task, checked without a meeting
Every wholesaling company eventually writes SOPs: a shared document with how a cold caller handles a lead, how acquisitions runs an appointment, how dispo sends a deal. A month later, nobody opens it. New hires read it once, the team drifts, and the owner is back to correcting the same mistakes by message. The fix isn't a better document, it's moving each rule to the place the work happens, so the CRM shows it when it matters, requires it when it must be right and reports on whether it was followed. This guide shows the five-line format I use for an SOP, the SOPs a 10 to 50 person team needs by role, and where in Salesforce each part belongs.
Write each SOP in five lines: the trigger, the owner, up to seven steps, a done-when check and a clock. Then put each piece where work happens: the steps as guidance on the Path or as tasks a flow creates, the must-haves as required fields and validation messages, the clock as an alert, and the done-when check as a report that shows how often it was met. Keep a short document only as an index and for the why.
Why do SOP documents stop being used?
- They live somewhere else. The rule is in a document and the work is in the CRM, so reading the rule is an extra step nobody takes under pressure.
- They're too long. A ten-page SOP is read once. A seven-step one is used.
- Nothing checks them. If skipping a step costs nothing and shows nowhere, it gets skipped.
- They go stale. The process changes, the document doesn't, and the team learns to ignore it.
- They describe an ideal, not the job. They say what should happen, not what the system shows, requires and records.
What is the five-line SOP?
- Trigger: the event that starts it. "A seller sets an appointment."
- Owner: one role or person. "The acquisitions rep on the lead."
- Steps: seven at most, each starting with a verb. If it needs more than seven, it's two SOPs.
- Done when: the observable result. "The appointment has a date, a confirmed address and every decision maker named."
- Clock: how long it may take, and what happens if it doesn't. "Confirmed by the morning of; alert to the manager if not."
A "done-when" that you can't check in the CRM is a warning sign. Either the CRM is missing a field or the SOP is too vague.
Which SOPs does each role need?
| Role | SOPs (one each) |
|---|---|
| Cold caller or VA | Working a list; logging a call outcome; handing off an interested seller; handling do-not-call and wrong numbers |
| Lead manager | First response to an inbound lead or missed call; reassigning an unclaimed lead; weekly duplicate clean-up |
| Acquisitions | Running an appointment; making and sending an offer; following up an offer; closing out a dead deal with a reason and a date |
| Dispositions | Marketing a contract to buyers; recording buyer responses; assigning and collecting the fee |
| Transaction coordinator | Opening title; tracking closing dates; confirming funding; filing documents on the deal |
| Marketing | Launching a campaign with its cost and source tags; loading a list (importing a list) |
| Ops or admin | Adding a user and their access; checking automations for errors; changing a field or stage safely |
That's about twenty SOPs for a full team, and a new company doesn't need all of them on day one; see "start with three" below. Who owns what in more detail is on team roles and the CRM.
Where does each part live in Salesforce?
| SOP part | Where it lives |
|---|---|
| Trigger | A record-triggered flow or a stage change, so the SOP starts itself |
| Owner | The record owner or a queue with a claim rule |
| Steps | Guidance on the Path step (up to 1,000 characters), or tasks created by a flow, one per step, with the instruction in the task description |
| Must-haves | Required fields and validation rules with specific messages ("Add the closing date before moving to Under contract") |
| Done when | The fields filled in, plus a checkbox or status that a manager can report on |
| Clock | A date field and a scheduled flow that creates a task or alerts a manager when it's late |
| Guided data entry | A screen flow for multi-step jobs such as logging an offer, so the user fills in the right things in the right order |
| The why and the exceptions | A short document linked from the record or the Path, kept to a page |
The pipeline stage rules in pipeline stages are SOPs in this form: entry, exit, owner and clock for each stage. The call outcomes in the cold-calling setup are another.
How do you check that SOPs are followed?
For each SOP, pick one measure the CRM can report and put it on a manager's screen:
- Appointment SOP: percentage of appointments with all decision makers named.
- Offer SOP: percentage of offers with a follow-up date set within a day.
- Handoff SOP: percentage of handoffs accepted by acquisitions without being sent back.
- Dispo SOP: time from contract to buyers contacted.
- Do-not-call SOP: number of records with a do-not-call flag that still have an open task.
A weekly look, five minutes, with one question per measure: who needs help? Not who to blame. If most of the team misses a step, the SOP or the system is wrong, not the people. The Monday numbers in the Monday 5 give the owner's view on top.
How should you train and update?
- Day one, on a practice record. A new hire works a test lead from new to closed, with the Path and tasks guiding them. They learn the SOPs by doing them, and you see where they stumble.
- One owner per SOP, who reviews it every quarter and whenever a mistake repeats.
- Change the system and the guidance together. If you rename a stage or add a field, update the Path guidance in the same change.
- Write down the reason. One line, "we require the closing date here because title can't open without it", saves a lot of arguments.
- Keep access narrow. People follow the SOP for their role more easily when they see only what that role needs; see who sees what.
What are the three to write first?
- First response to a new lead or missed call. It's where most money leaks (speed to lead).
- The cold-caller-to-acquisitions handoff. It's where most deals get lost between two people (handoff checklist).
- Offer sent to offer answered. It's where the pipeline sits longest (offer follow-up).
Write those three in the five-line form, build each into the CRM, run them for a month and look at the measures. Then add the next three. If you want the setup done once and properly, that's included in an audit and in ongoing support.
Questions
What SOPs does a wholesaling company need?
Roughly twenty for a full team, grouped by role: caller and VA, lead manager, acquisitions, dispositions, transaction coordinator, marketing and ops. A new company can start with three: first response to a new lead, the caller-to-acquisitions handoff, and offer follow-up.
How do I make my team actually follow SOPs?
Put each step where the work happens: guidance on the Path, tasks a flow creates, required fields with clear messages, and a manager report on whether it was followed. A document nobody opens can't change behavior; a field that won't save without the right data does.
How long should an SOP be?
Seven steps at most. If it needs more, it's two SOPs. Add a trigger, an owner, a done-when check and a clock, and keep the explanation of why on one page.
Where should SOPs live, in a doc or in the CRM?
In the CRM wherever possible, because that's where the work is done. Keep a short document as an index and for the reasons behind the rules, and link it from the record or the Path.
How do I train a new VA on my CRM?
Give them a practice record to work from new to closed, with the Path guidance and tasks leading them, limited access to what their role needs and a manager who checks their first week of work against the SOP measures.
How do I know whether an SOP is being followed?
Pick one measure per SOP that the CRM can report, such as the percentage of offers with a follow-up date set within a day, and review it weekly. If most people miss a step, fix the SOP or the system rather than blaming the team.
Related guides
Sources
Checked in October 2026. Salesforce and vendor features change with each release, so check the linked page before you rely on a detail.
- Trailhead: Visualize Success with Path and Kanban. Up to five key fields and up to 1,000 characters of guidance per path step
Want your SOPs built into the system?
The CRM Revenue Audit (USD 1,500, fixed price) shows which of your rules the CRM already enforces and which only live in people's heads, with a fix plan. It's for teams already on Salesforce.
Book a free callSee the Revenue AuditOr just ask one question about your setup: email · WhatsApp · LinkedIn
