SAP and SMEs: 5 prejudices that are no longer true in 2026

For a long time, small and medium-sized enterprises (SMEs) and SAP software did not seem to be particularly compatible. SAP implementation projects had a reputation for being too expensive and taking too long. In addition, SAP systems were considered complex to use, so many users avoided them rather than using them. Regardless of the truth of these assumptions, one thing is certain: the experiences reported refer to an SAP world that no longer exists.

Today’s reality: With SAP S/4HANA Cloud Public Edition, SAP offers a cloud ERP system that is specifically designed for small and medium-sized enterprises. So it’s high time to put five persistent prejudices about SAP and SMEs to the test.

Want to know how fit-to-standard and CAD integration work in mechanical engineering?

In our free white paper, “The Ultimate ERP Guide for Mechanical Engineers 2026,” we go into depth with a realistic roadmap, an edition comparison, and a checklist to help you make your decision.

Prejudice #1: “SAP is far too expensive for a company of our size.”

High costs may once have been a valid objection. Traditional SAP implementations required significant upfront investments in licenses, hardware, implementation, and internal personnel. This quickly added up to considerable sums before a single process was even up and running.
SAP S/4HANA Cloud Public Edition works differently. The cloud ERP system is based on a subscription model – similar to what many companies already know from Microsoft 365 or Salesforce. Predictable monthly costs, no investment in your own servers, no base team for ongoing operations. SAP takes care of hosting, maintenance, and updates.

This does not mean that the introduction or use of SAP S/4HANA Cloud Public Edition is free of charge. But the overall cost structure has changed fundamentally. Especially for medium-sized mechanical engineering companies who currently work with several isolated solutions in parallel – one system for accounting, one for production, one for purchasing, plus various Excel files – it is worth comparing: What do all these individual solutions cost together, including interface maintenance, double entry, and the risk of inconsistent data?

Prejudice #2: “SAP projects take forever.”

This experience also relates to the on-premise world. Classic SAP implementations with extensive customizing could indeed take 12 to 36 months, sometimes even longer.

SAP S/4HANA Cloud Public Edition turns this logic on its head. Instead of adapting the system to each individual business process, SAP delivers preconfigured best-practice processes that have proven themselves many times over and are ready for immediate use. The principle is called “fit-to-standard”: The company checks whether its own requirements can be mapped to the delivered SAP standard processes and whether the SAP Cloud ERP system is therefore the appropriate solution.

Sounds like a compromise? It isn’t – at least in most cases. Over decades, SAP has analyzed processes from hundreds of thousands of projects and translated them into standardized workflows. For areas such as finance, purchasing, and sales, this works extremely well in mechanical engineering. A pure finance project can go live in 16 weeks. Even more extensive implementations involving production and logistics can be realized in less than twelve months.

Prejudice #3: “We have no SAP expertise whatsoever internally.”

The GROW with SAP program is designed as a complete package aimed explicitly at new SAP customers. In addition to the SAP S/4HANA Cloud Public Edition cloud ERP system, it also includes activation services provided by certified partners, training resources on the SAP Learning Platform, and access to the SAP community for professional exchange.

The key point: Because SAP S/4HANA Cloud Public Edition is a Software-as-a-Service (SaaS) model operated entirely by SAP, companies do not need internal teams for system administration, database maintenance, or upgrade management. SAP takes care of all that. What companies need are employees who can operate the system and understand the processes – and that’s exactly what the training courses are for.

An experienced SAP implementation partner accompanies the introduction and ensures that knowledge is not only built up but also anchored in the company. Internal SAP expertise from day one? Not necessary. What is sufficient? A willingness to learn and a competent SAP partner.

Prejudice #4: “SAP is far too complex for a company of our size.”

The potentially true core of this prejudice relates to other SAP S/4HANA deployment options. As an on-premise version and in the private cloud, SAP S/4HANA can indeed be a powerful system with an enormous range of functions, but it is primarily tailored to upper mid-sized and large companies.

SAP S/4HANA Cloud Public Edition—the SaaS model of SAP S/4HANA from the public cloud—is a curated version that offers the functionality that a medium-sized company really needs, embedded in a modern, intuitive user interface called SAP Fiori. This is browser-based, mobile-enabled, and significantly more user-friendly than the classic SAP GUI that many still remember from the past.

Where the standard is not sufficient, SAP Business Technology Platform (BTP) offers the option of developing individual extensions without interfering with the core of the ERP system. This so-called clean core principle ensures that the system remains lean and updatable. Company-specific developments are not integrated into the software code, but connected via interfaces.

Prejudice #5: “Our industry is too specialized. SAP doesn’t know anything about mechanical engineering.”

SAP has been at home in the manufacturing industry for over 50 years. Mechanical engineering is one of the core industries for which SAP has developed specific best practices – from bill of materials management and production planning to quality assurance. A lot has happened in recent years, especially in the area of CAD and MES integration: With SAP Integrated Product Development (IPD), design data from common CAD systems such as SolidWorks, Inventor, or AutoCAD can be integrated directly into SAP S/4HANA. And with SAP Digital Manufacturing, a cloud-based MES solution is available that synchronizes production data with the ERP system in real time.

Of course, there are limits. A single-item manufacturer with highly complex variant configuration has different requirements than a series manufacturer. But that’s exactly what the fit-gap analysis at the start of the project is for: a structured review of what the standard covers and where extensions are needed. An honest analysis at this point protects against unpleasant surprises and is the hallmark of a competent SAP partner.

Conclusion: Does it match the individual requirements?

The bottom line is that medium-sized mechanical engineering companies and SAP are not operating in incompatible worlds. Consequently, the question “Is SAP even suitable for medium-sized companies?” is incorrectly phrased. The real question that SMEs need to answer for themselves is: “Does SAP S/4HANA Cloud Public Edition fit my specific requirements?” And the answer to this question can be found with a clean, holistic analysis.