Stage definition one-pager
A free 2-page PDF that helps you write down what has to be true before a deal moves, so your forecast rests on facts.
The problem
Two people can read the same stage name two different ways. One rep's "Proposal" is a draft. Another's is a signed quote. Your forecast mixes them, and nobody notices until the quarter ends.
What you get
A 2-page PDF.
- Page 1: a worked example. Six stages for a small B2B service team, each with an exit rule, the proof to look for in your CRM, and a max number of days.
- Page 2: your version. Blank boxes you can type into or print, plus a 10-minute Friday check.
How it works
- Name your stages (use the ones already in your CRM).
- Write one sentence for each: what has to be true before a deal leaves it.
- Pick the proof: the field, note or file that shows it.
- Set the most days a deal can sit there.
- Every Friday, run the 10-minute check.
What it costs
Free. It takes about 10 minutes to fill in the first time. It works in any CRM or a spreadsheet.
The catch
It only helps if you check it. The Friday check is the part that makes it stick. Your rules will also need a tweak after the first few weeks, and that is normal.
Who it's for
Owners and small sales teams without a RevOps person: usually 1 to 15 sellers, one pipeline, and a forecast that feels like a guess.
Who it's not for
Large teams that already have a documented sales process and a RevOps owner. You likely have this covered.
About me
I'm Seth Levanen. I help small business owners and sales-led teams cut busywork without cutting quality. I call that the smart-cut. More at sethlevanen.com.