Skip to content
cccskills
FreePublished on GitHub

revenue-intelligence-setup

Revenue Intelligence setup: activating the RI app and its CRM Analytics assets, Einstein deal insights, the opportunity-change waterfall, and forecast-accuracy analytics for sales leaders. NOT for configuring the Pipeline Inspection view, its metrics and review cadence - use admin/pipeline-review-design. NOT for forecast types, categories, rollups and quotas - use admin/collaborative-forecasts.

The English summary is being prepared. Showing the original description.

PranavNagrecha/AwesomeSalesforceSkills
Works withSalesforce

Run score Not tested

See how to install

Files included (7)

  • SKILL.md6.7 KB
  • references/examples.md7.3 KB
  • references/gotchas.md5.9 KB
  • references/llm-anti-patterns.md3.1 KB
  • references/well-architected.md7.7 KB
  • scripts/check_revenue_intelligence_setup.py3.5 KB
  • templates/revenue-intelligence-setup-template.md639 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Revenue Intelligence Setup

Activate when standing up Salesforce Revenue Intelligence (RI) for a sales organization: pipeline inspection for managers, deal-change waterfall for leaders, forecast accuracy analytics, and Einstein-powered deal insights. RI rides on top of Sales Cloud + CRM Analytics and depends on clean Opportunity discipline to work.

Before Starting

  • Confirm Revenue Intelligence license. Distinct from base Sales Cloud; the shipped app and its CRM Analytics assets only appear when enabled.
  • Audit Opportunity hygiene. RI surfaces deal deltas and coaching signals; if Opportunities have stale close dates, zero amounts, or skipped stages, the intelligence is garbage in, garbage out.
  • Decide the forecasting model. Collaborative Forecasts must be enabled, with revenue types and hierarchy confirmed — RI dashboards filter and segment by these.

Core Concepts

Pipeline Inspection

The headline UI for sales managers. Shows all team Opportunities with deal-change deltas: stage changes, amount changes, close-date slips, new deals, closed-won/lost. Driven by a nightly Opportunity History snapshot the RI package builds.

Deal Insights

Einstein-generated insights per Opportunity — sentiment from emails, activity gaps, champion turnover warnings, similar-deal outcomes. Requires Einstein Activity Capture (EAC) for emails and Sales Engagement signals.

Forecast Accuracy

RI dashboards compare forecasted revenue to actual closed revenue, broken down by manager, rep, product, segment. Requires historical forecast snapshots — if you just turned on Collaborative Forecasts, there is no history to analyze yet.

Underlying data: Opportunity History

RI pivots on OpportunityFieldHistory and OpportunityHistory. Field History tracking on Amount, Close Date, Stage, Forecast Category is mandatory; without it the waterfall is empty.

Common Patterns

Pattern: Weekly forecast call with Pipeline Inspection

Manager opens Pipeline Inspection Monday morning, filters to "Deals Slipped This Week" + "Amount Changed Last 7 Days". Review list with each rep; coaching notes captured on the Opportunity.

Pattern: Quarter-end deal review with waterfall

Sales leader opens the shipped dashboard showing starting pipeline → won → lost → slipped → added. Used for the quarterly business review conversation.

Pattern: Forecast accuracy trend

Head of sales reviews forecast vs actual across the last four quarters per segment. Informs where coaching investment drives forecast quality.

Decision Guidance

SituationRecommended ApproachReason
Manager needs deal-change visibilityPipeline InspectionShipped view, no rebuild
Leader quarterly reviewShipped RI dashboardsDon't hand-build
AI deal scoringEinstein Opportunity ScoringNative, no custom ML
Activity-based insightsEinstein Activity CaptureFeeds RI insights
Custom metric not shippedCRM Analytics recipe extending RI datasetReuses existing dataset

Recommended Workflow

  1. Enable Revenue Intelligence license; install the RI app from AppExchange if not auto-provisioned.
  2. Turn on Collaborative Forecasts with the organization's forecast categories and hierarchy.
  3. Enable Opportunity Field History tracking on Amount, Close Date, Stage, Forecast Category (minimum).
  4. Deploy Einstein Activity Capture for emails/events to power deal insights.
  5. Grant the Revenue Intelligence permission set group to managers and leaders; validate Pipeline Inspection loads.
  6. Customize dashboards: change defaults on filters, drill-down, and saved views per leadership segment.
  7. Plan rollout: 30-minute manager training, weekly coaching cadence tied to Pipeline Inspection filters.

Review Checklist

  • RI license enabled and app visible
  • Collaborative Forecasts set up with correct hierarchy
  • Opportunity Field History tracking on all pivot fields
  • Einstein Activity Capture deployed to sales org
  • Pipeline Inspection loads for a test manager with expected data
  • Shipped dashboards render with no zero/empty sections
  • Manager coaching cadence documented and trained

