How We Created SAP AMS as a Service: The Founding Story

I’ve been asked many times about how we came up with the SAP AMS as a Service offering. Why did we come up with the service in the first place? What was the business challenge we were trying to solve? How did we come up with the model? How did it evolve? Why did it become so successful? It’s an interesting story.

Early SAP Supprort as a Service Computers

Early Days in Brazil

You may be surprised to learn that Softtek pioneered the service in Brazil and not the U.S. or another Western country.

But you shouldn’t be surprised. Brazil is comparable to the U.S. in many ways. While the United States is the largest economy in the world, Brazil is not far behind at number 8. In population it’s comparable as well, with 223 million to the U.S.’s 352 million.

Consequently, Brazil is a very mature corporate environment and was one of the first Latin American markets to implement SAP across its enterprise landscape, mirroring U.S. adoption rates. The majority of SAP’s installed base was established a good 20 years ago, which contrasts with Mexico’s market adoption of SAP over the last five years.

I was based in Softtek’s Sao Paulo office, and around 2002 quite a few companies were going on their 4 or 5-year anniversaries with SAP and needed help with their maintenance and support.

At that time the Brazilian economy was red hot and prices were high – especially labor costs. Maintaining a full roster of SAP support personnel became cost-prohibitive, which presented us with a business opportunity.

We thought: “Why not offer SAP support on a shared services model and relieve the cost burden on companies who need to support their SAP installations?”

We wanted to roll out this new service to a friendly market. Since we were responsible for several SAP implementations in Brazil, we thought, ‘what better market than our own customers?’

We approached several former customers, including a large European multinational pharmaceutical and biologics company. They had contracted a high-cost service that lacked the quality and scalability they needed, so they seemed like the perfect fit. They agreed and decided to try us out.

Initial Service Model: Fixed Monthly Plus Pay-By-The Drink

We initially offered them 4 full-time equivalents on a shared services model with a single point of contact. We charged them a fixed monthly fee for basic maintenance, such as break & fix. In addition, we offered a variable “pay-by-the-drink” service that covered customizations to the service as well as training.

SAP service and support as a service(Read our other article on how to reduce SAP support costs without sacrificing quality).

At the time, the Brazilian federal government was in the habit of introducing new tax laws any chance they could, and each new regulation required extensive changes to SAP’s accounting modules. These we provided on a “pay by the drink” model.

Also, the high-cost labor market made turnover an issue, which increased training needs. We helped them by offering SAP training on a variable cost basis.

The initial engagement was a success; they increased their footprint with our service, which enabled us to go after a larger market. By 2004 we were up to 20 customers for our shared services model.

Changes to the Service

Over the next several years we made enhancements to the service offering and expanded into additional markets.

1. Rollover Hours

Almost from the beginning we offered a rollover of monthly unused hours. Think AT&T’s “rollover minutes” and you get the idea. There was cultural bias against paying for unused hours, which convinced us to offer the rollover concept for the basic “break & fix” service. Ironically, most companies we offered this to ended up using the bank of monthly hours every month anyway. There was always something broken that needed fixing.

2. The Ticketing Model

For the variable cost “add-on” services, we changed from an hourly service to a “per ticket” model. If a client needed to change a finance module or set up a training session, they would open a ticket with us and pay for the ticket.

3. Regional Expansion

Around 2006 we expanded outside of Brazil to other Latin American markets. We first went to Argentina, and then expanded to the rest of South America, Mexico and North America.

4. The Loyalty Model

Another innovative change we offered around 2010 was a sort of loyalty model. If a client stayed with the service for more than a year, we offered a 5-7% discount of the contracted value on the 2nd year.

5. The 100% Ticket Model

Around 2013 we started offering our service on a global basis, delivering SAP services from our Global Delivery Centers in South America, Mexico and Asia. With these economies of scale we were finally able to offer a completely variable cost, “pay by the drink” economic model by 2014. We eliminated the monthly cost for the “break & fix” and turned everything into a per ticket offering.

Conclusion

I feel very proud of what we’ve accomplished over the last decade and a half. We were able to develop a service based on the needs of one market (Brazil) that has resonated with companies globally.

We were also very fortunate about timing. When we started, the “as-a-service” term hadn’t even made it into the popular lexicon. But when we hit critical mass around 2007-8, the Software-as-a-Service revolution was trending, enabling us to piggyback on the “as-a-service” trend.

But if it wasn’t for the hard-working team we had in Brazil, we would never have been so fortunate – and that’s what I’m most proud of – our people. They made all the difference.

Find out more about Softtek's SAP Application Management Outsourcing Services

 

Topics: SAP

What is Nearshore?

Nearshore is "the transfer of business or IT processes to companies in a nearby country, often sharing a border with your own country", where both parties expect to benefit from one or more of the following dimensions of proximity: geographic, temporal (time zone), cultural, linguistic, economic, political, or historical linkages.

Posts by Topic

see all
To top