Signs your company has outgrown Excel: when a CRM or ERP makes sense

Excel is not a bad tool for managing a business. The problem starts when it ends up doing things it was not designed for.

You can calculate prices, track orders and organise customer lists in a file. For a small company, that may be enough.

But as activity grows, the file starts circulating among colleagues. Different versions appear, formulas nobody understands anymore, and information that has to be copied manually from one place to another.

At some point, you are no longer managing the company's activity. You are managing the files in which you tried to organise it.

That does not mean you must immediately buy an ERP. It means it is worth checking where the process is starting to get stuck.

The clearest sign: nobody has the same information

Imagine a company making custom furniture.

The salesperson has the quote in Excel. The customer confirms changes through WhatsApp. Production receives a PDF version, while accounting has other information in the invoicing software.

When the customer asks about the order's status, each department has to check separately.

The problem is not that the company uses Excel. The problem is that there is no shared source of up-to-date information.

Things become difficult when:

• The same order exists in different files.
• Changes are communicated through messages or phone calls.
• It is unclear which version of the quote was approved.
• Knowing a job's status depends on asking someone.
• Information has to be entered again in each department.

If you recognise these situations, the problem needs to be analysed at the process level, not just the file level.

The next sign: quoting depends on one person

In many manufacturing companies, there is a colleague who knows all the formulas, exceptions and calculation rules.

They know which accessories go into a product, when the price needs changing and which configurations cannot be made.

The rest of the team uses the file but does not fully understand how it works.

As long as that person is available, things work. When they are absent, questions arise that nobody can answer.

This is not necessarily about a CRM or ERP.

You may need a configurator that applies product rules. You may only need to document the formulas and protect certain fields.

What matters is taking critical rules out of a single employee's memory.

The next sign: an order must be rewritten after acceptance

The customer accepts the quote. Then someone takes the data and prepares the order for production.

Dimensions, materials, colours, accessories and special conditions are copied. If something changes, all relevant documents need updating.

This is where transcription errors can occur.

A connected system can take the approved configuration and use it for subsequent documents. Depending on the product, it can generate production information or the bill of materials.

But before automating, you need to establish which data is mandatory and who confirms the final version.

If the quote does not contain the correct information, automatic transfer does not solve the problem. It just passes the mistake along.

The next sign: quote requests get lost

Not every problem starts in production.

You may receive enquiries through the website form, phone, WhatsApp and email. Each salesperson keeps their own records.

Some enquiries get a reply, others have no owner. You do not clearly know which quotes have been sent and which customers need a follow-up.

Here, a CRM can be more useful than an ERP.

CRM stands for Customer Relationship Management. In short, it is a system for managing customer relationships and sales activity.

It can centralise:

• Customers' contact details.
• Enquiries and sales opportunities.
• Quotes and negotiation stages.
• The person responsible for each customer.
• The history of conversations and activities.

You do not need to implement a large system to get this organisation. What matters is choosing features the team will actually use.

CRM or ERP: what is the practical difference?

A CRM mainly tracks the commercial relationship.

It helps you see who requested a quote, who needs contacting, what you proposed and the opportunity's stage.

An ERP tracks the company's operational processes and resources, depending on the modules implemented.

For a manufacturer, it can connect orders with production planning, materials, execution stages and documents.

The difference becomes clear when you look at the question you want to answer:

• “Who do we need to send the quote to?” — a CRM problem.
• “Which orders have been confirmed?” — can be managed in a CRM or an order system.
• “What do we need to produce for each order?” — an operational problem, possibly for an ERP.
• “Which materials go into the ordered product?” — may require a configurator, BOM or production module.
• “Which jobs are ready for delivery?” — an operational tracking problem.

There is no requirement to implement everything together.

When Excel is still enough

For some companies, an ERP would bring more complexity than value.

If you work with a low order volume, have a simple process and well-organised information, you can continue using Excel.

Before buying software, check whether the problem can be solved through:

• A centralised file with controlled access.
• Documented formulas and rules.
• Standard fields for each order.
• A clear updating procedure.
• An existing tool you are not using correctly.

New software does not automatically compensate for missing responsibilities or internal rules.

If nobody updates order statuses, the same problem can appear in an expensive ERP too.

How to make the transition without disrupting operations

The riskiest approach is trying to change all processes at once.

A more manageable option is choosing the workflow causing the most problems.

For example, you can start by tracking quotes and confirmed orders.

Before implementation:

• Describe how a customer enquiry moves through the company today.
• Identify information entered repeatedly.
• Establish who is responsible for each stage.
• Decide which data from existing files needs keeping.
• Define what happens when changes or exceptions arise.
• Test the solution with real situations before expanding it.

Do not automatically move every old file into a new application. First check whether the information is correct and still needed.

Otherwise, you risk building a new system around the same problems.

Custom software or an existing program?

Not every company needs software developed to order.

If your activity is standard, an existing CRM or ERP may cover the requirements without additional development.

Custom software becomes relevant when you have product rules, sales workflows or production processes that standard solutions do not handle adequately.

For example, a company producing configurable gates may need to link dimensions, accessories, prices and materials to the production order.

A generic ERP will not automatically know these rules.

For Davos Europe, VIBEZ delivered a 3D product configurator and is extending, module by module, the platform that connects quoting with operational processes.

The selection criterion remains the same, however: does the problem justify the solution?

Where to start

Do not start with “which ERP should I buy?”. Start with the order your team finds hardest to manage.

See how processes can be connected through an ERP or CRM or talk to VIBEZ about your company's workflow.