When finance and marketing hijack sales’ CRM

•8 February 2012 • Leave a Comment

There are many different opinions on why you would implement CRM for sales. For me, sales productivity and sales effectiveness is the number one reason… surely you want them to sell more? Sales for many businesses is THE source of revenue.

But CRM and sales automation projects can get hijacked by finance and marketing. There is a direct and inversely proportional relationship between how useful CRM is as a sales productivity tool vs. a management information and marketing data tool. There is a balance to be found but so many businesses find, especially over time, that productivity gets forgotten as the business’s hunger for more data/more analysis/more information grows. Old reports that are no longer needed or used define the original field set up and workflow, but new reports create the need for new fields and changes to the workflow, the data entry burden grows and thus the system gets complicated, training headaches increase and sales …. well they carry on selling and stop using the CRM altogether and the bit of information you do get becomes useless.

It’s a massive generalisation but sales people and data entry are totally incompatible skills. If someone likes data entry, they are unlikely to be a great salesperson and vice versa. It’s a problem but you’re stuck with it and personally, if I have to choose, I’d rather they sold well and management were a bit less well-informed, than know a lot about why they weren’t selling much at all.

It’s all about balance and the very important element of high quality sales management. That is people who can manage sales teams without entirely relying on technology and reports. Make sure your desire for reporting and management information doesn’t swamp your sales system and that it remains very, very easy and good to use for the business of selling.

And as for marketers… make reasonable requests for data quality. Sure, it’s reasonable to insist that every contact record has a company, a tel number, a first and last name… but don’t expect someone on a sales call to capture company size, industry and shoe size. It will damage the effectiveness of the call as it breaks rapport. Think of other cunning marketing ways you can get what you need and always, consider how useful the data really is anyway.

Marketing Automation: What’s that about?

•26 January 2012 • 2 Comments

Splintering of Technology
There is a lot of hype and excitement around marketing automation technology presently. But what is it, do you need it, and how should you go about implementing it if you do? Firstly, let’s define our terms. Almost every single project we do, whether CRM, marketing automation, email automation, sales automation or combinations of those, start off with the client, 70 Fathoms (that’s us) and vendors needing to define what we’re talking about when we talk about the technology we’re planning to implement. We find the best way to cut through this language is to focus on the channels. Which channels are you using to sell and market your products and services? Which ones are you aspiring to use? When you define that, the technology choices and options start to get clearer. The tools available are increasingly becoming channel-specific, ironically when another big buzz word is multi-channel marketing, the technology is splintering. This is bewildering to buyers but actually a good thing. Old-school CRM was a jack of all trades, new technologies are masters in their own sphere. And yes, you can join up the data and often the technology platforms you are using, so don’t let that put you off.

Think by Channel
Marketing automation is not a clearly defined category of software but we broadly describe it as technology which will automate your marketing campaigns but across more channels than just email. Automate means sending communications to customers, or instructions to sales to communicate with customers, which are created in advance and triggered by changes to your dataset or hitting certain date rules but not by a marketer pressing “send”. In theory, marketers construct sophisticated and/or rules across a multiple of possible responses and across many channels (SMS, telesales and email perhaps) and then, ongoing, tweak those rules to maximise the results. Used well, it’s a great tool, but there aren’t many marketers with strong marketing automation skills yet and there’s a steep learning curve while they develop them. Conceptually, it’s a different sort of marketing – the sort of marketing that direct mail traditionalists will be more comfortable with learning probably – but often it’s brand marketing-driven firms who are adopting the technology first and they’re not used to the analysis and frankly the maths and statistics skills you need to make sense of your new information.

ROI & Training
If you’re going to invest in this sort of marketing software, make sure you know what it does do and what it doesn’t. The vendors will show you all the bells and whistles but don’t assume that it does things you thing are “standard”, check. (Notably consider the data management issues, especially if you’re in B2B. Marketing automation suits aren’t usually data warehouse substitutes or “marketing databases” with high-end data management tools. Listen to the old-school data managers who understand how hard it is for software to recognise that One Peach Tree Drive is the same as 1 Peach Tree Dr.). Make sure you can build a business case for the investment i.e. will it help you sell more or save you money? And most of all allow time and budget for training for your people. The software is only as good as the data that goes into it and the people who use it. It won’t come naturally to everyone, so back them up and support them while they learn.

Implementation
If you conclude it’s the right solution for you, remember you’re implementing change and manage it accordingly. This is a relatively new sphere of software and you may find that the vendors can be a little inexperienced in complex projects. Make sure you get the best implementation team in, who have implemented databases and integrated solutions (unless you’re literally starting from scratch with no data and no integration). The complexity of an implementation lies in these two areas – you need people who have detailed knowledge of what can go wrong and what to protect you against, to help it go well. But never forget the change and your users… once the dust has settled, your shining new system is in place and populated with freshly cleaned data, you don’t want marketers doing the same email campaigns they’ve always done but using a vastly more expensive system because they don’t know how to use it any other way.

Do you know which user requirements to ignore?

•7 February 2011 • 11 Comments

In CRM projects, you must talk to and involve the end users and understand their requirements, it’s necessary and also considerate to do so. It’s best not to impose a system on them and you should build a system that works for them but there is a lot of interpretation needed to translate what the users say they need, into a working useable system.

For example, people say things like “I’d like the accounts team to check a box on a customer record when they want to show the sales team that the account is on hold and we shouldn’t sell to them”. The translation being, sales teams need to be able to see when an account is on hold. Different CRM systems and different implementations can deliver this in different ways. Finding the most elegant solution, that will be the best in terms of usability, often means ignoring the stated requirement and reinterpreting it.

If this is done badly, you could have very unhappy clients and that’s why so many consultants prefer the safe route of taking down exactly what the clients ask for. They deliver software configured according to those requirements and voila, their backs are covered even if the result is an over engineered piece of software that’s awkward to use.

But a wise consultant will know the software, work with its predetermined structures as much as they can and gently steer user requirements so that the customisation is minimised and the inherent workflows and functionality that exist in the software are kept intact.

Great developers of great software understand that user requirements need interpretation. It shows in their software. Look for this software and look for consultants who understand people and how they use software, and good things will happen in your business.

 
Follow

Get every new post delivered to your Inbox.