Salesforce Data Cloud sizing read in plain language. The deployed-workload audit, the moderate-case forecast, the credit-rate-table mapping and the buyer-side artefact that aligns the commitment to actual consumption rather than to the marketing-led estimate.
Data Cloud sizing reads the workload as the unit of analysis. A workload is a data-ingestion source, an activation channel or a segmentation cadence that consumes credits from the pool. The user count is not the sizing input; the workload count is.
The sizing artefact inventories four components of the workload portfolio. The source-by-source ingestion plan reads the inbound data sources and their row volumes. The channel-by-channel activation plan reads the outbound activation surfaces and their record-out volumes. The segmentation portfolio reads the segmentations and their refresh cadences. The credit-rate-table mapping translates each workload into a credit total. The wider Data Cloud consumption credits spoke reads the credit basket.
The source-by-source ingestion plan inventories every data source that the Data Cloud ingests, the row volume per source, the change-data-capture frequency, the historical-back-fill scope and the ingestion-rate-table mapping at the contract version. The plan reads the CRM connector (typically the standard Salesforce CRM, included in the base entitlement), the ERP connector, the data-warehouse connector, the streaming-source connector and the third-party-CRM connector.
The buyer-side discipline is the back-fill scoping decision. A buyer that brings five years of historical CRM and ERP records into the platform at deployment consumes a multi-year ingestion budget in the first contract year. The discipline produces a back-fill scope sized against the use case, not against the available historical depth.
The channel-by-channel activation plan inventories every activation surface that the Data Cloud pushes records to. The Marketing Cloud Engagement activation is typically the highest-volume channel; the advertising activations (the Meta, Google, LinkedIn audience pushes) are the second-highest. The Service Cloud activation and the Account Engagement activation are typically lower-volume.
The activation forecast is the record-out volume against each channel times the activation cadence. A daily-refresh audience push to a million-record audience consumes a recurring activation-credit volume against a moderate baseline; an hourly push consumes a multiple. The wider Marketing Cloud tiers spoke reads the downstream consumption pattern.
The segmentation portfolio inventories every segmentation that the Data Cloud runs and its refresh cadence. The rules-based segmentation against the unified customer profile is the most common; the AI-assisted segmentation (the next-best-customer score, the look-alike segmentation) consumes additional segmentation credits per run.
The segmentation-cadence design is the operational lever. A weekly refresh of a million-customer audience consumes a fraction of the segmentation credits that a daily refresh consumes. The discipline produces a segmentation cadence that aligns to the actual marketing or service operational cadence rather than to a default daily schedule.
The moderate-case forecast is the sizing output. The forecast is the credit total against the sized workloads at the contracted credit-rate table. The forecast reads the moderate case: the deployed workload plus the near-term planned workload, not the aspirational portfolio that the account team's optimistic estimate supports.
The buyer-side artefact reads three forecasts in parallel. The base case is the strictly-deployed workload. The moderate case is the deployed-plus-near-term-planned workload. The upside case is the deployed-plus-aspirational portfolio. The commitment is sized to the moderate case; the upside case is the headroom that the overage rate or the supplemental purchase covers.
The sizing is iterated quarterly. The actual consumption against each of the four workload components is read against the moderate-case forecast; the variance is the input to the next renewal-cycle commitment. The discipline aligns the renewal commitment to the actual consumption baseline rather than to the optimistic forecast from a prior cycle.
The senior-advisor read produces the renewal evidence pack: the deployed-workload inventory, the actual consumption rate per workload component, the moderate-case forecast against the new contract year, the credit-rate-table mapping at the renewal version. The wider seat-reassignment policy spoke reads the parallel discipline on the seat-based contracts.
The credit basket and rate-table mechanics that the sizing audit translates.
The downstream activation cadence that drives Data Cloud activation credits.
A senior Admodum Salesforce advisor will read your Data Cloud workload inventory, your consumption-rate baselines and your commitment-design artefact on a private call. Active renewal moments route to Renewal Programme.