We had a difficult start to the week last week. It started with a cold shower on Sunday morning. Then, on Tuesday as I was sat in my office at home playing with data in a spreadsheet, I realised it should not be raining indoors. We had a leak.
After our early morning call of desperation on Monday – you really miss hot water when you don’t have it – our regular plumber diagnosed that our water pump had broken down. At some point during the fitting process, a pipe was dislodged from the tank in the loft. And so, our unexpected indoor water feature.
Marginally calmer on when the immediate drama was over, and the plumber had been and sorted out both the symptom and the cause of the leak, I was running queries in the database, it struck me how much database and CRM management as in common with plumbing.
We have kit we depend on – be it a boiler or a database – and have to do our best to look after it so in turn we can get the benefit from it.
We have an annual service for our boiler so we know it is in good shape and will run well – and in our database we run regular reports so we can adjust our performance according to the results we see, and may even have a spring clean and tidy up results every now and then.
We set a timer to manage our hot water and heating resources efficiently – we code activities and have set data entry processes to improve our data efficiency.
But no matter how well we may look after our boiler, there will come a time when something breaks down, furs up or starts clunking away behind the scenes. We can try fixing it by having a good look around at obvious stick points, asking someone in the office who might know or via a judicious bit of Googling to try and find the root of the issue. But the usual recourse is that we have to get someone in who knows what they’re doing to take a look at it.
CRM systems are no different – they can really benefit from the attentions of a professional who knows their way around the inner workings. They can point out where inefficiencies may be causing blockages or issues and identify new integrations (new parts in boiler language) that will help things work more smoothly and maximise and extend the life of your system so it will provide you with the benefits that you need.
On the rare occasions that the boiler breaks down completely, it’s time for a new one – the average lifespan of a CRM system is around 7-10 years so there is usually lots of time to anticipate the need for a development or change in system. Just as your service engineer is a good starting point for recommendations for a new boiler, so is a CRM expert for your database. Both will be able to identify what will fit your space, share what the options are on the market and the pros and cons of different models, give you an idea of cost and how long the task will take to complete.
Likewise, they will probably have given you a warning too about when the change might need to happen during their regular servicing so you are not unprepared and are able to plan for the change too.
Does your CRM need a service? Call Keith today to chat through our CRM Database Health Check service:
e: [email protected], or t: 0845 458 0250