Excel, CRM or custom system for tracking quotes: how to choose

A spreadsheet is enough while one person handles a few requests a week. A generic CRM works when several people need to see the same record. A custom system only makes sense when the company's process has rules that off-the-shelf tools cannot meet. The best choice is the simplest one that leaves no request stalled.

Anyone running a company that lives from quote requests ends up asking: do I stay with the sheet, buy a CRM or have something made to measure? There is no single right answer. There are questions that help you see where your company stands. In every case, the goal is the same: each request has an owner, a deadline and the date of the next contact, until there is an answer. That is what we call follow-up.

Five questions to decide

  1. How many requests arrive each week? As a rule of thumb, up to a dozen, one person can track them with a sheet. Above that, the effort of keeping the sheet current starts to weigh.
  2. How many people touch the requests? If it is one, the sheet is enough. If it is three or four, all needing to see and update the same record, start looking at a CRM.
  3. Do requests arrive through one channel or several? Email, phone, WhatsApp and a form together call for a place that collects them, or a lot of discipline.
  4. Do contact dates pass unnoticed? If so, you lack a tool that alerts.
  5. Does your process have its own rules? Internal approvals, deadlines by customer type, specific documents? If ready-made tools cannot follow this without much effort, look at something made to measure.

When Excel is enough

A shared spreadsheet is a good start and, in many cases, all you need. It is enough when:

  • requests are few and one person tracks them;
  • the record is made the same day, with the same fields;
  • someone looks at the sheet once a week and acts on overdue dates.

The advantage is cost and flexibility: you change a column in two minutes. The limit is discipline. The sheet alerts nobody, does not stop two people editing the same row and does not know a deadline has passed. If it works, do not swap it just because «it is time to have a CRM».

When a generic CRM works

A CRM is, at heart, a sheet with alerts, history and several users. It usually works when:

  • more than two or three people handle requests;
  • you want to see, without asking anyone, which requests are stalled;
  • you need reminders and a conversation history per customer.

The hidden costs are set-up and habit. A CRM with dozens of features the team does not use ends up as empty as a forgotten sheet. Choose one that fits your process, configure only the statuses you use and start with a small group. To understand what a CRM is, see what is a CRM and when an SME needs one.

When a custom system makes sense

A custom system, or a custom set-up on top of tools the company already uses, is justified when ready-made tools do not follow the process. For example:

  • requests arrive through several channels and should enter the record on their own;
  • there are own rules for owner, deadline and reminder by type of request;
  • the owner wants a single view of what is stalled, without asking for reports;
  • the company has already tried a sheet and a CRM and keeps losing requests for lack of a discipline nobody can sustain.

The risk here is paying for something bigger than needed. Always ask for a small, defined scope, and for the system and data to sit in your own accounts, so you can use it without depending on whoever built it. TMI works in this space, after understanding the process; if you want to compare with your situation, the stalled requests guide helps you measure the problem before deciding.

What does not change with the tool

Any of the three fails if the essentials are missing: an owner per request, a deadline to reply, contact dates set and a rule for when to stop. Without those, a custom system stands as still as a sheet. With them, a well-used sheet beats an expensive, badly used system. The full method is in how to follow up on quote requests.

How to switch without losing data

  • Start with simple columns and statuses that export easily to another place.
  • Keep the same statuses when changing tool, so the team does not have to relearn the process.
  • Import only open requests, not the whole history.
  • For two weeks, use both tools side by side and confirm nothing was lost.

In short

  • A spreadsheet is enough with few requests and one person tracking them.
  • A generic CRM works when several people need the same record, alerts and history.
  • A custom system is justified when the process has rules that ready-made tools cannot meet.
  • Owner, deadline and contact dates matter more than the tool you pick.

Quick questions

Can I start in Excel and move to a CRM later?

Yes, and it is a good path. Use simple columns and statuses that export easily, and keep them the same when you change tool.

Is a free CRM enough?

It can work to start, especially with few users. Check the limits on users, reminders and data export before putting your history in it.

What should I ask someone proposing a custom system?

Ask what gets installed, what it does not do, how much it costs to maintain and whether the system and data sit in your own accounts, so you can use it without depending on the supplier.

Want to see which level suits you?

The price of the quote is still decided by a person. What can be automated is the arrival of the request, the owner, the deadline and the reminders. You can start by doing the maths in the stalled requests calculator.

Prefer to talk? Book an exploratory call

Share on LinkedIn Share on WhatsApp Send by email