Purpose: To structure and manage the entire business-to-business sales lifecycle, from identifying corporate prospects and engaging key contacts to closing complex deals and forecasting revenue.

Why This Matters

Business Impact: This πŸ“‹ Function provides a single source of truth for all client and prospect interactions. It streamlines the sales process, improves forecast accuracy, enhances team collaboration, and provides clear visibility into pipeline health and individual performance.

The Big Picture

The B2B CRM function is built around three core entities: Companies, Contacts, and Deals.
  1. Account Management: A central repository of all client and prospect organizations (🧊 Company object) is maintained. All activities and data points related to an organization are stored here.
  2. Contact Management: Key decision-makers and influencers within each 🧊 Company are managed as 🧊︎ Contact records, linked to their parent organization.
  3. Opportunity Pipeline: Each potential sale is tracked as a 🧊︎ Deal object, which moves through a structured sales pipeline from initial qualification to final closure. Each 🧊︎ Deal is linked to a 🧊 Company.
This structure allows for a 360-degree view of the customer, ensuring that sales representatives have all the necessary context to manage relationships and close deals effectively.

Sneak peek

🏒 ACME Corporation (Organization)
β”‚
β”œβ”€β”€ πŸ“‚ MARKETING (Area)
β”‚   └── ⏹️ Lead Generation (Space)
β”‚
β”œβ”€β”€ πŸ“‚ SALES (Area)
β”‚   └── ⏹️ B2B Sales Pipeline (Space)  // You are here
β”‚       └── πŸ“‹ Function: B2B CRM
β”‚           └── 🧊 Company
β”‚               β”œβ”€β”€ 🧊︎ Contact (Sub-Object)
β”‚               └── 🧊︎ Deal (Sub-Object)
β”‚
β”œβ”€β”€ πŸ“‚ DELIVERY (Area)
β”‚   └── ⏹️ Project Management (Space)

OBJECT RELATIONSHIPS

A built-in, strict hierarchy where a β€œchild” object is a component of a β€œparent” object. This is ideal for work breakdown structures.
RelationshipDescription
🧊 Company β†’ 🧊︎ ContactEach 🧊 Company can have multiple 🧊︎ Contact records associated with it.
🧊 Company β†’ 🧊︎ DealEach 🧊 Company can have multiple 🧊︎ Deals over its lifetime.

PART 2: OBJECT TYPES & WORKFLOWS

1. 🧊 Company (Standard Object)

  • Business Process Description: This object acts as the master record for any organization the business interacts with. It holds firmographic data and serves as the anchor for all related contacts and deals.
  • Example: β€œInnovatech Solutions Inc.”, a tech firm with 500-1000 employees in the FinTech industry, is added as a new Prospect. The Account Executive is assigned as David Miller.
Company Workflow
PROSPECT β†’ ACTIVE CLIENT β†’ DORMANT β†’ CHURNED

2. 🧊︎ Contact (Sub-Object)

  • Business Process Description: Manages individuals at a parent Company. This allows tracking of roles, contact information, and engagement history for key stakeholders.
  • Example: Jane Doe, CTO at Innovatech Solutions, is added as a Contact linked to the company record. Her email is jane.doe@innovatech.com and phone is 555-0102.
Contact Workflow
ACTIVE β†’ INACTIVE
  ↑       ↓
  β””β”€β”€β”€β”€β”€β”€β”€β”˜

3. 🧊︎ Deal (Sub-Object)

  • Business Process Description: This is the core pipeline object, tracking an opportunity from discovery to closure. It contains all commercial information, such as deal value and expected close date.
  • Example: A deal named β€œInnovatech - Q4 Platform Upgrade” is created with a value of $75,000 and an expected close date of December 15, 2025.
Deal Workflow
QUALIFICATION β†’ NEEDS ANALYSIS β†’ PROPOSAL β†’ NEGOTIATION β†’ CLOSED-WON
      ↓               ↓               ↓               ↓
  CLOSED-LOST     CLOSED-LOST     CLOSED-LOST     CLOSED-LOST

AUTOMATION RULES

These rules run entirely within the B2B Sales Pipeline ⏹️ Space to enhance sales efficiency and ensure process consistency.
IDRule NameTriggerActionDescription
IC-01Update Deal Probability🧊︎ Deal status changesUpdate Probability field based on the new status.Ensures forecast data is always consistent with the deal’s pipeline stage.
IC-02Log Activity Date🧊︎ Deal or 🧊︎ Contact is updatedUpdate Last Activity Date on the parent 🧊 Company to now.Provides an at-a-glance view of the last engagement with any aspect of an account.

INTERFACE & REPORTING

#NameTypePurposeData Configuration
1Sales PipelineKanbanTo visualize and manage all active deals by their current stage.All 🧊︎ Deals with status not in (CLOSED-WON, CLOSED-LOST), grouped by Status.
2My AccountsTableA list of all companies owned by the current user for account management.All 🧊 Companies where Account Owner = Current User.
3Team Activity FeedListA chronological view of recent updates across all objects.All 🧊 Companies, 🧊︎ Contacts, 🧊︎ Deals sorted by Last Updated Date (Descending).

PART 6: PERMISSIONS & NOTIFICATIONS

These roles define the specific responsibilities and access levels within the B2B CRM function.
RoleResponsibilitiesPermissions & Notifications
Sales Development Rep (SDR)Identifies and qualifies new 🧊 Companies and 🧊︎ Contacts.Can create and edit 🧊 Companies and 🧊︎ Contacts. Read-only on 🧊︎ Deals. Notified on @mentions.
Account Executive (AE)Manages the full sales cycle for 🧊︎ Deals. Owns 🧊 Company relationships.Full control over their assigned 🧊 Companies, 🧊︎ Contacts, and 🧊︎ Deals. Notified on new assignments and deal progress.
Sales ManagerOversees team performance, manages territories, and approves discounts.View all objects in the function. Edit rights on all 🧊︎ Deals. Receives weekly pipeline summary and stale deal alerts.