What is a Discovery phase in a Salesforce project?

Discovery is the first phase of a Salesforce implementation — the time spent understanding what the business needs before building.

What happens in Discovery:

1. Stakeholder identification. Who are the decision-makers, end-users, and SMEs?
2. Current-state mapping. How does the business work today? What systems, processes, pain points?
3. Future-state vision. What should the experience look like post-implementation?
4. Requirements capture. Functional (what the system does), non-functional (performance, security, scale).
5. Solution exploration. What out-of-the-box features fit? What needs configuration vs custom?
6. Risk identification. Integrations? Data migration? Compliance? Change management.
7. Roadmap and sequencing. What's the phased delivery plan?

Outputs: Discovery Document (or Solution Design Document), stakeholder map, requirements catalogue, high-level architecture, timeline and budget estimate.

Typical duration: 2-6 weeks for a mid-size project, longer for enterprise.

Why it matters: building the wrong thing is the #1 reason projects fail. Discovery validates assumptions before commitment.

Common mistake: treating Discovery as a checkbox. Rushing produces vague requirements; vague requirements produce rework. A senior consultant pushes back when leadership wants to skip Discovery.