Part 20: Sales Cloud in Salesforce
Welcome to Part 20 of the Salesforce series — and this is the big one. Sales Cloud is the flagship product that put Salesforce on the map. It is the core CRM offering that most organizations purchase first, and it touches nearly every aspect of the sales process, from initial marketing campaigns all the way through to signed contracts and fulfilled orders.
This post is intentionally comprehensive. Sales Cloud covers a massive surface area, and understanding how all the pieces fit together is critical for any Salesforce administrator or consultant. We will walk through every major object, explain the configuration options, discuss licensing nuances, and finish with a hands-on project that ties everything together.
What is Sales Cloud?
Sales Cloud is Salesforce’s core CRM product designed to support the entire sales lifecycle. It provides tools for managing leads, tracking opportunities, generating quotes, processing orders, and forecasting revenue. At its heart, Sales Cloud is about giving sales teams a structured, automated, and data-driven way to move prospects through a pipeline and close deals.
Sales Cloud includes:
- Lead Management — Capture, qualify, route, and convert leads into accounts, contacts, and opportunities.
- Opportunity Management — Track deals through stages, assign teams, and forecast revenue.
- Campaign Management — Run marketing campaigns and track their influence on pipeline.
- Product and Pricebook Management — Define what you sell and at what price.
- Quote Management — Generate formal quotes from opportunities.
- Order and Contract Management — Process orders and manage contractual agreements.
- Forecasting — Predict revenue based on opportunity data.
- Territory Management — Organize your sales team by geography, product line, or other dimensions.
Sales Cloud is not just a set of objects — it is a set of features and automation built on top of those objects. Many of the objects (Accounts, Contacts, Opportunities) exist in every Salesforce org, but the Sales Cloud license unlocks specific features, automation capabilities, and page layouts that make them work together as a cohesive sales platform.
What License Do You Need to Use Sales Cloud?
This is one of the most commonly misunderstood areas in Salesforce licensing. Here is what you need to know:
Sales Cloud Editions
| Edition | Key Inclusions | Typical Use Case |
|---|---|---|
| Sales Cloud Starter | Basic lead, contact, opportunity management | Very small teams, simple sales processes |
| Sales Cloud Professional | Full lead management, campaigns, forecasting, quotes | Growing teams with structured processes |
| Sales Cloud Enterprise | Everything in Professional plus workflow automation, approval processes, advanced reporting | Mid-market and enterprise organizations |
| Sales Cloud Unlimited | Everything in Enterprise plus premier support, full sandbox, additional storage | Large enterprises with complex requirements |
What Actually Requires a Sales Cloud License?
This is where it gets nuanced. Many objects that people associate with Sales Cloud are actually available in any Salesforce edition:
| Object/Feature | Requires Sales Cloud License? | Notes |
|---|---|---|
| Accounts | No | Available in all editions |
| Contacts | No | Available in all editions |
| Opportunities | No | Available in all editions (basic) |
| Leads | No | Available in all editions |
| Campaigns | Yes (partially) | Basic campaigns available, but full Campaign Member management and campaign influence require Sales/Marketing Cloud |
| Products & Pricebooks | No | Available in all editions |
| Quotes | Yes | Requires Sales Cloud or specific quote permissions |
| Orders | No | Available in all editions |
| Contracts | No | Available in all editions |
| Forecasting | Yes | Collaborative Forecasting requires Sales Cloud |
| Territory Management | Yes | Enterprise Territory Management requires Enterprise+ with Sales Cloud |
| Opportunity Splits | Yes | Requires Sales Cloud Enterprise+ |
| Opportunity Teams | Yes | Requires Sales Cloud |
The key takeaway: many objects exist in every org, but the advanced features, automation, and integrations that make them powerful often require a Sales Cloud license. You can create an Opportunity in a Platform license org, but you will not get forecasting, splits, or team selling capabilities.
What Are the Major Out-of-the-Box Sales Cloud Objects?
Sales Cloud comes with a rich data model. Here is the complete picture of the major objects and how they relate to each other:
Core Objects
- Lead — An unqualified prospect. Exists independently until converted.
- Account — A company or organization you do business with.
- Contact — A person associated with an Account.
- Opportunity — A potential deal, tracked through stages to close.
- Campaign — A marketing initiative (email blast, trade show, webinar).
- Campaign Member — The junction between a Campaign and a Lead or Contact.
- Product — Something you sell (a good or service).
- Pricebook — A collection of products with specific prices.
- Pricebook Entry — The junction between a Product and a Pricebook (defines the price).
- Opportunity Product (OpportunityLineItem) — A product added to an Opportunity with quantity and price.
- Quote — A formal price proposal generated from an Opportunity.
- Quote Line Item — A product on a Quote.
- Order — A confirmed request to purchase.
- Order Product (OrderItem) — A product on an Order.
- Contract — A formal agreement between your organization and an Account.
- Forecast — A revenue prediction based on Opportunity data.
- Territory — A logical grouping for assigning accounts and opportunities to sales teams.
The Sales Cloud Data Flow
The typical flow through Sales Cloud objects looks like this:
Campaign → Lead → (Convert) → Account + Contact + Opportunity
↓
Opportunity Products (from Pricebook)
↓
Quote
↓
Order
↓
Contract
This flow is not rigid — organizations customize it heavily — but it represents the standard path that Sales Cloud supports out of the box.
Campaigns, Campaign Members, and List Emailing
What Are Campaigns?
A Campaign in Salesforce represents any marketing initiative — an email blast, a trade show, a webinar series, a social media push, or a direct mail effort. Campaigns let you track the cost of marketing activities and measure their effectiveness by linking them to the leads and opportunities they influence.
Key Campaign Fields
| Field | Purpose |
|---|---|
| Campaign Name | The name of the marketing initiative |
| Type | The category (Email, Trade Show, Webinar, etc.) |
| Status | Planning, Active, Completed, Aborted |
| Start Date / End Date | The campaign duration |
| Expected Revenue | How much revenue you expect this campaign to generate |
| Budgeted Cost | How much you plan to spend |
| Actual Cost | How much you actually spent |
| Expected Response | The expected response rate (percentage) |
| Num Sent | How many people received the campaign |
| Parent Campaign | Allows you to create campaign hierarchies |
Campaign Hierarchies
Campaigns support parent-child relationships, which is extremely useful for organizing multi-touch marketing efforts:
Annual Conference 2026 (Parent)
├── Pre-Conference Email Series (Child)
├── Conference Booth (Child)
├── Post-Conference Follow-Up (Child)
└── Conference Social Media Push (Child)
Parent campaigns automatically roll up statistics (responses, leads generated, opportunities influenced) from their child campaigns, giving you a holistic view of complex marketing initiatives.
What Are Campaign Members?
A Campaign Member is the junction object that links a Lead or Contact to a Campaign. Each Campaign Member record tracks:
- Status — The member’s response status (Sent, Responded, Attended, etc.)
- First Responded Date — When the member first responded
- Lead or Contact — Which person is associated
You can customize Campaign Member Statuses per campaign. For example, a webinar campaign might have statuses like: Invited, Registered, Attended, No Show. A trade show campaign might have: Invited, Visited Booth, Requested Demo.
Adding Campaign Members
There are several ways to add members to a campaign:
- Manually — Add individual leads or contacts from the Campaign Member related list.
- From a Report — Run a report of leads or contacts, select them, and add to a campaign.
- From a List View — Select leads or contacts from a list view and add them.
- Import — Use the Data Import Wizard to import campaign members from a CSV.
- Via API — Programmatically add members through Apex or integrations.
List Emailing for Campaigns
Salesforce provides a basic list email feature that lets you send emails to Campaign Members directly from the Campaign record. Here is how it works:
- Navigate to the Campaign.
- Click Send List Email from the Campaign Member related list.
- Choose an email template.
- Select which Campaign Members to send to (based on status).
- Send the email.
Important limitations of list emailing:
- It is not a marketing automation tool — it does not provide open tracking, click tracking, or sophisticated analytics.
- There is a daily limit on mass emails (typically 5,000 per day for most editions).
- Emails are sent from the individual user’s email address.
- For serious email marketing, you should use Marketing Cloud, Pardot (Marketing Cloud Account Engagement), or a third-party tool.
Campaign Influence
Campaign Influence tracks which campaigns contributed to closing an Opportunity. Salesforce supports two models:
- Primary Campaign Source — A single campaign gets credit for influencing an Opportunity (simple but limited).
- Customizable Campaign Influence — Multiple campaigns can share credit for an Opportunity, with configurable attribution models (first touch, last touch, even distribution, or custom).
To set up Customizable Campaign Influence, go to Setup → Campaign Influence → Enable Customizable Campaign Influence.
Leads
What Is a Lead?
A Lead represents an unqualified prospect — someone who has expressed interest but has not yet been vetted by your sales team. Leads are intentionally separate from Accounts and Contacts because they represent potential rather than confirmed business relationships.
Key Lead Fields
| Field | Purpose |
|---|---|
| Name | First and last name of the prospect |
| Company | The organization they belong to |
| Title | Their job title |
| Email / Phone | Contact information |
| Lead Source | Where the lead came from (Web, Trade Show, Referral, etc.) |
| Lead Status | Where they are in the qualification process (New, Working, Qualified, Unqualified) |
| Rating | Hot, Warm, or Cold |
| Industry | The prospect’s industry |
| Annual Revenue / Employees | Company size indicators |
Lead Lifecycle
The standard lead lifecycle in Sales Cloud:
Lead Created → Lead Assigned → Lead Worked → Lead Qualified → Lead Converted
↓
Lead Unqualified → Lead Recycled or Deleted
Setting Up Lead Conversion
Lead Conversion is one of the most important processes in Sales Cloud. When a lead is qualified, you convert it, which creates (or maps to existing) Account, Contact, and optionally Opportunity records.
How to configure lead conversion:
-
Map Lead Fields to Account, Contact, and Opportunity Fields
- Go to Setup → Object Manager → Lead → Fields & Relationships → Map Lead Fields.
- For each custom lead field, specify which Account, Contact, or Opportunity field it should map to upon conversion.
- Standard fields (Name, Company, Email, Phone) are mapped automatically.
-
Configure Converted Lead Status
- Go to Setup → Object Manager → Lead → Fields & Relationships → Lead Status.
- Ensure you have at least one status value marked as Converted (this is the status the lead moves to upon conversion).
-
Handle Duplicate Matching
- During conversion, Salesforce checks for existing Accounts and Contacts that match the lead’s data.
- You can configure Duplicate Rules and Matching Rules to control how strict this matching is.
-
Conversion Automation with Apex
- For complex conversion scenarios, you can use the
Database.convertLead()method in Apex to programmatically convert leads with custom logic.
- For complex conversion scenarios, you can use the
Lead Conversion Best Practices:
- Always map custom fields before your first conversion — unmapped fields lose their data.
- Decide upfront whether to create new Opportunities on conversion or not (this is a checkbox during conversion).
- Use validation rules on the Lead to ensure data quality before conversion.
- Consider using a Flow to automate post-conversion actions (assigning the opportunity, creating tasks, etc.).
Setting Up Lead Auto-Response Rules
Auto-Response Rules automatically send an email to a lead when they are created (typically through a web form). This acknowledges receipt and sets expectations.
How to set up Auto-Response Rules:
- Go to Setup → Lead Auto-Response Rules.
- Click New to create a new rule.
- Mark it as Active (only one rule can be active at a time).
- Create Rule Entries — each entry defines criteria and an email template.
- Rule entries are evaluated in order; the first match wins.
- Example: If Lead Source = “Website” and Country = “US”, send the US welcome email. If Lead Source = “Website” and Country = “UK”, send the UK welcome email.
- Create or select Email Templates for each rule entry.
Auto-Response Rule evaluation order:
Lead Created → Evaluate Rule Entry 1 → Match? → Send Email
↓ No
Evaluate Rule Entry 2 → Match? → Send Email
↓ No
Evaluate Rule Entry 3 → Match? → Send Email
↓ No
No email sent
Lead Assignment Rules
While we are on the topic, Lead Assignment Rules work similarly to Auto-Response Rules but control who the lead is assigned to:
- Go to Setup → Lead Assignment Rules.
- Create a new rule and mark it as Active.
- Create Rule Entries with criteria and assignees (user or queue).
- Leads matching the criteria are automatically assigned.
Pro tip: Always have a catch-all rule entry at the bottom that assigns to a queue so no lead falls through the cracks.
Web-to-Lead (and Why Not to Use It)
Web-to-Lead is Salesforce’s built-in mechanism for capturing leads from a web form. You go to Setup → Web-to-Lead, generate an HTML form, and embed it on your website. When someone fills it out, a Lead is created in Salesforce.
Why you should generally avoid Web-to-Lead:
- No CAPTCHA or spam protection — Your org will get flooded with spam leads. There is no built-in bot protection.
- Limited to 500 leads per day — If you exceed this, leads are queued and may be delayed or lost.
- No error handling — If the lead creation fails (validation rule, required field missing), the user gets no feedback, and you get no notification.
- No conditional logic — The form is static HTML with no ability to show/hide fields or validate input before submission.
- No styling control — The generated HTML is bare-bones and does not match your website design without significant CSS work.
- Security concerns — The form posts directly to Salesforce, exposing your org ID in the HTML source.
What to use instead:
- Salesforce Forms (if you have the license) or a third-party form builder (Formstack, Typeform, Gravity Forms) that integrates with Salesforce via API.
- Marketing Cloud / Pardot landing pages — Purpose-built for lead capture with tracking and analytics.
- Custom web forms with server-side integration that calls the Salesforce REST API to create leads — this gives you full control over validation, spam protection, and error handling.
- Experience Cloud (Community) forms if you are already using that product.
Products, Pricebooks, and Pricebook Entries
What Are Products?
A Product in Salesforce represents something your company sells — a physical good, a software license, a consulting service, a subscription, or anything else with a price. Products are defined once and then added to Pricebooks at specific prices.
Key Product Fields
| Field | Purpose |
|---|---|
| Product Name | The name of the product |
| Product Code | An internal SKU or identifier |
| Product Description | A description of the product |
| Product Family | A category (Hardware, Software, Services, etc.) |
| Active | Whether the product is currently available for sale |
| Is Archived | Whether the product has been archived |
What Are Pricebooks?
A Pricebook is a collection of products with specific prices. Every Salesforce org has a Standard Pricebook that serves as the master price list. You can then create Custom Pricebooks for different scenarios:
- A Retail Pricebook with standard retail prices.
- A Partner Pricebook with discounted partner prices.
- A Government Pricebook with GSA schedule pricing.
- A Regional Pricebook for different geographic markets.
What Are Pricebook Entries?
A Pricebook Entry is the junction between a Product and a Pricebook. It defines the price of a specific product in a specific pricebook. The same product can have different prices in different pricebooks.
The Product-Pricebook Data Model
Product ──── Pricebook Entry (Standard Price) ──── Standard Pricebook
│
├──── Pricebook Entry ($100) ──── Retail Pricebook
│
├──── Pricebook Entry ($80) ──── Partner Pricebook
│
└──── Pricebook Entry ($75) ──── Government Pricebook
Critical rule: A product must have a Standard Pricebook Entry before it can be added to any Custom Pricebook. The Standard Pricebook entry establishes the product’s existence in the pricing system.
How to Set Up Products
- Go to Setup → Object Manager → Product → Fields & Relationships.
- Configure the Product Family picklist with your categories (Hardware, Software, Services, Support, etc.).
- Navigate to the Products tab.
- Click New to create a product.
- Fill in the Product Name, Product Code, Product Family, and Description.
- Check Active to make it available.
- Click Save.
How to Set Up Pricebooks
- Navigate to the Pricebooks tab (you may need to add it to your app).
- Click New Pricebook.
- Enter the Pricebook Name and Description.
- Check Active.
- Click Save.
How to Set Up Pricebook Entries
- Navigate to a Product record.
- Under the Pricebook Entries related list, click Add Standard Price.
- Enter the standard price (list price).
- Click Save.
- Then click Add to Pricebook to add the product to custom pricebooks at custom prices.
Alternatively, from a Pricebook record:
- Navigate to the Pricebook.
- Under the Pricebook Entries related list, click Add Products.
- Select the products and set their prices for this pricebook.
Multiple Pricebooks
Using multiple pricebooks is a powerful strategy for handling different pricing tiers. Here is how it works in practice:
- Each Opportunity is associated with one Pricebook. When you add products to an opportunity, they come from that pricebook.
- If you need to change the pricebook on an opportunity that already has products, you must remove the existing products first.
- Sales reps select the appropriate pricebook when adding products to an opportunity.
- You can use record types on Opportunities or validation rules to enforce which pricebook should be used for certain deal types.
Pricebook selection strategy example:
| Customer Type | Pricebook | Discount Level |
|---|---|---|
| New Customer | Standard Retail | 0% |
| Existing Customer (Renewal) | Renewal Pricebook | 10% off |
| Channel Partner | Partner Pricebook | 25% off |
| Government | Government Pricebook | GSA Schedule |
| Internal Use | Internal Pricebook | Cost only |
Multi-Currency Pricebooks
If your organization sells internationally, you will likely enable Multi-Currency in Salesforce. This affects pricebooks significantly:
How to enable Multi-Currency:
- Go to Setup → Company Information → Currency Settings.
- Enable Multiple Currencies (this is irreversible).
- Add the currencies you need and set exchange rates.
How Multi-Currency works with Pricebooks:
- Each Pricebook Entry has a Currency field.
- You can have the same product in the same pricebook at different prices in different currencies.
- Exchange rates are managed centrally in Setup and can be updated manually or via the API.
- Advanced Currency Management (dated exchange rates) lets you maintain historical exchange rates so past opportunity values remain accurate.
Multi-Currency Pricebook Entry example:
| Product | Pricebook | Currency | Price |
|---|---|---|---|
| Enterprise License | Standard | USD | $10,000 |
| Enterprise License | Standard | EUR | €9,200 |
| Enterprise License | Standard | GBP | £8,000 |
| Enterprise License | APAC | JPY | ¥1,100,000 |
| Enterprise License | APAC | AUD | $14,500 |
Product and Pricebook Limitations
| Limitation | Details |
|---|---|
| Standard Pricebook required first | You must create a Standard Pricebook Entry before adding a product to any custom pricebook |
| One pricebook per opportunity | An opportunity can only be associated with one pricebook at a time |
| No pricebook change with products | You cannot change an opportunity’s pricebook if it already has products — you must remove them first |
| No product versioning | There is no built-in way to version products — you must archive old products and create new ones |
| Schedule limitations | Product schedules (quantity and revenue schedules) have limited flexibility |
| No bundle support OOTB | Product bundling requires CPQ or custom development |
| Multi-currency is irreversible | Once enabled, you cannot disable multi-currency |
| Price overrides | Sales reps can override prices on opportunity products unless you restrict this with validation rules or field-level security |
Opportunities
What Is an Opportunity?
An Opportunity represents a qualified deal — a potential sale that your team is actively working. It is the central object in Sales Cloud and is where most of the sales process tracking happens.
Key Opportunity Fields
| Field | Purpose |
|---|---|
| Opportunity Name | The name of the deal |
| Account | The account (company) associated with the deal |
| Close Date | When you expect the deal to close |
| Stage | Where the deal is in your sales process |
| Amount | The total value of the deal |
| Probability | The likelihood of closing (auto-set based on stage) |
| Forecast Category | How this opportunity rolls up into forecasts |
| Type | New Business, Existing Business, Renewal, etc. |
| Lead Source | Where this opportunity originated |
| Next Step | The next action item |
| Primary Campaign Source | The campaign that generated this opportunity |
Opportunity Stages
Opportunity Stages are the backbone of your sales process. They define the steps a deal goes through from creation to close. Each stage has a Probability and a Forecast Category associated with it.
Example stage configuration:
| Stage | Probability | Forecast Category | Description |
|---|---|---|---|
| Prospecting | 10% | Pipeline | Initial outreach and qualification |
| Discovery | 20% | Pipeline | Understanding the customer’s needs |
| Proposal | 50% | Best Case | Formal proposal submitted |
| Negotiation | 75% | Commit | Terms being negotiated |
| Closed Won | 100% | Closed | Deal won |
| Closed Lost | 0% | Omitted | Deal lost |
How to configure Opportunity Stages:
- Go to Setup → Object Manager → Opportunity → Fields & Relationships → Stage.
- Edit the picklist values.
- For each value, set the Probability and Forecast Category.
- If using Sales Processes (recommended), map stages to specific record types.
Sales Processes
A Sales Process lets you define different sets of stages for different types of opportunities. For example:
- New Business Process: Prospecting → Discovery → Proposal → Negotiation → Closed Won/Lost
- Renewal Process: Renewal Pending → In Review → Closed Won/Lost
- Channel Process: Partner Submitted → Internal Review → Approved → Closed Won/Lost
To set up Sales Processes:
- Go to Setup → Sales Processes.
- Click New.
- Select which stage values are included in this process.
- Associate the Sales Process with an Opportunity Record Type.
Opportunity Products (OpportunityLineItem)
Opportunity Products are the specific items being sold on a deal. They link a Product (via a Pricebook Entry) to an Opportunity with quantity, price, and other details.
Key fields on Opportunity Products:
| Field | Purpose |
|---|---|
| Product | The product being sold |
| Quantity | How many units |
| Unit Price | The price per unit (from the pricebook, can be overridden) |
| Total Price | Quantity × Unit Price |
| Date | The date associated with this line item |
| Discount | Percentage discount applied |
| Description | Additional details |
How adding products works:
- An Opportunity must have a Pricebook associated with it.
- When you add a product, you select from the products in that pricebook.
- The price defaults to the Pricebook Entry price, but can be overridden.
- The Opportunity’s Amount field is automatically calculated as the sum of all Opportunity Product Total Prices.
Important: Once you add products to an opportunity, the Amount field becomes read-only and is calculated from the line items. If you remove all products, the Amount field becomes editable again.
Opportunity Teams
Opportunity Teams allow you to associate multiple users with a single Opportunity, each with a defined role. This is essential for team-based selling.
How to enable and configure Opportunity Teams:
- Go to Setup → Opportunity Team Settings.
- Enable Team Selling.
- Define Opportunity Team Roles (Sales Rep, Sales Engineer, Executive Sponsor, etc.).
Key concepts:
- Each Opportunity Team Member has a Role and an Access Level (Read Only or Read/Write).
- The Opportunity Owner is automatically a team member.
- Users can set up Default Opportunity Teams that are automatically added to every opportunity they own.
- Opportunity Team Members can be used in Opportunity Splits (covered below).
Opportunity Contact Roles
Opportunity Contact Roles define the relationship between Contacts and an Opportunity. They answer the question: who at the customer’s organization is involved in this deal, and what role do they play?
Standard Contact Roles:
- Decision Maker
- Economic Buyer
- Business User
- Technical Buyer
- Evaluator
- Executive Sponsor
How to configure Contact Roles:
- Go to Setup → Object Manager → Opportunity Contact Role → Fields & Relationships → Role.
- Edit the picklist values to match your sales methodology.
Best practice: Use validation rules or flows to require at least one Contact Role (especially a Decision Maker) before an opportunity can be moved to later stages. Deals without identified stakeholders are at risk.
Opportunity Forecasting
Forecasting in Sales Cloud uses opportunity data to predict future revenue. Salesforce provides Collaborative Forecasting as the modern forecasting tool.
Key Forecasting Concepts:
- Forecast Type — What you are forecasting (Revenue, Quantity, or custom measure).
- Forecast Category — How each opportunity contributes (Pipeline, Best Case, Commit, Closed, Omitted).
- Forecast Hierarchy — Forecasts roll up through the role hierarchy (reps → managers → VPs → CRO).
- Adjustments — Managers can adjust forecasts submitted by their reports.
- Quotas — Target amounts that can be set per user per period.
How to Set Up Opportunity Forecasting
-
Enable Collaborative Forecasting:
- Go to Setup → Forecasts Settings.
- Enable Collaborative Forecasting.
- Choose your forecast types (Revenue is most common).
-
Configure Forecast Types:
- Select which opportunity fields to forecast on.
- Choose the time period (monthly or quarterly).
- Enable adjustments if managers need to modify forecasts.
-
Set Up Forecast Hierarchy:
- The forecast hierarchy follows the Role Hierarchy by default.
- Ensure your role hierarchy accurately reflects your sales organization.
- Each user in the hierarchy needs to be enabled as a forecasting user.
-
Enable Quotas (optional):
- Go to Setup → Forecasts Settings → Enable Quotas.
- Quotas can be entered manually or loaded via the API or Data Loader.
- Quotas appear alongside forecast amounts for easy comparison.
-
Configure Forecast Categories:
- Map each Opportunity Stage to a Forecast Category.
- Standard categories: Pipeline, Best Case, Most Likely, Commit, Closed.
- Ensure the mapping aligns with your sales methodology.
Using the Forecasts Tab:
- Navigate to the Forecasts tab.
- Select a forecast type and time period.
- View roll-ups from your team members.
- Make adjustments where necessary.
- Export forecast data for executive reporting.
How to Set Up Opportunity Splits
Opportunity Splits let you divide credit for an opportunity among multiple team members. This is essential for commission tracking in team-selling scenarios.
Types of Splits:
| Split Type | Behavior | Must Total 100%? |
|---|---|---|
| Revenue Splits | Divide the total opportunity amount among team members | Yes |
| Overlay Splits | Give credit to supporting roles (like sales engineers) | No (can exceed 100%) |
| Custom Splits | Custom split types you define | Configurable |
How to enable Opportunity Splits:
- Go to Setup → Opportunity Splits.
- Enable Opportunity Splits.
- The default Revenue Split type is created automatically.
- Click Add Split Type to create Overlay or custom splits.
- For each split type, configure:
- Name
- Whether splits must total 100%
- Which Opportunity Team Members can receive splits
Example split scenario:
| Team Member | Role | Revenue Split | Overlay Split |
|---|---|---|---|
| Jane (Rep) | Account Executive | 60% | — |
| Mike (Rep) | Sales Development | 40% | — |
| Sarah (SE) | Sales Engineer | — | 25% |
| Tom (Manager) | Sales Manager | — | 10% |
In this scenario, revenue splits total 100% (Jane 60% + Mike 40%), while overlay splits can be any amount because they represent additional credit rather than a division of the deal.
Quotes
What Is a Quote?
A Quote is a formal document that presents prices for products and services to a customer. In Salesforce, Quotes are created from Opportunities and pull in the Opportunity’s products, pricing, and customer information.
Key Quote Fields
| Field | Purpose |
|---|---|
| Quote Name | The name of the quote |
| Opportunity | The associated Opportunity |
| Status | Draft, Needs Review, Approved, Rejected, Presented, Accepted |
| Expiration Date | When the quote expires |
| Subtotal | Sum of all line items before tax and discounts |
| Discount | Any quote-level discount |
| Total Price | Final total after discounts |
| Tax | Tax amount (if applicable) |
| Grand Total | Total Price + Tax |
| Syncing | Whether this quote is synced with the Opportunity |
Quote Products (Quote Line Items)
Quote Line Items mirror Opportunity Products but exist on the Quote. When you create a Quote from an Opportunity, the Opportunity Products are copied to the Quote as Quote Line Items.
Key fields:
- Product
- Quantity
- Unit Price
- Discount
- Total Price
- Description
Opportunity-Quote Syncing
Salesforce allows you to sync a Quote with its parent Opportunity. When syncing is enabled:
- Changes to Quote Line Items automatically update Opportunity Products (and vice versa).
- Only one Quote can be synced to an Opportunity at a time.
- The synced Quote is marked with a special icon.
How syncing works:
- Create an Opportunity with Products.
- Create a Quote from the Opportunity (products are copied to the Quote).
- On the Quote, click Start Sync.
- Now, changes to either the Quote Line Items or Opportunity Products will be reflected in both.
- To stop syncing, click Stop Sync on the Quote.
Why use Quote syncing?
- Your team negotiates pricing on Quotes but the Opportunity amount needs to stay accurate for forecasting.
- It prevents discrepancies between what was quoted and what the Opportunity says the deal is worth.
Important considerations:
- If you have multiple Quotes for the same Opportunity (different pricing scenarios), only one can be synced at a time.
- Syncing creates a bidirectional relationship — be careful about who can edit what.
- Use approval processes on Quotes to control when pricing changes are locked in.
How to Create Quote PDFs
Salesforce provides the ability to generate PDF documents from Quotes. This is how you create professional-looking proposals to send to customers.
Standard Quote PDF generation:
- Navigate to a Quote record.
- Click Create PDF.
- Salesforce generates a PDF based on the Quote Template.
- You can email the PDF directly or save it to the Quote.
Setting up Quote Templates:
- Go to Setup → Quote Templates.
- Click New Template.
- Use the template editor to design your layout:
- Add your company logo.
- Configure which fields appear in the header (Company Name, Quote Number, Date, etc.).
- Define the line item table columns (Product, Quantity, Price, Discount, Total).
- Add footer text (Terms and Conditions, payment terms, etc.).
- Configure the totals section (Subtotal, Discount, Tax, Grand Total).
- Save the template.
- You can have multiple templates (e.g., one for domestic quotes, one for international).
Limitations of standard Quote PDFs:
- The template editor is limited in design flexibility.
- Complex layouts, dynamic content, and advanced formatting are difficult or impossible.
- For more sophisticated quote documents, consider Salesforce CPQ, Conga Composer, or a custom Visualforce/LWC PDF generator.
Orders
What Are Orders?
An Order in Salesforce represents a confirmed request to purchase products or services. Orders are typically created after a Quote has been accepted, or directly from an Opportunity. They represent the transition from “the customer wants to buy” to “the customer is buying.”
Key Order Fields
| Field | Purpose |
|---|---|
| Order Number | Auto-generated unique identifier |
| Account | The purchasing account |
| Contract | The associated contract (optional) |
| Status | Draft, Activated, Fulfilled, Cancelled |
| Order Start Date | When the order period begins |
| Effective Date | When the order takes effect |
| Type | New, Renewal, Amendment, etc. |
| Pricebook | The pricebook associated with the order |
Order Products (OrderItems)
Order Products are the line items on an Order. Like Opportunity Products and Quote Line Items, they reference a Product and Pricebook Entry.
Key fields:
- Product
- Quantity
- Unit Price
- Total Price
- Start Date / End Date (for subscription products)
Order Lifecycle
Draft → Activated → Fulfilled (or Cancelled)
- Draft — The order is being prepared. Products can be added, removed, or modified.
- Activated — The order has been confirmed. In many configurations, activated orders become read-only.
- Fulfilled — The order has been delivered/completed.
- Cancelled — The order was cancelled before fulfillment.
How to enable Orders:
- Go to Setup → Order Settings.
- Enable Orders.
- Configure Reduction Orders if you need to handle partial cancellations or returns.
Reduction Orders
Reduction Orders are a special type of order that represents a negative adjustment — a return, cancellation, or credit. They reference the original order and reduce the quantity or value.
When to use Reduction Orders:
- A customer returns some items from a large order.
- A partial cancellation is needed.
- A credit needs to be issued against a previous order.
Contracts
What Are Contracts?
A Contract in Salesforce represents a formal agreement between your organization and an Account. Contracts track the terms, duration, and status of business agreements.
Key Contract Fields
| Field | Purpose |
|---|---|
| Contract Number | Auto-generated unique identifier |
| Account | The account the contract is with |
| Status | Draft, In Approval Process, Activated, Expired, Terminated |
| Contract Start Date | When the contract begins |
| Contract Term (months) | The duration of the contract |
| Contract End Date | Auto-calculated from Start Date + Term |
| Owner Expiration Notice | How far in advance to notify the owner of expiration |
| Special Terms | Any custom terms or conditions |
Contract Lifecycle
Draft → In Approval Process → Activated → Expired (or Terminated)
- Draft — Contract is being prepared and negotiated.
- In Approval Process — Contract is awaiting internal or external approval.
- Activated — Contract is signed and in effect. Activated contracts become read-only by default.
- Expired — The contract term has ended.
- Terminated — The contract was ended early.
Setting Up Contract Automation
Expiration notifications:
- Use the Owner Expiration Notice field to set up alerts (30, 60, 90 days before expiration).
- Salesforce sends an email to the contract owner when the expiration notice period is reached.
Renewal automation:
- Salesforce does not have built-in contract renewal automation.
- Use Flows to create renewal opportunities or new contracts when a contract is nearing expiration.
- Common approach: A scheduled flow runs nightly, finds contracts expiring within X days, and creates renewal Opportunities.
Connecting Contracts to other objects:
- Contracts can be linked to Orders (the Contract field on Order).
- Contracts can be linked to Opportunities (via a custom lookup field).
- Contracts can have Cases related to them for tracking support issues related to the agreement.
Enterprise Territory Management
What Is Enterprise Territory Management?
Enterprise Territory Management (ETM) is a feature that lets you organize your sales team and accounts into logical territories based on criteria like geography, industry, revenue size, product line, or any combination of account attributes. It determines which sales reps have access to which accounts and opportunities.
Why use Territory Management?
- Fair distribution — Ensure accounts are evenly distributed among reps.
- Geographic alignment — Assign reps to specific regions.
- Product specialization — Route accounts to reps who specialize in certain product lines.
- Forecasting by territory — Forecast revenue by territory rather than just by rep.
- Flexible reassignment — When reps leave or territories change, reassignment is straightforward.
ETM Concepts
| Concept | Description |
|---|---|
| Territory Type | A category for territories (Geographic, Product-Based, Named Accounts, etc.) |
| Territory Model | A container for an entire territory hierarchy (you can have multiple models but only one active) |
| Territory | A node in the hierarchy (e.g., “North America,” “US West,” “California”) |
| Territory Hierarchy | The parent-child structure of territories within a model |
| Assignment Rule | Criteria that automatically assign accounts to territories |
| Territory Member | A user assigned to a territory |
How to Set Up Enterprise Territory Management
Step 1: Enable ETM
- Go to Setup → Territory Settings.
- Click Enable Enterprise Territory Management.
Step 2: Create Territory Types
- Go to Setup → Territory Types.
- Create types that represent your organizational structure:
- Geographic Territories
- Named Account Territories
- Product-Based Territories
- Set a Priority for each type (this determines the order of evaluation).
Step 3: Create a Territory Model
- Go to Setup → Territory Models.
- Click New Territory Model.
- Give it a name and description.
- The model starts in Planning state.
Step 4: Build the Territory Hierarchy
- Open the Territory Model.
- Click New Territory to create the top-level territories.
- Create child territories under each parent:
Global Sales (Territory Model)
├── North America
│ ├── US East
│ │ ├── Northeast
│ │ └── Southeast
│ ├── US West
│ │ ├── Pacific
│ │ └── Mountain
│ └── Canada
├── EMEA
│ ├── UK & Ireland
│ ├── Western Europe
│ └── DACH
└── APAC
├── ANZ
├── Japan
└── Southeast Asia
Step 5: Assign Users to Territories
- Open a Territory record.
- Add users as Territory Members.
- Each user can be in multiple territories.
Step 6: Create Assignment Rules (see below)
Step 7: Activate the Model
- Once your hierarchy, users, and rules are configured, change the model state to Active.
- Only one model can be active at a time.
- You can keep other models in Planning state for future reorganizations.
ETM Assignment Rules
Assignment Rules automatically assign Accounts to Territories based on account attributes. This is the powerful automation that makes ETM scalable.
How to create Assignment Rules:
- Open a Territory record.
- Click New Rule in the Assignment Rules related list.
- Define the criteria:
- Field: Billing State/Province
- Operator: equals
- Value: California, Oregon, Washington
- Save the rule.
- Click Run Rules to apply.
Rule examples:
| Territory | Rule Criteria |
|---|---|
| US West - Pacific | Billing State = CA, OR, WA |
| US East - Northeast | Billing State = NY, NJ, CT, MA, PA |
| Enterprise Accounts | Annual Revenue > $100M |
| SMB Accounts | Annual Revenue < $10M |
| Healthcare | Industry = Healthcare |
Important considerations for ETM rules:
- Rules evaluate account fields only — they cannot look at related objects.
- An account can be assigned to multiple territories if it matches multiple rules.
- Rules run in the order defined by Territory Type priority.
- When account data changes, rules are not automatically re-evaluated. You must run rules manually or on a schedule.
- Use scheduled flows or batch Apex to periodically re-run territory assignments.
ETM and Opportunity Assignment
When ETM is active, Opportunities can be assigned to Territories. This enables territory-based forecasting and reporting.
- Opportunities are assigned to territories based on the Account’s territory assignment.
- If an Account is in multiple territories, you choose which territory the Opportunity belongs to.
- Territory-based forecasting rolls up Opportunity amounts through the territory hierarchy.
What Is CPQ?
CPQ stands for Configure, Price, Quote. Salesforce CPQ (formerly Steelbrick) is an add-on product that extends Sales Cloud’s native quoting capabilities with advanced features for complex pricing scenarios.
When Do You Need CPQ?
You should consider CPQ when standard Products, Pricebooks, and Quotes are not enough:
| Scenario | Standard Quotes | CPQ Needed? |
|---|---|---|
| Simple product catalog, fixed prices | Sufficient | No |
| Volume discounts | Difficult | Yes |
| Product bundles (must buy together) | Not supported | Yes |
| Subscription pricing with renewals | Limited | Yes |
| Complex approval workflows for discounts | Basic | Yes |
| Guided selling (questionnaire-based product selection) | Not available | Yes |
| Dynamic pricing rules (if customer buys X, Y costs less) | Not available | Yes |
| Contract amendments and renewals | Manual | Yes |
| Multi-dimensional quoting (term, quantity, tier) | Not available | Yes |
Key CPQ Features
- Product Bundles — Group products together with required, optional, and excluded components.
- Pricing Rules — Automate discounts, markups, and price adjustments based on conditions.
- Discount Schedules — Define volume-based or term-based discounts.
- Guided Selling — Walk reps through a questionnaire to recommend the right products.
- Advanced Approvals — Multi-step approval workflows based on discount levels, deal size, or product combinations.
- Contract Management — Manage renewals, amendments, and co-termination of subscriptions.
- Quote Document Generation — Generate polished PDF quotes with dynamic content.
- Order Management — Create orders directly from quotes with proper billing and fulfillment details.
CPQ Licensing
CPQ is a separate license from Sales Cloud. It is typically priced per-user and comes in several tiers:
- CPQ — Core configuration, pricing, and quoting functionality.
- CPQ+ — Adds billing and order management capabilities.
- CPQ with Billing — Full quote-to-cash solution including invoicing and revenue recognition.
Important: CPQ is a complex product that requires significant implementation effort. It is not something you enable overnight — plan for a dedicated implementation project with experienced CPQ consultants.
What Is Revenue Management Cloud?
Revenue Management Cloud (formerly Revenue Cloud) is Salesforce’s broader vision for managing the entire revenue lifecycle. It encompasses:
- CPQ — Quote and pricing configuration.
- Billing — Invoice generation, payment collection, and revenue recognition.
- Subscription Management — Managing recurring revenue, renewals, and amendments.
- Revenue Lifecycle Management — End-to-end visibility into how revenue is generated and recognized.
Key Capabilities
| Capability | Description |
|---|---|
| Multi-Cloud Quoting | Unified quoting across Sales Cloud, Experience Cloud, and partner channels |
| Dynamic Revenue Orchestration | Automated workflows for complex deal structures |
| Usage-Based Pricing | Charge based on consumption rather than fixed fees |
| Revenue Recognition | Comply with ASC 606 / IFRS 15 standards |
| Subscription Management | Handle renewals, upgrades, downgrades, and cancellations |
| Asset Lifecycle Management | Track what a customer owns and manage changes over time |
Revenue Management Cloud is Salesforce’s strategic direction for combining CPQ, Billing, and Subscription Management into a unified platform. It is relatively newer compared to standalone CPQ and is evolving rapidly.
Sales Cloud Engagement and Sales Cloud Voice
Sales Cloud Engagement (formerly High Velocity Sales / Sales Engagement)
Sales Cloud Engagement provides tools for inside sales teams and sales development representatives (SDRs) who work high volumes of leads and contacts.
Key features:
- Sales Cadences — Automated sequences of steps (emails, calls, tasks) that guide reps through their outreach process. Think of it as a structured playbook.
- Work Queue — A prioritized list of actions for reps, pulling from cadences, tasks, and other sources. Reps work through the queue rather than deciding what to do next.
- Einstein Activity Capture — Automatically logs emails and events from Gmail or Outlook to Salesforce, reducing manual data entry.
- Email Tracking — Track opens, clicks, and replies on emails sent from Salesforce.
- Call Scripting — Provide reps with dynamic talk tracks based on the person they are calling and the stage of the engagement.
When to use Sales Engagement:
- Your team makes a high volume of outbound calls and emails.
- You need a standardized sales process for SDRs.
- You want to reduce the time reps spend deciding who to contact next.
- You need visibility into rep activity and engagement metrics.
Sales Cloud Voice (formerly Service Cloud Voice — now available for Sales too)
Sales Cloud Voice integrates telephony directly into Salesforce, so reps can make and receive calls without leaving the platform.
Key features:
- Integrated Dialer — Click-to-call from any Salesforce record.
- Call Transcription — Real-time transcription of calls powered by AI.
- Call Recording — Record calls for coaching and compliance.
- Intelligent Routing — Route incoming calls to the right rep based on account ownership, territory, or other criteria.
- Einstein Conversation Insights — AI analysis of call transcripts to identify trends, objections, and coaching opportunities.
Integration options:
- Amazon Connect — Salesforce’s native telephony partner.
- Partner Telephony — Integrate with other providers (Five9, Genesys, etc.) through the Voice partner program.
Section Notes
Key Takeaways
-
Sales Cloud is more than objects — It is a comprehensive platform with interconnected features. Understanding how the pieces fit together is as important as understanding each piece individually.
-
Licensing matters — Many objects are available without a Sales Cloud license, but the advanced features (forecasting, splits, territory management) require it. Always verify licensing before promising functionality to stakeholders.
-
Start simple — Do not implement every Sales Cloud feature at once. Start with Leads and Opportunities, add Products and Quotes when ready, and only bring in CPQ or Territory Management when the business truly needs it.
-
Data quality is critical — Sales Cloud features like Forecasting and Territory Management are only as good as the data they rely on. Invest in data governance, validation rules, and required fields.
-
The standard quoting functionality is basic — If your pricing is anything beyond straightforward (bundles, volume discounts, subscriptions), seriously evaluate CPQ early in the project rather than trying to make standard Quotes work.
-
Web-to-Lead has its place but know its limits — For quick proof-of-concept or very low-volume scenarios, Web-to-Lead works. For anything production-grade, use a proper form solution with API integration.
-
Territory Management is powerful but complex — ETM requires careful planning and ongoing maintenance. Do not enable it unless you have a clear business case and are committed to maintaining the territory model.
-
Multi-currency is a one-way door — Once you enable it, you cannot turn it back off. Plan carefully and test in a sandbox first.
Common Exam Topics (for those pursuing certification)
- Lead conversion process and field mapping.
- The relationship between Products, Pricebooks, and Pricebook Entries.
- Campaign hierarchy and campaign influence models.
- Opportunity forecasting categories and how they map to stages.
- The difference between Revenue Splits and Overlay Splits.
- Quote syncing behavior.
- Territory Management hierarchy and assignment rules.
- When standard Quotes are sufficient vs. when CPQ is needed.
PROJECT: Set Up a Sales Cloud Implementation
This hands-on project walks you through setting up a complete Sales Cloud implementation from scratch. We will configure the entire sales lifecycle: Campaigns through Leads through Opportunities through Products and Pricebooks through Quotes through Orders.
Scenario
You are the Salesforce Administrator for CloudTech Solutions, a B2B software company that sells two products:
- CloudTech Platform — An annual subscription software license.
- CloudTech Implementation Services — Professional services for implementation.
CloudTech sells to three customer segments with different pricing:
- Standard customers pay list price.
- Partner customers receive a 20% discount.
- Enterprise customers negotiate custom pricing.
Step 1: Configure Products and Pricebooks
Create the Products:
- Navigate to the Products tab.
- Create Product 1:
- Product Name: CloudTech Platform
- Product Code: CT-PLAT-001
- Product Family: Software
- Active: Checked
- Create Product 2:
- Product Name: CloudTech Implementation Services
- Product Code: CT-IMPL-001
- Product Family: Services
- Active: Checked
Create Standard Pricebook Entries:
- Open the CloudTech Platform product.
- Click Add Standard Price: $50,000.
- Open the CloudTech Implementation Services product.
- Click Add Standard Price: $25,000.
Create Custom Pricebooks:
- Navigate to the Pricebooks tab.
- Create Partner Pricebook:
- Name: Partner Pricebook
- Active: Checked
- Add products:
- CloudTech Platform: $40,000 (20% discount)
- CloudTech Implementation Services: $20,000 (20% discount)
- Create Enterprise Pricebook:
- Name: Enterprise Pricebook
- Active: Checked
- Add products:
- CloudTech Platform: $45,000 (10% discount — further negotiation expected)
- CloudTech Implementation Services: $22,000
Step 2: Set Up the Campaign
Create a Campaign:
- Navigate to the Campaigns tab.
- Click New.
- Fill in:
- Campaign Name: CloudTech Spring 2026 Webinar Series
- Type: Webinar
- Status: Active
- Start Date: 2026-03-01
- End Date: 2026-03-31
- Budgeted Cost: $5,000
- Expected Revenue: $200,000
- Save the Campaign.
Configure Campaign Member Statuses:
- On the Campaign record, go to Campaign Member Statuses.
- Remove the default statuses.
- Add custom statuses:
- Invited (Default: Yes, Responded: No)
- Registered (Default: No, Responded: Yes)
- Attended (Default: No, Responded: Yes)
- No Show (Default: No, Responded: No)
Step 3: Capture and Process Leads
Create a Lead:
- Navigate to the Leads tab.
- Click New.
- Fill in:
- First Name: Sarah
- Last Name: Johnson
- Company: Pinnacle Corp
- Title: VP of Engineering
- Email: sarah.johnson@example.com
- Phone: (555) 123-4567
- Lead Source: Webinar
- Lead Status: New
- Industry: Technology
- Annual Revenue: $50,000,000
- Save the Lead.
Add the Lead to the Campaign:
- On the Campaign record, go to Campaign Members.
- Click Add Members.
- Search for Sarah Johnson and add her.
- Set her status to Attended.
Set Up a Lead Auto-Response Rule:
- Go to Setup → Lead Auto-Response Rules.
- Create a new rule: “Webinar Follow-Up Rule”.
- Activate it.
- Add a Rule Entry:
- Criteria: Lead Source equals Webinar
- Email Template: Create or select a template that thanks the lead for attending and provides next steps.
Step 4: Convert the Lead
Convert Sarah Johnson’s Lead:
- Open the Lead record for Sarah Johnson.
- Click Convert.
- In the conversion dialog:
- Account Name: Pinnacle Corp (new)
- Contact Name: Sarah Johnson (new)
- Opportunity Name: Pinnacle Corp - CloudTech Platform
- Check Create Opportunity
- Click Convert.
Verify the conversion:
- An Account record for Pinnacle Corp should now exist.
- A Contact record for Sarah Johnson should be linked to that Account.
- An Opportunity record should be created.
- The Lead Status should be Converted.
- The Campaign Member record should still show Sarah’s association with the webinar.
Step 5: Configure the Opportunity
Set Up Opportunity Stages:
- Go to Setup → Object Manager → Opportunity → Fields & Relationships → Stage.
- Configure the following stages:
| Stage | Probability | Forecast Category |
|---|---|---|
| Qualification | 10% | Pipeline |
| Discovery | 25% | Pipeline |
| Proposal | 50% | Best Case |
| Negotiation | 75% | Commit |
| Closed Won | 100% | Closed |
| Closed Lost | 0% | Omitted |
Update the Opportunity:
- Open the Pinnacle Corp Opportunity.
- Set:
- Stage: Qualification
- Close Date: 2026-06-30
- Type: New Business
- Add the Standard Pricebook (since Pinnacle Corp is a new standard customer).
Add Products to the Opportunity:
- On the Opportunity, click Add Products.
- Add:
- CloudTech Platform: Quantity 1, Unit Price $50,000
- CloudTech Implementation Services: Quantity 1, Unit Price $25,000
- Save. The Opportunity Amount should now show $75,000.
Add Contact Roles:
- On the Opportunity, go to Contact Roles.
- Add Sarah Johnson with Role: Decision Maker and mark as Primary.
Step 6: Create a Quote
Generate a Quote:
- On the Opportunity, go to the Quotes related list.
- Click New Quote.
- Fill in:
- Quote Name: Pinnacle Corp - Initial Proposal
- Expiration Date: 2026-05-31
- Status: Draft
- Save. The Quote Line Items should automatically populate from the Opportunity Products.
Sync the Quote:
- On the Quote, click Start Sync.
- This Quote is now synced with the Opportunity.
Create a Quote PDF:
- On the Quote, click Create PDF.
- Select your Quote Template.
- Review the generated PDF.
- Click Save to Quote to attach it to the record.
- Optionally, click Email Quote to send it to Sarah Johnson.
Step 7: Process the Order
Move the Opportunity forward:
- Update the Opportunity Stage to Negotiation (assume the quote was well received).
- Then move it to Closed Won (the customer has agreed).
Create an Order:
- Navigate to the Pinnacle Corp Account.
- Go to the Orders related list.
- Click New Order.
- Fill in:
- Order Name: Pinnacle Corp - Order 001
- Status: Draft
- Order Start Date: 2026-07-01
- Pricebook: Standard Pricebook
- Contract: (leave blank for now)
- Save.
Add Order Products:
- On the Order, click Add Products.
- Add:
- CloudTech Platform: Quantity 1, Unit Price $50,000
- CloudTech Implementation Services: Quantity 1, Unit Price $25,000
- Save.
Activate the Order:
- On the Order, click Activate.
- The Order Status changes to Activated.
Step 8: Create a Contract
Create a Contract:
- Navigate to the Pinnacle Corp Account.
- Go to the Contracts related list.
- Click New Contract.
- Fill in:
- Status: Draft
- Contract Start Date: 2026-07-01
- Contract Term: 12 (months)
- Owner Expiration Notice: 60 days
- Save.
Link the Contract to the Order:
- Edit the Order.
- Set the Contract field to the newly created contract.
- Save.
Activate the Contract:
- On the Contract, change the Status to Activated.
- Save.
Step 9: Verify the Complete Flow
At this point, you should have a complete sales cycle in Salesforce:
| Object | Record | Status |
|---|---|---|
| Campaign | CloudTech Spring 2026 Webinar Series | Active |
| Campaign Member | Sarah Johnson | Attended |
| Lead | Sarah Johnson | Converted |
| Account | Pinnacle Corp | Active |
| Contact | Sarah Johnson | Active |
| Opportunity | Pinnacle Corp - CloudTech Platform | Closed Won |
| Opportunity Products | Platform ($50K) + Services ($25K) | — |
| Quote | Pinnacle Corp - Initial Proposal | Accepted |
| Quote Line Items | Platform ($50K) + Services ($25K) | — |
| Order | Pinnacle Corp - Order 001 | Activated |
| Order Products | Platform ($50K) + Services ($25K) | — |
| Contract | Pinnacle Corp Contract | Activated (ends 2027-06-30) |
Step 10: Set Up Forecasting (Bonus)
- Go to Setup → Forecasts Settings.
- Enable Collaborative Forecasting.
- Add a forecast type based on Opportunity Revenue.
- Set the period to Quarterly.
- Navigate to the Forecasts tab.
- Verify that the Pinnacle Corp opportunity shows up in the current quarter’s forecast under the Closed category.
Step 11: Review Campaign ROI (Bonus)
- Navigate back to the Campaign record.
- Check the Campaign Statistics:
- Total Leads: 1
- Converted Leads: 1
- Total Contacts: 1
- Total Opportunities: 1
- Total Value Opportunities: $75,000
- Total Value Won Opportunities: $75,000
- Calculate ROI: ($75,000 revenue - $5,000 cost) / $5,000 cost = 1,400% ROI.
This is the power of Sales Cloud — end-to-end visibility from the first marketing touch all the way through to a signed contract and fulfilled order.
What’s Next?
In Part 21, we will dive into Service Cloud in Salesforce — the other half of Salesforce’s core CRM offering. We will cover Cases, Entitlements, Service Level Agreements, Knowledge Base, Omni-Channel routing, and how Service Cloud works alongside Sales Cloud to deliver a complete customer experience. See you there!