Sales Operations Go To Market
Welcome to The Sales Operations GTM Page!
The purpose of this page is to centralize and document all key Go To Market policies & links for ease of use.
Account Ownership Rules of Engagement
Territory Tables
Territory Success Planning (TSP)
TSP is an automated process workflow intended to properly segment & route Salesforce accounts to the correct Sales territory & respective owner. This clarifies who should own which accounts & reduces current Ops overhead to manage manually. TSP fields are designed to be real time reflections of the best data we have, not necessarily the current Go To Market approach. Requests to override the TSP information can also be submitted in the Account Review section of the account.
Primary TSP Workflow Components
-
Account Routing (Next Owner recommendation process):
- Sales Segment (i.e. max employee count of the account hierarchy)
- Primary Account HQ Address (of top Parent Account in the hierarchy)
- Inputs for both are formulated via our standardized account enrichment tools (in order):
- Manual Override > DataFox > DiscoverOrg > Ship-To > Bill-To
- LeadData then compares these TSP Input Values against our SSoT Territory Mapping File & automatically outputs an Approved Next Owner and Territory.
-
Account Assignment (Account Transfer Process):
- (Re)Assignment of an account to the correct owner
- Updating of Account Territory, Sales Segment, Employees fields
Firmographic TSP Fields
[TSP] Sales Segment: Segment of the account based on the MAX employee count in that account’s hierarchy (regardless if MAX is parent or child).[TSP] Account Employees: Number of employees for this specific account[TSP] MAX Family Employees: MAX employee count (number) in hierarchy[TSP] Address (Street, City, State, Post Code, Country): Location of Ultimate Parent Account based on the TSP data hierarchy[TSP] Geo Story: Source of address data from TSP Data Hierarchy
Ownership TSP Fields
[TSP] Next Approved Owner: Owner of territory as determined by SSoT Territory Mapping File[TSP] Transfer Date: Date when account ownership will change to TSP Next Approved Owner
Territory TSP Fields
[TSP] Territory: Territory account falls under, as per the SSoT Territory Mapping File[TSP] Region: Sales territory region the account falls under[TSP] Subregion: Sales territory sub-region the account falls under[TSP] Area: Sales territory area the account falls under
Account Exclusions
The current TSP design supports our Geo sales accounts & territories.
- It does not currently support Named Accounts, PubSec Accounts, or Channel Accounts - as these require manual assignment.
- These accounts are intentionally filtered out of the TSP automation process, and will not be impacted by automated reassignment assuming.
Process for Requesting TSP Changes:
In the event our data enrichment tools are outdated or incorrect (primary address or employee count), you can submit a request to override this information.
-
Request:
- Enter desired TSP information into the following fields (this can be either Account, Employee Count, or both).
- Be sure to include source of correct data (ROE must still be followed)
-
[User Input] Employee Count
- [User Input] Employee Source
- [User Input] Address Street
- [User Input] Address City
- [User Input] Address State
- [User Input] Address Post Code
- [User Input] Address Country
- [User Input] Address Source
-
Operations Review:
Ops will review these requests on a periodic basis, and provide a response in the [TSP] Override Status field:
- Approved - Account changes accepted, &
[TSP] Effective Date populated by Ops.
- Rejected - Reason added to
[TSP] Decision Rationale field.
- Needs Approval/More Info - Info needed added to
[TSP] Decision Rationale field.
-
Execution:
- Turnaround time for Approved TSP changes to re-populate typically takes 24-48 hours.
- Accounts with a
[TSP] Effective Date populated will be re-routed each night to the [TSP] Next Approved Owner.
Account Territory, Sales Segment & Employees fields will also be updated upon TSP transfer, to continually align accounts.
Primary Quote System
The Primary Quote system is a 1:1 relationship in SFDC that connects the total transaction amount on a quote with the amount on its related opportunity. This is to ensure we are forecasting the same amount that we will book and enables further automation as the quote is sent to Zuora billing. To support sales situations that require multiple quotes (for instance: a small deal option and a big deal option), sales reps can identify which one of their quote is “Primary”.
Primary Quote technical documentation here:
Confused about how to use Chorus? Check out the instructions and links below for more information on how to get the most out of this important sales tool.
What is Chorus? Chorus is a call and demo recording software for customer-facing team members. This tool tracks keywords, provides analytics, and transcribes calls into both Salesforce and Outreach. Chorus is used to onboard new team members, provide ongoing training and development for existing team members, provide non-sales employees with access to sales calls, and allow customer-facing team members to recall certain points of a call or demo.
