Note

Salesforce consultant: 50 questions, grouped by what they protect.

The wrong Salesforce consultant costs you a year and a rebuild, and the warning signs are all available before you sign. Ask these 50 questions, grouped by what each one protects you from: technical depth, delivery approach, pricing, and who answers after go-live.

Salesforce consulting partner since 2010 · MVP Hall of Fame · 200+ agents in production · UAE, India and US desks

Listen for this

Red flags and green ones.

Red flags

Green flags

Vague answers about certifications
Named people and their certifications
No examples from your industry
Examples and references from your industry
"Implementation in 2 weeks"
Realistic timelines
Features, with no questions about your business
Clarifying questions about how you work
No talk of support after launch
Support options after go-live

After the questions

Five steps to a signed partner.

  1. Step 1

    Score and compare

    A matrix weighted by what matters to your business.

  2. Step 2

    Check references

    Three to five past clients. Promised against actual.

  3. Step 3

    Request proposals

    Written proposals from the top two or three.

  4. Step 4

    Solution workshops

    Finalists show their approach to your stakeholders.

  5. Step 5

    Negotiate

    Milestone payments, and knowledge transfer from day one.

Which questions to lead with

Start with what keeps you up.

  • Example

    Operations manager, Sharjah courier company

    Today: Dispatch runs on phone calls and a whiteboard.

    After: A good consultant asks how a job moves today before showing a single feature.

    Couriers and delivery
  • Example

    Marketing director, Dubai hotel apartments group

    Today: Every consultant shows the same retail demo.

    After: Examples and references from hospitality are asked for in the first call.

    Hotel apartments
  • Example

    Finance head, Kochi education trust

    Today: Wants the budget fixed before the board meets.

    After: The pricing questions come first: milestone payments, and what a change request costs.

    Education and non-profit
Examples of the readers this note is for. Not client stories.

Technical Expertise Questions

1. What Salesforce certifications does your team hold?

Why it matters: Certifications validate technical knowledge and commitment to staying current with Salesforce best practices.

What to look for: Multiple relevant certifications across the team, including Architect-level credentials for complex projects.

2. How many Salesforce implementations have you completed in our industry?

Why it matters: Industry-specific experience means faster implementation and better understanding of your unique requirements.

What to look for: Similar implementations in your industry, at a similar size, with a client you can call.

3. Which Salesforce clouds and products have you worked with?

Why it matters: Ensures expertise aligns with your planned Salesforce products.

What to look for: Deep experience with the specific clouds you plan to implement.

4. How do you approach data migration and integration?

Why it matters: Data migration is often the most challenging part of implementation.

What to look for: Structured methodology, experience with your systems, data quality processes.

5. Which Agentforce or Data Cloud work do you have in production?

Why it matters: Agents and unified data are where Salesforce is putting its new features, and a pilot in a demo org is not the same as one people use.

What to look for: A named production deployment, what the agent or data model does, and what they had to fix after go-live.

6. How do you handle custom development vs configuration?

Why it matters: Over-customization can lead to maintenance issues and upgrade problems.

What to look for: Configuration-first approach with custom development only when necessary.

7. What integration tools and middleware do you work with?

Why it matters: Most implementations require integration with existing systems.

What to look for: Experience with MuleSoft, Boomi, or other enterprise integration platforms.

8. How do you ensure solution scalability?

Why it matters: Your Salesforce solution needs to grow with your business.

What to look for: Architecture planning, governor limits consideration, performance optimization strategies.

9. What's your approach to security and compliance?

Why it matters: Data security and regulatory compliance are critical.

What to look for: Security best practices, compliance experience (GDPR, HIPAA, etc.), security testing processes.

10. How do you handle multi-org strategies?

Why it matters: Complex organizations may need multiple Salesforce instances.

What to look for: Experience with org strategy, data synchronization, and consolidated reporting.

Pricing and Contract Questions

11. What's your pricing model?

Why it matters: Understanding cost structure helps budget accurately.

What to look for: Transparent pricing, clear breakdown of costs, no hidden fees.

12. Do you offer fixed-price or time-and-materials contracts?

Why it matters: Different models suit different project types and risk tolerances.

What to look for: Flexibility to choose, clear scope definition for fixed-price projects.

13. What's included in your implementation cost?

Why it matters: Avoid surprise costs during implementation.

What to look for: Detailed list including licenses, training, data migration, integrations.

14. How do you handle scope changes?

Why it matters: Requirements often evolve during implementation.

What to look for: Clear change management process, transparent pricing for additions.

15. What are your payment terms?

Why it matters: Cash flow management and budget planning.

What to look for: Milestone-based payments, reasonable terms, performance-linked payments.

