ROI = (Benefits - Costs) / Costs, expressed as percentage or multiple over a time period.
Costs (typically captured well):
- License fees (per user, per month or year).
- Implementation services (consulting fees).
- AppExchange add-ons.
- Internal team time (often forgotten).
- Training.
- Ongoing support and admin team salaries.
- Hardware / connectivity (rare for Salesforce, but for Field Service mobile devices).
Benefits (harder to quantify):
Direct revenue impact:
- Faster sales cycle -> more deals closed in same time.
- Better lead conversion -> more revenue from same lead volume.
- Cross-sell / upsell visibility -> larger deals.
Cost reduction:
- Replaced legacy CRM licenses.
- Reduced headcount in routing/dispatching (automation).
- Reduced manual data entry hours.
- Faster case resolution -> fewer support staff per ticket.
Productivity:
- Sales rep time saved per week -> more selling time.
- Self-service deflection -> fewer support tickets.
Customer experience:
- Higher CSAT/NPS -> retention -> lifetime value.
- Faster response times -> customer satisfaction.
Strategic / harder to monetize:
- Better data quality -> better decisions.
- Single source of truth -> faster reporting.
- Compliance posture.
Typical ROI horizons:
- Year 1: often negative (heavy implementation cost vs partial benefit).
- Year 2-3: positive as adoption matures.
- Year 5+: significant multiple, especially if Salesforce replaces multiple legacy systems.
Senior consultant insight: capture baselines before go-live. "Sales cycle is 90 days; we expect 70 days post-implementation" — measurable. Without baselines, ROI claims are hand-wavy.
Common pitfall: only measuring at launch. The 12-month, 24-month, 36-month measurements often differ significantly. Track over time.