Is a Big Name Always the Safest Choice?

When a company begins looking for an ERPAn ERP system connects a company’s core processes—such as sales, finance, inventory, manufacturing, and service—in one place so teams can work with shared information. system, it is only natural to consider major international vendors such as Microsoft and SAP first. That makes sense. These vendors have extensive resources, established technologies, international experience, and widely adopted solutions. 

But does a well-known name automatically mean that an ERP system is the best fit for a particular business? More importantly, will a large vendor necessarily understand how your company operates better? 

A successful ERP implementation depends on far more than software features. It depends on the people who analyze your processes, recommend solutions, carry out the implementation, and remain by your side for years afterward. An ERP system is not just another software product. Over time, it becomes part of how the entire organization operates, and its provider becomes one of the company’s most important technology partners.

It Starts with the Right Questions, and Not a Software Demo

One of the clearest differences between an ordinary software supplier and a genuine ERP partner becomes apparent during the initial business analysis. 

A good consultant does not begin by showing off a long list of features. They begin by asking questions: How does the company operate? Where are the bottlenecks? How does information move between departments? Which processes generate the highest costs? What are the company’s growth plans? 

In a manufacturing business, for example, simply implementing production, inventory, and sales modules is not enough. The partner needs to understand how production orders are scheduled, materials are managed, costs are tracked, operations are recorded, and production interacts with other departments.

Two manufacturers in the same industry may be organized in entirely different ways. One may manufacture to individual customer orders while another produces in series. One may rely on complex production routings, while another works with short production cycles. 

That is why a one-size-fits-all approach is not always the best answer. Genuine ERP analysis is not about forcing a business into a predefined software model. It is about understanding which practices should be preserved, which can be improved, and how technology can support that development. 

This does not mean that every customer request should result in custom development. Sometimes a good ERP partner needs the confidence to say, “There is a better way to organize this process.” In order to offer that advice, they first need to understand the business thoroughly. 

What a High-Quality Initial ERP Assessment Looks Like

Before discussing license prices or implementation timelines, a company needs to establish what exactly is going to change. An initial assessment is neither a formality nor a checklist of features. It is a joint effort involving management, key employees and ERP consultants to map processes, information flows, pain points and objectives. 

In manufacturing, for example, the team should follow the entire journey from customer order to delivery: how the production schedule is created, materials reserved, bills of materials and operations managed, and scrap and downtime recorded. Equally important is how that information reaches procurement, warehousing, sales and finance. An assessment that looks at departments in isolation can miss the very dependencies an ERP system is meant to manage. 

A good assessment produces tangible outcomes: a map of key processes, priorities, responsibilities, measurable objectives, known constraints, and a clear distinction between standard functionality, configurationConfiguration sets up software using its existing options. In an ERP system, it adapts workflows, roles and other settings to the company's business processes. and custom development. It should also surface uncomfortable truths, incomplete data, conflicting definitions of the same metric, or an existing workflowA workflow defines the steps, responsibilities and decisions needed to complete work. An ERP system can guide tasks through these stages and show progress. that creates unnecessary work. 

The parties should agree in advance how success will be measured. For one manufacturer, that may mean more accurate materials planning; for another, better order traceabilityTraceability follows a product or material through its history, from origin to use or delivery. An ERP system connects the records needed to investigate issues and track affected items., less manual entry or more reliable costing information. Without clear criteria, even a technically successful implementation can leave management wondering where the promised business value went. 

When Your ERP Partner Knows Your Business Almost as Well as Your Own Team

Over time, the relationship between a company and its ERP provider can grow beyond the conventional customer–contractor model. 

The implementation team gradually gets to know not only the information systems but also the people, processes, and distinctive characteristics of the organization. They learn which production operations are critical, when demand peaks, how deliveries are planned, what challenges employees face, and which decisions matter most to management. 

That knowledge cannot be gained simply by reading technical documentation. It develops through conversations, working together, solving problems, and years of collaboration. 

