Caught between head office and seven markets.

You own the regional number. Head office wants a forecast from you, and your sales people are spread across several markets, so what you know about their deals is what they tell you. The number you send upward is only as good as their reporting. When it misses, the questions come to you.

Ask them again and you get the same answers, later. The reason is that each of your people decides for themselves what "nearly closed" means. One of them says it when the client sounds keen. Another waits for the budget to be signed off. Their answers mean different things, so adding them together gives you a total, and the total is a guess.

The CRM should settle this. In practice it holds a version everyone works around. It was set up to produce a monthly report, and the people expected to feed it were shown the login and left to work out the rest. So two things happen at once. The fields that do get filled are filled to satisfy the report, and plenty of them stay empty. What sits in the system is a partial picture bent toward the questions somebody asked last month, and the real one stays in their heads. You would check it before sending it anywhere.

So every month you go back to the spreadsheet. The spreadsheet is the real system.

The first course agrees, with your team, what each stage of a deal means and what has to happen before a deal moves on. The second puts exactly that into your CRM and builds the reports on top of it. After both, the number in the system is the number you send.

Where your people already work to an agreed process and the CRM is the part they have yet to learn, the second course alone is enough. Where the process itself is the argument, start with the first. Most teams have both gaps, and we will say which one we think you have after looking at your pipeline.

Five sales people, five standards, one number. Deals add up. Judgements made to different rules add up to a guess, which is why the forecast can move in a month where every deal stayed exactly where it was. Agreeing what each stage means is most of the work.

The course builds the stages for your product, and the trigger that moves a deal from one stage to the next. A trigger is an event someone can point at: the specification received, the trial booked, the quote sitting with procurement. Once every stage has one, the team agrees where a deal is, and a manager can check it in a minute.

From there it covers qualification applied the same way by everyone, deal review that surfaces problems while they remain fixable, and a forecast built on evidence.

It runs from your own pipeline. We ask for a current export in advance and work through it, so the definitions are argued out against real deals and the team leaves with a stage model they have already applied.

Two days in person, or three half-days online, with your sales people and their managers in the room together. Deals go in unattributed, and anyone can claim one and explain their thinking.

Salesforce, HubSpot, Zoho or whatever you already run. Two things break a CRM. It gets configured around the report management wants, and the people expected to feed it were shown the login and left to work the rest out. So your sales people keep the real pipeline in their heads and a ceremonial one in the system. Head office reads the one in the system.

The course starts further back than most people expect: the system itself. What the records are, how they relate to each other, and what each field is for. That is the part everyone skipped, and everything after it rests on it.

Then the stages and their triggers go in, so a deal advances when the evidence is there. Then your people build the reports on top: a pipeline by stage that means something, and a forecast a manager can check in a minute. Then they build the dashboard you send upward, carrying the same numbers you are looking at.

They build it, so they can change it. When head office asks a new question next quarter, your own team has the answer that afternoon.

Your administrator can show them where to click. Knowing which report answers a sales question, and what a pipeline by stage looks like when it is telling the truth, is a different job. That takes someone who has carried a number, which is why this course sits with us.

It also covers the habit: what a sales person updates, when they do it, and why it is worth their time. A record kept for somebody else decays. A record that answers the seller's own questions stays current.

The system carries the same stages, the same triggers and the same words the team agreed on, so a deal reads the same in the room and on the screen. At that point the forecast reports itself, which is why the two courses belong together. The directors we place run this way, which is how a regional operation stays legible from a distance.

Two days in person, or three half-days online, with your sales people and their managers. We ask for access to the CRM in advance, and for permission to build reports in it.