The company behind the SAP switch

Consider the moment after a company buys enterprise software. The demonstration has ended. The slides looked tidy. Now somebody must explain how a customer order becomes a shipment, how that shipment becomes an invoice, and why three departments have three different versions of the same customer. This is the territory ACS Systech Integrators occupied: the awkward stretch between a software purchase and a functioning business.

The San Jose company, founded in 2001, sold expertise around somebody else’s platform. Its old ACS name survives on LinkedIn, where the company directs visitors to Systech Integrators. Its former website now leads to Softtek. Following those breadcrumbs produces a useful business story: a specialist can become valuable because of the difficult work it knows how to repeat.

The expensive space after “install”

Systech’s offering covered business assessment, implementation, consulting, application management and hosting. Customers could deploy through SaaS, cloud or on-premise arrangements. SAP Business All-in-One partner solutions added packaged industry capabilities. These were different ways to get an enterprise system into use, with different choices about where it ran and who looked after it.

A hypothetical manufacturer makes the problem concrete. Purchasing needs materials data. Production needs schedules. Finance needs costs it can trust. Installing a shared application does not, by itself, settle disagreements about how those functions should work together. A systems integrator configures the software, connects applications and helps translate business requirements into working processes. Systech’s consulting and custom-development services addressed that work.

The commercial proposition extended beyond launch day. Application management provided a continuing support offering; hosting added responsibility for the operating environment. That gives the business a project component and an ongoing service component. For a buyer, the useful question is how much responsibility the provider accepts after implementation, when the presentation has become a production system.

A $65 million vote for specialization

In October 2006, Affiliated Computer Services acquired Systech. The announcement put the price at $65 million, with up to $40 million more tied to future performance. Systech had approximately $61 million in trailing annual revenue. ACS was buying an established SAP services operation, with a price roughly matching a year of sales.

The customer fit explains the attraction. ACS’s financial adviser described the deal as strengthening its position with Fortune 1,000 and mid-market companies. Its investor presentation highlighted SAP’s emerging middle market. Systech sat between the software maker and organizations needing help putting the platform to work. That position gave a larger outsourcer a ready-made capability to sell.

Then comes the less convenient number. ACS’s 2008 annual report recorded approximately $63.8 million in transaction value, plus related costs, and said the contingent-payment period had expired without any payment being earned or paid. The announced figure and the later accounting figure describe the deal differently. Neither justifies treating the possible $40 million as money received.

The performance condition was unmet. That is the limit of the evidence: it does not establish a failed customer installation or explain management’s private decisions. For anyone copying the acquisition strategy, the distinction matters. Buying capability and realizing the hoped-for financial result are separate tasks. A signed agreement can establish the first; only subsequent performance can establish the second.

The next buyer wanted a map

When Softtek announced its acquisition on February 7, 2013, the emphasis shifted. Systech brought SAP expertise, including cloud, mobility and HANA capabilities, and a delivery center in India. Softtek already had centers in Mexico, Brazil, Argentina, Spain and China. Adding Systech expanded the choices for where work could be delivered.

Sam Tyagi, Systech’s CEO and co-founder, moved into leadership of Softtek’s North American ERP practice. The announcement briefly retained the name “Systech, a Softtek Company.” The integration therefore included both delivery infrastructure and leadership. The interpretation is straightforward: Softtek could add specialist capacity and geographic reach together, rather than build each separately.

“We are thrilled about the new opportunities that lie ahead by joining Softtek.”Sam Tyagi / acquisition announcement, 2013

In October that year, Softtek’s Blanca Treviño described intensified investment in SAP through Systech and another acquisition, SCAi, alongside entry into India. Her account presents a deliberate expansion of an existing practice. Systech’s role was to add depth to a business that already understood SAP.

Buy the handover, too

Systech’s market position rested on concentration: SAP expertise across the application lifecycle, delivered from the United States and India. Its alternatives included other SAP specialists and large consulting firms with wider service portfolios. The practical comparison is the team’s relevant experience, industry understanding, support arrangements and delivery model. A familiar consulting logo cannot answer those questions.

For the customer, deployment and support belong in the same conversation. A hosted system still needs a clear division of duties. An on-premise system still needs specialists. The sensible buying exercise is to map the work, assign an owner to each part and agree how issues move between the customer and provider. Systech’s breadth makes that exercise especially relevant: a long service menu is useful only when the responsibilities are clear.

The approach has clear conditions. It makes sense for an organization using SAP that needs implementation capacity or continuing operational help. A company with simple accounting needs may have little use for that breadth. A buyer also needs internal people who can decide how the business should operate. Consultants can configure a process; they cannot make every unresolved organizational choice disappear.

The transferable lesson is to examine the handovers. Who owns the move from assessment to configuration? From configuration to launch? From launch to everyday support? Systech built an offering across those seams, and two buyers found reasons to acquire it. For an enterprise software customer, that is a more useful starting point than the demonstration: ask who will still be responsible when the system becomes ordinary.