Publish Date
0
About the Author
FAQ
It varies wildly based on scope:
- Small businesses (1-50 users, Sales Cloud only): $50,000-$150,000
- Mid-market (50-500 users, 1-2 clouds): $150,000-$500,000
- Enterprise (500+ users, multiple clouds, complex integrations): $500,000-$2,000,000+
Beyond the implementation cost, budget for:
- Licenses: $150-$165/user/month
- Managed services: $5,000-$50,000/month
- Staff augmentation: $100-$250/hour
Real talk: Don't buy the cheapest option. Budget conservatively (add 20% contingency) and focus on value, not minimum cost.
Depends on scope:
- Sales Cloud only (straightforward): 3-4 months
- Sales Cloud + integrations: 4-6 months
- Sales + Service Cloud: 6-8 months
- Multi-cloud (Sales, Service, Marketing, Commerce): 9-18 months
- Enterprise transformation: 12-24 months
Formula: Expect 1-2 weeks per user (for requirements gathering, process design, testing, training).100 users = expect 100-200 weeks of effort across the entire team.
Honestly? Use a partner for most of it.
DIY makes sense only if you have:
- Salesforce expertise internally
- Straightforward requirements (no complex customization)
- Limited integration needs
- 3-6 months to learn
Partner makes sense if you have:
- No Salesforce expertise (true for most companies)
- Any integration needs
- More than 50 users
- Industry best practices you want to leverage
- Risk of failure that you can't absorb
Reality: Most successful companies use a hybrid approach—partner for implementation and an internal team for ongoing administration.
You have good options:
- Option 1: Bring in a consultant to audit your current setup ($10-20K) and recommend improvements.
- Option 2: Hire a staff augmentation specialist to build new capabilities or fix issues.
- Option 3: Engage a managed services partner to optimize your system proactively.
- Our recommendation: Start with an audit. Identify the biggest gaps. Prioritize improvements. Then, engage either staff augmentation or managed services based on what you find.
This is actually the most important question. Technical implementation is less than half the battle. Adoption requires:
- Leadership support - Executives need to champion the change
- User involvement - Get users in the room during design
- Clear training - Not just technical, but why it matters for their job
- Early wins - Show value quickly
- Ongoing support - Make it easy to get help after go-live
- Change management - Acknowledge what's changing and why
- Pro tip: Look for partners who emphasize change management, not just technical implementation.
You have options:
- Early (first month): Can usually exit with a relatively small cost
- Mid-project (3+ months in): Trickier, but you can bring in a different partner to complete the work
- Post go-live: Can switch to a different managed services provider, Best approach: Choose carefully upfront. Interview 2-3 partners. Trust your gut about cultural fit.
Good question. Here's the truth: You won't avoid it completely. Once you're on Salesforce, you're invested. But you can minimize it:
- Insist on knowledge transfer - Your team should understand the system, not just the partner
- Documentation is critical - Get comprehensive documentation about your customizations
- Choose partners who support portability - Avoid over-customization that makes you dependent
- Plan to have switchable partners - Your managed services partner doesn't have to be your implementation partner
- Standard configurations are best - Avoid excessive customization when the configuration works
Key ones to verify: Foundational (important):
- Salesforce Certified Administrator
- Salesforce Certified Platform App Builder
- Cloud-specific certifications (Commerce Cloud, Marketing Cloud, etc.)
Advanced (very valuable):
- Salesforce Certified Platform Developer I & II
- Salesforce Certified Technical Architect (super rare and valuable)
- MuleSoft certifications (if integration is needed)
- Tableau certifications (if analytics is important)
Red flag: Partner can't easily list team certifications, and they don't align with your needs.
The questions that matter:
- What's your experience in [our industry?
- Can I speak with three clients similar to us who implemented in the past 18 months?
- Walk me through how you'd approach our project from discovery to go-live.
- How do you handle scope creep and change management?
- What's your approach to user training and adoption?
- What happens after go-live? What does post-implementation support look like?
- Have you failed before? What did you learn?
- Who specifically will work on our project, and what's their experience?
- How do you measure success?
- What's included in your proposal, and what costs extra?
Here's a good cadence, During implementation:
- Weekly status calls (1 hour)
- Bi-weekly steering committee meetings (executive level)
- Ad hoc technical discussions as needed
- Testing cycles (usually 2-week sprints with daily brief check-ins)
Post-go-live (managed services):
- Monthly business reviews (discuss optimization and new initiatives)
- As-needed technical support (escalation-based)
- Quarterly health checks (performance review)
- Quarterly updates (new Salesforce features and best practices)
Red flag: Partner is hard to reach, or communication is infrequent.
16192 Coastal Highway Lewes, Delaware 19958 USA
