Documenting standard versus custom scope and its cost with stakeholders
Key Takeaway
During discovery, list custom requirements next to the standard features in the high-level discovery (HLD) document. Use a standard feature when one meets the need. For each custom item, show the approver a 3-5 year total cost of ownership, not only the build cost.
Customers usually want more than a product does out of the box. Documenting standard versus custom scope means sorting each requirement into what standard features already cover and what needs custom work. You then show stakeholders the effort and cost of the custom part. When you do it early and keep it current, everyone has clear expectations before anything is built.
Sort requests into standard and custom
Start discovery by sorting the customer's feature wish list into items that are supported out of the box and items that are custom. Most customers want to customize something, so expect a mix.
If a standard capability meets the request...
Deliver the request with that standard feature.
If no standard capability fits the request...
The request is custom, so document it as a custom requirement and show its full cost before anyone approves it.
Partner Collaboration in Advanced Account Forecasting is one example of a standard capability. With it, partners such as suppliers and distributors track forecasts in your manufacturing Experience Cloud site. Salesforce admins can set up Experience Cloud sites so partners can track forecasts.