Blog

Hungry for knowledge? Check out the blog for articles written by our experts.

June 22, 2026

CRM in Excel – When Is It Worth Switching to a Sales System?

In many companies, the first CRM is built in Excel or Google Sheets. At first, it is simply a list of customers, contacts, inquiries, and statuses. Such a spreadsheet is quick to prepare, easy to change, and sufficient when the team is small and the sales process is simple.

Over time, however, the same file begins to contain much more than contact details. Quote values, discounts, margins, pricing variants, technical notes, reasons for lost opportunities, sales forecasts, approvals, and information needed to hand the case over for delivery begin to appear.

At that point, the company no longer has just a “CRM in Excel.” It has a spreadsheet that is beginning to act as an informal sales and quoting system.

This is an important distinction. Not every such case requires a dedicated application. Sometimes an off-the-shelf CRM will be the best next step. Sometimes organizing the spreadsheet, adding a dashboard, or creating an integration will be enough. However, there are situations in which a standard CRM will not solve the problem because the spreadsheet supports a process broader than a customer database and contact history alone.

This article shows where that boundary lies.

If Excel is used only as a customer list, it may work well enough. But if the same file also contains quotes, discounts, margins, approvals, statuses, and reports, it is no longer just a contact database.

It is a sign that the spreadsheet has started supporting the sales and quoting process — and it is worth checking whether the current tool is still keeping pace with the company.

Łukasz Rompca 
owner of evolabs.dev

Excel Can Be Sufficient as a Customer Database

The fact that a company keeps customer data in Excel is not a problem in itself. If the spreadsheet is used for a simple contact register, it can work well for a long time.

In that case, a few basic pieces of information are enough: company name, contact person, phone number, email address, inquiry source, conversation status, responsible person, and a short note. With a small number of opportunities, this way of working can be completely reasonable.

The problem begins when the spreadsheet stops answering only the question “who is the customer?” and starts answering operational questions:

what quote was prepared?
which version of the quote is current?
does the discount require approval?
is the margin within the agreed assumptions?
has the opportunity been handed over for delivery?
has the data been passed to ERP, accounting, or the project team?
does the sales report show the current state of the process?

At this point, the spreadsheet stops being a supporting list. It becomes the place where the company handles the logic of sales, quoting, and passing data on to the next stage.

Not Sure Whether Excel Is Still Enough?

If several people use the same spreadsheet, data is copied manually, and reports or statuses constantly need to be corrected, it is worth checking whether the problem goes beyond sales itself.

When Does an Excel CRM Become a Quoting Spreadsheet?

In many organizations, the boundary between CRM and quoting gradually becomes blurred.

First, the spreadsheet contains a customer list. Then inquiries are added. Next come conversation statuses. Later there are quote values, discounts, margins, pricing variants, approvers, technical comments, quote validity dates, and information needed for delivery.

After some time, one table supports several different areas:

a customer database,
a sales opportunity register,
a simple pipeline,
quote calculation,
approval of terms,
reporting,
handover of data to the next department.

This is the point where it is worth stopping and reassessing the situation. The company may still need a CRM, but the problem is no longer only about CRM.

An off-the-shelf CRM is good at organizing contacts, activities, conversation history, and a basic pipeline. However, it does not always handle company-specific quoting logic well: calculations, pricing dependencies, exceptions, approval thresholds, quote versioning, or passing data to delivery, production, project teams, accounting, or ERP.

If the spreadsheet contains these elements, it should not be analyzed only as a customer list. It is better understood as a record of the sales and quoting process that needs to be understood properly before selecting a tool.

Do You Have an Excel CRM That Has Grown More Than You Planned?

Show us the spreadsheet your sales team uses. We will check whether an off-the-shelf CRM, automation, a dashboard, or an integration is enough — or whether a dedicated sales and quoting module would be a better direction.

A Status Column in a Spreadsheet Is Often Not Enough

In CRM spreadsheets, the “status” column usually serves a descriptive purpose. It indicates that an opportunity is “new,” “contacted,” “quote sent,” “negotiation,” “won,” or “lost.”

This works as long as the status is only simple information. The problem begins when subsequent actions depend on that status.

Example:

a “needs pricing” status means that the technical department should prepare the data for the quote. A “discount awaiting approval” status means that the quote should not be sent without a manager’s approval. A “won” status means that the data must be passed to delivery, the ERP system, or the team responsible for further customer service.

In Excel, these dependencies are usually handled manually. Someone has to remember to send an email, re-enter the data, mark the opportunity, prepare a report, or check whether the next person completed their task.

In a system, status can be part of the process rather than just a description in a column. It can trigger a notification, prevent a quote from being sent without approval, create a task, record decision history, or pass data to another tool.

This is not simply a matter of having a “nicer CRM.” It is the difference between a table that describes a process and a tool that helps control it.

A Status in Excel Does Nothing by Itself

If you change a spreadsheet status to “awaiting approval,” someone still has to remember to send a message, check the discount, or pass the opportunity on.

