Portfolio strategy · Sales forecasting · Customer value
What evidence belongs in a cross-sell forecast?
Identify customers who can use the additional product, test the incremental value and track the path from interest to a completed sale. Keep eligibility, conversion and delivery assumptions visible.
Define an eligible customer group
Begin with a specific customer need that the additional product could serve. Explain what the customer gains beyond the capabilities they already have. Salesforce’s cross-selling guidance emphasizes matching complementary products to current needs; a portfolio inventory alone leaves that fit untested.
Create an eligibility view for each proposed combination. Check the relevant product version, deployment arrangement, integration requirements, purchasing rights and implementation capacity. Record which customers can use the offer now and which require a prerequisite change. Avoid treating a planned migration as completed eligibility.
Inspect overlap from the customer’s perspective. Ask which existing work or spending the second product would replace and which capability it would add. Where the products duplicate each other, test whether the offer provides enough additional value to justify adoption effort.
Observe the path from interest to use
Test the offer with a defined group and record the next meaningful action: a qualified conversation, an agreed evaluation, a purchase or successful implementation. Track the denominator at every step. A response rate among selected enthusiasts should remain attached to that selection process.
Choose success measures and an observation period before reviewing results. Microsoft Research’s experimentation guidance recommends a clear hypothesis, relevant metrics and a suitable unit of assignment. Where a controlled offer test is feasible, involve an analyst in its design, including account-level effects and sample-size limitations.
Where randomization is impractical, use the pilot to document objections, buying steps and delivery constraints. Treat its conversion rate as evidence from that group and period. Include customers who decline or cannot implement; those outcomes help explain the limits of the opportunity.
Build the forecast from dated assumptions
Separate eligible accounts, qualified opportunities, expected purchases and completed sales. Salesforce’s forecasting documentation distinguishes opportunity stages and forecast categories. Adopt definitions that the sales team can apply consistently, then inspect the underlying customer evidence rather than relying solely on the category label.
Model the time needed for customer approval, prerequisites and implementation. Keep the expected purchase date distinct from the date the product can be used. Ask finance to determine how any proposed commercial arrangement maps to recognized revenue; a sales forecast should not silently make that accounting decision.
Version the assumptions for eligibility, conversion, value and timing. Show how the result changes if migration slows, an offer replaces existing spend or the sales cycle extends. Reconcile later outcomes with the original assumptions so the next forecast reflects observed customer behavior and actual delivery capacity.