What is expected from CRM in B2B?
CRM—customer relationship management—software keeps customer information in one place: who was contacted, which quote was given, the stage of each opportunity, and what happens next. In B2B, this differs from B2C in four ways:
- Account and branch hierarchy. The customer is a company with branches, regional offices, and separate account records rather than one person.
- Multiple decision-makers. Procurement, technical teams, and finance play different roles in the same opportunity; the sales cycle lasts weeks or months.
- Quotes and approvals. Quotes develop through revisions; a discount above a set threshold requires manager approval.
- Contract pricing and dealers. Prices are specific to the customer, dealer group, or contract rather than a standard list price, and are often held in the ERP.
How much of this an off-the-shelf product covers determines much of the decision. We explain a framework applicable to all software types in our guide comparing off-the-shelf and custom software; here we focus on CRM-specific questions.
When is off-the-shelf CRM enough?
If the following conditions apply, start with an off-the-shelf CRM and leave custom development aside for now:
- Your sales process is a standard funnel. Lead, meeting, quotation, won or lost. Off-the-shelf products are designed for precisely this flow.
- Users are internal. The sales and customer service teams use the CRM; dealers and customers do not log in.
- Integration needs are limited. Existing connectors for email, calendars, and accounting are sufficient; only account and invoice data are read from the ERP.
- You need to start quickly. An off-the-shelf CRM can be set up quickly; the sales team stays in Excel while waiting for custom development.
- You do not yet know what you need. Working on a free or lower-tier plan for a few months is the least expensive way to learn what you actually need.
The sign that you have reached the limits of an off-the-shelf CRM is not the product itself but the workarounds accumulating around it: lists exported to Excel, approvals circulating by email, and quotes re-entered manually into the ERP.
When does custom CRM make sense?
Custom CRM makes sense when something other than ordinary sales tracking is being done under the CRM label. Five signals:
- The CRM is really an ordering or dealer process. If representatives mainly enter orders on dealers' behalf and check balances rather than track opportunities, the need is an ordering system.
- Quotes are tightly tied to the ERP. Prices, stock, credit limits, or production capacity must be read from the ERP for each quote; approval rules are specific to your company.
- There are many field users. Service technicians or field salespeople need a mobile app that works offline and allows fast entry; per-user licensing grows quickly at this scale.
- The data model is unusual. The central entity is a contract, device, maintenance interval, or project rather than an opportunity; everything in the off-the-shelf product is built through custom fields and temporary links.
- External users will access the system. Dealers or customers need to see their own records, but implementing this through the CRM's portal licenses is costly or restrictive.
The trade-off is clear: the initial investment is higher, maintenance is your responsibility, and features included in off-the-shelf products—funnels, email tracking, and reports—must also be built. A fully custom CRM should therefore rarely be the first option.
The middle ground: off-the-shelf CRM and a custom layer
In B2B, this is often the first approach to consider. The sales team stays in an off-the-shelf CRM; the distinctive part of the business—a quote and approval module, service work-order app, or dealer portal—is built alongside it and connected to both CRM and ERP. The rule is simple: do not rewrite what the CRM already does well; build the custom layer only for the process that does not fit.
For example, in the Dealer Ordering Platform product concept the sales team's visit and target dashboard and the dealer's ordering app are separate interfaces; X Dağıtım in the concept is fictitious. The scope, process, and delivery conditions for such a layer are described on our custom software development service page.
| Criterion | Off-the-shelf CRM | Off-the-shelf CRM + custom layer | Custom CRM |
|---|---|---|---|
| Suitable work | Standard sales funnel | Standard sales plus a company-specific process | A process centered on an unusual data model |
| Cost structure | Ongoing per-user licensing | Internal user licenses + development and maintenance of the layer | Development + hosting and maintenance |
| Field and external users | Limited by the product's mobile app and portal licenses | A separate app or portal designed for them | Designed to fit requirements |
| ERP connection | Within the limits of the existing connector and API | The layer connects to the ERP at the required depth | Connects at the required depth |
| Outflow | Depends on export coverage | With a decoupled connection, the layer remains even if the CRM changes | Code and data handover depends on the contract |
CRM versus ERP: where should quotes and orders live?
In brief, CRM manages the relationship before a sale, while ERP manages transactions after it. Contacts, opportunities, conversations, and quotes live in the CRM; stock, orders, dispatch, invoices, and accounts live in the ERP. The difficulty lies in the quote–order–dispatch flow between them. A sound split is:
- Quotes are prepared in CRM, but prices, stock, and credit limits are read from the ERP; prices are not entered manually in the quote.
- Once a quote is accepted, the order is created in the ERP. The ERP holds the master record; CRM displays the order number and status.
- Dispatch, invoicing, and collection remain in the ERP. e-Invoice and e-Archive documents are issued through the ERP or an authorized service provider; CRM displays these documents rather than generating them.
- Approval rules are defined in one place. If tiered discount approvals and contract pricing are complex, consolidate them in a quotation module rather than scattering them across CRM custom fields: either the CRM's configure-price-quote (CPQ) extension or a custom layer.
What is CRM integration, and what needs attention?
CRM integration means automatically sharing data between CRM and systems such as ERP, email, or a portal according to defined rules. A single master source for each data type sits at the heart of the plan: account records originate in ERP; contacts and opportunities in CRM. A field editable in both systems eventually holds two different values. The table showing which data flows in which direction and how often is in our step-by-step ERP integration planning guide.
How do you compare licensing and development costs?
The first-year bill can mislead: licenses recur every year, while development investment is concentrated upfront. Calculate both options over the same 3- and 5-year periods:
- Off-the-shelf CRM: user count × monthly per-user license × 12 × years + extensions + setup and customization + integration + training.
- Custom CRM or custom layer: discovery, design, and development + hosting + annual maintenance and minor improvements + integration + training.
Record the currency, price-check date, whether VAT is included, and user counts by year for each line. If licensing is priced in foreign currency, note exchange-rate assumptions and contractual price-increase conditions too.
Hypothetical example: a manufacturer with a service team
Consider a manufacturer that sells and services industrial equipment: a 10-person sales team, 35 service technicians, and corporate customers with maintenance contracts. Expressing the three options with the same formula clarifies the decision:
- A. Everyone in off-the-shelf CRM: 45 users × (license + field service extension) × 12 × 5 + customization. Cost grows linearly with technician count.
- B. Off-the-shelf CRM and a custom service app: 10 users × license × 12 × 5 + service app development and 5 years of maintenance + CRM and ERP integration.
- C. Fully custom CRM: The funnels and reports the sales team would find in an off-the-shelf product must also be built; without a distinctive need to justify it, this is the most expensive route.
In this scenario, the decision is often between A and B, determined by two questions: does technicians' work, including offline use, fit the product's work-order model, and how many technicians will there be in five years? Compare offline task recording, conflict handling, and on-device data decisions with the enterprise mobile app scope. Fill the figures using your own quotes, not general averages.
Moving from Excel to CRM, data migration, and adoption
Whichever route you choose, data is often the longest part of the transition. Before moving the customer list from Excel:
- Deduplicate. Merge different spellings of the same company using its tax number, and connect branches to the parent company.
- Choose the master source. If account data exists in the ERP, feed it into CRM from the ERP rather than Excel; use Excel only for contacts and conversation information absent from the ERP.
- Simplify and test. Do not migrate columns nobody fills in; move a small sample first and check record counts with the sales team.
- Remember personal data and permissions. Names, phone numbers, and email addresses are personal data; assess the hosting country under KVKK from the start. If you plan promotional email or SMS, assess recipient type, message purpose, consent, and opt-out records under the Message Management System (İYS) and current legislation with your legal adviser. Having a contact address in CRM does not imply permission to send messages for every purpose.
- Secure an exit from the start. For off-the-shelf CRM, obtain written confirmation that all records can be exported with attachments and relationships, and how long access lasts after the contract ends. For custom CRM, the contract should assign source code, database, and hosting accounts in your name.
A CRM is only as valuable as the freshness of its data; if salespeople see recordkeeping as extra work, data soon becomes stale. To encourage adoption, minimize required fields, enable email and calendar connections on day one, use CRM reports in meetings, and start with a pilot team.
How do you choose CRM? 10 questions for a trial
Every CRM looks smooth in a demonstration; differences emerge in your exceptions. Trial it using a slice of your own data rather than sample data.
Trial checklist
- Can your parent company, branch, and account structure be represented without distortion?
- Does your most complex quote—contract pricing, tiered discounts, approval—fit the product?
- How, and with what delay, are prices, stock, and credit limits read from the ERP?
- Can an accepted quote become an order without manual entry into the ERP?
- Can field users enter records while offline?
- How, and under which license, do external users such as dealers or customers gain access?
- Which license tier enables the API, and what are its call limits?
- In what format can all data be exported, including attachments and relationships?
- Which country hosts the data, and how are İYS records managed?
- At your projected user counts in years 3 and 5, what are total licensing costs and price-increase conditions?
If two of the first six answers are “no,” consider the middle ground before abandoning the product: resolving the ill-fitting part in a custom layer preserves the rest of the CRM.
We can also answer these questions together for your own processes in an initial conversation.