In a system, the same change can immediately trigger the next action: a notification, a task, a block on sending the quote, or the transfer of data to another department.

Quoting Often Goes Beyond a Standard CRM

In many companies, Excel’s biggest limitation does not appear at the customer-contact stage, but when preparing a quote.

A standard CRM usually handles the information that a sales opportunity has a specific value quite well. It becomes more difficult when that value is not a simple amount but the result of a more complex calculation.

Examples:

} the price depends on many product or service parameters,

} the quote has several variants,

} the discount depends on the order value, customer type, or delivery date,

} the margin must be checked before the quote is sent,

} selected parts of the quote require technical approval,

} the quote must be prepared in several versions,

} data from the quote must later be passed to delivery without being re-entered.

In such cases, a CRM may still be needed as a customer database and contact-history system, but it may not be sufficient as the tool for handling the entire process.

A dedicated quoting module, calculator, approval workflow, or integration with another system may make more sense than trying to fit everything into a standard CRM.

Do Not Move a Quoting Spreadsheet 1:1 into a New System

If Excel contains calculations, discounts, margins, statuses, and comments, it is not worth simply copying it into an application. First, you need to check which elements should really be part of the system and which are only a consequence of working in a spreadsheet.

A Sales Report Should Not Be a Separate End-of-Week Project

In companies that work with spreadsheets, a sales report is often created only after the data has been organized manually. Someone updates statuses, corrects customer names, removes old opportunities, checks amounts, fills in missing information, and only then prepares a summary for the owner, management board, or sales director.

In this model, the report is not a direct view of the process. It is the result of additional work performed on the data.

The problem is not only the time needed to prepare the report. More importantly, the report depends on the quality of manual processing. If statuses are ambiguous, values are outdated, and some information is stored in emails or separate files, the report reflects the state of the cleaned-up spreadsheet more than the actual state of the process.

Simply connecting a dashboard will not always solve this problem. If the input data is inconsistent, the dashboard will only display inconsistent data faster.

That is why, before automating reporting, it is worth checking where the data comes from, who updates it, which fields affect the report, and whether the report should rely only on the CRM or also on data from quotes, delivery, ERP, the invoicing system, or other sources.

One View Instead of Manually Assembling Reports

In a project for a logistics company, EvoLabs created a system that brought operational data into one place and gave management current access to key information.

This is a good example of a situation where the problem was not the report itself, but manually collecting data from many sources.

An Off-the-Shelf CRM as a Good Solution for the Standard Part of the Process

An off-the-shelf CRM is worth considering when a company primarily needs to organize the standard part of its customer-facing work.

It works particularly well when the main needs include:

a shared customer and contact database,
activity history,
tasks and reminders,
a simple sales pipeline,
assignment of opportunity owners,
basic reports,
recording won and lost opportunities.

In this situation, there is no point in building a dedicated application merely to reproduce functions that are already available in off-the-shelf CRMs. The cost would be too high relative to the problem.

An off-the-shelf CRM can be a very good component of the target ecosystem. However, it is important not to assume that it will solve every problem visible in the spreadsheet.

If Excel also contains quoting logic, calculations, approvals, handover to delivery, or reporting according to custom rules, an off-the-shelf CRM may organize only part of the process. The rest will still require separate spreadsheets, manual exports, or additional workarounds.

CRM, Automation, Dashboard, or Application?

Not every Excel spreadsheet needs to be replaced with a dedicated system. Sometimes an off-the-shelf tool is enough, sometimes automation is enough, and sometimes an application is the right solution.

When Might an Off-the-Shelf CRM Not Be Enough?

An off-the-shelf CRM may be insufficient when the sales spreadsheet supports company-specific elements that cannot be handled conveniently within a standard pipeline.

This applies especially when sales is closely connected with quoting, operations, or internal systems.

Most common signs:

the quote requires a custom calculation,
the discount or margin requires approval,
the quote status triggers tasks for other departments,
after a sale, data must be passed to delivery, the project team, production, or ERP,
reporting requires custom categories and calculation methods,
several departments use the same data at different stages,
the process has exceptions that cannot be handled conveniently with a standard CRM configuration.

In this case, a dedicated solution does not have to replace the entire CRM. A better approach is often a dedicated process layer that handles the part of the work that is specific to the company.

This could be a quoting module, calculator, approval panel, ERP integration, sales-and-operations dashboard, or an application that combines data from several sources.

You Do Not Have to Choose Between a CRM and an Application Immediately

If your sales process currently runs in Excel, start by analyzing the spreadsheet. We will identify what is simply a customer database, what belongs to quoting, where manual work appears, and which data should later flow to delivery, ERP, or reports.

Off-the-Shelf CRM as the Database, Custom Module as the Process Layer

In practice, the best solution is often not a choice between an off-the-shelf CRM and a dedicated application. A hybrid model may be more sensible.

An off-the-shelf CRM can serve as the database for customers, contacts, and activities. A dedicated module can handle company-specific elements: quote calculation, margin approval, preparation of variants, handover of data to delivery, operational reporting, or integration with other tools.

