CRM software: off-the-shelf or built for your business?

For most teams choosing CRM software, the right place to start is an off-the-shelf CRM; if your sales process resembles a standard funnel, packaged products do the job well. If your sales flow has steps peculiar to your sector, customer data arrives from several systems, or the team has quietly stopped using the CRM you bought, a custom CRM — or a custom layer on top of a packaged one — is the better fit.

Below we set out what to look at when making that call. We are a studio that builds custom software. Even so, we often say in first conversations that a packaged CRM will do. The real question is not which software is better, but which one your team will actually use.

What is a CRM for?

A CRM (customer relationship management system) keeps everything about your customers in one place: who wrote, when, and through which channel; which proposal went out; which call took place; what the next step is, and whose job it is.

In a sales team without a CRM, that information is scattered. Some sits in email, some in WhatsApp, some in a spreadsheet and some only in a sales rep’s head. When the rep goes on leave or moves on, the customer relationship goes with them.

A well set-up CRM brings three things:

• Memory. The history with a customer belongs to the company, not to one person.
• Follow-up. Fewer forgotten proposals, uncalled customers and missed opportunities.
• Visibility. A manager can see from reports where sales are getting stuck.

Off-the-shelf CRM versus custom CRM

	Off-the-shelf CRM	CRM built for your business
Getting started	Fast	Needs a development process
Sales flow	You fit the product’s funnel	Designed around your flow
Interface	Feature-rich, sometimes crowded	The screens the team actually uses
Integrations	As far as the product supports	As far as you need
Cost structure	Ongoing per-user subscription	Initial investment plus maintenance
Data	On the vendor’s platform	Entirely yours, if you wish
Changes	Depend on the vendor’s roadmap	Your decision

The great strength of packaged CRMs is maturity. They have been tested for years across thousands of companies, and parts such as email integration, reporting and a mobile app come ready. Their weakness is that they are general. A product made for everyone may fit no one exactly.

Which, and when?

When is an off-the-shelf CRM enough?

• Your sales process follows a familiar line: lead, meeting, proposal, won or lost.
• Customer contact runs mostly through email and phone.
• Your team is small and your processes have not yet settled; you want to bring some order first.
• Your reporting needs are basic: how many proposals, how many won, who did what.

In that case, starting with a packaged CRM is both quick and instructive. As you use it, you learn what really matters to you. If you later want a custom system, that experience becomes its most valuable input.

When do you need a custom CRM?

The signs we see most often:

• The team doesn’t use the CRM. One was bought, but sales still run on spreadsheets and messages. The usual reason is that the product’s flow does not match how the team really works.
• There are sector-specific steps. A site survey, sending samples, technical sign-off, contract and installation — each the responsibility of different people.
• Data comes from many places. The web form, WhatsApp, Instagram, a dealer portal, the phone system. All of it needs to meet in a single customer record.
• The CRM must talk to other systems. An accepted proposal opening a record in accounting, an order dropping into the production plan, a service request being assigned to the technical team.
• Cost rises with headcount. Per-user pricing means part of the team never gets access to the CRM at all.
• Data ownership matters. Customer data has to be kept on your own server or in a particular country.

We set out the general decision framework in six questions in off-the-shelf or custom software; the same questions apply to a CRM.

A third way: a packaged CRM plus a custom layer

It does not have to be all packaged or all custom. For many companies the most balanced answer is to keep a packaged CRM at the centre and add custom pieces around it:

• An integration that brings data into the CRM from the messaging channels you actually use.
• A custom interface that simplifies the handful of screens the team uses every day.
• A service that carries CRM data across to the accounting or production system.

These connections are usually built through the CRM’s API and webhooks — the means by which one system lets another talk to it, or tells it when something has happened. The advantage is meeting your own needs without giving up the CRM’s mature parts. The drawback is that both sides need looking after: when the CRM vendor changes something, the connection has to be checked too.

Messaging channels and the CRM

For many businesses — in Türkiye especially — customer conversations happen on WhatsApp and Instagram far more than over email. That bears directly on the CRM decision. If messages never reach the CRM, the CRM sees only part of your sales.

The Meta Cty platform we built is not a CRM; it is a SaaS product that gathers WhatsApp and Instagram conversations into one panel and automates sales flows. But it grew out of the same problem: messages flowing across separate screens, conversations getting lost and opportunities that nobody could follow. Bringing the channels into one panel is often the first step to take before moving to a CRM. For the rules on the WhatsApp side, see WhatsApp Business API sales automation.

A concrete example: an industrial equipment supplier

Picture a company selling machinery and spare parts. Its sales process runs like this: an enquiry comes in, the field team goes out for a site survey, the technical team confirms suitability, a proposal is prepared, a contract is signed, installation is scheduled — and then years of maintenance and spare-part sales follow.

The company has bought a packaged CRM. But the product’s funnel ends at “proposal, won”. There is nowhere for the survey and technical sign-off steps, and the relationship after installation does not appear at all. So the team keeps survey notes in a spreadsheet and only enters things in the CRM at the proposal stage.

There are two routes here. Either custom fields and an installation-and-maintenance module are added to the packaged CRM, or a custom system is built that shows sales and after-sales in a single flow. Which is right depends on how deep the differing steps go and how many systems need to be connected. In a first conversation we draw these steps out together and make the decision from there.

A checklist before you decide

1. Map your sales flow. Which steps does a customer pass through, from first contact to sale? Who is responsible at each one?
2. List your channels. Where do customers reach you from? Which is busiest?
3. Write down the systems to connect. Accounting, invoicing, orders, service, calendar.
4. Count users and roles. Who should see what, and who may change what?
5. Describe the reports. Which question are you trying to answer each week?
6. Make the data decision. Where should customer data live? Will the data in your current spreadsheets be migrated?
7. Work out the total cost. For a packaged CRM, the ongoing per-user fee; for a custom CRM, the initial investment and monthly maintenance. Compare both over the same period.

This list also largely sets the cost and timeline of a custom CRM: the number of steps and roles, the systems to integrate, the volume and cleanliness of the data to migrate, and the complexity of the reports.

Frequently asked questions

Does a small business need a CRM?

Yes, once the customer list grows and more than one person is talking to customers. At the start, even a well-kept spreadsheet works; but when you need follow-ups and reminders, moving to a CRM saves time. We have gathered other automation opportunities for small businesses in automation for small businesses.

Can our existing customer data move into a new CRM?

Yes. Data in spreadsheets or an old system can be carried into the new structure. Cleaning the data and merging duplicate records beforehand matters — otherwise the mess simply moves into the new system.

Will we own the source code of a custom CRM?

If you wish, the source code is handed over to you at delivery. The system can run in the cloud or on your own server, under your own domain.

Can a custom CRM grow later?

Yes. When the architecture is designed for growth from the start, new modules, roles and integrations can be added later. Our advice is to begin with the part that will take the most workload off the team, and grow it piece by piece.

We can look together at whether a packaged CRM, a custom system or a mix of the two suits your sales flow. See our custom software and SaaS page, or write to us with a short description of how you work today.