The Salesforce development sandbox strategy CIO playbook is the load bearing Salesforce sandbox conversation across the Salesforce platform framework.
Salesforce sandboxes anchor the broader Salesforce development framework. Customers running multiple Salesforce sandboxes face material commercial sensitivity to the sandbox allocation. The framework anchors against the customer's actual Salesforce development footprint.
Key Takeaways
- Four sandbox types shape the deal. Developer, Developer Pro, Partial Copy, and Full.
- Storage scales sharply. 200MB Developer to full production copy on Full.
- Refresh cadence varies. 1 day for Developer, 29 days for Full.
- Edition determines allocation. Enterprise, Unlimited, and Performance each carry different included sandbox counts.
- Right size the sandbox count first. Most estates carry surplus Partial Copy and Full sandboxes.
- Eleven move buyer side playbook. Compounds across the sandbox renewal cycle.
The framework typically delivers fifteen to thirty percent savings across the Salesforce sandbox framework at the renewal cycle.
The Salesforce development sandbox strategy pillar framework intersects with eight principal commercial dimensions. Each one anchors the framework against the customer's actual deployment estate.
The cumulative effect is that the framework matches the customer's actual deployment estate rather than the publisher's broad coverage. The framework typically delivers fifteen to thirty five percent savings at the renewal cycle.
The Salesforce sandbox types framework
The Salesforce sandbox types framework anchors the broader Salesforce sandbox framework. It segments across four core sandbox tiers plus bespoke configurations at upper customer scale.
Salesforce sandbox type comparison
| Sandbox type |
Data storage |
File storage |
Refresh interval |
| Developer | 200MB | 200MB | 1 day |
| Developer Pro | 1GB | 1GB | 1 day |
| Partial Copy | 5GB | 5GB | 5 days |
| Full | Production copy | Production copy | 29 days |
The sandbox allocation framework
The sandbox allocation framework is the second principal commercial framework. Included allocation varies by Salesforce edition.
- Enterprise edition. Carries a defined included sandbox bundle.
- Unlimited edition. Carries a broader included sandbox bundle.
- Performance edition. Carries the broadest included sandbox bundle.
- Additional sandboxes. Purchased separately at standalone list prices.
The sandbox refresh framework
The sandbox refresh framework is the third principal commercial framework. Refresh cadence drives developer productivity and budget exposure.
Developer and Developer Pro refresh on a 1 day cadence. Partial Copy refreshes every 5 days. Full sandbox refresh runs on a 29 day cadence. Faster refresh requires additional purchases.
The use cases framework
The use cases framework is the fourth principal commercial framework. The right sandbox type maps to the right use case.
- Development. Developer or Developer Pro sandbox.
- Integration testing. Partial Copy or Full sandbox.
- User training. Partial Copy sandbox.
- Staging and user acceptance testing. Full sandbox.
The sandbox rightsizing framework
The sandbox rightsizing framework is the fifth principal commercial framework. The framework segments across sandbox count, sandbox type, refresh frequency, and bespoke rightsizing populations. Read the related Salesforce license utilization calculator.
The contracting framework
The contracting framework is the sixth principal commercial framework. The framework segments across bundled sandbox contracting (included with Salesforce edition), additional sandbox contracting, and bespoke configurations at upper customer scale.
The renewal framework
The renewal framework is the seventh principal commercial framework. Read the related Salesforce renewal negotiation playbook landing.
The audit framework
The audit framework is the eighth principal commercial framework. Read the related Salesforce license compliance audit readiness CIO playbook.
The eleven buyer side moves
The buyer side framework has eleven moves that compound across the Salesforce sandbox renewal cycle.
- Anchor against actual deployment. Match the customer's actual sandbox usage, not the publisher's broad trajectory.
- Anchor the contracting term. Against the actual sandbox framework.
- Run the product framework. Across the principal product populations.
- Run the user framework. Against the customer's actual user count.
- Run the contracting framework. Across the principal contracting populations.
- Run the renewal framework. Across the principal renewal populations.
- Negotiate the contracting term. Multi year commitments only when price protection is durable.
- Negotiate the user framework. Match the customer's actual active user count.
- Negotiate the price escalator. Against the publisher's annual escalator framing.
- Build a competitive posture. Salesforce DX, scratch orgs, and alternative dev tooling on the table.
- Run the audit framework alongside renewal. Audit posture and renewal close together.
The framework is set out in detail across the Salesforce services practice, the Salesforce knowledge hub, the Salesforce contract negotiation service, the Salesforce renewal negotiation playbook landing, the CIO playbook for Salesforce platform and custom apps licensing strategy, and the Salesforce license utilization calculator.
What to do next
The seven step checklist below opens the buyer side sandbox conversation before the publisher locks the renewal anchor.
- Inventory active sandboxes by type. Developer, Developer Pro, Partial Copy, Full.
- Pull telemetry on each sandbox. Identify dormant or under utilized sandboxes.
- Map sandbox to use case. Confirm the type matches the actual workload.
- Right size the count. Eliminate dormant sandboxes before the renewal window opens.
- Open a competitive frame. Salesforce DX with scratch orgs as an alternative for some dev workloads.
- Cap the annual uplift. Three to five percent is achievable with multi year commitment.
- Co terminate with the Salesforce master. Align sandbox renewal with Sales Cloud and Service Cloud for aggregation leverage.
Frequently asked questions
What are the four core Salesforce sandbox types?
Developer, Developer Pro, Partial Copy, and Full. They differ on data storage, file storage, refresh cadence, and whether they include data from the production org.
How many sandboxes does each Salesforce edition include?
Enterprise, Unlimited, and Performance editions each carry different included sandbox allocations. Additional sandboxes are purchased separately. Confirm the actual allocation with your Salesforce account team and your existing order form.
What is the typical Salesforce sandbox saving?
Fifteen to thirty five percent on a typical enterprise renewal. The compression comes from sandbox count rightsizing, sandbox type rightsizing, and refresh frequency rightsizing.
When should the sandbox negotiation start?
Nine to twelve months before the contract end date. The first six months focus on internal rightsizing. The negotiation with Salesforce starts in the final six months.
How we engage
- Salesforce development sandbox strategy scoping. Six week engagement that scopes the Salesforce development sandbox strategy framework, anchors the customer's actual Salesforce development sandbox strategy deployment framework, and identifies the immediate commercial moves at the next Salesforce development sandbox strategy renewal cycle. Vendor Shield.
- Salesforce development sandbox strategy negotiation. Contract negotiation engagement that handles the Salesforce development sandbox strategy framework, the user framework, the contracting framework, and the broader Salesforce development sandbox strategy renewal conversation across the renewal cycle. renewal program.
- Salesforce development sandbox strategy audit defense. Audit defense engagement that handles the Salesforce development sandbox strategy audit framework, the compliance framework, and the broader Salesforce development sandbox strategy audit response framework. audit defense kits.
- Vendor Shield. Always on multi vendor management posture that covers the Salesforce development sandbox strategy framework alongside the broader enterprise software estate. Vendor Shield.
- Run the assessment. The software spend assessment sizes the Salesforce development sandbox strategy framework against the customer's actual Salesforce development sandbox strategy deployment framework.
- Cross vendor benchmarking. The benchmarking practice benchmarks the Salesforce development sandbox strategy framework against the broader market framework.
