CRM vs. ERP: what does a small business actually need?

The German business dictionary Gabler Wirtschaftslexikon describes an ERP system as software with modules connected through a shared database (Gabler: ERP system, in German). The modules cover purchasing, production, sales, human resources, and finance and accounting. The dictionary defines CRM more broadly, as a strategic approach to all processes that involve contact with customers. CRM software is the tool within that approach (Gabler: CRM, in German).

The official survey on IT use in businesses draws a clearer line. In the questionnaire of Germany’s Federal Statistical Office, ERP is software that manages resources by exchanging information between functional areas, such as accounting, planning and production. CRM is software for managing information about customers. The questionnaire adds that ERP software can also be software a company built itself (Destatis, quality report and questionnaire 2025, in German).

Two German sources written for small businesses show what each system contains in practice. A market study on small companies by the Fraunhofer Institute for Material Flow and Logistics covers ERP (Fraunhofer IML, ERP market study, Mar 2021, in German). It lists master data on items, customers and suppliers, along with quotes, orders, purchase orders, invoices and production planning. A checklist from Mittelstand 4.0-Agentur Handel, a federally funded initiative that helps small and mid-sized retailers and wholesalers go digital, covers CRM (Agentur Handel, CRM checklist, Jan 2018, in German). It lists contact data, a contact history, search and filters, reports, roles, and import and export.

The numbers in the “Sources” column refer to the source list at the end of this article.

The overlap is built into the products. The Fraunhofer study counts a CRM module among the software modules of an ERP system. Documenting communication with individual contacts was standard at all 34 vendors surveyed. Creating a sales opportunity wasn’t standard at all of them. Conversely, the Agentur Handel checklist says quotes, invoices and delivery notes for a contact can also be stored in a CRM. It calls the connection to the ERP system especially important.

You decide where to draw the line. The checklist considers it important to settle which system owns the data and which system may write to which. Our suggestion is one system of record per type of data:

The other system only reads the data or receives it through an integration. Without this rule, two people maintain the same customer in two places. The Fraunhofer study describes the result for small companies: inconsistent data and non-uniform master data.

Strengths: Customer data and conversations are in one place. If someone is sick or on vacation, everyone on the team has the same information, and tasks such as following up on a quote become visible (Agentur Handel checklist). According to the checklist, many vendors offer trial versions. For a cloud system, it says, an internet connection is practically all you need.

Limits: A CRM alone doesn’t manage inventory, purchase prices or bookkeeping. It only works if everyone keeps it up to date. In an interview in the checklist, one company names getting its data into a consistent structure as its biggest challenge and disciplined upkeep as an ongoing task. The checklist also advises small businesses to stick to the features they really need.

Use case: consulting firms, planning and engineering offices, agencies and other service providers whose sales take several conversations. One question from the checklist helps here: do you have enough customer contacts that aren’t anonymous? For a business with just a few regular customers, a CRM often pays off only later, in our view.

The Fraunhofer study names triggers such as data silos, material planning in Excel, and errors in order processing caused by manual or paper-based steps. According to the study, an ERP system makes sense when a company can’t otherwise ensure that all resources are available at the right time, in the right quantity and in the right place. The need usually grows with the number of employees, systems and orders.

Strengths: Purchasing, warehouse, orders and invoicing all work from the same data. According to the study, a central order status improves the information you can give business partners. Prices come from centrally maintained price lists, and recurring processes become consistent.

Limits: Even with few users, there’s a baseline effort, because according to the study, costs don’t rise in line with functionality. For a small company with 15 users, a survey of ERP vendors in May and June 2020 put the combined cost of licenses and services at €2,600–4,000 per user. The authors explicitly call this a rough guide, and these aren’t current prices. On top of that come staff time, maintenance and release upgrades, which most vendors recommend every two years. Our five-year cost comparison shows how to calculate all costs over the same period.

Use case: retailers, wholesalers and manufacturers with items, inventory and bills of materials, and businesses with their own warehouse. If a business only handles goods, a merchandise management system (inventory and purchasing software) may be enough. According to the study, such systems usually have no features for finance and accounting or for production planning. Bookkeeping then stays in a separate program.

For 2023, Eurostat, the EU’s statistical office, reports the share of enterprises that used at least one of the three systems: 22.5%. The remaining 77.5% used none of them. In this size class, 16.9% used an ERP and 12.8% a CRM (Eurostat, size classes, Feb 27, 2026). Business intelligence (BI) means software for analysis and reporting.

Consider moving to a system as soon as two or more people need the same customer data every day, or only one person understands the list. Our section on when Excel reaches its limits as a database lists the warning signs.