16. Do you offer any guarantees or warranties?

Why it matters: Protection against implementation issues.

What to look for: Bug-fix warranty period, satisfaction guarantees, SLAs.

17. What's your policy on intellectual property?

Why it matters: Ownership of custom code and configurations.

What to look for: Clear IP ownership transfer, documentation rights.

18. Are there ongoing fees after implementation?

Why it matters: Total cost of ownership planning.

What to look for: Transparent support costs, optional vs required services.

19. What happens if we're not satisfied?

Why it matters: Risk mitigation and exit strategies.

What to look for: Clear escalation process, refund policies, transition planning.

20. How do you handle budget overruns?

Why it matters: Financial risk management.

What to look for: Early warning systems, approval processes, cost control measures.

Implementation Process Questions

21. What's your implementation methodology?

Why it matters: Structured approach increases success probability.

What to look for: Proven methodology (Agile, Waterfall, Hybrid), clear phases, deliverables.

22. How long will our implementation take?

Why it matters: Timeline impacts business planning and resource allocation.

What to look for: Realistic timelines based on similar projects, buffer for complexities.

23. Who will be on our implementation team?

Why it matters: Team quality directly impacts project success.

What to look for: Named resources, relevant experience, dedicated vs shared resources.

24. How do you handle requirements gathering?

Why it matters: Thorough requirements prevent scope creep and rework.

What to look for: Structured workshops, stakeholder involvement, documentation processes.

25. What's your approach to testing?

Why it matters: Quality assurance prevents post-launch issues.

What to look for: Comprehensive test plans, UAT support, automated testing where applicable.

26. How do you manage project communication?

Why it matters: Clear communication prevents misunderstandings and delays.

What to look for: Regular status meetings, project portals, escalation procedures.

27. What project management tools do you use?

Why it matters: Visibility into project progress and issues.

What to look for: Professional tools (Jira, Monday, etc.), client access, real-time updates.

28. How do you handle deployment and go-live?

Why it matters: Smooth transition minimizes business disruption.

What to look for: Deployment checklist, rollback plans, go-live support.

29. What's your data validation process?

Why it matters: Data integrity is crucial for user adoption.

What to look for: Validation rules, data quality checks, reconciliation processes.

30. How do you manage risks and issues?

Why it matters: Proactive management prevents project derailment.

What to look for: Risk registers, mitigation strategies, regular reviews.

Support and Training Questions

31. What training do you provide?

Why it matters: User adoption depends on effective training.

What to look for: Role-based training, multiple formats, training materials.

32. Do you offer post-implementation support?

Why it matters: Ongoing support ensures long-term success.

What to look for: Support tiers, response times, dedicated resources.

33. How do you handle knowledge transfer?

Why it matters: Your team needs to maintain the system independently.

What to look for: Documentation, admin training, code walkthroughs.

34. What documentation do you provide?

Why it matters: Documentation is essential for maintenance and troubleshooting.

What to look for: Technical specs, user guides, process documentation.

35. Do you offer managed services?

Why it matters: Some organizations prefer outsourced administration.

What to look for: Service levels, included activities, pricing models.

36. How quickly can you respond to issues?

Why it matters: Downtime impacts business operations.

What to look for: SLA commitments, escalation procedures, 24/7 availability.

37. Do you provide release management support?

Why it matters: Salesforce has three releases annually requiring updates.

What to look for: Release testing, impact analysis, update support.

38. How do you ensure user adoption?

Why it matters: Technology success depends on user engagement.

What to look for: Change management approach, adoption metrics, ongoing support.

39. What's your approach to continuous improvement?

Why it matters: Systems need to evolve with business needs.

What to look for: Regular reviews, optimization recommendations, roadmap planning.

40. Do you offer emergency support?

Why it matters: Critical issues need immediate attention.

What to look for: Emergency procedures, response times, escalation paths.

Strategic Alignment Questions

41. How do you align Salesforce with business strategy?

Why it matters: Technology should support business goals.

What to look for: Business analysis approach, strategic planning experience.

42. What's your experience with digital transformation?

Why it matters: Salesforce is often part of broader transformation.

What to look for: Transformation methodology, change management expertise.

43. How do you measure implementation success?

Why it matters: Clear metrics ensure value delivery.

What to look for: KPI definition, measurement tools, success criteria.

44. Can you help with organizational change management?

Why it matters: People and process changes are as important as technology.

What to look for: Change management methodology, communication planning.

45. How do you ensure ROI from Salesforce?

Why it matters: Investment must deliver measurable returns.

What to look for: ROI models, benefit tracking, optimization strategies.

46. What's your approach to innovation?

Why it matters: Technology landscape constantly evolves.

What to look for: Innovation labs, new feature adoption, thought leadership.

