A new inquiry arrives. An employee responds and then goes away, leaving a colleague unsure whether a quotation was sent or what the customer was promised. Buying CRM accounts does not automatically close that gap. You need agreement about customer ownership, follow-up records and handover, followed by a system configured to reflect those decisions.
When reading a CRM implementation proposal, look for the work that turns a license into a sales process the team can use. Do not compare only user counts or screen names. Start with the practical question: can an authorized colleague understand a specific opportunity and take the next step without reconstructing scattered messages?
Map one opportunity before discussing settings
Consider a fictional services company receiving inquiries through its website and telephone. A contact and source are recorded, a salesperson checks whether the request is suitable, a discussion is scheduled, a proposal is sent, and the outcome and reason are recorded. This is not a universal sales model. Its purpose is to give the implementer a concrete journey to review.
For every step, identify the owner, required information and next action. If “interested customer” means something different to each employee, renaming a stage will not resolve reporting problems. Agree on meaning first, then ask for it to be represented and tested with practical cases.
What should the implementation proposal explain?
Salesforce guidance describes implementation as more than installing software: understanding needs, configuration, integration and training are part of the work. To apply that distinction to any proposal, use the following buyer questions. They are not a guaranteed feature list for every product.
| Implementation area | Practical question | Deliverable |
|---|---|---|
| Sales stages | What evidence moves an opportunity, and who approves closure? | Stage definitions, transition conditions and test cases. |
| Fields and records | What is mandatory, who updates it, and how are companies linked to contacts? | A data dictionary and clear sample records. |
| Responsibility | Who receives an inquiry, including when someone is absent? | Assignment, handover and exception rules. |
| Migration | Which records, history and attachments will move? | A migration map, trial results and reconciliation. |
| Adoption and handoff | What must a user complete independently before launch? | Role-based training, acceptance records and reference materials. |
Add reporting and integration needs specific to your operation. “Customization as requested” needs boundaries: identify included fields, flows and reports and what needs a new estimate. If discovery is a separate phase, agree on the deliverable that will make implementation estimable afterwards.
Distinguish the product license from the company's service
A subscription may provide product capabilities, but working on your processes, records and connections needs a specific agreement. Request separate items for the product, analysis, configuration, development, migration, training and support. Clarify what you pay directly to the platform provider and what the implementer handles.
Check which plan is needed for each proposed function, including any user, storage or integration limits that require verification at purchase. A demonstration may not use the plan you will receive. Ask for the assumptions rather than relying on a single product name.
Do not migrate disorganized files unchanged
Before migration, establish the source of customer records and the duplicate-detection rules. One person may appear with differently formatted phone numbers or an old email address; two different companies may share a name. Ask how conflicts will be surfaced for review rather than merged without a clear decision.
Salesforce's migration guidance includes configurations and processes alongside records and emphasizes planning, cleaning, testing and training. Turn that into a representative trial migration with a report showing what moved, what was excluded and what needs review. Row counts alone do not establish that relationships and history are correct.
Integration needs an operational result
If website inquiries enter the CRM, test a new inquiry, a duplicate and a submission lacking required information. Check source, owner, notification and next action. For email or messaging channels, ask which accounts and permissions are needed and how messages are associated with the correct contact.
Document who follows up on failed connections, how staff discover an inquiry that did not arrive and who reprocesses it. Automated follow-up does not imply uncontrolled messaging. It must follow the communication rules and choices adopted by the business and its service providers.
Request reporting with explainable numbers
A dashboard may display the value of open opportunities, but its meaning changes depending on whether staff enter expected or approved values and whether dates refer to opening or closure. Choose an important report, define it in the team's language and request a route from its total to the underlying records.
Decide who can see the whole team and who can see only assigned opportunities. Test permissions with separate accounts. Hiding a field on one screen does not prove that search or exports protect it. Ask the implementer to identify what was tested and what remains outside scope.
A short acceptance session can reveal a lot
Follow a fictional inquiry from its source to closure. Have a salesperson record a follow-up, schedule a discussion, hand the opportunity to a colleague and update its result. A supervisor reviews the report, while another user tries to access information outside their role. Record outcomes, issues and who approves the corrections.
If users need help with every click, investigate before extending training. Are labels unclear? Is the system demanding information the business does not need? Have the process steps themselves been agreed? Training matters, but it cannot compensate for a confusing workflow or unresolved responsibility.
Use the CRM cost-components guide for budgeting. When requesting CRM implementation, include the opportunity journey and this matrix. The comparison will then focus on how your team will work rather than on competing feature names.
Preparation sources
The Salesforce CRM implementation guide and CRM migration guide were checked on 3 November 2026 for general implementation and migration concepts. The example, matrix and acceptance session are original proposals, not a client case or published outcome. This text was prepared with AI assistance and review of its content and sources.
