Foundation: data model
Account object setup. Decide upfront: do accounts represent legal entities, business units, or both? The choice drives every downstream report.
Account hierarchies. Set up parent-child relationships before any data load. Hierarchies are hard to back-fill later.
Custom fields. Add ICP scoring fields, MEDDPICC fields, and account tier fields on the Account object before reps start using it.
Page layouts by tier. Tier 1 accounts get the deep page layout (account plan, relationship map, whitespace). Tier 3 gets the minimal layout.
Opportunity object best practices
Stage definitions with exit criteria. Reps can't advance stages without completing the required fields.
Custom MEDDPICC fields. Eight fields, one per dimension, plus calculated score.
Probability calibrated to historical conversion rates, not Salesforce defaults.
Required fields by stage. Force discipline.
Contact and stakeholder management
Contact roles on the Opportunity. Identify who's economic buyer, champion, technical evaluator, etc.
Custom fields for influence and support scores. 1-5 scales.
Relationship hierarchy on Contacts where the organizational structure matters.
Integration with relationship mapping tool (Prolifiq CRUSH is Salesforce-native; data lives on Contact records).
Integration architecture
Pick native AppExchange apps where they exist. CRUSH and ACE are native; many alternatives are connected.
Avoid duplicate sync paths. If a tool syncs to Salesforce, no other tool should also write to the same fields.
Audit API consumption. Connected apps can hit Salesforce API limits faster than expected at enterprise scale.
Standardize on the canonical Salesforce object IDs for integrations. Don't let third-party tools create their own keys.
User adoption
Train sales managers first. They cascade adoption to reps.
Page layouts that surface what reps need without 30 fields they don't.
Make required fields actually required. Validation rules at stage transitions.
Dashboards that show reps their own performance vs targets. Self-service.
Don't change processes constantly. Adoption suffers when the system changes weekly.
Reporting and analytics
Pipeline reports by tier, segment, and rep. Standard.
Forecast reports built on MEDDPICC score, not just stage.
Account-level rollup reports for KAM programs.
Activity reporting tied to outcomes (which activities correlated with closed deals).
Common implementation mistakes
Custom-coding what could be configured. Apex code costs ten times more to maintain than declarative configuration.
Over-customizing the data model. More custom fields equal more friction and slower performance.
Letting integration partners define the schema. Define your data model first, then layer integrations on top.
Skipping the data hygiene work. Garbage in produces garbage reports.
Big-bang launches. Phased rollouts with smaller user groups validate the design before broad release.
Frequently asked questions
What's the most important Salesforce implementation best practice?
Set up the data model (Account hierarchies, custom fields, page layouts) before loading data or going live. Foundation choices are hard to reverse.
Should I custom-code or configure Salesforce?
Configure whenever possible. Custom Apex code costs ten times more to maintain than declarative configuration.
How do I drive Salesforce adoption?
Train managers first, design page layouts that surface what reps need, enforce validation rules at stage transitions, and avoid constant process changes.
CTA
Implementing Salesforce for account planning? See how Prolifiq CRUSH installs natively in days and avoids the data sync problems of connected apps. [Book a Demo]