Salesforce-Specific Gotchas

  1. Opportunity History tracking limits fields. You can only track 20 fields per object; choose wisely — removing history later loses the pre-removal data.
  2. Einstein Activity Capture is sticky. Once deployed with Exchange sync, migrating off is painful; pilot carefully with a small group first.
  3. RI dashboards are partitioned by forecast hierarchy. If forecast hierarchy and role hierarchy diverge, managers may not see their own team's data.

Output Artifacts

ArtifactDescription
RI activation runbookLicense, field history, EAC, dashboards
Adoption planTraining, cadence, coaching integration
Dashboard customization guideSaved views per leader segment
Forecast accuracy baselineFirst snapshot to measure improvement

Related Skills

  • admin/collaborative-forecasts — upstream setup requirement
  • admin/einstein-activity-capture-setup — insight source
  • admin/analytics-dashboard-design — custom extensions

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

acceptance-criteria-given-when-then

Free

Use this skill when writing test-first, behavior-driven acceptance criteria in Given/When/Then format for a Salesforce user story. Covers happy path, edge cases, negative paths, permission boundaries, and data-state preconditions so the AC block can drive UAT scripts and Apex test design downstream. Trigger keywords: given when then, gherkin, behavior driven AC, test first acceptance criteria, scenario outline, BDD acceptance criteria. NOT for the user-story format itself (use admin/user-story-writing-for-salesforce). NOT for UAT script writing (use admin/uat-test-case-design). NOT for Apex test method generation (use agents/test-class-generator). NOT for high-level UAT planning (use admin/uat-and-acceptance-criteria). More triggers: acceptance criteria record, ac_id, req_id on a criterion, artefact under test, negative case for a rule-type requirement, no-match fall-through criterion, oracle for a Then clause, test type apex flow manual, criteria linter, check_ac_format.py, --manifest-dir.

The English summary is being prepared. Showing the original description.

PranavNagrecha/AwesomeSalesforceSkills23Updated Oct 21, 2026

activity-and-task-patterns

Free

Task and Event objects: polymorphic WhatId/WhoId, Activity object model, ActivityHistory vs OpenActivity, activity timeline customization, bulk task creation, Einstein Activity Capture boundaries. NOT for turning on EAC or calendar sync — use admin/einstein-activity-capture-setup. NOT for Email-to-Case — use admin/case-management-setup. Covers ActivitiesSettings metadata, enableActivities, shared Task/Event custom fields and FLS, TaskStatus value sets, Shared Activities and TaskRelation/EventRelation, recurring and child activities, and partial-success bulk DML on Task.

The English summary is being prepared. Showing the original description.

PranavNagrecha/AwesomeSalesforceSkills23Updated Oct 21, 2026

agent-action-error-handling

Free

Design Invocable Apex actions that return deterministic, agent-friendly errors instead of surfacing raw exceptions to the LLM. NOT for authoring the action itself — @InvocableMethod schema, labels, security context — use agentforce/custom-agent-actions-apex. NOT for the Apex tests that force each error branch — use agentforce/agent-action-unit-tests.

The English summary is being prepared. Showing the original description.

PranavNagrecha/AwesomeSalesforceSkills23Updated Oct 21, 2026

agent-action-input-slot-extraction

Free

Use when designing how an Agentforce agent extracts structured input parameters (slots) from a user's natural-language utterance to invoke an action. Triggers: 'agent extract date from user', 'agent action argument extraction', 'agentforce slot filling', 'agent invocable input mapping', 'agent fails to fill required parameter'. NOT for action authoring (use agentforce/agent-actions) or for prompt-template variable binding (use agentforce/prompt-builder-templates).

The English summary is being prepared. Showing the original description.

PranavNagrecha/AwesomeSalesforceSkills23Updated Oct 21, 2026

agent-action-unit-tests

Free

Apex test patterns for @InvocableMethod agent actions: per-reason-code branch coverage, bulk safety, callout mocking, deterministic assertions. NOT for testing whether the agent routes to the right topic or answers well — use agentforce/agent-testing-and-evaluation. NOT for designing the error envelope the tests assert on — use agentforce/agent-action-error-handling.

The English summary is being prepared. Showing the original description.

PranavNagrecha/AwesomeSalesforceSkills23Updated Oct 21, 2026

agent-actions

Free

Designing or reviewing Agentforce actions: Flow actions, Apex invocable actions, prompt-template actions, action naming, input and output contracts, confirmation requirements, and safe error behavior. Triggers: 'agent actions', 'build an agent that can look up an order', 'make the agent able to check order status', 'give the agent a capability', 'agent that can retrieve a record', 'flow action for agent', 'agent invocable action', 'action schema design'. NOT for writing the Apex class itself — use agentforce/custom-agent-actions-apex. NOT for the reason_code error envelope that stops an agent retry loop — use agentforce/agent-action-error-handling.

The English summary is being prepared. Showing the original description.

PranavNagrecha/AwesomeSalesforceSkills23Updated Oct 21, 2026

See all skills by PranavNagrecha

Report a problem with this skill