Book a Call
CRM and Internal Tools

Spreadsheet, off-the-shelf platform or custom CRM? A practical guide to the signs it is time to change, what each option suits, and how to decide without overspending.

Comparison of a spreadsheet, an off-the-shelf platform and a custom CRM built around a sales and delivery pipeline

Every business has a way of tracking leads, clients and follow-ups. Sometimes it is a spreadsheet, sometimes a popular CRM platform, sometimes a mix of both plus a lot of memory. You almost certainly need a CRM of some kind. The real question is which kind, and when a custom CRM is worth building instead of buying.

The short answer: a custom CRM is a customer and pipeline system built around your own process instead of a standard sales funnel. A small business usually needs one when its work does not fit the pipeline model, sales and delivery live in separate tools, or per-user fees and workarounds keep growing faster than the value. If a standard CRM fits your process with light setup, keep it.

This guide walks through the three realistic options, the signs that you have outgrown your current setup, and a simple way to decide.

The three options, honestly compared

A CRM (customer relationship management system) is where you keep track of who your customers and prospects are, what you have discussed with them and what happens next. You can get there three ways:

  • A spreadsheet or shared document. Free, flexible and familiar. Fine for a small team with a simple sales process.
  • An off-the-shelf CRM such as HubSpot, Pipedrive, Salesforce or Zoho. Quick to start, full of features, priced per user. Fits businesses whose process looks like the vendor's idea of sales.
  • A custom CRM, built around how your business actually wins and serves customers. More upfront work, but it fits your process, your data and your other systems.

None of these is the right answer for everyone. Plenty of businesses should stay on a well-configured platform for years. The aim is to spot when the tool is shaping your process instead of the other way round.

When a spreadsheet stops working

Spreadsheets fail gradually. Nobody decides to stop trusting them; it just happens. Common signs:

  • Several versions exist, and people argue about which is current.
  • Follow-ups are missed because nothing reminds anyone.
  • You cannot see the history of a client without asking the person who handled them.
  • Columns have been added for every new idea, and half are empty.
  • Access control is all or nothing, so everyone can see and edit everything.

At this point the next step is usually an off-the-shelf CRM, not a custom build. Moving to a proper system also means cleaning and structuring the data, which we cover in moving from spreadsheets to a proper system.

When an off-the-shelf CRM is the right choice

Popular platforms are good products. They make sense when:

  • Your sales process is a fairly standard pipeline: lead, qualified, proposal, won or lost.
  • You want email tracking, marketing tools and reporting without building anything.
  • Your team is small enough that per-user pricing stays reasonable.
  • Your other tools already have good built-in connections to it.

Spend time configuring it properly before deciding it does not fit. Many frustrations come from default setups that nobody tailored: unused fields, unclear stages and no agreed rules for data entry.

Signs your business needs a custom CRM

A custom CRM becomes worth considering when the gap between your process and the platform keeps costing time. Look for these patterns:

01

Your process does not fit the pipeline model

You sell through tenders, multi-stage approvals, referral partners, recurring contracts or projects with several decision makers. The platform forces everything into one funnel, so people track the real status somewhere else.

02

Sales and delivery live in different worlds

Once a deal is won, the work moves into another tool or spreadsheet. Account managers cannot see delivery status, and delivery teams cannot see what was promised. A custom CRM can cover the whole client lifecycle, not just the sale.

03

Workarounds have become the system

Custom fields, tags and notes are being used to hold information the platform was never designed for. Reports need exporting and fixing by hand before anyone trusts them.

04

Integrations are fragile or missing

You need the CRM to talk to an industry system, a booking tool or your own database, and the platform either cannot or needs a chain of add-ons. See our guide to how software integrations connect business systems for what is involved.

05

Costs grow faster than value

You pay for higher tiers to get one or two features, or per-user fees climb as you add staff who only need to see a few records. Look at the full cost over several years, not only this year.

06

You need control over your data

Client data has specific handling requirements, or you want it held in your own systems, with your own access rules and audit history.

What a custom CRM usually includes

A custom CRM does not need to copy every feature of a large platform. The best ones are focused. A typical first version might include:

  • Contacts and companies with the fields your business actually uses.
  • A pipeline or workflow with your real stages and rules for moving between them.
  • Tasks and reminders tied to clients, so follow-ups are not left to memory.
  • Activity history: calls, emails, notes and documents in one timeline.
  • Role-based access, so each team sees what it needs.
  • Connections to accounting, your website forms and your delivery tools.
  • Reports and a simple dashboard built around the questions you ask each week.

