Как правильно нанять и собрать идеальный отдел продаж

Курс о том, как спроектировать структуру отдела продаж, подобрать сильных сотрудников и выстроить управляемую систему достижения плана. Вы научитесь формировать профиль кандидата, проводить эффективный отбор, адаптацию и обучать команду, а также внедрять мотивацию, KPI и контроль качества продаж.

1. Цели, стратегия и роль отдела продаж в компании

Цели, стратегия и роль отдела продаж в компании

Отдел продаж часто пытаются строить с конца: «давайте наймём менеджеров, поставим план и они начнут продавать». На практике устойчивые продажи появляются только тогда, когда в компании заранее определены роль продаж, стратегия выхода на рынок и понятные цели, которые связывают ежедневные действия команды с бизнес-результатом.

Эта статья задаёт фундамент для следующих тем курса: как выбрать структуру отдела, какие роли нанимать, какие компетенции проверять на интервью, как ставить KPI и как управлять воронкой.

Роль отдела продаж

Отдел продаж — это функция, которая превращает спрос и интерес рынка в контракт и выручку через управляемый процесс взаимодействия с клиентом. В зависимости от бизнес-модели роль продаж может быть разной.

Ключевые роли продаж в компании:

  • Создавать предсказуемый поток новых сделок (pipeline).
  • Конвертировать интерес в оплату через переговоры и закрытие.
  • Подтверждать ценность продукта: что и почему покупают, какие возражения мешают.
  • Удерживать фокус на целевом клиенте (ICP) и приоритете сегментов.
  • Синхронизировать ожидания клиента с тем, что реально поставит продукт и сервис.
  • Важно: отдел продаж — не «герои, которые спасают месяц». Это производственная система. Если система не описана, то результаты будут зависеть от отдельных людей и удачи.

    Продажи как часть стратегии компании

    Стратегия компании отвечает на вопросы: кому продаём, какую проблему решаем, почему купят у нас и как мы доставляем ценность. Продажи — это способ реализации этой стратегии на практике.

    Чтобы не строить отдел продаж «в вакууме», заранее зафиксируйте:

  • Целевые сегменты и география.
  • Идеальный профиль клиента (ICP) и ключевые сценарии использования.
  • Позиционирование и основную ценность (value proposition).
  • Модель монетизации и тип сделки (разовый платёж, подписка, лицензия).
  • Каналы привлечения (маркетинг, партнёры, outbound, inbound, product-led).
  • Полезные понятия для ориентира:

  • Go-to-market стратегия — как компания выводит продукт на рынок и организует продажи.
  • Отдел продаж — базовое определение и функции.
  • Как связать цели бизнеса и цели отдела продаж

    Цель продаж — не «делать звонки» и не «закрывать побольше». Цель — достигать бизнес-результата через управляемые показатели.

    Разложение целей обычно выглядит так:

  • Бизнес-цель: рост выручки, прибыльности, доли рынка, удержания.
  • Коммерческая цель: план по новой выручке, продлениям, расширениям.
  • Операционные цели продаж: достаточная воронка, нужная конверсия, контроль цикла сделки.
  • Удобный подход — формулировать цели по принципу OKR:

  • Objective — качественная цель (что хотим изменить).
  • Key Results — измеримые результаты (как поймём, что достигли).
  • Пример (упрощённо):

  • Objective: сделать продажи предсказуемыми в сегменте SMB
  • Key Results:
  • 1. Достичь плановой новой выручки за квартал 2. Обеспечить минимальный размер активной воронки на конец каждого месяца 3. Сократить средний цикл сделки

    Здесь важно: цели не должны противоречить друг другу. Например, цель «сильно поднять средний чек» часто конфликтует с целью «сильно сократить цикл сделки», если продукт и рынок к этому не готовы.

    Стратегия продаж: что именно должно быть определено

    Стратегия продаж — это набор решений, которые делают действия команды повторяемыми.

    Что нужно определить до массового найма:

  • Сегментация: какие сегменты приоритетны и почему.
  • Пакетирование и предложение: что продаём (пакеты/тарифы), какие ограничения и что считается «успехом» сделки.
  • Процесс сделки: этапы воронки и критерии перехода между этапами.
  • Каналы: inbound, outbound, партнёры, PLG — и доля каждого.
  • Роли: кто ищет лидов, кто квалифицирует, кто закрывает, кто ведёт аккаунты.
  • Коммерческие правила: дисконт-политика, условия оплаты, стандарты договора.
  • Конкурентная позиция: против кого чаще всего продаём и чем отвечаем.
  • !Воронка продаж с этапами, критериями и метриками

    Если вы не задаёте правила игры, их зададут менеджеры «как привыкли». Это приводит к разнородной воронке и невозможности прогнозировать.

    Какие метрики отражают стратегию (и зачем они нужны)

    Метрики нужны не ради контроля, а чтобы понимать: стратегия работает или нет.

    Базовый набор (адаптируйте под модель):

  • Выручка: новая, повторная, расширение.
  • Воронка: объём pipeline и его качество.
  • Конверсия по этапам: где «протекает» процесс.
  • Скорость: длина цикла сделки и длительность этапов.
  • Юнит-экономика: стоимость привлечения и окупаемость.
  • Если у вас модель с долгосрочными отношениями (подписка, регулярные продления), важно знать:

  • Пожизненная ценность клиента (CLV) — сколько в среднем приносит клиент за всё время.
  • Метрики без интерпретации вредны. Например, «больше звонков» не равно «больше выручки», если звонки идут не в тот сегмент или менеджеры не умеют квалифицировать.

    Где отдел продаж заканчивается и начинается работа других команд

    Сильный отдел продаж опирается на согласованные границы ответственности.

    Типовая стыковка:

  • Маркетинг → продажи: маркетинг формирует спрос и лиды, продажи квалифицируют и закрывают.
  • Продажи → продукт: продажи передают сигналы рынка, продукт решает, что развивать.
  • Продажи → внедрение/аккаунтинг/поддержка: продажа обещает только то, что команда доставки реально выполнит.
  • Чтобы не было конфликтов, заранее закрепите:

  • Определение «качественного лида» (что считается подходящим контактом).
  • Кто и когда отвечает клиенту, и как фиксируется следующий шаг.
  • Как эскалируются скидки, нестандартные условия и «особые обещания».
  • Типовые ошибки, которые ломают продажи ещё до найма

  • Нанимают «универсальных сильных продавцов», но не описывают сегмент, оффер и процесс.
  • Ставят план по выручке без понимания, откуда взять достаточную воронку.
  • Не фиксируют этапы и критерии воронки, из-за чего CRM становится «списком контактов».
  • Подменяют стратегию активностью: отчётность по звонкам вместо управления конверсией.
  • Обещают клиентам то, что продукт/сервис не может стабильно дать.
  • Практический итог: что должно быть готово перед построением отдела

    Минимальный набор артефактов, которые стоит подготовить до найма ключевых ролей:

  • Портрет целевого клиента (ICP) и список приоритетных сегментов
  • Короткое и чёткое ценностное предложение
  • Описанная воронка продаж с этапами и критериями
  • Правила квалификации (что мы считаем хорошей возможностью)
  • Базовая коммерческая политика (цены, скидки, типовые условия)
  • Набор метрик для управления (не больше 8–12 на старте)
  • В следующей статье логично перейти к тому, какую структуру отдела продаж выбрать под вашу стратегию и какие роли действительно нужны на первом этапе, чтобы не переплатить и не построить «отдел активности» вместо отдела результата.

    2. Структура отдела: роли, воронка и модель продаж

    Структура отдела: роли, воронка и модель продаж

    В предыдущей статье мы зафиксировали основу: роль продаж, стратегию выхода на рынок и цели, которые связывают работу команды с бизнес-результатом. Теперь следующий шаг: превратить стратегию в операционную конструкцию.

    Структура отдела продаж — это ответ на три практических вопроса:

  • Как мы продаём: модель продаж (откуда берутся клиенты и как идёт сделка).
  • Через какие этапы проходит клиент: воронка продаж (процесс и критерии).
  • Кто выполняет работу на каждом этапе: роли, ответственность и передачи.
  • Если эти три элемента не согласованы, у вас почти неизбежно появятся проблемы: в CRM “всё на 70%”, прогноз не сходится, менеджеры спорят “чья задача”, а найм превращается в лотерею.

    Как связаны модель продаж, воронка и роли

    Один и тот же продукт можно продавать разными способами. Но структура всегда должна быть логичной:

  • Модель продаж задаёт тип контакта и длину пути клиента.
  • Воронка описывает повторяемый маршрут от интереса до оплаты.
  • Роли обеспечивают пропускную способность воронки и качество работы на каждом шаге.
  • Простой ориентир: если у вас длинный цикл сделки и много действий до контракта, то разделение ролей обычно повышает эффективность. Если сделки короткие и простые, то универсальные менеджеры часто выигрывают по скорости и стоимости.

    Модель продаж: как клиент приходит и как вы закрываете

    Модель продаж отвечает на вопрос: какой основной путь клиента к покупке.

    Чаще всего встречаются такие источники сделок:

  • Inbound: клиент сам оставляет заявку или приходит из маркетинга.
  • Outbound: вы сами инициируете контакт (холодные письма, звонки, LinkedIn).
  • Партнёры: сделки приходят через интеграторов, реселлеров, реферальные программы.
  • Product-led: клиент начинает пользоваться продуктом, а продажа подключается позже.
  • Также важно различать тип сделки:

  • Транзакционные продажи: короткий цикл, небольшой чек, решение простое.
  • Консультативные продажи: нужно выяснять потребности, собирать требования, считать эффект.
  • Корпоративные продажи: много стейкхолдеров, тендеры, безопасность, юридические согласования.
  • Ниже — практичная карта, которая помогает выбрать первичную структуру.

    | Признак | Если так | Что это означает для структуры | |---|---|---| | Размер сделки | Небольшой чек | Часто достаточно full-cycle менеджеров | | Цикл сделки | Дни или 1–2 недели | Меньше смысла дробить роли | | Источник спроса | Много inbound-лидов | Нужны скорость обработки и квалификация | | Источник спроса | Outbound — основной канал | Нужны роли, которые ежедневно генерируют встречи | | Сложность внедрения | Простая активация | Меньше нагрузки после закрытия | | Сложность внедрения | Сложное внедрение и обучение | Нужны внедрение и/или customer success |

    Полезная точка опоры для терминологии процесса: Sales process.

    Воронка продаж: этапы, критерии и управляемость

    Воронка продаж — это не “красивые стадии в CRM”, а единый стандарт, по которому команда понимает:

  • где находится сделка;
  • что уже сделано и что обязательно сделать дальше;
  • по каким признакам сделка может двигаться вперёд;
  • кто отвечает за следующий шаг.
  • Важно различать:

  • Этап — часть процесса (например, “диагностика”).
  • Критерии перехода — наблюдаемые условия, при которых этап считается завершённым.
  • Следующий шаг — конкретное запланированное действие (встреча, письмо с КП, согласование).
  • Если критериев нет, этапы превращаются в субъективные оценки (“мне кажется, клиент тёплый”), и прогноз становится недостоверным.

    Ниже пример базовой воронки для B2B с разделением труда. Подстройте названия и логику под вашу модель.

    | Этап | Цель этапа | Критерии перехода (пример) | Ответственный | |---|---|---|---| | Лид | Понять, есть ли контакт и компания | Контакт валиден, есть способ связи | SDR/BDR или маркетинг | | Квалификация | Проверить соответствие ICP и интерес | Подтверждены сегмент, задача, роль ЛПР/влияющего | SDR/BDR | | Диагностика | Понять проблему, ценность, контекст | Зафиксированы потребность, текущая ситуация, критерии выбора | AE | | Предложение | Сформировать решение и условия | Отправлено КП, согласованы ключевые условия | AE | | Переговоры | Снять риски и возражения, согласовать договор | Согласованы цена, сроки, юридические правки | AE + руководитель | | Закрытие | Получить подписанный контракт и оплату | Подписано, выставлен счёт, подтверждена оплата | AE + финансы | | Передача | Передать клиента в внедрение/аккаунтинг | Зафиксированы ожидания, план запуска, ответственные | AE → CSM/внедрение |

    !Схема показывает этапы воронки и распределение ответственности по ролям

    Отдельно: CRM должна поддерживать именно этот стандарт. CRM — это инструмент фиксации процесса, а не “записная книжка”. Справка по понятию: Customer relationship management.

    Роли в отделе продаж: кто за что отвечает

    Ниже — основные роли, которые чаще всего встречаются в коммерческой функции. Не все нужны сразу: роль должна появляться тогда, когда без неё “узкое место” начинает ограничивать рост.

    SDR/BDR (развитие продаж)

    Задача: создавать поток квалифицированных встреч и возможностей.

  • SDR часто фокусируется на inbound (быстро обработать и квалифицировать заявки).
  • BDR чаще ассоциируют с outbound (самостоятельно инициировать контакт).
  • Типовые результаты роли:

  • назначенные встречи с подходящими компаниями;
  • квалифицированные возможности, переданные дальше.
  • AE (Account Executive, закрытие сделок)

    Задача: провести клиента от диагностики до контракта.

    Типовые результаты роли:

  • закрытая новая выручка;
  • прогнозируемый pipeline по своим сделкам;
  • корректные обещания клиенту для успешной передачи.
  • AM (Account Manager, развитие действующих клиентов)

    Задача: расширять выручку в текущей базе, работать с допродажами и апсейлом.

    Типовые результаты роли:

  • расширения (up-sell/cross-sell);
  • рост доли продукта у клиента;
  • план аккаунта по крупным клиентам.
  • CSM (Customer Success Manager)

    Задача: обеспечить ценность после продажи, снизить отток и увеличить продления.

    Важно: CSM — не поддержка “по тикетам”, а управление успехом клиента. Базовое определение: Customer success.

    Типовые результаты роли:

  • успешное внедрение/запуск;
  • продления;
  • рост использования и удовлетворённости.
  • Presales / Sales Engineer (если продукт сложный)

    Задача: помочь технически продать решение (демо, архитектура, безопасность, интеграции).

    Типовые результаты роли:

  • качественные демо и пилоты;
  • снятые технические риски;
  • стандартизированные ответы на вопросы безопасности и интеграций.
  • Руководитель продаж (Head of Sales / Sales Manager)

    Задача: управлять системой — людьми, процессом, воронкой, прогнозом.

    Типовые результаты роли:

  • выполнение плана и управляемый прогноз;
  • развитие менеджеров;
  • дисциплина процесса и качество данных.
  • Sales Ops / RevOps (когда появляется масштаб)

    Задача: обеспечить повторяемость и эффективность — CRM, отчётность, правила, компенсации, инструменты.

    Эта роль часто окупается, когда:

  • растёт число менеджеров и источников лидов;
  • руководитель продаж тонет в операционке;
  • качество данных в CRM мешает управлению.
  • Типовые модели структуры отдела

    Ниже — несколько рабочих “шаблонов”. Их можно комбинировать.

    Full-cycle менеджеры

    Один менеджер ведёт весь цикл: поиск → квалификация → закрытие.

    Подходит, если:

  • сделки относительно простые;
  • цикл короткий;
  • лидов немного и их нужно “добывать” самим;
  • важна гибкость и скорость.
  • Риск: менеджер постоянно переключается между задачами, а верх воронки часто проседает.

    Разделение SDR/BDR + AE

    SDR/BDR создаёт и квалифицирует возможности, AE закрывает.

    Подходит, если:

  • есть регулярная потребность в генерации встреч;
  • лидов много, но качество разное;
  • цикл сделки требует глубокой диагностики и переговоров.
  • Риск: плохая передача и “споры за качество” без чётких критериев квалификации.

    Hunter / Farmer

  • Hunter: фокус на новых клиентах.
  • Farmer: фокус на базе (продления и расширения).
  • Подходит, если:

  • выручка сильно зависит от удержания и расширения;
  • есть база клиентов, с которой нужно системно работать;
  • продукт раскрывает ценность со временем.
  • Риск: если границы ответственности не закреплены, клиент получает “двух хозяев”.

    Pods (мини-команды по сегменту)

    Небольшая связка ролей на сегмент: SDR + AE + CSM (иногда пресейл).

    Подходит, если:

  • у сегмента свой сценарий продаж;
  • важно быстро учиться на обратной связи;
  • нужна плотная связка продажи и запуска.
  • Риск: дороже в управлении, требует зрелых процессов.

    !Пример структуры отдела по сегментам с pods и общей функцией Ops

    Как выбрать структуру: практический алгоритм

    Чтобы не выбирать “как у конкурента”, привяжите структуру к вашей стратегии и ограничениям.

  • Опишите 1–2 приоритетных сегмента и их ICP (из предыдущей статьи).
  • Зафиксируйте “основной путь сделки” для каждого сегмента: inbound, outbound, партнёры, product-led.
  • Запишите этапы воронки и критерии перехода.
  • Найдите узкое место, отвечая на вопросы:
  • Где чаще всего срываются сделки: на входе, в диагностике, в переговорах, на юридическом этапе?
  • Чего не хватает: встреч, квалификации, качественных демо, времени на переговоры, ресурса на запуск?
  • Кто перегружен: один менеджер “всё делает” или наоборот, слишком много передач?
  • Подберите роли так, чтобы разгрузить узкое место, а не “сразу построить корпорацию”.
  • Практичное правило: сначала стабилизируйте процесс и критерии, и только затем масштабируйте людей. Иначе вы просто масштабируете хаос.

    Минимальная структура на старте: что нанимать первым

    Ниже — ориентиры, от которых удобно отталкиваться. Это не универсальная истина, а стартовая рамка.

    Если продажи простые и цикл короткий

  • 1–3 full-cycle менеджера
  • 1 руководитель (часто фаундер/коммерческий директор на старте)
  • Когда добавлять SDR:

  • когда менеджеры перестают успевать генерировать встречи и закрывать сделки одновременно;
  • когда inbound много, но конверсия в встречи низкая из-за медленной реакции.
  • Если продажи сложные и цикл длинный

  • SDR/BDR (или фокус на лидогенерации у одного человека)
  • AE
  • Presales (по необходимости, часто частично занятость)
  • CSM/внедрение (если без запуска клиенты не получают ценность)
  • Главный фокус: качественная диагностика, доказательство ценности, контроль ожиданий на передаче.

    Стыки между ролями: как избежать “провалов”

    Структура ломается не на ролях, а на передачах.

    Что обязательно стандартизировать:

  • Определение квалифицированной возможности: что должен подтвердить SDR/BDR до передачи.
  • Шаблон передачи в сделку: контекст клиента, цель, боли, участники, следующий шаг.
  • Правила “кто главный” в коммуникации с клиентом на каждом этапе.
  • Момент передачи в CSM/внедрение: не после оплаты “как получится”, а по чек-листу.
  • Если у вас много входящих лидов от маркетинга, зафиксируйте SLA между маркетингом и продажами:

  • что считается лидом нужного качества;
  • за какое время продажи обязаны отреагировать;
  • что маркетинг получает обратно (статусы, причины отказов).
  • Типовые ошибки при проектировании структуры

  • Нанимают роли “по моде”, а не под узкое место воронки.
  • Делают слишком много этапов воронки без критериев и ответственности.
  • Дробят роли рано: появляется много передач, а качество не контролируется.
  • Не разделяют “новые продажи” и “работу с базой” там, где база уже даёт существенную выручку.
  • Считают, что CRM сама наведёт порядок без стандарта процесса.
  • Итог: что должно быть готово перед наймом в структуру

    Перед тем как нанимать людей в конкретные роли, подготовьте артефакты:

  • описание модели продаж по приоритетным сегментам;
  • воронку с этапами и критериями перехода;
  • карту ролей и зон ответственности (кто, что делает и что передаёт);
  • минимальные требования к качеству данных в CRM;
  • понимание первого узкого места (что именно должны улучшить новые люди).
  • В следующих материалах курса логично перейти к тому, как описать профили кандидатов под выбранные роли и как проводить интервью так, чтобы нанимать людей под вашу модель продаж и воронку, а не “просто опытных продавцов”.

    3. Портрет идеального продавца и требования к компетенциям

    Ideal Salesperson Profile and Competency Requirements

    In the previous articles, we defined the role of sales in the company, the go-to-market decisions, and then translated strategy into an operating design: sales model, funnel stages with criteria, and roles (SDR/BDR, AE, AM, CSM, presales, leader). Now we can answer the hiring question correctly: who exactly should we hire.

    There is no universal “best salesperson”. There is only the best fit for your sales model, funnel, and role boundaries.

    This article shows how to build a role-specific ideal salesperson profile and convert it into measurable competency requirements you can use for:

  • job descriptions that attract the right people
  • structured interviews that reduce hiring mistakes
  • a consistent hiring scorecard
  • onboarding plans that develop what is trainable
  • Why an “ideal seller” depends on your model and funnel

    A salesperson is a production unit inside your revenue system. If your system is unclear, you will end up hiring “experienced sellers” who succeed in their own way, but not necessarily in yours.

    Your ideal profile should be derived from:

  • Sales motion: inbound, outbound, partner-led, product-led
  • Deal type: transactional, consultative, enterprise
  • Sales cycle length and number of stakeholders
  • Funnel stages and exit criteria (what must be true to move forward)
  • Role split (full-cycle vs SDR+AE, hunter/farmer, pods)
  • Example: a strong outbound SDR needs high activity discipline and messaging iteration, while an enterprise AE needs stakeholder mapping, value cases, and negotiation stamina.

    Define the role outcome first (not the personality)

    Start the profile from outcomes, not from traits like “charismatic” or “extrovert”. Outcomes are stable and measurable.

    For each role, write 3–6 outcome statements.

    Outcome examples by role

  • SDR/BDR
  • - produces qualified meetings with ICP-fit accounts - turns “no response” into conversations through systematic follow-up - maintains clean handoffs with context and next steps
  • AE (closing new business)
  • - runs structured discovery and quantifies the problem - advances deals stage by stage with documented criteria - closes agreements without overpromising to delivery teams
  • AM (account growth)
  • - expands usage and revenue in existing accounts - builds account plans and multi-threading (more than one contact) - identifies churn risks early and acts on them
  • CSM (customer success)
  • - drives adoption and measurable value realization - increases renewals through proactive success plans - coordinates stakeholders across the customer organization

    If you cannot express the outcome, you cannot accurately assess it.

    Build a competency model: what must be true for outcomes to happen

    A practical competency model has four layers:

  • Knowledge: what the person must understand
  • Skills: what the person must be able to do repeatedly
  • Behaviors: how they operate day-to-day under pressure
  • Values and ethics: what they will not compromise
  • You do not need a large framework. You need a usable hiring standard.

    The difference between must-have and trainable

    Not every competency should be a hard requirement.

  • Must-have: hard to teach fast, high risk if missing
  • Trainable: can be developed with onboarding and coaching
  • Typical must-have examples:

  • integrity (no manipulation, no lying in CRM, no hidden discounts)
  • learning ability and coachability
  • baseline communication (clarity, structure)
  • role-specific core skill (for SDR: outreach and follow-up discipline; for AE: discovery)
  • Typical trainable examples:

  • product details
  • internal tools and CRM workflows
  • your specific pitch and messaging
  • parts of your negotiation playbook
  • Core sales competencies (role-agnostic) and how to define them

    Below is a set of competencies that appear in most sales roles. The goal is not to include all of them, but to define which ones matter most for this role.

    Communication clarity (spoken and written)

    What good looks like:

  • uses short, structured explanations
  • confirms understanding and next steps
  • writes emails/messages with one clear objective
  • How to assess:

  • role-play: “Explain your product in 60 seconds to an ICP buyer”
  • writing sample: “Write a follow-up email after a discovery call”
  • Customer discovery (needs and context)

    What good looks like:

  • asks questions that reveal business impact and decision process
  • avoids pitching before understanding the situation
  • summarizes accurately and gets confirmation
  • How to assess:

  • mock discovery call with a realistic scenario
  • structured interview using the STAR method to verify past behavior
  • Qualification discipline (fit and priority)

    What good looks like:

  • identifies whether the account matches the ideal customer profile (ICP)
  • confirms the buyer’s role, urgency, and success criteria
  • stops low-probability deals early, and explains why
  • Define ICP in simple terms: a description of the kind of company and buyer where you win most often and deliver value consistently.

    Value messaging (why buy, why now, why you)

    What good looks like:

  • ties features to outcomes
  • uses customer examples or quantified impact
  • adapts messaging by segment
  • How to assess:

  • presentation task: “Deliver a 5-minute value pitch to a CFO”
  • Process discipline and CRM hygiene

    What good looks like:

  • updates stages based on criteria, not hope
  • always has a scheduled next step
  • can forecast their pipeline based on evidence
  • How to assess:

  • case exercise: “Here is a pipeline snapshot; clean it and explain the true forecast”
  • Reference concept: Customer relationship management.

    Resilience and consistency

    What good looks like:

  • handles rejection without emotional volatility
  • keeps daily activity standards stable
  • learns from losses and adjusts
  • How to assess:

  • behavioral interview: “Tell me about a quarter you missed. What changed next?”
  • Coachability and learning speed

    What good looks like:

  • asks clarifying questions
  • can repeat feedback and apply it in the next attempt
  • does not protect their ego at the cost of results
  • How to assess:

  • short role-play, then feedback, then repeat the role-play to see improvement
  • Ethics and reliability

    What good looks like:

  • does not promise what delivery cannot deliver
  • does not hide deal risks
  • escalates issues early
  • This competency protects revenue quality and customer retention.

    Role-specific competency emphasis

    Do not assess every candidate with the same “sales template”. Select and weight competencies by role.

    | Competency | SDR/BDR emphasis | AE emphasis | AM/CSM emphasis | |---|---|---|---| | Prospecting and outreach | High | Medium | Low | | Discovery and diagnosis | Medium | High | Medium | | Negotiation and closing | Low | High | Medium | | Account planning | Low | Medium | High | | Process discipline (CRM, next steps) | High | High | High | | Stakeholder management | Medium | High | High | | Product/technical depth | Low to Medium | Medium | Medium to High |

    If your product requires structured questioning, you can borrow concepts from SPIN selling as a shared language for discovery.

    Convert the profile into a hiring scorecard

    A scorecard is a one-page document that turns “gut feeling” into consistent decisions.

    Your scorecard should include:

  • Role outcomes (3–6)
  • Competencies (6–10) with clear definitions
  • Evidence sources (which interview or task verifies each competency)
  • Scoring rules (for example, 1–5 with anchors)
  • Non-negotiables (ethics, communication baseline, role-critical skills)
  • !A practical scorecard template that standardizes how you evaluate sales candidates

    How to define scoring anchors (so “4 out of 5” means something)

    Write short behavioral anchors.

    Example for Discovery:

  • 1: pitches immediately, asks random questions, no summary
  • 3: asks relevant questions, captures some impact, partial summary
  • 5: drives a structured conversation, quantifies impact, confirms decision dynamics and next steps
  • Anchors reduce bias and make interviews comparable.

    How to assess competencies reliably

    A good hiring process uses multiple evidence types, because resumes and self-reports are noisy.

    Use a balanced mix:

  • Structured interview: same questions, same rubric, evidence-focused
  • Work sample: role-play, written task, pipeline cleanup, account plan
  • Reference checks: confirm patterns, not vague impressions
  • If a competency is critical, assess it twice in different forms.

    Common false signals (and what to do instead)

  • “Years of experience” is not proof of skill
  • - Use work samples and outcome questions
  • “Confidence” can mask lack of structure
  • - Ask for frameworks, steps, and evidence
  • “Big brand background” may hide low ownership
  • - Ask what exactly the candidate personally controlled

    Red flags that usually predict poor fit

    Treat red flags as hypotheses to verify.

  • blames market, leads, or product for everything, with no personal adjustments
  • cannot explain a sales process they actually follow
  • avoids documenting next steps and decision criteria
  • pushes for discounts early without a value case
  • overpromises and treats delivery as “someone else’s problem”
  • Practical output of this article

    By the end of this step, you should have:

  • a role-specific ideal profile defined by outcomes
  • a shortlist of must-have vs trainable competencies
  • a scorecard with definitions and scoring anchors
  • a mapping of competencies to interview stages and work samples
  • In the next article, we will convert this into a concrete hiring system: how to write job descriptions, source candidates, run structured interviews, and make decisions consistently across interviewers.

    4. Подбор и оценка кандидатов: воронка найма и интервью

    Candidate sourcing and evaluation: hiring funnel and interviews

    In the previous articles, you defined where sales fits in your strategy, then translated strategy into a sales model, funnel stages with exit criteria, and clear roles. You also built an ideal salesperson profile and a scorecard (outcomes, competencies, and evidence).

    This article turns those artifacts into an execution system: a repeatable hiring funnel and a structured interview loop that consistently selects candidates who will perform in your motion (inbound, outbound, enterprise, transactional) rather than “good talkers” who only interview well.

    What “good hiring” means in sales

    A good hiring system produces three results at the same time:

  • Speed: you can fill roles without stalling growth
  • Quality: you can predict performance better than chance
  • Consistency: two interviewers looking at the same evidence reach similar conclusions
  • If you optimize only for speed, you will overhire. If you optimize only for quality, you will never staff the team. The hiring funnel is the mechanism that balances both.

    The sales hiring funnel

    A hiring funnel is a sequence of stages where each step answers a specific question and filters candidates using evidence, not impressions.

    !A practical view of the hiring funnel from role definition to offer

    Stage outcomes: what each stage must decide

    Use the funnel to make explicit decisions.

    | Stage | The decision you make | Primary evidence | |---|---|---| | Role definition | Do we know what “good” is for this role? | Scorecard, outcomes, must-haves vs trainable | | Sourcing | Are we talking to enough right-fit people? | Source mix, response rate, pipeline volume | | Recruiter screen | Is the candidate worth manager time? | Motivation, basics, constraints | | Manager screen | Is there plausible role fit? | Past outcomes, sales process, learning behavior | | Work sample | Can they perform the core job tasks? | Role-play, writing task, pipeline exercise | | Final panel | Is the fit consistent across stakeholders? | Structured interviews, calibrated scoring | | References | Do external signals confirm patterns? | Reference notes tied to competencies | | Offer | Will they join and ramp? | Offer acceptance, start date, pre-boarding plan |

    A common failure is to run many interviews without a clear decision per stage. That creates fatigue and bias.

    Start with the scorecard and convert it into an interview plan

    Your scorecard should already define:

  • Role outcomes (what results they must produce)
  • Competencies (what must be true for outcomes to happen)
  • Evidence sources (how you will verify each competency)
  • Now map it into an interview plan where every competency is assessed intentionally.

    A simple evidence map (example)

    | Scorecard area | Best assessment method | Why it works | |---|---|---| | Prospecting discipline (SDR/BDR) | Outreach sequence task + follow-up role-play | Tests systematic behavior, not confidence | | Discovery (AE) | Mock discovery call | Reveals questioning structure and control | | Value messaging | 5-minute pitch + Q&A | Tests clarity and adaptation under pressure | | Process discipline | Pipeline cleanup exercise | Tests decision criteria and forecasting logic | | Coachability | Role-play → feedback → repeat | Tests learning speed in real time | | Ethics and reliability | Behavioral questions + scenario | Surfaces boundaries and escalation behavior |

    Sourcing: get more right-fit candidates, not more candidates

    Sourcing quality determines how hard interviews will feel. For sales roles, the best results often come from a mix.

    Practical sourcing channels

  • Referrals (high signal, but can reduce diversity of backgrounds)
  • Inbound applicants (fast, but noisy without a strong job post)
  • Outbound recruiting (targeted, best for specific motions)
  • Communities and events (role-specific groups, meetups)
  • Internal talent (CS, support, partnerships can produce strong sellers)
  • The job post is a filter, not an advertisement

    A strong job post reduces unqualified applicants and increases conversion of the right ones.

    Include:

  • Who you sell to (ICP in plain language)
  • Sales motion (inbound, outbound, enterprise, etc.)
  • What the first 90 days look like (activities and outcomes)
  • What “good” means (2–4 measurable outcomes)
  • What you will assess (work samples, role-plays)
  • Avoid vague phrases like “rockstar” and “must be charismatic”. They attract the wrong profile and add bias.

    Screening: keep it short, evidence-based, and role-specific

    Recruiter screen (15–30 minutes)

    Goal: confirm basic fit and avoid wasting manager time.

    Use consistent questions:

  • Why this role now?
  • What sales motion have you done (inbound/outbound/enterprise)?
  • What were your quota and results (with context)?
  • What are constraints (location, compensation, start date)?
  • What to listen for:

  • clarity (do they answer directly?)
  • ownership (do they describe what they did?)
  • integrity (are numbers believable and consistent?)
  • Hiring manager screen (30–45 minutes)

    Goal: check whether past behavior matches your scorecard.

    Use structured behavioral interviewing and ask for specific evidence. A useful structure is the STAR method: Situation, Task, Action, Result.

    Example questions (AE):

  • Tell me about a deal you rescued. What exactly changed after you got involved?
  • Tell me about a deal you lost that should have been winnable. What did you learn and change?
  • Walk me through your discovery approach. What do you always confirm before you present a solution?
  • Example questions (SDR/BDR):

  • Show me your best-performing outbound sequence and why it worked.
  • Tell me about a week you had low connect rates. What did you change?
  • How do you decide when to stop pursuing an account?
  • Work samples: the highest-signal part of the process

    Sales hiring is full of false positives because interviews reward confidence. Work samples reduce that risk by testing actual job tasks.

    Principles of good work samples

  • they simulate your real motion
  • they are short (30–60 minutes) and standardized
  • they have a rubric tied to the scorecard
  • they are fair: candidates get the same prompt and context
  • Work sample types by role

    SDR/BDR

  • Prospecting task: write a 5-touch sequence for one ICP account
  • Live role-play: cold call opener and objection handling
  • Prioritization: choose which accounts to contact first and explain why
  • AE

  • Mock discovery call (with a realistic ICP scenario)
  • Demo or value pitch (if your process includes it)
  • Pipeline exercise: given deal notes, set stages using exit criteria and forecast risk
  • AM/CSM

  • Account plan: expansion and renewal strategy for an existing customer
  • Risk scenario: churn signals, stakeholder change, low adoption
  • How to score a work sample (rubric example)

    Use 1–5 anchors so “4” means something.

    Example for Discovery structure (AE):

  • 1: pitches immediately, few relevant questions, no recap
  • 3: asks relevant questions, partial recap, next step is vague
  • 5: controls the flow, quantifies impact, confirms decision process, sets a clear next step
  • Structured interviews: reduce bias and increase comparability

    Unstructured interviews are inconsistent. A structured interview uses:

  • the same questions per role
  • a shared scoring rubric
  • evidence-based notes
  • independent scoring before discussion
  • This improves fairness and predictive accuracy. Background concept: Structured interview.

    Recommended interview loop (example)

    Keep the loop lean. A common pattern:

  • Recruiter screen
  • Hiring manager screen
  • Work sample (role-play or case)
  • Final panel (2–3 people, each owns specific competencies)
  • References
  • Offer
  • Panel rule: each interviewer owns a subset of competencies. Nobody “interviews for everything”.

    Panel competency ownership (example)

    | Interviewer | Competencies to assess | Method | |---|---|---| | Hiring manager | Process discipline, forecasting, coachability | Behavioral + pipeline exercise | | Peer AE/SDR | Role craft quality (discovery or prospecting) | Role-play | | Cross-functional (CS/implementation) | Expectation setting, ethics, handoff behavior | Scenario questions |

    Reference checks: verify patterns, not opinions

    References should not be a formality. They should confirm or challenge your observed signals.

    Rules:

  • ask for specific examples tied to your scorecard
  • verify patterns across time, not one-off stories
  • treat references as additional evidence, not a veto based on vague feelings
  • Example questions:

  • In what environment did they perform best (motion, deal size, cycle length)?
  • What would you coach them on in their first 30 days?
  • How reliable were they with CRM updates and internal communication?
  • Tell me about a time they handled a difficult customer situation.
  • Decision-making: how to avoid “strong opinions, weak evidence”

    The decision meeting should be short and rule-based.

    A simple decision protocol

  • Everyone submits scores independently (before discussion).
  • Start with the scorecard outcomes: do we believe they can deliver them?
  • Discuss the biggest gaps and the evidence.
  • Decide:
  • - hire - no hire - hold (only if a specific missing data point can be gathered quickly)

    Common evaluation mistakes

  • Halo effect: one great trait inflates all scores
  • Similarity bias: “they remind me of our best rep”
  • Overweighting confidence: smooth talk without structure
  • Ignoring motion mismatch: success in inbound does not guarantee outbound performance
  • The scorecard exists to prevent these errors.

    Offer and closing: treat candidates like customers

    Strong sales candidates evaluate you the way prospects evaluate products.

    Your offer process should include:

  • clarity on compensation structure and what drives payout
  • written role expectations for the first 60–90 days
  • start-date plan and onboarding outline
  • fast turnaround time (avoid losing candidates to delay)
  • If you sell with structure, hire with structure.

    What to implement right after this article

    You should be able to produce these artifacts:

  • A documented hiring funnel with stages, owners, and decision criteria
  • A role-specific interview plan mapped to your scorecard
  • At least one standardized work sample with a scoring rubric
  • A decision protocol that requires evidence, not impressions
  • In the next step of building an ideal sales team, you will connect hiring to onboarding and ramp: how to turn a “good hire” into consistent performance through training, coaching, and pipeline discipline.

    5. Онбординг и обучение: быстрый выход на результат

    Onboarding and training: fast time-to-productivity

    You can hire the right people and still miss the number if new reps ramp slowly, learn different ways of selling, or improvise the process in CRM. In the previous articles, you built the foundation for predictability: strategy and goals, then roles, funnel stages, and exit criteria, then an ideal profile and scorecard, and finally a structured hiring funnel with work samples.

    This article connects hiring to performance: how to onboard and train sales hires so they reach consistent results fast in your sales motion, not just in general.

    What “good onboarding” means in sales

    Onboarding is successful when a new hire can produce outcomes independently and repeatably.

    A practical definition of done includes:

  • They can explain your ICP and prioritize accounts accordingly.
  • They can run your sales process using funnel stages and exit criteria.
  • They can use CRM correctly and keep data forecastable.
  • They can execute the core role activities at quality and volume.
  • They can hand off customers without overpromising.
  • This is why onboarding must be measurable. Training hours and completed slide decks do not predict performance.

    Start onboarding from the sales system artifacts you already created

    Onboarding is not a generic “sales training”. It should be built from the same artifacts that your hiring scorecard and interview loop used.

    The logic is simple:

  • Your strategy defines who you sell to and why you win.
  • Your sales model and funnel define how deals move.
  • Your roles and handoffs define who does what.
  • Your scorecard defines what good performance looks like.
  • Turn these into onboarding modules and assessments.

    | Artifact you already have | What to train | How to verify (assessment) | |---|---|---| | ICP and segments | Account selection, prioritization, disqualification | Short written ICP test + account ranking exercise | | Value proposition and positioning | Messaging consistency, benefit-to-outcome mapping | 60-second pitch + 5-minute value pitch | | Funnel stages and exit criteria | Stage discipline, next steps, risk recognition | Pipeline staging exercise in CRM | | Qualification rules | What is a real opportunity vs noise | Discovery role-play + qualification checklist | | Commercial policy (pricing, discounts, terms) | Negotiation boundaries, escalation, margin protection | Scenario questions + approval path quiz | | Handoff rules to CS/implementation | Expectation setting, clean transitions | Handoff role-play + checklist completion |

    If you do not assess it, you do not control it.

    Build role-specific ramp plans (not one plan for everyone)

    A strong ramp plan is role-specific because the work is different.

    !A 0–90 day ramp timeline with milestones and role-specific differences

    A practical 30-60-90 framework

    Use 30-60-90 as a planning tool, not as bureaucracy. Each period must have:

  • skills to learn
  • work to practice
  • outputs to produce
  • | Role | First 30 days | By 60 days | By 90 days | |---|---|---|---| | SDR/BDR | Learn ICP, messaging, tools; execute supervised outreach | Run full sequences; consistently book qualified meetings | Hit steady activity and quality; predictable meeting output | | AE (new business) | Learn discovery, demo flow, proposal rules; shadow calls | Run discovery and proposals with coaching; build early pipeline | Manage a forecastable pipeline; close first deals or be near close | | AM/CSM | Learn customer outcomes, adoption metrics, renewal path | Run business reviews and success plans with support | Own renewals/expansions for a defined book with measurable adoption |

    The exact targets depend on your sales cycle length and lead flow. What matters is that outputs align with your funnel.

    Design training around practice, not information

    Most sales onboarding fails because it over-invests in product knowledge and under-invests in execution.

    A balanced onboarding program typically includes:

  • Customer and ICP context
  • Messaging and talk tracks
  • Process and CRM execution
  • Role craft practice (calls, emails, demos)
  • Negotiation and commercial rules
  • Internal collaboration and handoffs
  • Customer and product context

    Goal: a rep understands who buys, why, and what success looks like.

    What to include:

  • ICP explanation in plain language
  • Top customer problems and desired outcomes
  • Competitive landscape and common alternatives
  • A useful framework for discovery questioning is often inspired by SPIN selling, but you should translate it into your own call structure.

    Messaging and talk tracks

    Goal: a rep can explain value clearly and adapt by segment.

    Train:

  • a short pitch (one clear point)
  • a structured discovery opening
  • objection handling for your top objections
  • Verify with:

  • a recorded role-play graded with a rubric
  • a short writing task for follow-ups
  • Process and CRM discipline

    Goal: CRM reflects reality so the team can forecast and improve.

    Train:

  • funnel stages and exit criteria
  • required fields and what “next step” means
  • what qualifies as a real opportunity
  • Reference concept: Customer relationship management.

    Verify with:

  • a pipeline cleanup exercise
  • a staging exercise using your exit criteria
  • Negotiation and commercial rules

    Goal: reps protect revenue quality and avoid hidden risk.

    Train:

  • discount policy and escalation
  • legal and security basics (if relevant)
  • what a rep can and cannot promise
  • Verify with:

  • scenario questions
  • a mock negotiation where approvals are required
  • Use “certification” to create a quality bar

    Certification is an internal checkpoint: a rep demonstrates minimum competence before running deals alone.

    A simple two-step certification model:

  • Certification A: messaging, ICP, basic process
  • Certification B: role craft quality (discovery, demo, negotiation) and CRM hygiene
  • Each certification should have:

  • a standardized prompt
  • a scoring rubric (1–5 anchors)
  • a pass threshold
  • This reduces variance across reps and prevents early bad habits.

    Instrument ramp with a small set of metrics

    Do not measure everything. Measure what indicates movement through your funnel.

    Examples of ramp metrics:

  • Time to first qualified meeting (typical for SDR)
  • Time to first qualified opportunity (SDR or AE depending on role split)
  • Time to first proposal sent (AE)
  • Time to first closed-won (AE)
  • Conversion quality indicators (stage-to-stage conversion, no-next-step rate)
  • Use metrics as feedback, not as punishment. If a rep is active but conversions are low, the problem is usually skill, targeting, or messaging.

    Coaching system: how managers turn training into performance

    Training creates knowledge. Coaching creates behavior.

    A practical coaching cadence:

  • Weekly 1:1 focused on one skill and one constraint
  • Weekly pipeline review with evidence-based stage checks
  • Weekly call review using 1–2 recorded calls and a rubric
  • Call review is especially high leverage because it reveals real discovery quality, clarity of next steps, and objection handling.

    If you use structured interviews in hiring, keep the same discipline in coaching: clear criteria, specific evidence, and consistent scoring. Background concept: Structured interview.

    Document a sales playbook that matches your funnel and roles

    A playbook is not a long document. It is a usable system that prevents reinvention.

    Minimum playbook sections that support fast ramp:

  • ICP definition and disqualification triggers
  • Funnel stages with exit criteria
  • Discovery question bank and note structure
  • Objection handling for top objections
  • Email templates and follow-up sequences
  • Pricing, discount rules, and approval path
  • Handoff checklist to CS/implementation
  • Competitor notes and positioning
  • Keep it versioned and owned. Outdated playbooks create confusion.

    Common onboarding failure modes (and how to avoid them)

    Typical reasons new hires ramp slowly:

  • Too much theory and too little practice.
  • No clear definition of done for each stage of ramp.
  • Inconsistent coaching and no call review.
  • CRM rules are unclear or not enforced.
  • Handoffs are messy, so customers start unhappy.
  • Lead flow is insufficient, so reps cannot practice on real opportunities.
  • Most of these are system problems, not individual problems.

    Implementation checklist: what to build next

    Use this to turn the article into action.

  • Create a 30-60-90 plan per role with measurable outputs.
  • Convert your funnel exit criteria into a CRM staging guide.
  • Define two certifications with prompts and scoring rubrics.
  • Build a short playbook aligned to ICP, funnel, and handoffs.
  • Set a coaching cadence with weekly call reviews.
  • Choose 5–8 ramp metrics tied to funnel movement.
  • When onboarding is built from your sales system, ramp speed improves and performance becomes more predictable. This is how you turn a “good hire” into a consistent producer.

    6. Мотивация, KPI и план продаж: система управления результатом

    Motivation, KPI, and Sales Quota: a system for managing outcomes

    In the previous parts of the course, you built the sales system: strategy and goals, roles and funnel stages with exit criteria, an ideal candidate profile, a hiring funnel, and onboarding that creates repeatable behavior. This article adds the management layer: how to set KPIs, design motivation and compensation, and build a quota and planning system that makes results predictable.

    A key principle: compensation and KPIs do not create performance by themselves. They amplify whatever system you already have. If your ICP, funnel criteria, lead flow, or handoffs are unclear, a strong variable plan will mostly amplify chaos.

    !How goals translate into KPIs and compensation

    What motivation and KPI systems must achieve

    A workable system produces three things at the same time:

  • Focus: reps spend time on the highest-impact actions for your sales motion
  • Fairness: strong performers feel rewarded and weak performers feel accountable
  • Forecastability: management can predict outcomes from pipeline evidence, not hope
  • If you only optimize for focus, you often get short-term behavior and long-term damage. If you only optimize for fairness, you get a plan that is “nice” but does not push outcomes. If you only optimize for forecastability, you create bureaucracy and slow selling.

    KPI basics: lagging versus leading indicators

    A KPI is a metric you will manage to. Not every metric is a KPI.

    Two KPI categories matter in sales:

  • Lagging indicators: outcomes that happen at the end of the process
  • - examples: revenue, closed-won, renewals, churn
  • Leading indicators: actions or intermediate results that drive lagging outcomes
  • - examples: qualified meetings, qualified opportunities, stage conversion, pipeline coverage

    A good rule: you should be able to draw a simple cause-and-effect story from leading indicators to lagging indicators.

    KPI quality checklist

    A KPI is useful when it is:

  • Defined: everyone agrees what counts and where the data comes from
  • Controllable: the role can realistically influence it
  • Timely: you can observe it early enough to correct behavior
  • Hard to game: it does not reward empty activity
  • For background context on measurement systems, see Key performance indicator.

    Choose KPIs from the funnel and exit criteria

    In earlier articles you defined funnel stages and exit criteria. That work now pays off: your KPIs should measure movement through those criteria.

    If you do not have exit criteria, you will end up measuring activity volume because it is the only thing that looks objective.

    Typical KPI sets by role

    Below are common KPI patterns. Use them as a starting point, then adapt to your motion.

    | Role | Primary output KPI | 2–4 supporting KPIs (examples) | Key anti-pattern to avoid | |---|---|---|---| | SDR/BDR | Qualified meetings or qualified opportunities accepted by AE | Speed to first response, conversion from lead to qualified, show rate, ICP-fit rate | Measuring calls or emails only, without quality gates | | AE (new business) | Closed-won revenue or gross profit | Pipeline created, stage conversion, cycle length, forecast accuracy | Paying on signed deals that are not collectible or not deliverable | | AM (account growth) | Expansion revenue | Adoption indicators, multi-threading coverage, account plan execution | Paying expansion while ignoring churn risk | | CSM | Net revenue retention or renewals | Time to value, product adoption, renewal risk reduction | Turning CSM into reactive support with no success plan |

    For subscription businesses, a widely used outcome metric is net revenue retention. See Net dollar retention.

    How to set a sales quota that is achievable and performance-driving

    A quota is a commitment: what you expect a role to produce within a time period.

    A quota is unhealthy when it is:

  • set from a top-down wish without checking lead flow and conversion
  • changed frequently, destroying trust
  • linked to metrics the rep cannot control
  • Quota should be consistent with capacity and the funnel

    A practical quota-setting logic starts with capacity:

  • How many real opportunities can an AE run at once without quality loss?
  • How many opportunities per month can SDR generate at quality?
  • What is your cycle length and stage conversion?
  • If the system cannot produce enough qualified opportunities, your quota will fail no matter how motivational the comp plan looks.

    Pipeline coverage as an early warning signal

    To manage predictably, many teams use a simple concept: pipeline coverage.

    A basic version is:

    Explanation of parts:

  • Pipeline amount is the sum of deal values that are in active stages and meet your exit criteria
  • Quota is the target revenue for the same time period
  • This ratio is not a universal truth. It is a management signal. If coverage is consistently low, you must fix pipeline generation, qualification, or lead flow. If coverage is high but revenue is low, your pipeline quality or stage discipline is weak.

    Forecasting: how KPI discipline becomes management discipline

    Forecasting should be evidence-based:

  • A deal is in a stage because it meets exit criteria
  • The next step is scheduled and confirmed
  • Risks are documented, not hidden
  • If your CRM is treated as optional, KPIs and quotas become theater.

    Background concept: Sales forecasting.

    Compensation design: principles that prevent gaming and churn

    Compensation is part economics, part psychology. Your goal is not to “pay less”. Your goal is to pay for the behavior that creates durable revenue.

    Core components

    Most plans are combinations of:

  • Base salary: stability, reduces desperation selling
  • Variable pay: commission or bonus tied to measurable outcomes
  • OTE: on-target earnings, what a rep earns at 100 percent of quota
  • Compensation structures vary by market and seniority, but the design principles below are broadly applicable.

    Design principles

  • Pay for outcomes first
  • - SDR: for accepted qualified meetings or opportunities, not raw activity - AE: for collected revenue or clearly defined closed-won milestones
  • Make the plan simple enough to explain in 5 minutes
  • - if reps cannot calculate expected payout, they stop trusting the plan
  • Align payout timing with revenue quality
  • - avoid paying for deals that churn immediately or cannot be delivered
  • Use accelerators carefully
  • - accelerators reward overperformance, but can also create end-of-period discounting

    For a general reference on variable incentive structures, see Commission (remuneration)).

    Common compensation patterns by role

    | Role | Typical variable basis | Notes | |---|---|---| | SDR/BDR | Qualified meetings or opportunities accepted by AE | Add a quality gate to prevent calendar spam | | AE | Revenue or gross profit closed-won, sometimes with partial payment on signing and partial on collection | Consider deal quality rules and discount governance | | AM | Expansion and renewals | Incentives should not conflict with retention | | CSM | Renewals and retention outcomes, sometimes adoption milestones | Avoid turning CSM into a discount channel |

    Team components and cross-functional alignment

    Sales outcomes depend on marketing, product, implementation, and support. A small team component can reduce destructive silo behavior.

    Use team components when:

  • handoffs affect customer outcomes
  • success depends on implementation capacity
  • sales and CS must cooperate to prevent churn
  • Be careful: if the team component is too large, high performers feel punished for others.

    KPI governance: definitions, owners, and data hygiene

    A KPI system fails most often because of definitions, not because of intent.

    Create a one-page KPI dictionary:

  • KPI name
  • exact definition
  • inclusion and exclusion rules
  • data source and owner
  • reporting frequency
  • Example definition clarity:

  • Qualified meeting is not “a meeting happened”. It is “a meeting with an ICP-fit account, correct persona, confirmed agenda, and a defined next step”.
  • If you use CRM as the system of record, align this with your CRM rules. Background concept: Customer relationship management.

    Operating cadence: how leaders manage to KPIs

    KPIs matter only if management uses them to improve behavior.

    A practical cadence:

  • Weekly
  • - pipeline review using exit criteria - call review focused on one skill and one bottleneck
  • Monthly
  • - KPI review: leading indicators, conversion, cycle length - segment review: where you win and where you lose
  • Quarterly
  • - quota calibration, territory and account allocation review - compensation plan adjustments only if the model changed

    The best teams treat KPI reviews as problem-solving sessions, not blame sessions.

    Typical mistakes that break motivation and performance

  • Paying SDR for meetings without quality gates, creating low-quality pipeline and AE burnout
  • Paying AE on bookings while delivery fails, creating churn and internal conflict
  • Over-weighting activity metrics that are easy to game
  • Changing quotas mid-period without a clear structural reason
  • Using too many KPIs, so nothing is truly managed
  • Setting KPIs that the role cannot control, damaging trust
  • Implementation checklist

    Use this checklist to turn the article into action:

  • Define 1 primary output KPI per role and 2–4 supporting KPIs tied to funnel exit criteria.
  • Build a KPI dictionary with definitions, owners, and CRM data sources.
  • Set quotas based on capacity, lead flow, and conversion reality, not only top-down targets.
  • Align compensation with outcomes and revenue quality, and add quality gates where gaming is likely.
  • Establish a weekly and monthly operating cadence that uses KPIs for coaching and system improvements.
  • With KPIs, quotas, and compensation aligned to your funnel and roles, you move from “managing activity” to managing outcomes. This is the final step that turns hiring and onboarding into predictable revenue production.

    7. Контроль качества, коучинг и развитие команды продаж

    Quality control, coaching, and development in a sales team

    In the previous articles, you designed the sales system: goals and strategy, the sales model, funnel stages with exit criteria, role boundaries, hiring scorecards, structured interviews, onboarding, and KPI and compensation. This article adds the final layer that makes the system durable: quality control, coaching, and team development.

    Without these practices, sales performance depends on a few “heroes”, quality drifts as the team grows, CRM becomes unreliable, and onboarding stops working because new reps learn inconsistent behaviors.

    What “quality” means in sales

    Quality in sales is not “people are nice on calls”. It is consistent execution that produces revenue without damaging future revenue.

    A practical definition:

  • Quality = the right customer + the right expectations + the right process evidence
  • This links directly to your earlier work:

  • ICP and segmentation define the right customer.
  • Value proposition and handoff rules define the right expectations.
  • Funnel exit criteria and CRM rules define the process evidence.
  • Quality must be managed in four places:

  • Customer targeting
  • Customer conversations (discovery, messaging, objections)
  • Deal execution (next steps, stakeholders, risks)
  • Handoffs and delivery expectations
  • Quality control is a system, not “manager intuition”

    A quality control system answers three questions:

  • What exactly is considered “good” in this sales motion?
  • How do we detect drift early (before revenue misses)?
  • How do we correct it through coaching, training, or process changes?
  • This is the same logic as continuous improvement in operations. A useful reference model is the PDCA cycle: Plan, Do, Check, Act.

    !A PDCA loop showing how sales execution turns into measurable quality control and continuous improvement

    The minimum quality control loop to implement

    Quality control becomes manageable when you standardize what you check, how often, and what happens after.

    What to audit (and why)

    Use audits that are tied to your funnel exit criteria and onboarding certifications.

    | Audit area | What you check | Why it matters | Typical owner | |---|---|---|---| | Call quality | Discovery structure, value articulation, next step clarity | Predicts conversion and cycle length | Sales manager or enablement | | CRM hygiene | Stage accuracy, required fields, next step set, close dates realistic | Forecast reliability and coaching focus | Sales manager or RevOps | | Qualification quality | ICP fit, business problem, decision process, disqualification discipline | Pipeline quality and win rate | Sales manager | | Deal risk review | Stakeholders, competition, legal/security risks, delivery fit | Prevents end-of-quarter surprises | Sales manager + presales/CS | | Handoff quality | Expectations, scope boundaries, success criteria, timeline | Protects retention and prevents churn | Sales + CS leader |

    Audit sampling rules (keep it simple)

    Start with small, consistent sampling. The goal is trend detection, not surveillance.

  • Call QA: review 2 recorded calls per rep per week.
  • CRM QA: check 5 active opportunities per rep per week.
  • Deal QA: review all late-stage deals weekly.
  • If you do not record calls today, introduce it with a clear purpose: coaching and quality, not punishment. If relevant to your region, align with local privacy laws and consent requirements.

    Build rubrics so “quality” is measurable

    A rubric is a shared scoring guide. It reduces bias and makes coaching repeatable.

    A strong rubric has:

  • 4–6 criteria (not more)
  • clear “what good looks like” statements
  • scoring anchors (for example, 1–3–5)
  • Example: discovery call quality rubric

    | Criterion | 1 (weak) | 3 (acceptable) | 5 (strong) | |---|---|---|---| | Problem clarity | Talks about product, not customer | Identifies problem but not impact | Quantifies impact and confirms urgency | | Stakeholder mapping | Speaks to one contact only | Identifies roles loosely | Confirms decision makers and process | | Value connection | Lists features | Connects some benefits to needs | Links value to outcomes and metrics | | Next step | Vague “follow up” | Schedules next step | Next step is scheduled with agenda and mutual confirmation |

    This rubric should match your earlier funnel exit criteria. If an exit criterion for “Discovery complete” includes “decision process confirmed”, your rubric must score that explicitly.

    Coaching: turning quality signals into behavior change

    Quality control finds issues. Coaching changes behavior.

    Sales coaching is a management skill set, not a personality trait. General background: Coaching.

    The coaching stack: what happens weekly

    Use a consistent cadence so reps know what to expect and managers do not “coach only when things break”.

  • Weekly 1:1 (development and performance)
  • Weekly pipeline review (deal execution and forecast)
  • Weekly call review (skill improvement)
  • !A weekly cadence that makes coaching and quality control predictable

    Use a simple coaching structure

    A practical structure for 1:1 coaching is the GROW model: Goal, Reality, Options, Will.

    Applied to sales, it prevents unproductive conversations like “just work harder”.

  • Goal: what outcome are we trying to improve this month?
  • Reality: what do the funnel data and call evidence show?
  • Options: what specific behaviors could change?
  • Will: what exactly will the rep do before the next session?
  • Coaching is not the same as managing

    A common failure is mixing coaching with administrative pressure. Separate the modes.

    | Mode | Purpose | Typical tool | |---|---|---| | Coaching | Improve skills and decisions | Call review + practice | | Management | Ensure execution and accountability | KPI review + pipeline review | | Training | Transfer knowledge and standard methods | Playbook + certifications |

    A rep can be accountable for activity standards while still receiving supportive skill coaching.

    The highest-leverage coaching technique: call review + redo

    A fast improvement loop:

  • Listen to a 3–5 minute call segment.
  • Identify one moment that mattered (question quality, pushback, next step).
  • Give one piece of feedback.
  • Re-run the moment as a short role-play.
  • This is more effective than general advice because it converts feedback into muscle memory.

    Deal quality control: pipeline reviews that prevent surprises

    Pipeline review is not reading CRM out loud. It is validating evidence against exit criteria.

    A strong pipeline review checks:

  • Stage correctness: does the deal meet the stage exit criteria?
  • Next step: is there a scheduled, confirmed next step?
  • Stakeholders: are we multi-threaded or single-threaded?
  • Risks: competition, budget, procurement, security, delivery constraints
  • Introduce a lightweight “deal desk” for late-stage deals

    A deal desk is a short cross-functional review for deals that can create risk or require exceptions.

    Use it when:

  • discount exceeds the policy threshold
  • non-standard terms are requested
  • delivery capacity or scope is uncertain
  • security/legal complexity is high
  • This protects revenue quality and reduces churn created by overpromising.

    If you need a standard way to clarify responsibilities across Sales, CS, Legal, and Finance, use a RACI matrix.

    Development: building a team that improves over time

    Quality and coaching prevent performance drift. Development ensures the team scales.

    Development has three parts:

  • skill progression and career paths
  • enablement systems that reduce reinventing
  • feedback loops to improve product and marketing
  • Create a competency matrix by role

    A competency matrix is a simplified version of your hiring scorecard used for growth.

    | Competency | SDR/BDR | AE | AM/CSM | |---|---|---|---| | Targeting and ICP judgment | High | Medium | Medium | | Discovery and diagnosis | Medium | High | Medium | | Value messaging | High | High | Medium | | Deal control and next steps | High | High | High | | Negotiation | Low | High | Medium | | Handoff and expectation setting | Medium | High | High |

    Use it to answer:

  • What does “level up” mean?
  • What should be coached now vs trained later?
  • Who is ready for bigger deals or leadership?
  • Define a career ladder that matches your sales motion

    Avoid generic titles. Define roles by responsibility and deal complexity.

    | Track | Example levels | What changes as they grow | |---|---|---| | SDR/BDR | Junior → Mid → Senior | ICP judgment, messaging iteration, meeting quality, mentoring | | AE | SMB AE → Mid-market AE → Enterprise AE | stakeholder complexity, deal cycles, negotiation and risk management | | Management | Team lead → Manager → Head of Sales | coaching skill, forecasting discipline, system design |

    Promotion should require evidence: call quality, stage discipline, consistent outcomes, and reliable forecasting.

    Build an enablement system that stays alive

    A “playbook PDF” that nobody updates is not enablement.

    To keep enablement useful:

  • Assign an owner (often Sales Enablement or a manager).
  • Version the playbook and communicate changes.
  • Update from real evidence: win/loss notes, objection patterns, call QA themes.
  • A playbook should include only what improves execution:

  • ICP and disqualification triggers
  • funnel stages and exit criteria
  • talk tracks and objection handling
  • pricing rules and escalation paths
  • handoff checklist
  • The feedback loop: turning sales reality into company learning

    A mature sales team improves the company, not just revenue.

    Create a monthly learning review:

  • Top win reasons (what value message worked and for whom)
  • Top loss reasons (with evidence)
  • Product gaps versus positioning gaps
  • Competitor patterns
  • Process friction (handoffs, legal, implementation capacity)
  • This is the bridge between sales execution and product/marketing strategy.

    If you want a simple customer outcome signal for CSM and account teams, you can track Net promoter score alongside retention metrics, but do not replace behavioral evidence and adoption data with NPS alone.

    Common failure modes (and how to prevent them)

  • You measure activity because quality is hard to define
  • - Fix: implement rubrics tied to exit criteria.
  • Managers do pipeline reviews but never coach skills
  • - Fix: schedule weekly call reviews and “redo” practice.
  • Coaching is inconsistent across managers
  • - Fix: run monthly calibration sessions using the same calls and rubrics.
  • Sales overpromises and churn increases
  • - Fix: deal desk for exceptions + strict handoff checklists.
  • Top performers are not replicable
  • - Fix: capture their patterns into playbook updates and training drills.

    Implementation checklist

    Use this as your practical next step.

  • Define 1–2 quality rubrics (discovery and CRM hygiene) and roll them out.
  • Set the weekly cadence: 1:1, pipeline review, call review.
  • Start sampling audits: 2 calls and 5 deals per rep per week.
  • Introduce a late-stage deal desk with clear discount and exception rules.
  • Build a role-based competency matrix and a simple career ladder.
  • Run a monthly win/loss and learning review and feed updates into the playbook.
  • When quality control is connected to coaching, and coaching is connected to development, you stop “managing salespeople” and start managing a revenue production system that improves over time.