Short answer: for most SMEs a ready-made CRM is the first place to look; a custom CRM makes sense only when no ready-made product can cover your data model or process
There are three ways to choose a CRM: buy a ready-made (cloud) CRM, use your ERP's own CRM module, or have a custom CRM built. The right path does not depend on your team's size but on three questions: is your sales process standard, is the customer account in the ERP the real source of customer data, and do you have the resources to keep a software team going for a long time?
This article compares the three on cost items, flexibility and risk. In the cost table we give no lira figures: prices depend on the product, the number of users, the exchange rate and the contract, and an invented number would mislead you. Instead we show, for each option, which items you need to calculate.
The three options at a glance
| Criterion | Ready-made CRM | ERP-linked CRM | Custom CRM |
|---|---|---|---|
| Time to start | Days to weeks | Quick if your ERP has a CRM module; otherwise a module purchase and setup | Months (sourced range below) |
| Flexibility | Configuration, no code; the vendor sets the limits | As far as the ERP goes | Unlimited, but you carry every constraint |
| Customer data | Usually on the vendor's servers | In the same place as the ERP | Where you choose |
| Link to the ERP | Needs a connector or integration | Natural: same customer account | A link you define by design |
| Ongoing load | Per-user licences, add-ons, an administrator | ERP licence and maintenance | A development team, hosting, security, releases |
| Ease of exit | As far as you can export data | Tied to the ERP | You own the code and data |
This table is our own summary, not a standard.
Ready-made CRM: when is it the best choice?
According to Rework's comparison of off-the-shelf, low-code and custom CRM, a ready-made CRM reaches first value in days to weeks, while a custom build takes 6 to 18 months and needs 2 to 5 full-time engineers on an ongoing basis. The same source recommends buying if you need a working pipeline in under 60 days or have fewer than three engineers for internal tooling, and says most growing B2B companies land on a well-configured off-the-shelf CRM. This is a software company's guide, so it is an opinion; but the criteria it uses (time, engineer count, flexibility) are worth testing against your own situation.
Typical risks of a ready-made CRM:
- Over-customization. Oracle's implementation guide says over-customization is one of the most common reasons CRM implementations go over budget and miss deadlines, and that customizations are often the most costly and time-consuming part; it adds that choosing an application that meets your requirements natively can dramatically lower total cost of ownership. This is a CRM vendor's view, but the conclusion is sensible: it is cheaper to fit your process to what the product does than to bend the product to your process.
- Per-user licences. Cost rises linearly as the team grows, and add-ons come on top (Rework notes that seat fees compound and add-ons add up).
- Where is the data? Customer data sits on the vendor's infrastructure; we look at the personal data consequences below.
ERP-linked CRM: who owns the customer account?
If your ERP already holds the customer account, orders, invoices and collections, the most critical input to a CRM lives there. You then have two paths: use the ERP's CRM module, or integrate a standalone CRM with the ERP. Our assessment:
- The ERP's CRM module: the same customer account, one data owner, no integration to maintain. In return, the usability a sales team needs (mobile, quick notes, task tracking) may not be as good as in a standalone CRM. Check in the demo whether a sales rep could really use it; a screen only the accounting team likes is not enough.
- Standalone CRM plus ERP integration: the sales team gets a better interface, but customer records now exist in two places. If it is not written down which one is the "master", duplicate customers and mismatched phone numbers and addresses are unavoidable. We described integration approaches in our dealer portal and ERP integration article; the same logic applies to a CRM.
Before deciding, fill in this table (a data ownership table, as a suggestion):
| Data | Master source | CRM's role |
|---|---|---|
| Company name, tax number, address | ERP (customer account) | Reads, sends a change request if needed |
| Contacts, meeting notes | CRM | It is the master |
| Quote and opportunity | CRM | Passes to the ERP as an order |
| Order, invoice, collection | ERP | Reads, shows on the customer record |
| Price list, discount | ERP | Reads, applies in the quote |
Custom CRM: when is it worth it and when is it a burden?
A custom CRM mirrors your data model and processes exactly, and you set up the link to the ERP and other systems as you want at design time. According to a custom software firm's article, SaaS CRMs impose API limits, data volume constraints and integration patterns designed for average use, which can turn into structural limits at high transaction volumes (Pretius). That is the view of a firm that sells custom software; do not read it as a factual claim of superiority, but as a hypothesis to test in your own case.
The real burden of a custom CRM is ongoing maintenance: Rework foresees 2 to 5 engineers continuously and 6 to 18 months to first value for a custom build, and suggests that if you have a workflow that is truly a competitive edge, you build only that differentiating layer and buy the commodity layer. Itransition says the total investment in a custom CRM typically runs into hundreds of thousands of dollars, and for platform-based solutions an implementation budget starts at $10,000 for smaller projects. These are a foreign software firm's estimates in dollars; offers in Turkey will differ, so read the figures only as an order of magnitude.
When a custom CRM fits:
- Your data model does not fit any ready-made product (for example a nested relationship between projects, dealers, product families and users).
- There are constraints on data location or access rules that a ready-made product cannot meet.
- The sales process itself is your competitive edge and keeps evolving.
- You have the resources to sustain a team for a long time, or a partner under a maintenance contract.
If none of these apply, choose the ready-made product or the ERP module. We covered this decision framework in our off-the-shelf vs custom software decision matrix and the contract side in our software development contract article. There is also a middle way: buy a ready-made CRM and have only the missing piece built as a custom integration or a small application. Rework recommends that if deep integration with a proprietary internal system is needed, you start with an off-the-shelf CRM plus a custom integration layer, and move to a custom build only if the integrations fail.
The items in a three-year cost
Without giving a number, these are the items you should calculate for each option over 3 years:
| Item | Ready-made CRM | ERP-linked CRM | Custom CRM |
|---|---|---|---|
| Licence / development | Users × monthly fee × 36 months | Module licence (if any) | Development fee (analysis, design, coding, testing) |
| Setup / adaptation | Configuration and data migration | Configuration and data migration | Included, but continues across releases |
| Integration | Connector with the ERP and other systems | None or low | By design, but maintenance is yours |
| Training | Per user | Per user | Per user plus documentation |
| Annual maintenance / administration | Administrator time, add-ons | ERP maintenance fee | Hosting, security updates, bug fixes |
| Exit / migration | Exporting data | If the ERP changes, so does the CRM | Migration to a new system |
Use this table to compare offers: ask each vendor for every row in writing. We described how to calculate the total cost of an ERP in our 5-year cost article; the same method works for a CRM.
KVKK: responsibility for customer data stays with you
A CRM holds personal data of customers and prospects. The Personal Data Protection Authority's Personal Data Security Guide reminds that under the second paragraph of Article 12 of the Law, data processors are jointly responsible with the data controller for data security; the guide also says a written contract must be made with the data processor and that the processor may act only on the controller's instructions. In a ready-made cloud CRM the vendor is the data processor: your contract should make visible the data security obligations, where the data is stored, the right to deletion and export, and any sub-processors. Where services are hosted abroad, transfer rules are assessed separately; get an opinion from a legal adviser. This article is not legal advice.
Demo-day checklist
- ☐ Watch a sales rep enter a new meeting note from a phone
- ☐ Change the same customer in the ERP and the CRM: which wins, and how is the conflict resolved?
- ☐ Turn a quote into an order: how does it flow into the ERP, and where is the price list applied?
- ☐ Export all customer data: in what format, and how fast?
- ☐ Double the number of users: how does the price change?
- ☐ Add a field from the admin panel: does it need no code?
- ☐ Ask for the data processing agreement and where the data is held, in writing
- ☐ Remove a user from the system: what happens to their records and access?
Frequently asked questions
Is Excel enough instead of a CRM for a small team?
For a few customers and one sales rep it can be. As the number of customers, opportunities and follow-ups grows, several people use the same file and past conversations need to be searched, Excel becomes unreliable. For the logic of moving off it, see our 90-day Excel-to-ERP plan.
Our ERP has a CRM module; do we still need a separate CRM?
First check whether the sales team can really use the module. If they can, a separate CRM creating a second customer record is an unnecessary cost. If they cannot, it is healthier to link a separate CRM through an integration that treats the ERP as the master source.
How long does a custom CRM take?
It depends on scope. Rework foresees 6 to 18 months to first value for a custom build; starting with a small core and expanding in stages shortens that. To estimate a duration we need the scope, the number of users and the integration list; an estimate can only be given with those.
After choosing a ready-made CRM, is custom development still needed?
Often only for small pieces: an integration, a report or a workflow. Keep Oracle's warning in mind: over-customization is what most often pushes projects over budget and schedule. If needed, having a custom piece built as a separate small job through our custom software development service is healthier than changing the product from the ground up.
If you want to assess CRM, ERP and custom software options together against your process, see our custom software development service or get in touch.
Sources: CRM Build vs Buy: How to Decide (Rework), CRM Implementation (Oracle), Customer Relationship Management (CRM) Implementation Guide (Itransition), Custom CRM vs Salesforce cost (Pretius), Kişisel Veri Güvenliği Rehberi, Teknik ve İdari Tedbirler (Personal Data Protection Authority, April 2025)