For processes that look similar in many businesses, there’s industry-specific software. The German trade newspaper Deutsche Handwerks Zeitung names project management, invoicing and time tracking as typical uses. These products usually come with ready-made integrations (Deutsche Handwerks Zeitung, Oct 20, 2020, in German). In our view, in the skilled trades they often do the jobs of a CRM and an ERP at once, even if they aren’t called that.

With 250 or more employees, 89.4% used an ERP and 61.1% a CRM (Eurostat, size classes). Eurostat’s size classes count employees and self-employed persons. Across the EU, 46.45% of enterprises with 10 or more employees used ERP in 2025 and 28.51% used CRM; with 10–49 employees, the figures were 41.08% and 24.69%. Shares differ sharply by sector. We compiled the breakdown below ourselves from Eurostat data.

Source: Eurostat, sectors, Feb 27, 2026. In construction and in transportation and storage, nearly twice as many businesses use ERP as use CRM. Among professional and technical service providers, the two are close. Of the sectors shown, CRM is more common only in information and communication.

Our calculation: The Eurostat tables we used don’t report how many businesses use both. A minimum can be calculated, though: ERP + CRM − (ERP, CRM or BI). For enterprises with 10–49 employees, that gives 37.48 + 25.95 − 45.56 = 17.87%. So of the businesses this size that use a CRM, at least 68% also use an ERP. The data doesn’t show which system came first, or whether both were needed from the start.

Limits of the data: The survey is based on self-reporting and is voluntary, and in Germany it had a response rate of 24.6% in 2025 (Destatis). Sector figures exist only for enterprises with 10 or more employees; for micro-enterprises, the latest data is from 2023. The CRM series starts only in 2023 and doesn’t allow a longer comparison. The German ERP series for 10–49 employees also swings widely, for example between 50.05% in 2015 and 22.12% in 2019. Treat the figures as a rough guide.

Eurostat describes both routes: linking data between different applications, or using a single ERP with modules (Eurostat, E-business integration, May 2026). An API (application programming interface) is the defined way two programs exchange data. To avoid data silos, Gabler Wirtschaftslexikon says a CRM used in day-to-day customer contact should connect to ERP systems through capable interfaces.

• One system saves you the integration. Customer, quote and order sit together from the start. In our view, the CRM module is often leaner than a standalone CRM, and you depend more on one vendor. Ask whether the module manages sales opportunities, because according to the 2021 Fraunhofer study, that wasn’t standard in every ERP.
• Two programs give sales more features. In exchange, you pay for the integration and its upkeep. Before you buy, clarify which fields it transfers, in which direction and how often.

Sequence: Start with the system that solves your biggest bottleneck. Keep later expansion open by checking at the first purchase that all your data can be fully exported. Our section on the middle ground between buying and building explains when it makes sense to add your own software alongside an off-the-shelf product.

1. Do you carry goods, materials or bills of materials? If yes, the path leads to an ERP, merchandise management or industry-specific software. If no, go on to question 2.
2. Where do you lose time or money? If it’s before the order, for example in follow-ups and handoffs, that points to a CRM. If it’s after the order, in materials, scheduling and billing, that points to an ERP or industry-specific software.
3. Do two or more people need the same customer data every day? If no, a customer list is usually still enough.
4. Does industry-specific software cover your core? If yes, check it first.
5. Do sales and fulfillment work separately? If yes, you need clear data ownership, and usually two connected systems or an ERP with a strong CRM module.

The sequence and the recommendations are our assessment.

The BSI also factors the effort for training and data migration into the selection (BSI, IT-Grundschutz module APP.6). Also check:

• Requirements: Separate must-haves from nice-to-haves. Our guide to writing a software requirements specification shows how.
• Test: Use a trial version, then start with only a basic version, as the Agentur Handel checklist recommends.
• Upkeep: Decide who is responsible for the data and what rules apply to entering names, phone numbers and categories.
• Export: Check whether conversation history and attachments come along too. Run the export once yourself during the trial.
• Dependence: The BSI says to clarify during planning whether a piece of software will make you dependent on one manufacturer.
• Costs: Calculate per-user licenses, rollout, training and upkeep over the same period. We don’t compare prices of individual products here because they change constantly.
• Personal data: A CRM contains data about people. Ask your data protection advisor what you need to put in place.
• Invoices and retention: Ask your tax advisor whether a system meets your obligations for e-invoices and record retention.

Our build vs. buy comparison helps you decide whether building is worth it at all. It shows a five-year calculation and names the cases where off-the-shelf software is clearly better. In our view, a custom web app is worth it mainly where your team relies on Excel lists, Access databases or paper today and no product covers the process.

In the process check for custom business software, we map your process, sketch your data and assess whether off-the-shelf software is enough. If a CRM, an ERP or industry-specific software fits, we’ll recommend it. You can also use the report if you then go ahead with an off-the-shelf product.