Supplier configuration and deliverables
The supplier can accept and test these against agreed specifications.
The quote covers configuration, but who will agree the data definitions, clean the records, test the workflows and train the teams? The software cost may be clear while the internal work — and who owns it — is not.
Budget for supplier fees and licences plus your team's time defining processes, cleaning and reconciling data, testing, training and taking ownership after launch. Whether those items are included depends on the actual proposal: do not assume every omission is a hidden charge.
| Cost or activity | Where to look | Question for your supplier or team |
|---|---|---|
| Licences and recurring charges | Users, tiers, contacts, API limits, add-ons | How will cost change if usage increases? |
| Process and data definitions | Pipeline stages, objects, reasons, ownership | Who makes decisions when teams disagree? |
| Migration and clean-up | Legacy duplicates, missing links, order history | Who prepares source data and validates the result? |
| Integrations | Finance, service, website, email, fulfilment | Which direction does data travel, and what is out of scope? |
| Internal delivery time | Manager, admin, subject-matter experts | Who is released from daily work to support the project? |
| Testing and adoption | Exceptions, UAT, training, user feedback | Which real cases prove the configured system works? |
| Ongoing ownership | Reports, permissions, changes, data quality | Who keeps the information reliable after handover? |
A practical planning estimate is supplier fees + licences + internal staff time + migration and integration costs + training and testing + ongoing administration.
Do not count a staff member's full salary as an extra cash payment if they are already employed. Internal time is an opportunity cost: their other work must wait, be reduced or be covered.
Likewise, time saved by automation is not automatically money saved. The value depends on whether the freed capacity prevents extra hiring, reduces paid overtime or increases useful output.
A proposal includes reporting on lost deals. The CRM fields and dashboard can be delivered as specified. But the company still needs agreement on what the reasons mean, who checks entries, and how management reviews findings. Without that work the software can be configured correctly and still produce little useful explanation.
The supplier can accept and test these against agreed specifications.
The customer may need to assign staff time and decision-making authority.
A second opinion is useful when the proposal looks detailed but it is unclear which expected outcomes it supports, what the business must prepare and how success will be accepted.
Check a CRM proposal →Scope, responsibilities, dependencies and tests.
Proposal checklist →Define the required business change first.
Explore the decision →Check definitions and data capture before requesting more dashboards.
Troubleshoot →The implementation budget should include internal process design, data preparation, testing, training and the operational disruption of change.