ServicesSalesforce consultingArchitectureImplementationOrg health checkDevelopmentIntegrations and APIsData migrationTesting and QAManaged supportSpecialist supportMarketing Cloud auditDeliverability
SolutionsMarketing Cloud EngagementMarketing Cloud NextSalesforce + BrazeAccount EngagementData Cloud (Data 360)Identity resolutionInsights and segmentsAgentforce and AIMCP integrationsSales and Service CloudReal-time personalisationIntegration solutionsEnterprise AI integrationBy industry
ArchitectureSalesforce CRMData 360Salesforce + BrazeAgentforceCustomer 360API-led integrationEvent-drivenMCP host, client and serverIdentity and consentMCP securityData governanceCI/CD and releasesOur public MCP server
ResourcesEngineering journalDecision guidesSolution blueprintsSalesforce productsProjects and achievementsSales ROI calculatorWhere we workChecklists and templatesPlanning toolsReadiness assessmentGlossaryAbout GeekMidstOur approachOur expertiseContact
CompanyAbout GeekMidstOur approachDelivery methodologyTrust and evidenceProjectsAchievementsBook a consultationContactWhere we workSecurity and data
Book a Consultation

Salesforce Sales Forecasting Consulting

We design and configure Salesforce forecasting: forecast types, hierarchy and quotas, Einstein Forecasting prerequisites, Pipeline Inspection and Revenue Intelligence.

Consultant arranging cards into a reporting hierarchy as a sales manager adds coloured quota stickers

A forecast in Salesforce is only as good as the hierarchy, forecast types and opportunity data behind it. GeekMidst sets up and tidies Sales Cloud forecasting remotely from India, so managers submit and adjust numbers in Salesforce instead of spreadsheets. If Sales Cloud itself still needs building, start with Sales Cloud implementation. For a plain-English primer, read Salesforce forecasting explained.

The four tools, and what each needs

Pipeline Forecasting (formerly Collaborative Forecasts). Salesforce Help now says Pipeline Forecasting, while Trailhead and some prerequisites still say Collaborative Forecasts. Each forecast type combines an object, a measure, a date field and a hierarchy, for example Opportunity, Amount and Close Date, and up to four can be active. The forecast hierarchy follows the role hierarchy, but users must be enabled and forecast managers assigned. Quotas are set per user, period and forecast type.

