Salesforce release management and DevOps: shipping containers in ordered rows, seen from above

Release Management and DevOps

Consultants who run Salesforce releases alongside your RevOps team until your team owns the pipeline

Release management as continuous improvement

Small increments, each measured and improved, until your own team runs the release process with confidence.

Diagram of a Salesforce release management pipeline from sandbox to production
Each change promoted from developer sandbox to production, with tests at every gate.

From an assessment of today's process to a team that owns its pipeline

Diagram of the Salesforce DevOps stages, from process review to team enablement
Each stage fitted to your constraints, without interrupting the release calendar.

Configuration released with the discipline applied to code

Salesforce Revenue Cloud stores pricing and product rules as records, so our consultants version, test and promote them with Prodly in the same release as the metadata.

  • Revenue Cloud configuration

    Product catalog, pricing procedures, decision tables, rate cards, configurator rules, templates and orchestration plans.

  • Approval chains

    Promoted with the price and product changes they govern.

  • Regression suites

    Quoting, amendment, renewal and billing scenarios executed before every promotion.

Questions about release management

What is Salesforce release management?

It is the process that carries a change from a sandbox to production: source control, environments, testing and the release calendar, as Salesforce's DevOps guidance describes it. With Revenue Cloud it extends to configuration records, because pricing and product rules live as data rather than metadata and must travel in the same release as the metadata that depends on them.

Why does Revenue Cloud need a data deployment tool?

Revenue Cloud stores much of its configuration as records, such as pricing procedures and decision tables, and standard metadata tools do not move records. Our consultants deploy them with Prodly, versioned and tested, in the same release as the metadata that depends on them, so quotes, renewals and bills keep working after each release.

Who runs the pipeline after the project?

Your own administrators and developers. Enablement is the final stage of the engagement: runbooks, training and ownership pass to your team so that, once our part is complete, your people run each release with confidence.

Plan the next release

Talk with the consultants who would lead the work.

Talk to our experts