Knowledge base · processes

The sales process: how to describe it so people use it

in short

A working description of a sales process fits on one page and has four columns: stage, who does it, by when, and what the result is. A twenty-page diagram gets used by nobody except the person who drew it. There is one test that matters: a new rep should be able to read it and know what to do next without asking a colleague.

The four columns

  • Stage. The name of an action, not of a state.
  • Who. A role, not a name.
  • Deadline. Specific, in hours or days.
  • Result. What now exists: a record created, an invoice sent, a payment received.

What to describe and what to leave out

  1. Describe what repeats. One-off arrangements are not part of a process.
  2. Describe the handovers between people: that is where most things get lost.
  3. Do not describe what a person does alone inside their own stage.
  4. Do not describe exceptions at the start: get the main route down first.

Where a sales process breaks most often

  • the handover from marketing to the team: it is unclear who takes the enquiry
  • the handover from the rep to production or the warehouse: lead times get promised without confirmation
  • the handover to accounts: the invoice is assembled by hand and arrives late
  • a customer coming back after a pause: it is unclear whose customer they are
On a legal project the biggest lift came from one automation on a handover: when the rep books a customer for a consultation, the date and time go into the lawyer's calendar automatically. The lawyers stopped talking to customers before payment and started working to a schedule.

How to test the description

  1. Hand it to a new rep and ask them to run one deal using the document alone.
  2. Write down every question they asked a colleague. Each question is a hole in the description.
  3. Fix it and repeat with the next new rep.

Questions people ask

Do I need a BPMN diagram?

For teaching people, a one-page table is enough. A formal diagram earns its place when the process gets automated and needs to be unambiguous.

How often should the description be updated?

Every time you change the process. A description that has fallen behind reality does more harm than none at all.

Sources: our own sales-team build schedule, the plan we run projects to; lead response speed (Harvard Business Review, Lead Response Management Study, 2025-2026 roundup); deal cycle and touches per closed deal (Gartner B2B Sales Benchmark, 939 companies, 2025); field sales productivity (RepMove, 2025). Market figures are averages, mostly non-Ukrainian. Project figures are Double Sales' own measurements on 2026 engagements.
if you need this done in your company

We describe your sales process and tie it into your records and phone system. Part of the build, from $1500 a month.

Book a call