Custom CRM vs Salesforce: Configure, Extend or Build?
On this page
Start by evaluating Salesforce when the main need is to manage customers, opportunities and a sales team's activity. Consider extending or connecting it when the gap is a specific operational handoff. A custom CRM becomes a stronger candidate when essential workflows remain difficult after that assessment and the business can fund both development and ongoing ownership.
Compare the cost and practicality of the same workflow, including its exceptions. This fictional distributor assessment draws on public documentation checked on 7 October 2026; the workflow has not been tested in a Salesforce sandbox.
Compare the same job
Assume 25 internal users across two sales regions. A salesperson creates a customer and quote; discounts above an agreed threshold need approval. An accepted quote becomes an order in the existing ERP. The warehouse can ship six of ten units now and four later. Sales needs the remaining quantity and an exception owner without re-entering the order.
The ERP remains authoritative for stock and shipments. Accounting remains in the existing accounting system. A customer portal is optional and separately scoped. Apply these boundaries to both proposals so that scope and cost remain comparable.
Compare nine workflow requirements
The matrix separates documented configuration options, proposed development and requirements still to scope. An unknown needs investigation; it does not establish that Salesforce lacks the capability. Validate every requirement in the quoted edition and environment.
The custom column describes work to build and accept. Under each requirement, the acceptance row specifies the result to demonstrate for both options; documentation alone does not establish that the workflow passes.
| Salesforce: path to assess | Custom CRM: proposed development |
|---|---|
| Customers and sales pipeline | |
| Configuration Map accounts, contacts and opportunities to the sales process. Sales features | Build customer records, stages, activity history and search. |
Acceptance criterion Create a customer, move a deal and find its history. | |
| Discount approval | |
| Configuration Assess an approval process against the required threshold and approver rules. Approval processes | Build approval states, permissions and an audit trail. |
Acceptance criterion An unapproved discount cannot enter the order handoff. | |
| Regional record access | |
| Configuration Design record sharing alongside object and field permissions. Record access | Build and enforce the regional access policy across UI and API. |
Acceptance criterion A user from another region cannot read the restricted record. | |
| ERP order handoff | |
| Development Confirm API entitlement and user permissions; scope the connector. API access by edition | Build the same mapping, retries, receipts and reconciliation. |
Acceptance criterion A repeated request creates one order; failures remain visible. | |
| Partial shipment history | |
| Configuration + development Evaluate custom records for shipment lines and integrate ERP updates. Custom objects and fields | Build order-to-shipment relationships and the operations view. |
Acceptance criterion Six shipped units and four remaining stay linked to the original ten. | |
| Cross-system late-order report | |
| Unknown until scoped Confirm the reporting option after mapping the required source data. Edition feature comparison | Define the metric and build its dataset, access rules and report. |
Acceptance criterion Report totals reconcile with the agreed order and shipment cutoff. | |
| Data export and transition | |
| Configuration + validation Select an export method and verify files, relationships and cadence. Data export methods | Specify export formats, identifiers, documentation and a restore exercise. |
Acceptance criterion Reconstruct a sample customer, order and shipment from the export. | |
| Customer self-service portal | |
| Unknown until scoped Obtain a separate design and licence assessment for external users. Pricing questions for the supplier | Price a separate portal with customer isolation and account recovery. |
Acceptance criterion A customer can see only their own orders and documents. | |
| Operation and future changes | |
| Unknown until scoped Agree platform support, administration and connector maintenance separately. Support and add-on scope | Agree hosting, support, upgrades and engineering ownership. |
Acceptance criterion Named owners can resolve an incident and release a tested change. | |
For this distributor, evaluate configuration and integration first: retain the standard sales workflow and prototype the ERP handoff and shipment updates. Use the results and complete proposals to decide whether replacement is justified.
Evaluate extension before replacement
Keep Salesforce in the shortlist if users can complete the standard sales process and the remaining difficulty is an ERP exchange, a specialised screen or a report. Salesforce documents custom objects and fields; a non-standard record is not, by itself, a reason to replace the platform.
Ask the proposed delivery team to demonstrate the awkward case: approve the quote, transmit it, repeat the request after a lost response, receive a partial shipment and show the remaining quantity to the right user. Record configuration, custom development, dependencies and unresolved limitations separately. The CRM–ERP integration guide describes the checks behind that exchange.
Assess a custom build when a trial exposes an unmet mandatory rule, extensions that cannot be maintained economically, or a user workflow with a demonstrable business benefit. Record the failed requirement and compare a scoped alternative against it.
Confirm the commercial edition and API entitlement
On 7 October 2026, the US-dollar Salesforce Sales pricing page listed Core at USD 195 per user per month, billed annually. Use this dated list price only as an illustration; confirm the appropriate package and commercial terms in a current quote.
The API access article uses edition labels including Enterprise and Professional, and distinguishes included API access from an add-on. Ask Salesforce to map your quoted product to its actual entitlements. Confirm the required API, call allowance, integration-user permissions, environments, external users and paid additions in writing. Buying capacity and obtaining permission to use an API are different questions.
Compare one implementation plus 36 operating months
Use the same user population, data volume, integrations and operating period. For a constant 25 chargeable users at the observed USD 195 monthly list rate, the arithmetic is 25 × 195 × 36 = USD 175,500. That is only a three-year licence line under an unchanged-rate assumption. It excludes discounts, renewal changes, taxes, implementation and any other required products or services. It is neither a total cost nor a forecast.
For each option, add the relevant lines:
- Discovery, configuration or development, migration, testing, training and release.
- Licences, hosting, storage, usage charges and any retained systems.
- Administration, support, monitoring, backups and recovery exercises.
- Connector maintenance and a defined allowance for future business changes.
- Export, documentation and transition work if the supplier changes.
Leave unquoted lines marked unknown rather than assigning zero. A custom proposal still needs engineering, hosting, support and future changes; replacing CRM does not automatically eliminate the ERP or other subscriptions. Our custom CRM cost guide separates module examples from migration and rollout work. Full Horizon Dynamics custom software projects start at USD 50,000, but that starting point is not a comparable total for this distributor. Use pricing and delivery to frame the scope discussion.
Compare CRM proposals on the same terms
Record evidence for nine requirements, separate unknown costs and document what would change the decision. Includes a provisional distributor assessment.
- Configuration, development and unknowns for each requirement
- Implementation plus 36 operating months for both options
- Prototype evidence, decision owner and exit checks
Editable text file (.txt)
Fill it in locally using a text editor or your own document. Share a non-confidential summary when you contact us.
Test your exit path and operating responsibility
Salesforce provides data export methods. Verify the selected method's cadence and which records and files it includes. An export existing does not prove that another team can reconstruct the required customer, order and shipment relationships.
Ask both suppliers to demonstrate that reconstruction with a sample. Separately document configuration or source-code access, environments, integration credentials, deployment instructions and responsibilities after handover. Platform support, application administration and a bespoke connector's support are different scopes.
Request a prototype of the uncertain workflow
Before committing to replacement, ask the proposed delivery team to demonstrate the order handoff, partial shipment and regional access checks. Agree who accepts the results and obtain implementation and operating costs for the same scope. That assessment should establish which requirements Salesforce can meet and whether a custom component or CRM is justified.
For the broader decision, use build, configure or connect. If a specific constraint remains, explore custom CRM development or share the workflow your current CRM cannot handle. Bring the exception, current tools and constraints; we can help define what needs to be verified before choosing a delivery approach.