We have control at our fingertips ...

What is the main task of CRM? Right! Bring the sales process to an easy and pleasant pastime. Chatting on the phone is fun and the statistics of these events neatly add up to the client’s history. Send KP with one click, issue invoices, contract, specification and terms of reference by pressing 1 button on the keyboard. Paid invoices evenly cover the entire screen, the sales funnel looks like a vertical column with an indicator of 100%. But there is one “cute” fad between paying the bill and signing the closing documents. It is called “performance of work” (or delivery of goods, or the provision of services, etc.). Here lies a small but insidious “system bug”.


On the one hand, the manager has done his job, the manager can leave. But! On the other hand, very often, the transaction is not closed, which means that it does not fall into the plan of completed tasks. The amount of payments does not count towards the manager. And if, God forbid, the terms have also been “steamed” ... Then the dissatisfied customer is calling whom ???? Right! To someone who sweetly sang on the phone about the reliability of the company, about the inviolability of the contract and other pleasures of life. What to do? To lead a project? But this is another accounting system, another interface and other difficulties of this project management system. Yes, and this does not need to happen. I just want to know that Vasya drew the website design in time, Kolya made it up in time and gave it to the programmer Semyon. And Semyon at the appointed time created a prototype site and gave it to Alexander for testing. Alexander thoroughly tested it, wrote a bug report and Semyon corrected everything as soon as possible and provided the site to the customer. One timely call to the people involved will not let the project fall at the peak of deadline raking. What is provided for inYoollaCRM ? In our system there is the concept of control points . These are events that are not directly related to the sale process itself, but indirectly affect the success of the transaction. They can be installed both by the manager himself and his supervisor. This is an option, and you can skip it and not set breakpoints at all. And you can put only part of them. How to use them?
To begin, define the control points themselves. How many there will be, how they will be called. The

control point can be attached to the stage of the transaction, but you can not tie it. If you tie it to a stage, then you can change it to the next only if the control point is executed. For example, subject to payment.
By adding a breakpoint you can specify roles and users who have access to this breakpoint.

In our case, we added the following points: creating a design, creating a prototype, testing, the work was done completely.
When starting work, the manager has an idea how much time is spent on each stage. And sets the control points, according to this knowledge.

Having set the control points, we get something like this in the transaction card.

When passing the control points, a mark about the actual performance of the work will appear. Later, the head will be able to analyze reports where there were problems in the execution of the transaction.
And the employee on the desktop in the "Health" section shows a display of all his transactions and their status. If the checkpoint (or the whole deal) has expired, but it is not marked as completed, then such a deal will be colored red in the list. A deal in which everything is going according to plan is marked in green. A deal in which there are no control points has a white background.

By clicking on the transaction, we can see which control point is closest and how much is left before the “deadline”.

Were there any payments and when the transaction should be closed.

As a result of such simple movements, we get closer control over the process of performing work. This is to replace a complete project management system. But for most small and small enterprises this is enough to conduct their projects. Find out when the car comes with spare parts to send the craftsmen to the client to repair the refrigerator. Check when the printing house prints your circulation of flyers to send promoters to the BC. Check the delivery time of paper for sending self-adhesive labels to the client for printing, etc. etc. And it’s not at all necessary for the manager to know how many man-hours are required for programming the prototype. Is it enough to call the head of the development department (or write in a corporate chat) with the question "are we getting on time, Semyon"? Semen will check the wards, give acceleration sluggish and ... TA-YES !!! The project was completed on time. Everyone received bonuses and rode pink ponies on a rainbow ... It’s enough just not to forget about the people who “saw” the project with you. And just as the manager depends on the execution of work, so the developers, designers, analysts and the like, the other, the other, the other depend on the work of the manager. Therefore, it is better to do everything as a team. AYoollaCRM will actively help you with this.

Also popular now: