Building a sales department that doesn't depend on one person.

With what is already there: how customers arrive, who works with them and by what rules. Usually it turns out the rules exist but live in one person's head. The first step is to get them out and write them down; only after that does automating anything make sense.

No. People, hiring and decisions stay with a human. The system takes the counting, the reminders, the deal reviews and the keeping of the rules — the things a live manager usually runs out of day for.

Yes, and that is most often how it starts. The owner gets a ready weekly rhythm and clear rules, so the department doesn't need them present every day.

The audit and assembling the rules usually take two to three weeks. Another month goes on making the rhythm stick: that is a matter of team habit, not of technology.

Yes, without one the rules stay a document. If there is no CRM, or it is kept only formally, we start there — otherwise the prompts and reports would be built on nothing.

They will, if the rules are assembled from their own successful work and take away routine instead of adding paperwork. That is why we write them together with the team rather than hand them over ready-made.

The plans, the rules, the scripts and the settings in your CRM — all of it is yours and stays with you. We don't build the kind of dependency where the system stops working without the contractor.

From scratch the order is the reverse of the usual one: process first, people second. First we describe the path of a deal from enquiry to money, put it into the CRM and define which tasks are set automatically and what counts as work done.

Hiring makes sense after that. A new person needs a place where it is already clear what to do today — otherwise the department rests on the manager's memory and falls apart the moment he goes on holiday.

A rule is not a document for an inspector but an answer to the question «what do I do now». If an employee cannot find the answer in it within a minute, they do not use it.

Four rules are enough for a sales department, and all of them are verifiable: how quickly we answer an enquiry in each channel; what has to be in the record for a deal to count as live; which event moves a deal to the next stage; what to do when a customer goes quiet.

Every rule must be visible in CRM. «We answer quickly» is not a rule — it cannot be checked. «We answer a website enquiry within one working hour, and the time of the first reply is visible in the record» is a rule.

You do not need to write them from scratch. The rules already exist; they simply live in the head of your strongest rep. The work is to bring them out, agree them with the team and put them into the system so that compliance is visible without supervision.

A rule nobody watches dies within a month. That is why we do not write a set of rules separately from CRM: a rule and the way to check it appear together.

A script is useful not because it is read out loud but because it saves the rep from inventing wording on the fly.

Taking somebody else's template is useless: it holds someone else's services, someone else's objections and someone else's tone. Working scripts are assembled from your own conversations — the ones that ended in a sale. They already contain the words that worked.

The order is this. We listen to conversations and write out objections word for word, as customers say them. We group them — usually five to seven recurring ones come up. For each we find the answer that in your own conversations already led to a next step. We test it on new deals and correct it.

This is not a forty-page sales book but short wordings for specific moments: the first reply, clarifying the task, a price that has been named, the pause after a quotation, a refusal.

It is worth agreeing separately where a script is compulsory and where it gets in the way. At first contact it saves time. In a difficult conversation, where the customer has an unusual task, a memorised phrase only does harm.

To keep a script from going stale, it is reassembled. A review of refusals shows which new objections have appeared and which answers have stopped working.

Monitoring starts not with listening to calls but with the question of what exactly you want to see. Without an answer, the check turns into selective listening: it takes hours and changes nothing.

There are three things worth watching. Whether the rules are followed — the time of the first reply, the filling in of the record, the presence of a next step; this is visible from CRM and needs no person. What happens in the conversation itself — did the rep clarify the task, name the next step, how did they answer the objection. And what became of the lost deals: the reason for a refusal separates lost demand from a mistake in the work.

The first layer is covered by configuring CRM. The second used to require listening by hand, so only a handful of conversations out of a hundred were ever checked. An AI listens to every conversation and every chat, scores them against your checklist and shows where a deal was lost.

Monitoring works when an action follows from it. A score on its own does not change behaviour. A review does: a specific deal, a specific moment in the conversation, a specific wording that would have worked better.

And one last thing: monitoring must not read as surveillance. If the team sees it as a tool for review rather than grounds for a penalty, nobody works around the system.

The head of sales is responsible for the plan being met by repeatable work rather than heroics. That is what their duties are built from.

They break the goal down into weekly actions: how many enquiries, meetings and invoices are needed to reach the figure. They watch the movement of deals and step in where a deal has stalled, not where the complaints are loudest. They review lost deals and carry the conclusions into the rules. They bring new reps up to results so that training does not come down to «sit and listen».

A noticeable share of this is counting and remembering: who did what during the day, which deals are sitting with no next step, where the plan is falling behind. It eats the time that should have gone into review and into people.

That part can be taken off. Plan and actual count themselves, deals with no next step are shown separately, the review of conversations arrives ready. Decisions, hiring and negotiations stay with the human.

If there is no head of sales in the department, the duties do not go anywhere — the owner performs them, usually in snatches. Then the point of the system is not to replace a manager but to let the owner spend hours on the department instead of days.

A team meeting stops being management when it turns into a report around the table. Everyone names their figures, the manager listens, no decisions are taken, and a week later it all repeats.

To avoid this, the figures must be known before the meeting. Plan, actual and the gap are visible in the system; there is no point saying them out loud. The meeting is for what does not follow from the system: why a deal stalled, what to do with a customer who went quiet, which objection has started to repeat.

The working order is simple. First the deviation: where we are behind and at which point — too few enquiries, deals that are not moving or too few closings. Then the specific deals that make up a noticeable share of the plan. Then one review — a conversation or a refusal from which the whole team draws a conclusion. At the end, agreements with names and deadlines, not general intentions.

A short daily meeting holds the next step in place; a longer weekly one takes the reasons apart. It is not worth mixing them: the daily one has no time for a review, and in the weekly one talk about yesterday's tasks eats everything.

A meeting after which not a single task changed in CRM did not take place.