This is where one of the most valuable qualities of a good ERP partner emerges: rather than remaining an external supplier processing tickets, the partner begins to function as a natural extension of the customer’s team. 

• When a problem occurs, the customer does not need to explain the company’s entire history again.
• When production expansion is being planned, the ERP partner can join the discussion early.
• When a new business process is introduced, the partner already understands the existing organization and can recommend a solution in the context of the entire system. 

That kind of partnership is built over time, through trust. 

From Implementation to Shared Responsibility

Personal attention should not mean that the customer depends on a single individual. Quite the opposite: a healthy partnership rests on clear roles, documented decisions and shared knowledge. Key users on the customer’s side should participate in testing, understand the new workflows and be able to train colleagues. The ERP team, in turn, needs to know who makes business decisions, approves requirements and accepts deliverables. 

This becomes especially important at go-live. Questions arise that no presentation can fully anticipate: missing data, unusual orders, different practices across shifts or warehouses. A useful partner does not disappear once the system goes live. It helps prioritize issues, distinguish defects from training needs and introduce sensible adjustments. 

The customer has responsibilities, too. No vendor can compensate for the absence of an internal project owner, contradictory management decisions or resistance to change. The strongest ERP relationships work both ways: the vendor contributes technology and consulting expertise, while the customer brings business knowledge and a commitment to improvement. 

Customer Relationships Should Be Personal

In family businesses, there is often an unwritten rule: when someone faces a problem, the others do not stand by. Not because a formal procedure requires it, but because everyone’s success is connected. Of course, an ERP company and its customer are independent organizations, with separate responsibilities and contractual obligations. But their relationship can still be guided by a similar principle. 

A customer’s problem should not be just another ticket number in a support system. An ERP partner should approach it with an understanding of the real consequences for the business. When a production line is disrupted by an information-system issue, it is not merely a technical incident. It can mean delayed orders, idle capacity, additional costs, and dissatisfied customers. 

When the sales team cannot access accurate stock information, opportunities may be lost. When the finance team cannot complete an important report on time, the consequences can affect management across the company. A good ERP partner understands these connections. Their concern is not simply whether a technical ticket has been processed, but whether the customer’s business can continue operating normally. 

Large Companies Have Resources. But Who Takes Personal Responsibility?

International ERP vendors have undeniable advantages: scale, investment, standardization, security, and broad solution ecosystems. Yet scale does not always translate into a shorter path from identifying a problem to resolving it. In complex corporate structures, support may pass through several layers of service teams, partners, consultants, and developers. Each has a role, but customers may struggle to identify who can actually make a decision. 

Smaller, specialized ERP companies may have an advantage here. When consultants, business analysts, and developers work closely together, communication can be more direct and decisions more flexible. Even more importantly, customers may work with people who already know their organization and take personal responsibility for service quality. 

Of course, size alone does not guarantee this approach. A small company without sufficient specialists or well-organized support can create serious difficulties too. The real advantage is not being small; it is combining professional expertise with personal commitment and genuine accountability to the customer. 

What Does a Fast Response Mean in Practice?

For a company that relies on ERP every day, the promise “we are always here for you” is not enough. It needs to know how to report an issue, how severity is assessed, how quickly the report will be acknowledged and when the next update will arrive. Good support has a human face, but it also has a predictable process. 

Imagine a factory that cannot release production orders. The support team must first establish the scope: are all users affected, and does the issue involve data, infrastructure or a specific operation? It should then identify who owns the case and whether a safe temporary workaround exists. If developer involvement is required, the customer should understand how escalation will work. 

It is essential to distinguish initial response time from resolution time. No responsible vendor can promise the same fix time for every incident. It can, however, commit to measurable standards for communication, prioritization, diagnosis and post-incident review. Those commitments turn personal attention from a good intention into a verifiable service quality. 