AI can add real value here too: summarizing long email threads into the client record, drafting follow-up messages for a person to review, or flagging deals that have gone quiet. These features are easier to shape when you control the system. Our CRM and internal tools work usually starts with a small version like this and grows from there.

Custom CRM examples by type of business

What "custom" means depends on how the business makes money. A few patterns we see often:

  • Agencies: one record per client that holds the deal, the retainer, the projects and the monthly report, so account managers stop jumping between a CRM, a project tool and a spreadsheet.
  • Property management: owners, properties, tenants and maintenance requests linked together, with updates owners can see without calling the office.
  • Field and trade services: leads that turn into quotes, quotes that turn into scheduled jobs, and jobs that turn into invoices, all in one flow.
  • Professional services: client intake, document collection and engagement tracking, often joined to a client portal.

Many of these also benefit from small AI steps, such as turning call notes into CRM updates. Our guide on where to start with AI automation explains how to add that safely.

How to decide: a short checklist

Before committing to a build, work through these questions with the people who will use the system every day.

  1. Write down your real sales and client process, step by step, including the awkward exceptions.
  2. Mark where your current tool fits well and where people use workarounds.
  3. Try configuring a platform to cover the gaps. Run a trial with real data if you can.
  4. Estimate the ongoing cost of the platform route, including add-ons, integration tools and admin time.
  5. Ask who will own a custom system after launch: hosting, updates, support and new features.
  6. Decide what the first version must do, and what can wait.

If the platform covers most of your needs after proper setup, stay with it. If the gaps are in the core of how you make money, a custom CRM, or a custom layer around a platform, is worth a serious look. Our broader guide on why growing businesses outgrow ready-made software covers the same decision for other systems.

Questions to ask before anyone builds it

If you speak to a developer or agency about a custom CRM, these questions will tell you a lot about how they work:

  • How will you learn our process before designing screens? Who from our team needs to be involved?
  • What will the first usable version include, and what is deliberately left for later?
  • How will our existing data be cleaned, matched and imported, and how will we check it?
  • Which systems will it connect to on day one, and how are failed syncs handled?
  • Who hosts it, who is responsible for security updates and backups, and how do we get support?
  • Do we own the code and data outright? Could another team take it over if needed?
  • How will staff be trained, and how will you collect feedback in the first weeks after launch?

Good answers are specific and mention your people, not only technology. Vague answers about features usually mean the process has not been understood yet.

Mistakes to avoid

  • Building everything at once. Start with the part of the process that hurts most, launch it, then extend it.
  • Skipping the users. A CRM that managers like but salespeople avoid will be empty within months. Involve the people entering the data.
  • Migrating messy data. Deduplicate and agree field definitions before importing. Our data migration team treats this as a project in its own right.
  • Forgetting ownership. Make sure you own the code and the data, and that the system is documented.
  • Ignoring design. Speed and clarity of the screens decide whether people keep using it.

Frequently asked questions

What is a custom CRM?

A custom CRM is a customer management system designed around your own sales and client processes, data and integrations, rather than a general platform configured to fit.

Is a custom CRM better than HubSpot or Pipedrive?

Not automatically. Platforms suit standard sales pipelines well. A custom CRM is better when your process, integrations or data needs do not fit the platform without constant workarounds. We compare the two side by side in custom CRM vs HubSpot.

Can we keep our existing CRM and add custom parts?

Often, yes. A custom layer can sit around a platform, adding screens, workflows or integrations it lacks, while the platform keeps doing what it does well.

Can we move our data from spreadsheets or another CRM?

Yes. Contacts, companies, deals and history can usually be migrated. Plan time to clean duplicates and agree field definitions first, so the new system starts with data people trust.

Who owns a custom CRM once it is built?

You should. Make sure your agreement gives you ownership of the code and data, along with documentation and access to the hosting.

A sensible next step

Map your process on one page and mark every point where people leave the CRM to get work done. If those points are few, improve your configuration. If they are the heart of your business, it is time to look at a custom CRM.

We are happy to look at your current setup and give an honest view of which route fits, including when the answer is to stay where you are.