Replacement
Part of CRM costs and vendor selection
Estimating CRM implementation and support costs
Scope CRM migration, configuration, training and support, then separate first-year and recurring costs.
Estimate CRM implementation from the work needed to reach an agreed first release, then price post-launch support. Ask who performs each task, what completion means and whether the quoted fee includes it. Subscription price alone cannot answer those questions.
Define the first release
List the records to move, workflow to configure, users who need access and reports required at launch. Count each source system and integration. Name work that can wait, and the approved manual route for any deferred task that must still be done.
| Work package | What drives the estimate | Completion evidence to agree |
|---|---|---|
| Data preparation and migration | Sources, record types, fields and uncertain matches | Intended records, values and links reconcile |
| Configuration | Pipelines, permissions, fields and reports | Intended roles can complete their tasks |
| Integrations | Sending and receiving systems, error handling and owners | Representative events reach the right destination |
| Training and cutover | Roles, sessions and transition period | Users can work and the old process has a handover plan |
| Post-launch help | Channels, hours and internal administration | Issues have an owner and escalation route |
These are estimating categories; a small first release may not need all of them. Ask for assumptions and exclusions beside every supplier fee. Include internal time for data decisions, business rules and acceptance even when a partner does the configuration.
Check what onboarding includes
Vendor onboarding may provide guidance without performing a migration or integration. Read its statement of work. Check whether a vendor's published pricing or support policy lists onboarding charges, and confirm what that charge covers. Quote any extra partner work separately.
Pipedrive's billing guidance identifies seats, add-ons and top-ups as cost drivers. Projects, LeadBooster and Smart Docs are included in Premium and Ultimate but are add-ons on Lite and Growth. Include them only when the first release needs them, and check the proposed allowance before assuming a top-up solves a limit.
Zoho lists Classic support with paid editions. Its published policy prices Premium support as an additional share of the subscription fee and includes one-to-one onboarding guidance. Confirm the work that guidance covers. Its maximum response times concern an initial response, not resolution.
CRM Onboarding Inclusions by Vendor
- HubSpotGuidance provided; migration and integration not included in standard onboarding
- PipedriveOnboarding guidance included; add-ons (e.g. Projects, LeadBooster) are separate; top-ups may be required
- ZohoClassic support included with paid editions; Premium support is additional; one-to-one onboarding guidance provided
Build two totals
First year: recurring subscription, required add-ons and separately charged support, plus one-off onboarding and delivery work and internal project time.
Later year: recurring subscription, required add-ons and separately charged support, plus expected internal administration and change work.
Keep the same currency and GST basis. Count included services only once. Rely on quoted supplier charges and labelled internal estimates; show a range when migration work remains uncertain. State any growth scenario, such as more seats or records, and obtain the resulting price and limits in writing.
Control changes to scope
Before work begins, assign owners for data decisions, configuration, checks and sign-off. Ask for a written estimate when scope changes. After launch, distinguish defects in agreed work from requests for new features so support costs and additional implementation work remain clear.
