Almost every sales team playbook we have been shown lives in Google Docs and runs to 14 pages. The first three are the company mission, then come rules for talking to customers, the dress code and the holiday policy. Not a single deadline. Managers read it once when they joined.
A working playbook is shorter and duller. It is a table: pipeline stage, what has to happen there, how much time it gets, and what counts as leaving the stage.
A sample playbook with deadlines
Below is a sample for a company selling custom furniture through Instagram, Telegram and calls. The numbers are illustrative, the structure carries over to almost any business.
| Stage | What the manager does | Deadline | Exit |
|---|---|---|---|
| New lead | Replies, finds out what is needed | 15 minutes | Customer replied, or lead rejected with a reason |
| Qualification | Sizes, budget, timing, decision maker | 2 hours | Enough data for a quote |
| Measurement | Books a visit | 1 working day | Visit in the calendar |
| Quote | Sends a proposal with price and timing | 1 working day after the visit | Proposal sent, receipt confirmed |
| Decision | Calls, answers questions | 3 working days | Contract, or refusal with a reason |
| Prepayment | Issues the invoice, follows up | 2 working days | Money received |
Look at the last column. The most common mistake is describing a stage by an action ("prepare a proposal") instead of a result. A manager can always claim the action was done. A result can be checked: the proposal is in the chat or it isn't.
The manager's rules and the sales head's rules
They usually get mixed into one document. The manager's part says what to do with the customer and by when. The sales head's part says what to do when deadlines slip: who reads the report, how often, what triggers a conversation. Without the second part the first one dies within a couple of months. The minimum fits in three lines: every morning, open the overdue cards and go through the oldest; every week, check the on-time share per manager and per stage; every month, revisit the targets.
Deadlines and KPIs
Paying a bonus for the on-time share is tempting. We would hold off. Once speed affects pay, managers start moving cards to the next stage without doing anything, just to keep the timer green. Keep results (revenue, conversion) in the KPI and use deadlines to find out why results are missing. A useful check is how many lost deals in a month went through an overdue stage.
Moving the playbook into the CRM
In shamCRM a deadline is set for every pipeline status, separately for leads and deals. The timer runs only during the working hours from the pipeline's localization, so "1 working day" means exactly that, without nights, weekends or holidays. When a customer is handed to another manager, the SLA settings decide whether the deadline continues or starts from zero.
For the sales head there are reports by manager and by stage, a manager × stage matrix, a journal per card and Excel export. The journal cannot be edited by hand, and bulk moves of cards are recorded too.