What the CRM quote excludes
Compare promised deliverables with the work your team must do to use them.
Review questions →A supplier can configure exactly what was requested while your teams still disagree about when a deal is qualified, who owns a handover or which record is correct. Resolve those decisions before the software makes an unclear rule permanent.
Check scope, missing prerequisites, responsibilities and what you can actually accept at handover.
Check the proposal → 02 · You want to automateCheck where work waits, what happens next and how savings could be realised.
Assess the decision → 03 · Something is already wrongStart with the result that has changed. The possible causes can be investigated from there.
Explore the problem →A proposal may include pipeline configuration, data migration and dashboards. It may not include agreeing what qualifies as an opportunity, who validates records, or who acts on an exception after go-live.
Those tasks remain real even when they are outside the supplier's scope. See the costs and responsibilities often overlooked in a CRM project.
Compare promised deliverables with the work your team must do to use them.
Review questions →Include licences, staff time, clean-up, testing and continuing ownership.
Cost checklist →Test whether local time saved can change fulfilment, capacity or margin.
Five checks →A useful review should tell you which questions really need an answer before you commit, who is responsible for answering them and whether anything in the proposal should change.
Ask about a proposal review