Throughout 2011 Audaxium has been working with more and more companies and we’ve seen some interesting situations. In working on NetSuite fixups, and implementing Pardot with customers with various CRM systems, both NetSuite and Salesforce, we’ve noticed companies getting into trouble in systematic ways. Often, problems happen when the data in the system doesn’t match what’s happening in real life.
Life is complicated. People like simplicity. And getting people to use CRM properly can be challenging depending on your organization. So why not just keep things simple? Doesn’t KISS apply?
Here are some examples of somewhat common decisions that cause problems later.
Custom Field for Sales Rep
The client decided, that, in order to not let sales reps think they “Own” accounts, to not put the rep in the default Sales Rep Field. Instead they used a custom field for Sales Rep and left the main field blank. Result? Difficulty in using standard reports. Difficulty in getting notifications to Reps. Difficulty in integrating with marketing campaigns.
Duplicate Contacts on Customers
The client decided that, to make it easier on the tech support team, if a person called in to discuss an issue at a certain customer location, (which they were tracking as sub-customers), they would enter a NEW contact on that company record, with the same name, email address and phone number. Result? Massive contact duplication in the database, no single source of the truth with regards to communication and emails.
Manual Prices on Items
To make it “easy” on order entry, the client decided to put only a few items in the item master, and overwrite the description and price. Result? No ability to report on the delivery and fulfillment of particular types of services.
The above are just a couple of examples of compromises made that lead to problems later. But anecdotes are just that, there are, to my mind, 3 main reasons why you should truly map what’s going on in your business in your CRM or ERP system.
3 Reasons Why Reality is Important
Information Accuracy
There is a balance between segmenting your data for reporting purposes, and capturing every last detail. What level of accuracy do you need to both operate, and make decisions?
Take a company that sells chickens and eggs. You could weigh and measure every egg you sell, sell them by grade, sell eggs separate from chickens, or sell 1 item called “Chicken and by-products”. In this case, the reality is that the customer buys eggs by grade, either by the flat or by the dozen.
To take an example closer to home, what about our contacts example above? There is only one person with a particular name, email address and phone number. There should be only one contact, but that contact should be attached to multiple companies as most CRM systems allow.
Easy to Train Multiple Teams
Sometimes by oversimplifying, you’ll need to be constantly explaining how fields are to be used and how to look up certain information. Because most people in your company will understand how you do business, it’s easier to have them understand the system if it matches real life processes. The sales team, support team, and services teams need to think of each other when considering how data gets entered. There’s nothing like hearing things like; “the main contact field is whoever is the decision maker, until they are closing, then it’s the buyer, until they’re a new customer, then it’s the project lead, until they renew, then it’s whoever cares about the renewal”
Your CRM system should enable your business process, not be a workaround for it. If your processes are too hard for your team to enter into a system, consider changing your processes.
Integration with Other systems
We’re in a world of integrated applications, and when a company writes an integration with another app they make certain assumptions of how you’ll use it. You’ll need to think long and hard about taking default functionality and using it for another purpose. Just why are you using a custom field when there’s a similar default field available? By getting creative with core fields, you’ll risk giving yourself more work down the road when it comes to integration. Sometimes that work can be worth the extra effort, but make sure it’s necessary.
Challenges
Often, customers do understand the above, so why do mistakes get made? Here are some common reasons.
No system is Perfect
Sometimes they can’t represent the reality of your business because they lack the functionality. Until recently, a good example was NetSuite’s multi-currency function. You couldn’t create transactions in multiple currencies to the same customer. This caused un-wanted duplication of records and work-arounds needed to be found. Fortunately this is no longer an issue. When evaluating systems, ask your implementation partner just what the ramifications of a certain functional limitation are.
Clicks and Keystrokes
Often, when selecting systems, the client, and the end user, will focus on how “easy” things look and feel on some standard screens. If they have to fill in two more fields, or wait 5 more seconds for a screen to load, they’ll be frustrated and complain about productivity. It doesn’t matter than those 2 fields save their co-worker 10 minutes. It won’t matter that they can see information they’ve never had access to on that new screen.
Saving someone a few seconds at the price of a messy database is a bad trade-off.
Implementation by Department
I’ve seen NetSuite implemented a few times for a particular department and only later does the client discover that they’ve painted other departments in to a corner. Both Sales and Finance are equally notorious for doing this with NetSuite. Unless both groups are considered during an implementation, the easy options will be chosen that don’t let the system represent what really happens for the other team. Even if you’re just implementing for one group, work with an implementation partner who understands the bigger picture.





Everyone has experienced it. You have a wonderful experience with an account manager while you’re investigating a solution. And then, magically, once your purchase order hits their email inbox… silence. It’s deafening.