RevOps Docs for Startups
  • Welcome
  • Getting Started
    • Quickstart
    • About LeanScale
  • Growth Modeling
    • Building a Growth Model
      • Growth Model Assumptions
      • Growth Model Approaches
      • Growth Model Segmentations
    • Sales Capacity Plan
    • Marketing Plan
    • Customer Success Plan
  • Go-to-market Lifecycle
    • Go-to-Market Lifecycle
    • Lead Lifecycle
    • Sales Lifecycle
    • Customer Lifecycle
    • Proof of Concept Lifecycle
    • Lifecycle Measurement
  • Lead Attribution
    • Attribution Overview
    • Lead Source Taxonomy
  • Measuring Metrics
    • Reporting and Data Analytics
    • Sales Metrics
      • Created Pipeline
      • Weighted Pipeline
    • Marketing Metrics
      • Lead Impact Matrix
      • CAC to LTV
    • Customer Success Metrics
      • Net Retention
    • Partnership Metrics
    • Presenting Metrics
  • GTM Tech Stack
    • GTM Tech Stack Overview
    • When To Buy New Systems
    • Driving System Adoption
    • CRM Considerations
      • User-Oriented CRM
      • Data & Reporting CRM
      • Security-Focused CRM
  • Aligning Sales/Marketing
    • Alignment Overview
    • How to Align?
    • What is an SQL?
    • Building Marketing Operations
    • Defining GTM Process
    • Interviewing GTM Leaders
    • Finding The Right Talent
  • System Demos
    • Data Enrichment
      • Clay
      • Traction Complete
    • Conversational Intelligence
      • Gong
      • Unthread
    • CPQ
      • Dealhub
      • Salesbricks
    • Data Analytics
      • RevVue
      • QFlow
  • CRM Tips
    • Salesforce
      • Create Opp from Contact
      • Validation Rules in Flow
      • Roll Up Summary Field
      • Close Date Change Counter
      • Lead Stages
      • Sales Stages
      • Customer Stages
      • Next Step Fields
      • Lead Source Taxonomy
      • Proof of Concept Stages
      • Displaying Record Information
      • Display Dynamic Lists
      • Messages to End Users
      • Create Custom Buttons
      • Tips for Data Loader
      • Salesforce Inspector Reloaded
      • SFDC Navigator for Lightning
      • Bypass Validation Rules
      • Sales Manager Notes Field
      • Renaming Fields and Objects
      • Getting Faster to Record ID
    • Hubspot
      • Disable Picklist Options
      • Create Yesterday's Date
      • Create Today's Date
  • Strategic Walkthroughs
    • Revenue Operations Flywheel
    • Post-Fundraise Playbook
    • Building Board Decks
    • Building Dashboards
      • CEO Dashboards
      • Executive Dashboards
      • Marketing Dashboards
      • Sales Dashboards
      • CS Dashboards
      • Funnel Analytics
    • ChatGPT as a Salesforce Admin
    • Sales Commission Plans
    • Building Sales Territories
Powered by GitBook
On this page
  • POC Object
  • Automation
  • Custom Button
  • Opportunity Page Layout
  • Conclusion

Was this helpful?

  1. CRM Tips
  2. Salesforce

Proof of Concept Stages

PreviousLead Source TaxonomyNextDisplaying Record Information

Last updated 7 months ago

Was this helpful?

POC Object

The POC (Proof of Concept) object in Salesforce contains several custom fields that are used to track the progress of a product-led capability through various stages. These fields include:

  • POC with Account Record: This field links the POC to an account record.

  • Opportunity Record: This field links the POC to an opportunity record.

  • POC Name: This field specifies the name of the POC.

  • POC Stage: This field indicates the current stage of the POC.

  • POC Comments: This field allows users to add comments or notes about the POC.

  • POC Start Date: This field specifies the start date of the POC.

  • POC End Date: This field specifies the end date of the POC.

  • POC Result: This field indicates the outcome of the POC (e.g., "success" or "failure").

  • POC Stage Timestamps: These fields capture the timestamps for each stage of the POC.

Automation

To ensure that all the POC stage timestamps are recorded accurately, even if users skip stages, a record trigger flow is created. This flow triggers whenever a record is created or updated in the POC object. The entry condition for the flow is when the POC stage of the record is different from the POC stage of the prior record.

The flow then uses assignment elements to update all the POC stage timestamps at the same time. Each assignment element uses a formula to determine whether to update the timestamp based on the current PC stage and the value of the corresponding timestamp field.

Custom Button

To make it easier for users to create a POC from the opportunity object, a custom button is created. This button is an action that creates a new record in the POC object. The button is configured to be visible only if the opportunity stage is not equal to "SQL" or "Discovery Demo Completed".

When the button is clicked, it opens a form that allows the user to enter the required information for the POC, including the account record, POC name, POC stage, start date, and end date. The button also includes a success message that is displayed after the POC record is created.

Opportunity Page Layout

The POC records are also added to the opportunity page layout so that users can easily see all the POC that are running for a particular account. The POC records are displayed in a box on the opportunity page, and each record shows the POC name, POC stage, and POC start and end dates.

Conclusion

This document provides a technical overview of the POC object, including the custom fields, automation, custom button, and opportunity page layout that are used to manage and track product-led capabilities in Salesforce.