47. How do you stay current with Salesforce updates?

Why it matters: Platform evolves rapidly with new capabilities.

What to look for: Training programs, Trailhead engagement, certification maintenance.

48. Can you help with Salesforce roadmap planning?

Why it matters: Long-term planning maximizes platform value.

What to look for: Strategic planning experience, roadmap templates.

49. How do you handle competing priorities?

Why it matters: Business needs often conflict requiring trade-offs.

What to look for: Prioritization frameworks, stakeholder management.

50. Why should we choose you over competitors?

Why it matters: Understanding unique value proposition.

What to look for: Clear differentiators, relevant strengths, cultural fit.

Which questions to lead with

Start with what keeps you up.

  • Example

    Operations manager, Sharjah courier company

    Today: Dispatch runs on phone calls and a whiteboard.

    After: A good consultant asks how a job moves today before showing a single feature.

    Couriers and delivery
  • Example

    Marketing director, Dubai hotel apartments group

    Today: Every consultant shows the same retail demo.

    After: Examples and references from hospitality are asked for in the first call.

    Hotel apartments
  • Example

    Finance head, Kochi education trust

    Today: Wants the budget fixed before the board meets.

    After: The pricing questions come first: milestone payments, and what a change request costs.

    Education and non-profit
Examples of the readers this note is for. Not client stories.

Red Flags to Avoid

Warning Signs in Consultant Responses:

• Vague or evasive answers about certifications or experience

• No specific examples or case studies from your industry

• Unwillingness to provide references or client contacts

• Promises that seem too good to be true (e.g., "implementation in 2 weeks")

• Focus only on technical features without understanding business needs

• No clear methodology or structured approach

• Pushing unnecessary products or premium features

• Lack of post-implementation support discussion

• No mention of change management or user adoption

• Inflexible contract terms or unclear pricing

Green Flags to Look For

Positive Indicators in Consultant Responses:

• Specific examples and case studies relevant to your industry

• Asking clarifying questions about your business needs

• Transparent pricing and contract terms

• Strong references with measurable results

• Investment in team training and certifications

• Clear communication and project management approach

• Focus on business outcomes, not just technical delivery

• Comprehensive support options post-implementation

• Realistic timelines and expectations

• Strong partner ecosystem and vendor relationships

Listen for this

Red flags and green ones.

Red flags

Green flags

Vague answers about certifications
Named people and their certifications
No examples from your industry
Examples and references from your industry
"Implementation in 2 weeks"
Realistic timelines
Features, with no questions about your business
Clarifying questions about how you work
No talk of support after launch
Support options after go-live

Next Steps After Evaluation

After gathering answers to these questions, follow this structured approach to make your final decision:

1. Score and Compare Responses

  • Create a scoring matrix based on your priorities
  • Weight criteria according to business importance
  • Compare consultants objectively using scores
  • Identify gaps and strengths for each option

2. Check References Thoroughly

  • Speak directly with 3-5 past clients
  • Ask about actual vs promised outcomes
  • Understand challenges and how they were handled
  • Verify claims made during evaluation

3. Request Detailed Proposals

  • Get written proposals from top 2-3 candidates
  • Ensure all discussed points are documented
  • Review timelines, costs, and deliverables
  • Clarify any ambiguities before proceeding

4. Conduct Solution Workshops

  • Have finalists demonstrate their approach
  • Include key stakeholders in workshops
  • Evaluate communication and collaboration style
  • Test cultural fit with your organization

5. Negotiate and Finalize Terms

  • Ensure contracts reflect all commitments
  • Negotiate payment terms and milestones
  • Include performance guarantees where possible
  • Plan for knowledge transfer from day one

Remember: Quality Over Cost

While budget is important, choosing based solely on price often leads to failed implementations. Focus on:

  • Proven expertise in your industry
  • Clear methodology and communication
  • Strong support and partnership approach
  • Alignment with your business goals
  • Long-term value over short-term savings

The right Salesforce consultant becomes a strategic partner in your success. These 50 questions help ensure you find a partner who understands your business, has the technical expertise you need, and can support your long-term growth.

After the questions

Five steps to a signed partner.

  1. Step 1

    Score and compare

    A matrix weighted by what matters to your business.

  2. Step 2

    Check references

    Three to five past clients. Promised against actual.

  3. Step 3

    Request proposals

    Written proposals from the top two or three.

  4. Step 4

    Solution workshops

    Finalists show their approach to your stakeholders.

  5. Step 5

    Negotiate

    Milestone payments, and knowledge transfer from day one.

The brief

Tell us where it is stuck.

The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.

Next

Related work

Processes clients hand us first. If yours looks like one of these, we already know the objects.