I wanted to see what is the best approach to take for the below scenario outlined.
We are currently exploring how best to incorporate a stream of our business into Salesforce. This side of the business would contain a project and multiple phases. While we plan to utilise Opportunities to capture the overarching (parent) project, the complexity arises in how we manage the delivery structure of the phases. Many of these projects can include a significant number of phases often 20, 30, or even 50+ each with its own associated value and cost etc. The project would have a different sales process and custom fields to the phases so i understand if it is opportunities (and child Opps) we have to go with seperate RTs will be needed.
Given this, we’re unsure whether standard Opportunity records alone are the most effective solution.
I would greatly value any thoughts on how best to implement this in our org.
@* Sales Cloud - Best Practices * @* Sales Cloud - Getting Started *
,
We actually have a similar model internally.
- Opps represents the deal (High-level project/deal)
- Each opp may have multiple phases (custom object)
- Each phase may have multiple items (custom object MD to Phases)
When an opp closes 1 or multiple projects get created (based on the number of phases).
Phases has a status to differentiate between a currently approved phase, future approved phase and not approved phase. Only the currently and future approved phases generates a project
Projects have requirements (Phases items) and multiple invoices
At the end, opportunities are use for forecasting and invoices are actuals