Turn leads into loyal customers

Most CRM failures are not software failures. The team is asked to keep a second record of a job they already did somewhere else, and within a quarter the pipeline is a month out of date and the manager has stopped trusting it.

The test is simple. Ask what a rep gets from opening the system on a Tuesday morning. If the honest answer is nothing, the rollout will fail whatever the software costs.

Here the answer is the day's calls and visits, the customers nobody has contacted in a month, the quotations waiting on a reply, and the live stock position behind the item a customer asked about yesterday.

Route planning matters most for businesses selling into shops and small accounts, where coverage is the whole game. If a customer has not been visited in six weeks, somebody should know that without a manager driving the route himself.

The visit record is also the honest version of the week. A rep who made twelve calls and closed nothing has a different problem from a rep who made three, and the two need different conversations.

The honest caveat: the system holds whatever people put in it. Wizard cannot make a rep write a note after a call. What it can do is make the note quick to write and useful to somebody else, and put it where a manager is already looking.

That is a management problem more than a software problem, and it is worth settling in the first month. Most companies land on the same short list of what counts as a record: who was met, what was discussed, what was promised, and when the next contact is due.

Most sales meetings are spent gathering information rather than deciding anything. When the numbers are already on the screen, the meeting can start at the argument instead of ending there.

This is where a CRM bolted onto the side of an accounting system leaks. Sales knows the relationship, finance knows the money, and nobody knows both at the moment it matters, which is during the phone call.

It also changes how an account is judged. Repeat orders, collection behaviour and service load sit against the same customer, so the value of an account stops being measured by revenue alone.

The setup decision that matters is the stage list. Copying a generic pipeline from somewhere else is how you end up with stages nobody updates. Write down how a deal actually moves in your business, including the step where it sits waiting on the customer, and build the stages from that.

The second decision is what a rep must fill in before a lead can move forward. Ask for too much and the team will route around it. Ask for too little and the reports are decoration.