Getting to Know the SAP Customer
- The traditional SAP customer is alive and well
- New SAP solutions must attract a very different kind of buyer
- Traditional users, who used to value the strict structure of SAP of old, now apparently want a more agile product. That’s SAP position but the reality is that these buyers will still want more of the same.
On the flight to Atlanta this last Sunday for Sapphire 2007, I sat next to an executive who shared with me why his firm has spent a princely fortune implementing SAP. He was the CIO of a Fortune 500 firm that has had difficulty becoming a single, coordinated global firm. His firm hired a major systems integrator who has expended thousands of hours of effort and billed tens of millions of dollars implementing SAP to help make this change happen.
This conversation took me back – way back to my Accenture (nee Andersen Consulting) days where I advised countless companies on what high-end software to buy or run away from.
In the 1990s, I encountered a number of firms whose users wanted the flexibility and features of best of breed solutions but whose management wanted the suite that SAP offered. While I could see the wisdom of either decision (given the right circumstances), I would occasionally run into an executive (often the client CEO) who had a sense of logic that I found troubling then and still feel bothered by it today.
SAP – The Sword and the Shield
For some CEOs, the conformity that an SAP implementation imposed on an organization was a good thing. If you were a CEO who ran a loose confederation of legal entities, product lines and functional groups and you wanted your firm to be a single-minded globally competitive juggernaut, you want a unified (not fractured) software solution.
To be a global CEO, one needed:
- an organization that has a consistent data architecture (e.g., Can we all agree on what ‘customer’ means in our company?)
- systems that operate in real-time (e.g., Why does it takes weeks/months to close the books around here?)
- little redundancy in the systems (e.g., Why do we have a different accounts payable solution in every country that we operate in?)
- clear, concise information throughout the enterprise (e.g., Why don’t our people in one division/location ever share information with staff in other parts of the firm?)
- etc.
To the global CEO, SAP was a dream come true. It had an exceptionally broad product line with applications/modules in almost all verticals and worked in most geographies. Competitor’s products were often either lacking in vertical depth, global coverage or application suite completeness.
Systems integrators were all too happy to help these soon-to-be global CEOs and bring their systems and organizations into shape. 8, 9, 10-figure consulting fees were not unusual.
What global CEOs paid for with the joint SAP-Systems Integrator solution was:
- a massive change management effort that the CEO did not believe was possible without outside intervention
- a significant data cleanup and standardization project
- a material reduction in the number and variety of systems being supported
- scale economies
- an opportunity to improve the quality, velocity and access to corporate information
What the global CEO was also doing, in many of these cases, was:
- implying that his/her own staff was incapable of pushing this type of change through the company
- signaling that a decentralized, laissez-faire IT approach was no longer wanted or valued
- indicating that power was being re-centralized and concentrated. Decisions were now going to be made globally (not locally, divisionally, or by product-line). A command and control environment is being phased into the company.
In contrast, a CEO could be a global CEO if he/she had political savvy, a clear and compelling vision for the company and a plan for how IT in the new business economy should work. Trouble was, there weren’t either enough of these leaders or those that existed lacked the time, patience and knowledge to develop global firms with non-SAP solutions. You can make a global solution out of best of breed components. But, to do so, you need an architect with clout.
The CEOs who used SAP in this fashion weren’t necessarily selecting the best solution functionally or technically, they were selecting SAP because of its ability to affect change in their firm. They used SAP as sword (to force change on their own employees) and as a shield (to justify how their firm would become a stronger, global competitor).
The Sapphire Experience: Customers Haven’t Changed
Just about every software vendor’s user conference has that moment where the vendor welcomes one or more major customers up on stage and gives them some kind of award. A lot of mutual backslapping occurs where the vendor’s EVP of sales whips up the crowd to congratulate some poor unfortunate for having spent a kingly fortune with the vendor and some systems integrator.
I guess we’re supposed to be impressed when a company sinks a pile of cash into a software deal. I’m not. I’m uncomfortable with this and the spectacle that goes with it. Why? If I were the CEO, VP of Investor Relations, CFO or other position with that software customer’s firm, I’d be embarrassed to let the world know that our firm just set a record for IT spending. Destroying shareholder value is not a good thing. How would you feel if a car dealership wanted to highlight you as the customer who overpaid the most this year?
The users that should be showcased at these events are the ones who spent a pittance and got a ton of value. Morever, the focus should be on highlighting the customers who were able to figure out a lot of the change management challenges on their own and actually solved them without the use of consultants or a strait-jacketing piece of technology.
What I saw at Sapphire 2007 reinforced for me that the SAP customer of the 1990s is still here and may be the life blood of the company. In a compelling exchange with Hennig Kaggerman, he and I discussed how a client has spent $1 billion (USD) on a SAP implementation. He admitted that some firms would be better off spending $4 billion on a new manufacturing facility than $1 billion on implementing their software. One of these capital decisions can deliver decades of value via the products it produces for sale. The other is a cost of doing business. He’s right about this choice.
In the same conversation, we both discussed how some executives are buying SAP solutions because of their need to make their firms global juggernauts. He agreed that they need a lot of systems integrator time/effort to affect the scale of change their firm requires. In other words, the old and new customers are still the same.
The SAP Customer Profile
Jason Busch (www.spendmatters.com and www.azulpartners.com ) and I have spent a fair bit of time assessing the IT sophistication of large global companies. We have developed a database of the top 3700 firms globally. In that database, we created proxies for the Geoffrey Moore Chasm categories (i.e., Innovator, Early Adopter, Early Majority, Late Majority and Laggards).
For more than 20 years, SAP has been a favorite of the Early and Late Majority. It’s also hot with the Laggards, too. In contrast, PeopleSoft had a large number of Innovators, Early Adopters and Early Majority buyers as customers.
What Jason and I have learned is that the large SAP customer:
- is conservative
- likes to buy from the market leader
- can be patient to a fault. They can wait years for SAP to develop a capability that other vendors already possess.
- travels in herds. They like knowing that they’re buying the same solution others in their industry have acquired.
- wants competitive parity not competitive advantage.
- approaches change tepidly
Now, the customer demographics and psychographics may change and this could be something to watch.
The New SAP Customers
SAP leaders repeatedly discussed how SAP’s customers want their businesses to become more agile, more innovative, more successful and faster at adapting to change. This apparently will be true whether these are large firms (the traditional clientele of SAP), Business One customers, A1 customers or A1S customers.
There’s something ironic in all of this. Here is the poster child for rigid software trying now to be positioned as an agile solution to large and small companies.
Small companies, from my experience, are quite agile to begin with. They move with incredible speed and often owe their continued existence to the fact that they can respond to changing customer needs far faster than ossified, bureaucratic, disorganized larger competitors. To date, small firms have made do with minimalist, low-end functional IT solutions and have created all manner of technical and non-technical workarounds to overcome systemic limitations. Any new solution for a small business will have to be:
- very low cost
- capable of phenomenal adaptation capability
- vertically relevant
- straightforward
As SAP executives describe A1S, this solution will have a lot of pre-defined functionality, few(er) configuration options to speed up implementation time, and eventually a broad catalog of vertical bolt-ins.
As customers go, the A1S customer will not be the same as the large R/3 (or current NetWeaver) buyer. Just as the Business One customer is different from the R/3 user, so will the A1S buyer be different. The reason for this is straightforward: different size businesses have very different business needs and systems wants.
For the traditional SAP target market (i.e., Global 2000 firm), these buyers should be quite content with SAP today. They’re getting a well-tested product from a company with a pretty good track record for delivering a quality software product. The only downside for these customers is delivery pace for new products. As SAP’s product line has grown, the time to develop and test new/modified products seems to have grown as well. Several people I spoke with at Sapphire bemoaned the lateness with which some functionality is due to arrive.
Conclusions
Annual events, like Sapphire, cause all of us to reflect on the changes over the last year and beyond. They make us take note of progress and new market conditions. Specific to the SAP customer, I must conclude that:
- The high-end customers are, surprisingly, unchanged. I’m not sure they’ve gotten more or less sophisticated. However, the point may be moot as there are so few large firms left that aren’t SAP customers.
- Prospects of the small business persuasion are quite different from the traditional SAP buyer. I’m still not convinced that SAP is totally ready to attack this space. Yes, it’s lining up channel partners; however, I’m more concerned that SAP’s big, expensive image will bleed into and stall sales in the low-end of the marketplace.
- Some prospects will still be attracted to other solutions. SAP competitors who are attractive to Innovative and Early Adopter segments (e.g., Workday) will continue to find opportunities to compete. The speed with which these firms are delivering new solutions to the marketplace will likely give them an advantage.
- ORCL customers, no matter how good Fusion is/becomes, will be more vulnerable to defection to SAP than vice versa. Too many ORCL customers still refer to the software they use by its pre-acquisition name (e.g., Datalogix, JDEdwards, Peoplesoft) and their loyalty to ORCL may be suspect to some degree. SAP customers have clearly drunk the Kool-Aid and won’t be changing for the most part. Think of SAP customers as 3rd generation Republicans while Oracle/PeopleSoft users are ‘Independents’.