Making
Sales Force Automation Work
By Chad Symens and published by CrainTech
In this tough
economy many companies are struggling to maintain
the revenue growth they sustained a few short
quarters ago. The days of sales reps sitting
in the office taking orders is gone and not
likely to return anytime soon which is causing
many organizations to focus intensely on identifying
ways to increase sales. Many sales managers
are turning to sales force automation (SFA)
solutions in an effort to automate their sales
process and make their sales reps more effective.
However, numerous studies have shown that
nearly 3 out of 5 SFA implementations fail
to achieve their stated objectives.
This article explores the
keys to a successful SFA project. The seven
keys are:
1. Build a quantifiable
business case
2. Commit an executive sponsor
3. Define and refine your sales process
4. Provide incentives to use the system
5. Provide integration to key applications
6. Conduct the project in small manageable
phases
7. Invest heavily in documentation and training
Build the business
case first
Stephen Covey is famous for popularizing the
phrase "begin with the end in mind,"
and it could not be more relevant in SFA projects.
If you do not take the time to build a comprehensive,
well-reasoned business case before you start
the project you significantly increase your
chances of failure. It stands to reason if
you do not define where you want to go you
will have a hard time getting there. Make
sure your business case at minimum addresses
the following points. First, define the vision
and goals of the project in measurable terms.
For example, one goal might be to increase
sales by 15% within 120 days of implementing
the system. Other common SFA project goals
include increasing sales revenue per sales
representative, increasing average order size,
and increasing order accuracy. Second, calculate
a rough return on investment (ROI) for the
project. A rudimentary ROI equation is simply
the present value of the total cost, divided
by the present value of the total expected
benefit. This may seem deceptively simple
but it can be difficult to calculate because
many of the benefits will be intangible and
difficult to quantitatively measure. However,
the exercise itself will be valuable in thinking
through all the nuisances and impacts the
project will have on the organization. The
last two items to include in the business
plan include project risks and critical success
factors. In other words what might go wrong
as we conduct this project, and what things
must happened in order for this project to
be successful. Armed with this simple business
plan you will have defined the desired "end
state" and will be able to communication
your vision and success criteria.
Commit an executive
sponsor
If you want to avoid becoming a statistic
of a failed SFA initiative it is absolutely
critical that you get a senior executive committed
to sponsor the project. The commitment must
be substantial enough so that a majority of
their time is focused on making the SFA project
successful.
This provides focused leadership
that can proactively communicate the benefits
of the finished project, combined with someone
you can make tough decisions and own the budget.
But most importantly it demonstrates the importance
of the project to the sales reps, which combined
with an incentive compensation plan, reinforces
the urgency to accept and use the system.
After building a business
case and getting executive support for your
sales automation project, it is important
that your organization develops a good understanding
of its sales process.
Define and refine
the sales process
Every organization has a sales process. It
may be well structured and follow a standard
sales methodology like Solution Selling, or
it might be an informal process that has just
developed over time. But at the end of the
month executive management is going to have
some type of reporting expectations from sales
reps that will measure activity and sales
pipeline by some type of meaningful phase.
Many organizations implement an SFA solution
without taking the time to clearly define
their sales process and address any changes
that may be necessary. If the system does
not reflect the accepted sales process then
users will be forced to do their work "off-line"
and then translate that into the system, which
duplicates users workload and reinforces the
impression that the system is not important.
Technology is a great tool for automating
processes and making them faster and easier
to complete. But automating a bad process
just produces bad results faster.
Provide incentives
to use the system
If you want to get a sales reps attention
do one of three things; change their quota,
compensation plan, or both. The opposite also
holds true; if you do not provide some type
of incentive to use the SFA system your chances
of gaining end user buy-in and acceptance
are greatly reduced. Let's face it, when a
majority of your compensation is based on
performance you are most likely to focus on
those things that allow you to feed your family.
A trait common to successful
salespeople is the ability to segment their
time into "paid" vs. "non-paid
activities." Non-paid activities are
typically administrative duties like writing
and editing proposals, updating sales activity
reports, and writing and addressing greeting
cards. These are necessary tasks but a highly
effective sales rep recognizes that there
are a limited number of hours in the day that
can be spent in one-on-one dialogue with customers
while administrative work can be accomplished
outside those hours. This provides an insight
into the basic psychology of a successful
sales executive, they are typically highly
motivated and goal oriented.
There are many ways to
tie compliance and compensation together to
reward good behavior as opposed to implementing
punitive rules that adversely effect morale
and increase turnover. For example, a sales
rep that consistently keeps their sales funnel
and contact records up-to-date would be eligible
for a 0.5% increase in commission for the
entire quarters sales. The incentive could
be factored into the sales reps overall earning
potential and would create buy-in, and a strong
commitment to use the system. I can hear some
executives saying, "I'm not going to
pay my sales reps extra money to complete
basic requirements of their job!" No
I am sure you won't - and you won't have any
reliable data in your system at the end of
the year either.
Provide integration to key applications
The application must provide seamless access
to the resources the sales rep requires to
do their job without adding any layers of
complexity. For example, a very common implementation
mistake involves not providing automatic synchronization
between the contact records in the users personal
productivity package (Microsoft Outlook, Lotus
Notes, etc), the SFA tool, and the users electronic
PDA (Palm Pilot, Visor, etc.).
This seemingly simple obstacle
of entering the same data multiple times will
be very likely to cause the sales rep not
to enter their contact information. Remember
a sales rep is highly motivated and goal oriented.
They will focus strictly on the tasks that
they perceive will assist them in achieving
their goals, whether that be more income,
quota achievement or peer recognition. Double,
or triple entering business cards into their
PC is not going to qualify on their list of
"paid" activities and therefore
will simply not get completed. Make a list
of the key applications your sales reps use
each day to do their job. The functions and
data associated with these applications should
be available in the SFA tool through either
direct data integration, or at minimum a seamless
link to access the functions.
In our fast paced, competitive
environment very few organizations have the
resources to undergo a long, drawn out sales
automation implementation process.
Deploy a manageable
project
Instead organizations are defining
projects in small manageable phases that greatly
reduce their "time to value." By
prioritizing the implementation to attack
the most immediate needs and highest ROI areas
you can build critical user support and annuitize
your investment over multiple business quarters.
Separate the implementation into 3-4 meaningful
phases that group similar tasks according
to how your sales reps complete their jobs.
Determine which group has the highest potential
value impact and attack that phase first.
This process will not only make the project
more manageable but it will also increase
end user acceptance as they see the practical
benefits of using the system.
Invest heavily
in documentation and training
If you are going to roll-out a new tool it
seems like common sense that you are going
to have to provide your end users with documentation
and training. But in almost every project
I have been part of at some point the budget
for documentation and training gets scrutinized
and typically reduced, if not eliminated.
In any project the most difficult aspect of
success is the change management involved
in helping the users learn the tools and how
to incorporate them into their daily jobs.
Without very good documentation and training
end user adoption simply cannot be achieved.
Analysts estimate that
approximately 10% of your implementation budget
should be targeted toward training. For example,
using standard ratios if your organization
purchases $50,000 in software licenses you
should expect approximately $75,000-$100,000
in implementation services; $7,500 to $10,000
of which should be budgeted for training.
These are only guidelines so your actual expenditures
will depend heavily on the customizations
required, amount of integration, timeline,
and level of user sophistication. If your
project is budgeting significantly less that
10% you should reevaluate your strategy.
Final thoughts
Although many SFA projects fail there are
also many success stories. Some organizations
report increases in sales of 8-10% as a result
of their SFA implementations. Sales reps are
a highly adaptive and goal oriented group
of people.
Making the SFA project
successful will require understanding the
basic psychology that makes them tick, and
adapting the project to address those specific
needs. Ultimately the system has to provide
value to the sales rep in completing their
day-to-day job and achieving their goals.
Unfortunately, many SFA implementations are
undertaken with the only goal being to have
better visibility into the sales pipeline.
While this is a valuable benefit of the system
it does not by itself provide much value to
the sales rep.
If you provide real
value and communicate the benefits proactively,
and consistently your organization can win
by implementing sales force automation.
|