Einstein Forecasting. It has not been retired: a Salesforce Help article published on 28 May 2026 documents current activation. Per that article you need:

  • Collaborative Forecasts with a user role hierarchy (territory forecasts aren't supported).
  • The Opportunity Revenue forecast type on the standard Amount field.
  • At least one forecasting user reporting to a forecast manager, and a Gregorian fiscal year.
  • A production org; it isn't available in sandboxes.
  • The Sales Cloud Einstein permission set licence.
  • At least 12 months of opportunity history, with Amount filled in on at least 80% of open opportunities.

Don't confuse it with Einstein Close Date Predictions, which a third-party source reports was retired.

Pipeline Inspection. It shows Einstein Opportunity Scoring, deal insights, 7- and 30-day activity metrics and a stakeholder panel. Its side-panel insights need at least one of Conversation Intelligence, Einstein Deal Insights, Einstein Email Insights or Einstein Opportunity Scoring. Check supported editions in Salesforce Help.

Revenue Intelligence (add-on). A premium analytics offering combining Sales Cloud with CRM Analytics Plus, including Predictive Forecasting, Pipeline Inspection and Revenue Insights dashboards. It is sold standalone or included in Max. Salesforce doesn't say whether Predictive Forecasting is the same as Einstein Forecasting, so we confirm what your licence covers.

What's included

AreaWhat we cover
Forecast designForecast types, measures, date fields, adjustments and quotas
HierarchyRole hierarchy review, forecast managers and enabled users
Data readinessStage, close date and Amount completeness checks
Einstein ForecastingPrerequisite check and activation in production
Pipeline InspectionSetup and the insights your licences support
Revenue IntelligenceA fit review against what you already own

How we work

  1. 01

    Discovery

    We review how managers forecast today, your role hierarchy and opportunity data quality.

  2. 02

    Design

    We agree forecast types, quota sources and who can adjust what.

  3. 03

    Build

    We configure forecasting in a sandbox, then in production where Einstein features require it.

  4. 04

    Test

    Managers check rollups against known numbers before anyone relies on them.

  5. 05

    Launch

    We switch forecasting on team by team with short, role-based training.

  6. 06

    Support

    We review data gaps after the first forecast cycles.

Prerequisites and licences

Salesforce describes Core as including "advanced pipeline management and forecasting". Einstein Forecasting needs the Sales Cloud Einstein permission set licence, Predictive Forecasting is available for purchase on Core, and Revenue Intelligence is a paid add-on or part of Max. Edition placement couldn't be fully confirmed, so check with your account team.

Who it suits

Teams whose forecast lives in spreadsheets, orgs with forecasting switched on but unused, and teams weighing Revenue Intelligence.

Common mistakes

  • Activating Einstein Forecasting before opportunity history meets the requirements.
  • A role hierarchy that doesn't match who forecasts for whom.
  • Too many forecast types, so nobody knows which number counts.

Workflow diagram

Explore how the pieces fit together. Select a step to read what happens there.

Workflow

Sales forecasting

Open full size
Sales forecastingReps update their deals, stages map to forecast categories and amounts roll up the forecast hierarchy. Managers review changes and either accept the roll-up or record an adjustment, and leadership compares commit with quota on dashboards.Sales forecastingSales repSales CloudSales managerLeadershipYesNoAdjustedDeals updated: Amount, close date, stage. Forecasts are built from opportunity data, so the weekly habit of updating amount, close date and stage matters more than any forecasting setting.Deals updatedAmount, close date,stageCategory mapped: Pipeline, Best Case, Commit. Each stage maps to a forecast category. Reps can override the category on a deal where allowed, which is how their judgement enters the forecast.Category mappedPipeline, Best Case,CommitHierarchy roll-up: By forecast type and period. Amounts roll up through the forecast hierarchy, usually based on the role hierarchy, for each forecast type such as opportunity revenue or product family.Hierarchy roll-upBy forecast type andperiodManager review: Changes since last week. Managers look at what moved: new deals, pushed close dates and category changes. Reviewing changes is faster and more useful than re-reading every deal.Manager reviewChanges since lastweekForecast realistic?. The manager compares the roll-up with their own judgement and with past results. A big gap is a reason to inspect specific deals, not only to change the number.Forecast realistic?Adjustment: Manager records a reason. Where adjustments are enabled, a manager can adjust a forecast without editing the deals. Ask for a reason, so later reviews can see why the number differed.AdjustmentManager records areasonLeadership view: Commit vs quota. Leaders see commit, best case and pipeline against quota for the period. Quotas are loaded per user and period, often from a planning spreadsheet or system.Leadership viewCommit vs quotaForecast set: Weekly trend kept. Comparing each week with the last shows whether the forecast is converging. Tracking accuracy over several quarters is what builds trust in the number.Forecast setWeekly trend keptStartSystem or platformPerson or teamDecisionProcess stepEnd or outcomeOriginal GeekMidst explanatory diagram, not an official Salesforce reference.

Select any step in the diagram, or use Step through, to see what happens at that point and why.

Text version: every step in order
  1. Deals updated Sales repAmount, close date, stage

    Forecasts are built from opportunity data, so the weekly habit of updating amount, close date and stage matters more than any forecasting setting.

    Next: Category mapped

  2. Category mapped Sales CloudPipeline, Best Case, Commit

    Each stage maps to a forecast category. Reps can override the category on a deal where allowed, which is how their judgement enters the forecast.

    Next: Hierarchy roll-up

  3. Hierarchy roll-up Sales CloudBy forecast type and period

    Amounts roll up through the forecast hierarchy, usually based on the role hierarchy, for each forecast type such as opportunity revenue or product family.

    Next: Manager review

  4. Manager review Sales managerChanges since last week

    Managers look at what moved: new deals, pushed close dates and category changes. Reviewing changes is faster and more useful than re-reading every deal.

    Next: Forecast realistic?

  5. Forecast realistic? Sales manager

    The manager compares the roll-up with their own judgement and with past results. A big gap is a reason to inspect specific deals, not only to change the number.

    Next: Yes: Leadership view; No: Adjustment

  6. Leadership view LeadershipCommit vs quota

    Leaders see commit, best case and pipeline against quota for the period. Quotas are loaded per user and period, often from a planning spreadsheet or system.

    Next: Forecast set

  7. Adjustment Sales CloudManager records a reason

    Where adjustments are enabled, a manager can adjust a forecast without editing the deals. Ask for a reason, so later reviews can see why the number differed.

    Next: Adjusted: Leadership view

  8. Forecast set LeadershipWeekly trend kept

    Comparing each week with the last shows whether the forecast is converging. Tracking accuracy over several quarters is what builds trust in the number.

    End of the flow.

Reps update their deals, stages map to forecast categories and amounts roll up the forecast hierarchy. Managers review changes and either accept the roll-up or record an adjustment, and leadership compares commit with quota on dashboards. Original GeekMidst explanatory diagram; not an official Salesforce reference architecture.

For a worked architecture, see the forecasting and Revenue Intelligence solution. For dashboards beyond forecasts, see Tableau and CRM Analytics consulting.

Questions we hear

Is Einstein Forecasting being retired?
No retirement notice was found. Salesforce Help published current activation requirements on 28 May 2026. The retired feature people often mean is Einstein Close Date Predictions.
Can we test Einstein Forecasting in a sandbox?
No. Per Salesforce Help it works in production orgs only, so we plan validation around that.
Do we need Revenue Intelligence to forecast?
No. Pipeline Forecasting works on its own. Revenue Intelligence adds CRM Analytics Plus dashboards and predictive features.
Can Einstein Forecasting use territory forecasts?
Not per the current Help article, which requires a user role hierarchy.

Get a forecast your managers trust

Share how you forecast today and we will suggest which Salesforce tools to set up first.

Talk to us →

Next step: Salesforce Sales Forecasting Consulting

  1. We read it A practitioner reads your message and replies by email.
  2. Short call We confirm goals, constraints and what success looks like.
  3. Written scope You get a scope and estimate before any work starts.

Tell us what you are trying to fix.

Share your Salesforce setup, goals and constraints. A practitioner reads every message and replies with questions, first thoughts or an honest view of whether you need outside help at all.

Talk to a Salesforce Expert
Book a Consultation