There is a widespread habit in growing companies: the CRM is decided in one room and the ERP in another. Sales and marketing compare sales tools; finance and operations talk about invoicing, stock and margins. Each team chooses well within its own perimeter and, months later, someone discovers that connecting both worlds costs more than the software itself. That is why CRM and ERP integration should not be the last item on the agenda, but one of the first decision criteria.
This debate was recently put on the table by SAP in an article in its newsroom titled «The Suite Advantage: Why Enterprises Don’t Evaluate CRM in Isolation» (source: SAP News Center, news.sap.com/2026/10/suite-advantage-why-enterprises-do-not-evaluate-crm-in-isolation/). It is a vendor text and, logically, it defends its own suite. But the underlying diagnosis is valid beyond the brand, and it is worth looking at from the perspective of a mid-sized Spanish company evaluating its management system.
The org chart is not the architecture
Separating the CRM decision from the ERP decision makes sense on an org chart: they are different departments, with different budgets and priorities. The problem is that the customer does not perceive departments, the customer perceives answers.
When a salesperson promises a delivery date, they are checking inventory. When they apply a discount, they are touching price and margin conditions. When they accept an order from a customer with overdue invoices, they are making a financial risk decision. All of that information lives in the ERP, not in the CRM. If the two systems do not talk to each other, what happens is that the person serving the customer works with an incomplete picture, and the rest of the organisation spends hours filling in the gaps: internal calls, spreadsheets, emails asking for confirmation.
The cost that does not appear in the budget
SAP’s article puts at 20-30% the time that salespeople without access to ERP data spend on tasks that are not selling: chasing price approvals, checking availability or validating the status of an order
Beyond the exact percentage, the pattern is recognisable to anyone who has seen a sales operation from the inside. And it has three chained effects: the sales cycle gets longer, forecasting loses reliability because it is fed by data that nobody cross-checks, and the promised return of the CRM gradually dilutes. There is no loud failure; there is a silent erosion.
To that is added the permanent cost of maintaining connectors between two data models that were never designed to understand each other. Every update of either system is a small project. Every new field requires reviewing the mapping. It is a recurring expense that rarely appears in the licence comparison used to decide.
Which figures should be read with caution
The original article provides striking data on the benefits of an integrated suite: integration cost reductions of between 25% and 80%, productivity improvements of 25% to 90% and a five-year ROI of between 214% and 726%, according to a study by Enterprise Strategy Group commissioned in that context
At Tisa we prefer to be honest: these are vendor figures about its own ecosystem and based on specific samples. They serve to illustrate a direction —integrating from the outset is cheaper than integrating afterwards—, not as a promise transferable to your company. What is extrapolable is the reasoning: where you decide the integration risk should live is a strategic decision, not an implementation detail.
CRM and ERP integration seen as an architecture decision
Approaching CRM and ERP integration as architecture, and not as a subsequent project, changes the questions you ask during the evaluation phase. These are the ones we recommend putting on the table:
- Do they share a data model? Customer, product, price list and commercial terms should be a single truth, not two tables synchronised overnight.
- Is synchronisation real-time or batch? A stock figure from twelve hours ago is no use for committing to a delivery.
- Who maintains the bridge? If the answer is «an in-house development», calculate the cost of the next five years, not that of the go-live.
- What happens when you update? Cloud platforms evolve several times a year. The integration must survive those cycles without being rebuilt.
- Does the total cost reflect all of this? Licences, connectors, middleware, support hours and the internal time spent today reconciling information.
Why this matters even more with AI in the mix
There is an additional, very current reason. The AI assistants and agents being integrated today into management tools —Copilot in the Microsoft environment, among others— are only useful if they have access to orderly and coherent data. An assistant that answers about a customer’s status with partial information does not save work: it multiplies it, because it forces you to verify every answer. Without connected and governed data, AI does not deliver. It is the same conclusion we reach in every data project we support.
How we bring this down to earth at Tisa
Our ground is Microsoft Dynamics 365 Business Central, the cloud ERP for small and medium-sized companies, which already covers eight functional areas: finance, manufacturing, supply chain, sales and marketing, human resources, projects, services and reporting. That means a good part of the customer relationship can be managed within the same system where stock, price and collections live.
When a company needs more sales capability than the standard offers, the Microsoft ecosystem allows extending towards Dynamics 365 and Power Platform (Power Apps, Power Automate, Power BI) relying on Dataverse, so that the data remains the same instead of being duplicated
And when the sector asks for something no standard covers, we develop the missing piece: we have done it with our own verticals on Business Central for hospitality, multi-warehouse distribution, point of sale, sports centres and fleet management. You can see examples by sector at grupotisa.com/casos-de-exito.
The practical conclusion
The value of a CRM is not created in the CRM. It is created at the crossing point between customer information and the operational reality of the company: what is in the warehouse, what it costs to produce it and what the customer owes. Evaluating the two pieces separately is, at best, postponing an invoice.
If you are in the middle of a decision process —or you already have an ERP and a CRM coexisting through patches—, let’s talk about it with no obligation. At Tisa we have been implementing management solutions for private companies since 1987, and the conversation always starts with your processes, not with a list of features.
Write to us at info@grupotisa.com or call us on (+34) 971 305 885 and we will give you an honest assessment of your situation.
