CRM buying guide

Custom CRM vs off-the-shelf: which fits your business?

Choose an existing CRM when its configured workflows fit your team. Consider custom development when a necessary workflow or integration cannot be supported well at a reasonable total cost.

The useful comparison is between a configured platform and a scoped custom system. A subscription price and a development quote usually cover different things. This guide helps you compare the same work, people and operating period.

By Elevéa Cloud · Published 6 October 2026

Compare what you would actually deploy.

Off-the-shelf does not mean unchangeable. Platforms can offer custom fields, processes, reports and extensions, depending on the plan. Custom does not automatically mean unrestricted ownership or lower costs: those depend on the contract, dependencies and support model.

Questions to resolve before choosing a CRM approach
Decision	Configured platform	Custom CRM
Workflow fit	Test the actual workflow using configuration and supported extensions.	Specify the workflow, exceptions and acceptance tests before estimating the build.
Cost	Include paid seats, the required plan, add-ons, setup, migration and support.	Include discovery, development, migration, hosting, third-party licences and maintenance.
Integrations	Check whether the connector and API access exist in the plan you will buy.	Check API access on both sides, authentication, retries and responsibility for changes.
Permissions	Test record and field access with representative users; plan names alone are insufficient.	Define and test who may view, edit, export and delete each type of information.
Change & support	Understand vendor updates, plan limits, extension support and export options.	Agree source access, documentation, ownership terms, backups and an ongoing support arrangement.

For example, Salesforce’s published comparison lists customization, roles, permissions and API capabilities across its plans. HubSpot describes contact management, integrations and user permissions alongside its free and paid offerings. Check the current plan and limits for your actual requirement before deciding that a custom build is necessary.

What does a CRM cost over three years?

Use the same number of users, workflow scope and period for both options. A useful starting point is a 36-month comparison. Include implementation and operation; a cheaper first month may not produce a cheaper system.

Configured platform

Setup, migration and training + months × (users × monthly licence + monthly add-ons, integrations and support).

Custom CRM

Build, migration and training + months × (hosting, licences, integrations and maintenance).

Ask each supplier which costs are included and who pays for future changes. For proposals from any country, compare in one currency, keep the tax treatment consistent and check annual-billing commitments. The calculator uses your inputs; it supplies no assumed vendor prices.

This is an estimate from your inputs, not an Elevéa Cloud quote. It assumes constant users and monthly costs, and excludes tax, financing and future scope changes unless you include them. Currency selection changes the display; it does not convert values. Calculations run in your browser and these inputs are not sent to us.

Test one complete sales workflow.

Write a short scenario that both suppliers must demonstrate. For example: a website enquiry creates a lead, an owner is assigned, an overdue follow-up is visible to a manager, and a won opportunity passes to operations. Include a duplicate contact and a failed integration, not just the ideal journey.

Define the records. List the information a lead, organisation and opportunity must contain, and which fields are required.
Define the rules. State who may reassign an opportunity, approve a change or reopen a closed record.
Test access. Sign in as a salesperson, manager and administrator. Verify exports and sensitive fields as well as visible screens.
Test the exception. Disconnect an integration and explain how the team will discover the failure, retry it and avoid duplicates.
Test the handover. Ask someone who did not build the demonstration to complete the process using the proposed instructions.

Permission checks are particularly important. Microsoft’s Dataverse documentation explains that privileges can accumulate across roles and teams. Giving a user a restrictive role may not cancel broader access granted elsewhere. Test effective access instead of judging it from role names.

If a platform handles the scenario cleanly, configuration may be enough. If the essential step requires a fragile workaround, document that limitation and assess a custom integration or build. A hybrid solution can retain an existing CRM while adding a focused portal or workflow.

Plan the data move before the launch.

Review a sample export early. Map fields, decide how duplicates will be resolved, preserve record relationships and identify records that should not be migrated. Test an import and reconcile the results before the full move.

Agree the cutover time, who can edit the old system during migration, validation responsibilities and a rollback approach. A successful login alone does not prove the data arrived correctly.

Make the handover specific.

Who owns the accounts, data and agreed custom code?
Can you export records and attachments in a usable format?
Who manages access, backups and integration credentials?
What does maintenance include, and how are new features priced?
What happens if you change suppliers?

What should you send for a CRM estimate?

Prepare the number of users and roles, one complete sales workflow, a sample of your current records, required integrations, essential reports and a target rollout period. Mark requirements as essential or optional. Use anonymised examples when sharing a brief publicly.

Elevéa Cloud provides custom CRM development and integration. We can discuss whether configuration, an integration or a custom application fits your requirements. Where the project crosses into a portal or internal tool, explore our web application development services.

Sources and scope.

This guide combines our project-scoping approach with current vendor documentation. Vendor plans and limits can change; the calculator is a planning aid, not a quotation or a guarantee of savings.

Sources reviewed 6 October 2026.