Salesforce Consulting & Discovery
Before defining a single field,
define what the system needs to achieve.
Sound discovery connects business goals to the technology solution. It prevents unnecessary development, reduces misunderstandings, and creates a shared foundation for leadership, users and the technical team.
What we map
A full picture of the organization before decisions are made
- Current state
- Desired state
- Users and stakeholders
- Business processes
- Existing systems
- Data sources
- Data quality
- Permissions and data sensitivity
- Integrations
- Success metrics
- Risks
- Priorities
Problems this service solves
What happens when discovery is skipped
Requirements that change every week
Without structured discovery, every stakeholder pushes a different item to the top of the list. Discovery produces a single document all parties sign off on and enables managed change control.
A solution chosen before the problem is defined
Sometimes an organization buys licenses or a module before it's clear why. Upfront discovery checks whether the solution actually answers the business problem, and what's missing beyond the license itself.
Inability to estimate budget and timeline
Without defined scope, every estimate is a guess. The discovery deliverable lets vendors give a responsible estimate, and lets the client compare them fairly.
Tension between departments
Sales, service and operations each see the same process differently. Discovery workshops create a shared language and decide upfront where trade-offs are needed.
How we work
Seven defined steps
- 01Kickoff & stakeholder mapping
- 02As-is process workshops
- 03Mapping existing systems and data
- 04Designing the to-be process
- 05Initial data model & integration map
- 06Building the roadmap & estimate
- 07Presenting deliverables & sign-off
What you get
Deliverables you can actually work with
Requirements document
Clear documentation of business needs, scenarios, users and constraints.
Process map
As-is and to-be diagrams showing how work happens today and how it should happen.
Solution architecture
Design of the system, data, permissions, integrations and core components.
Roadmap
Phasing, milestones, quick wins and dependencies.
Backlog
Broken down into epics, user stories and tasks that can be prioritized and implemented.
Estimate & work plan
Scope, timeline, ownership and risk estimate based on known information.
Success metrics
Defined upfront so you can say a year from now whether the investment paid off.
Decision point
A 30-minute initial discovery call
In the call we'll clarify whether you need a full discovery, a short discovery, or a Health Check on an existing system.
When this service fits
Typical starting points
- Before purchasing Salesforce.
- Before an implementation project.
- Before extending an existing system.
- After a project that didn't reach its goals.
- Before Agentforce or AI.
- Before a complex integration.
- When multiple departments need to work in the same system.
- When there's no organizational agreement on the desired process.
Decision factors
Four decisions that determine the quality of discovery
Scope of discovery
A focused, single-department discovery is enough for a quick-win project. Cross-organizational discovery is needed when the process crosses departments and depends on shared data sources.
Depth of process documentation
Not every process needs a BPMN diagram. We invest deep documentation in core processes and lighter documentation in sub-processes.
Success metrics
We define three to five business — not just technical — KPIs upfront, so we can say a year from now whether the investment was worth it.
Prioritizing momentum over completeness
A roadmap that moves the needle within three months beats a complete plan that only launches a year from now.
Common mistakes
What to watch out for during discovery
- Starting discovery without a clear executive sponsor.
- Documenting the current state instead of defining the desired state.
- Loading up on 'everything we'd like' requirements instead of separating must-haves from nice-to-haves.
- Skipping the mapping of data sources and data quality.
- Closing discovery without confirming real users actually saw the deliverable.
Go deeper
Related guides and services
FAQ
Consulting & discovery — questions we hear often
What's the difference between Salesforce consulting and project discovery?
How long does discovery take?
Do you need discovery for an existing Salesforce org too?
Who from the client side needs to be involved in discovery?
Does the discovery deliverable commit you as the implementer?
Next step
Find out where to start
A short consulting call to map processes, flag gaps, and recommend the right discovery track.
Next step
Initial discovery call
A short 30–45 minute call to understand context and open decisions.