This way, the company does not build standard functionality from scratch, but it also does not try to force its own process logic into a tool that was not designed for it.

Example:

The CRM stores customers, contact persons, and conversation history. A dedicated module handles quote configuration, price calculation, discount approval, and passing approved data to delivery. The dashboard retrieves data from both places and shows not only the value of sales opportunities, but also the status of quotes, approvals, and handovers for further processing.

This approach is often more practical than building a complete CRM from scratch or, conversely, continuing to keep the most important parts of the process in Excel despite implementing an off-the-shelf CRM.

What Should Go into the CRM, and What into a Dedicated Module?

When analyzing a sales spreadsheet, it is worth separating standard CRM data from company-specific logic.

Area	An off-the-shelf CRM is usually enough	Consider a dedicated module
Customers and contacts	Company data, contact persons, activity history	Non-standard relationships between customers, branches, projects, or structures
Sales pipeline	Standard stages, opportunity owner, value, probability	Statuses that trigger approvals, tasks, calculations, or integrations
Quotes	Simple information about the quote value and stage	Quote variants, versioning, configuration, price calculation
Discounts and margins	Informational fields or simple rules	Decision thresholds, blocks, approval workflow, approval history
Reports	Basic pipeline and activities	Custom metrics, data from multiple systems, sales and operational reports
Handover to delivery	Changing the status to “won”	Automatic creation of a project, job, order, or ERP record
Integrations	Standard connections available in the CRM	Custom APIs, non-standard data mapping, complex synchronization rules

This division helps avoid two extremes.

The first is building a dedicated application for functions that an off-the-shelf CRM handles well. The second is implementing a CRM while the most important quoting, approval, and reporting logic still remains in Excel.

How Much Does Keeping Sales in Excel Continue to Cost?

If the team manually updates statuses, corrects quotes, re-enters data into other systems, and prepares sales reports, the company is already bearing a cost — even if the spreadsheet itself appears to be free.

Practical Questions Before Making a Decision

Before choosing a solution, it is worth analyzing the current CRM spreadsheet using several specific questions.

1. Does the spreadsheet contain only contact data, or does it also handle quoting?

If it contains prices, discounts, variants, margins, approvals, or quote versions, the issue goes beyond a simple customer database.

2. Does the status in the spreadsheet only describe the situation, or does it trigger subsequent actions?

If changing a status means that an approval, data handover, report update, or task by another person is required, something more than a standard pipeline may be needed.

3. After a sale is won, does the data need to be re-entered somewhere else?

If so, it is worth checking whether the real problem is the lack of a connection between sales and delivery.

4. Is the sales report created from current data, or only after manually cleaning up the spreadsheet?

If the report requires cleaning every time, the way data is collected needs to be improved, not only the way it is presented.

5. Will an off-the-shelf CRM handle most of the process without workarounds?

If so, it may be a good choice. If a significant part of the process would still have to remain in Excel, it is worth considering a dedicated module.

6. Which elements are standard, and which are genuinely specific to the company?

Contacts, activities, and the basic pipeline are usually standard. Calculations, approvals, handover to delivery, and custom reporting often require an individual approach.

Show Us the Spreadsheet That Currently Acts as Your CRM

You do not need to know whether you need an off-the-shelf CRM, an application, a dashboard, or an integration. You only need to show us your current sales spreadsheet.

We will identify where the company is losing time, where the risk of errors appears, and which solution makes the most business sense.

Summary

A CRM in Excel can be a good solution at the beginning if it serves as a simple list of customers, contacts, and sales opportunities. Not every spreadsheet of this kind requires an application.

However, it is worth looking carefully at the point when the spreadsheet starts containing more: quoting, calculations, discounts, approvals, variants, reports, integrations, or data passed on for further delivery. At that point, the problem is no longer only the customer database. It concerns the sales and quoting process and the flow of information between different areas of the company.

An off-the-shelf CRM can organize the standard part of the work: contacts, activities, pipeline, and basic reports. A dedicated solution makes sense when the company needs to handle its own quoting, approval, calculation, data-handover, or reporting logic.

The best decision should not begin with the question “which CRM should we choose?” It is better to start by analyzing the spreadsheet: which data is standard, which comes from the company’s specific way of working, which activities are performed manually, where errors arise, and which information needs to flow on to other systems or departments.

Only then can you consciously decide whether an organized spreadsheet, an off-the-shelf CRM, a dashboard, an integration, automation, or a dedicated application will be enough.

Let’s Analyze the Spreadsheet That Currently Acts as Your CRM

If your list of customers, quotes, or sales opportunities currently runs in Excel or Google Sheets, it is worth checking whether it is still a supporting spreadsheet or has already become an informal sales and quoting system.

At EvoLabs, we analyze such files from the perspective of data, statuses, quotes, calculations, reports, manual activities, and integrations with other tools. On this basis, it is possible to assess whether the right next step is organizing the spreadsheet, an off-the-shelf CRM, a dashboard, automation, an integration, or a dedicated solution tailored to the company’s way of working.