Enterprise Sales Cloud rollouts have specific architectural challenges.
Key dimensions:
1. Multi-region / multi-currency
- Multi-currency org (irreversible decision; plan early).
- Region-specific record types, page layouts, processes.
- Currency conversion strategy (Advanced Currency Management for historical accuracy).
- Localisation (translations, locale-aware formats).
2. Multi-segment go-to-market
- Often: SMB, mid-market, enterprise — each with distinct sales motions.
- Record types per segment differentiating opportunity stages, required fields, approval thresholds.
- Different page layouts, paths, validation rules.
3. Sales hierarchy
- Role hierarchy mirroring sales org chart (rep -> manager -> director -> VP).
- Territory Management 2.0 if sales territories matter (geographic, account-based, hybrid).
- Account Teams for enterprise cross-functional engagement.
4. Forecast strategy
- Collaborative Forecasts with multiple Forecast Types (revenue, ARR, opportunity quantity).
- Quota loading by user/period.
- Multi-stage forecast adjustments through the hierarchy.
5. Integration with non-Sales systems
- Marketing automation (Pardot/MCAE/Marketo) for lead nurture.
- ERP (SAP/Oracle) for orders, accounts, customer data.
- Customer Success platforms (Gainsight, Vitally) for renewal signals.
- Data warehouse for unified analytics.
6. CPQ (Configure, Price, Quote)
- Salesforce CPQ vs Apttus vs custom.
- Product catalog complexity (configurable products, bundles).
- Approval workflows for non-standard pricing.
- Quote-to-Order-to-Invoice handoff.
7. Sharing model
- Account: typically Public Read (everyone sees customer data).
- Opportunity: often Private with role hierarchy + Account Teams (deal teams need access; not everyone).
- Lead: usually Public Read for routing visibility.
- Custom objects: case-by-case.
8. Reporting strategy
- Operational dashboards (rep daily view).
- Manager dashboards (team pipeline, activity, forecast).
- Executive dashboards (revenue, run-rate, win-rate, segment performance).
- CRM Analytics for cross-region / cross-segment analytics.
9. Adoption & training
- Role-based training programs.
- Champions network within sales.
- Quarterly retraining as features evolve.
- Adoption metrics (login frequency, record creation, dashboard views).
10. Change governance
- Multiple sandboxes (Dev, UAT, Staging, Production).
- DevOps platform (Gearset/Copado/Salto) for orchestration.
- Release calendar (typical: monthly minor, quarterly major).
Senior architects sequence the rollout: Phase 1 might be Lead -> Opportunity -> reporting; Phase 2 adds CPQ; Phase 3 adds integrations and advanced forecasting. Big-bang enterprise rollouts often fail; phased reduces risk.