When the Answer Is “You’ll Have to Wait”

On November 12–13, 2026, a Microsoft 365 service disruption affected Outlook, Teams, and other tools relied upon by organizations around the world. According to Reuters, difficulties lasted approximately 12 hours, while independent monitoring by Cisco ThousandEyes identified global availability issues. For affected organizations, that meant hours of uncertainty and limited ability to influence the recovery process directly. 

This incident does not prove that Microsoft Dynamics 365 is a less reliable ERP system, or that smaller providers never experience outages. Microsoft 365 and Dynamics 365 are different products. The example illustrates something else: when a critical service depends on centralized infrastructure, even a provider’s enormous scale cannot guarantee immediate restoration for an individual customer. 

For a manufacturing company, that dependency raises practical questions: what happens to order planning, inventory, and deliveries if access to a key system is restricted? Who will explain the impact, suggest a temporary workaround, and coordinate action until service is restored? 

This is where a personal partnership matters. A smaller, specialized ERP provider may offer more direct access to people who understand the customer’s processes and participate in technical decisions. But that advantage is real only when backed by adequate capacity, redundancy, clear procedures, and agreed response times. Personal attention is no substitute for operational resilience. 

A fast response does not necessarily mean an instant fix. It means timely information, personal accountability, an assessment of the consequences, and a concrete action plan. That is what distinguishes a partner who understands your business from a supplier who simply logs another ticket. 

Sources for the incident: Reuters and Cisco ThousandEyes 

Resilience Matters More Than a Promise That Nothing Will Ever Go Wrong

Outages at major cloud services attract attention because they reveal how many organizations depend on shared infrastructure. The lesson, however, is not that a local or smaller vendor is immune to disruption. The better question is how the system and the team supporting it are prepared for risks that cannot be eliminated entirely. 

When choosing an ERP partner, discuss backups, disaster recovery, access management, system monitoring and dependencies on third parties. Where is data stored? Who is authorized to restore service? How often is a backup actually tested? What happens if an internet connection or an integrated service becomes temporarily unavailable? 

These are not questions reserved for multinational corporations. For a mid-sized manufacturer, several hours of downtime can be a serious operational risk. Reliability should therefore be judged by architecture, procedures and agreed responsibilities — not by the size of the logo on a slide. Personal contact matters, but it does not replace technical preparedness. The strongest offering combines both. 

Partnership Is Proven After the Contract Is Signed

At the beginning of every ERP project, there are presentations, demonstrations, plans, and promises. But the true quality of the relationship emerges later: when an unexpected situation arises, production must be reorganized, a new warehouse opens, a production line is added, or the company enters a new market. 

At that point, customers need more than a supplier who delivers the agreed services. They need a partner who understands why change is necessary, how it will affect other processes, and how to implement it sensibly. 

A long-term partnership does not mean an ERP provider must agree to every request. Sometimes the most valuable contribution is professional disagreement: a consultant explaining why a proposed change would create more problems than benefits. That, too, is a form of responsibility. 

The ERP Partner as Part of the Company’s Extended Family

The word “family” may seem unusual in the context of enterprise software. Yet many successful business relationships are built on principles we associate with family: trust, mutual support, open communication, and a willingness to help when things get difficult. 

When an ERP company works with a customer for years, it comes to understand that company’s strengths, challenges, and ambitions. It celebrates the customer’s achievements because it helped make them possible. And it takes the customer’s problems seriously because it understands what is at stake. 

This does not mean blurring professional boundaries or contractual responsibilities. On the contrary, real trust requires clear commitments, honest communication, and a willingness to be accountable. 

The most valuable ERP partnership is one in which customers do not feel alone when facing their business’s technology challenges. They know there are people behind the system who know them, understand them, and care about their long-term success. 

How to Build Trust That Lasts for Years

