There is no responsible single price without a scope
A CRM quote should be based on the customer journey, records, roles, workflows, data, integrations and acceptance checks being delivered. A simple pipeline and a multi-team operating system are different projects even when they use the same platform. CompanyConnect does not publish a generic Rand range here because an unqualified number can hide important exclusions and create a misleading comparison.
Separate the four cost buckets
Compare one-off implementation, recurring software, internal team effort and ongoing improvement separately. Implementation covers diagnosis, design, configuration, migration, integration, testing, training and handover only where listed. Recurring costs can include CRM licences, integration services, messaging or model usage. Internal effort includes decisions, data preparation, testing and training. Ongoing support should state its response boundary and included work.
Configuration scope drives build effort
List the pipelines or service journeys, stages, roles, permissions, fields, views, automations, templates, dashboards and approval rules in scope. A proposal should distinguish standard configuration from custom development. It should also state which platforms and environments are included, who owns administrative access and what evidence will show that each workflow behaves as agreed.
Data work needs its own line item
Record every source, approximate record count, required fields, identity and duplicate rules, ownership gaps and retention constraints. Moving clean, agreed records is different from reconciling several inconsistent spreadsheets or a legacy system. The proposal should say who cleans the data, what will not migrate, how a trial import is checked and how the original source is preserved for recovery.
Integrations have build and running boundaries
For each connection, name the source, destination, trigger, mapped fields, supported interface, expected volume, failure handling and accountable owner. Keep third-party subscriptions and usage charges visible instead of burying them in the implementation fee. A connector logo does not prove that the required fields, limits or recovery behaviour are supported, so acceptance should use representative normal and exception cases.
Training, launch and stabilisation are measurable deliverables
State which roles receive training, what documentation and administrative handover are included, who approves go-live and how defects are handled after launch. A lower build price can become expensive when data preparation, testing, training or stabilisation is excluded. Conversely, do not pay for broad workshops or customisation that does not support a defined operating outcome.
How to compare two CRM proposals
Put both proposals into the same matrix: operating outcomes, included records and workflows, integrations, migration responsibility, permissions, testing, training, handover, recurring services, exclusions, assumptions, change control and support. Check whether VAT and third-party subscriptions are included or separate. Compare the evidence and recovery plan as well as the headline amount. Ask for ambiguous items to be made explicit before approval.
Prepare a decision-ready request
Bring one customer journey, the current tools, user roles, sample data with sensitive details removed, required reports, common exceptions and the result that matters. CompanyConnect can then scope a focused workflow, a connected operation or an ongoing systems relationship. Use the browser-local savings calculator to model your own handling-time assumptions; it is a planning scenario, not a promised return or a CompanyConnect price.