A project is moving from the design phase to the build phase.

As a Salesforce Revenue Cloud project moves from design into the build phase, it is essential to follow Salesforce’s recommended development lifecycle and environment strategy to ensure a smooth, secure, and scalable implementation.

Per the Salesforce Revenue Cloud Implementation Guide and Project Delivery Framework, the consultant must:

Set up multiple environments: such as Developer Sandbox (for configuration and coding), UAT Sandbox (for user testing), and Production (for go-live)

Establish a deployment strategy and toolset: using tools like Change Sets, Salesforce CLI, DevOps Center, or third-party CI/CD platforms

Maintain proper version control and release planning

This approach ensures code quality, traceability, and a safe pathway for validating changes before going live.

Option B, while valid during design and requirement gathering, should have been completed before build.

Option C (building directly in production) violates best practices, increases risk, and lacks rollback and testing controls.

Exact Extracts from Salesforce Revenue Cloud Documents:

Revenue Cloud Delivery Framework – “Environment Strategy”:“Create isolated sandboxes for development, QA, and UAT. Always deploy to production through a structured release process.”

Salesforce Implementation Lifecycle – “Build Phase”:“Establish a deployment toolset and environment strategy at the beginning of the build cycle to ensure governance and minimize risk.”