Partnership is not created by a single promise of “tailored service.” It is demonstrated through small, repeated actions: a consultant remembers why a decision was made; the team warns about a risk early; after go-live, discussions cover improvement opportunities as well as defects. The customer knows whom to contact and receives explanations in clear business language. 

This becomes particularly valuable as the company grows. A new workshop, an additional warehouse, an acquisition or a change in planning methods can affect many processes at once. An ERP partner familiar with the history behind earlier decisions can identify consequences sooner and suggest realistic options. Sometimes the answer is configuration, sometimes an organizational change, and sometimes a project that should wait until the business is ready. 

This is where the family metaphor has value, provided it is not taken literally. It describes a relationship in which nobody hides behind formalities, yet everyone respects agreed boundaries. Trust does not eliminate difficult conversations about budgets, deadlines or mistakes. It makes it possible to have those conversations early and openly. 

How to Recognize the Right ERP Partner

When choosing an ERP system, it is worth looking beyond features, price, and technical architecture to examine how the provider builds relationships with its customers. 

1. Who will conduct the initial analysis of our business processes, and what experience do they have in our industry? 
2. Will we work with a consistent team that gradually gets to know our organization? 
3. How do consultants, support specialists, and developers communicate with one another?
4. What specific commitments does the provider make when critical problems occur?
5. Can the system evolve with our business without every change becoming a complex and expensive project?
6. Is the provider willing to advise us against a change when it is not in our best interests? 

The answers to these questions often reveal more about a future partnership than even the most impressive product demonstration. 

How to Test Promises Against Reality

Before making a decision, ask for more than a product demonstration: request an outline of the assessment and implementation plan. Have the vendor explain which activities it performs directly, which depend on partners and who will be your main point of contact. Ask how specific requirements are documented and how the impact of proposed changes is evaluated. 

It is also worth speaking with existing customers, ideally companies with a similar profile. Ask not only whether the system works, but how the initial assessment was handled, how disagreements were resolved and what happened when the first serious post-implementation issue arose. These conversations provide a more realistic picture than general claims about “excellent service.” 

Compare proposals against consistent criteria: total cost of ownership, functional coverage, integrationIntegration connects systems so they can exchange information or coordinate actions. An ERP integration helps link business tools and reduce manual transfers between them. options, security, team capacity, support terms and future development. The lowest initial price is not necessarily the lowest long-term cost. Nor is the best-known brand automatically the lowest-risk choice. The right decision is the one whose benefits and limitations are understood before the contract is signed. 

SIX ERP is built on the idea that business software should support how companies actually work, rather than operate separately from their day-to-day reality. Explore SIX ERP. 

Whether the focus is manufacturing, warehousing, sales, field service, or financial management, an ERP system creates value by connecting processes and providing reliable information for decision-making. 

But technology is only one side of a successful implementation. The other is the relationship between the people who develop and implement it and those who rely on it every day. See real examples of the business value delivered by SIX ERP. 

When evaluating SIX ERP, it is therefore important to consider not only functionality but also how business analysis, implementation, customizationCustomization changes or adds software functionality beyond standard settings. In an ERP project, it can meet specific business needs while adding development and maintenance work., and ongoing support are handled. That is where the trust required for a long-term partnership is built. 

Conclusion: The Right ERP Partner Takes Your Success to Heart 

Large international ERP vendors have their place and undeniable strengths. But brand recognition should not be the only selection criterion. 

For many companies, the quality of the initial business analysis, an understanding of specific processes, personal communication, and the provider’s ability to respond effectively to problems may matter more. 

An ERP system is not a one-time purchase; The selection process of an ERP is a vital decision for your company’s future. It marks the beginning of a long-term relationship that will span change, challenges, and new opportunities. 

Perhaps the best ERP partner is not the one with the most customers, but the one that makes every customer feel important. 

Not just as a contract number, but as a business whose growth matters. 

Because when a partner knows your business, understands your people, and treats your success as its own, it is no longer just an outside supplier. It is part of your team.