Sales OS · Systems
A foundational mapping of the systems, workflows, and department responsibilities that run a modern revenue operation. The products named are common examples of each category; substitute your own. The value is the mapping: what each tool is for, who owns it, and how it connects to the CRM.
Example: Salesforce. Owner: RevOps. The central platform for lead, opportunity, and revenue management, and the system of record for pipeline, reporting, account management, and cross-functional workflows. Its integrations make it the hub the rest of the stack connects to. Core workflows: the lead lifecycle (capture, qualification, conversion), opportunity stages, product and price-book management, and post-sale implementation records.
Example: PandaDoc. Owner: RevOps; used by Sales and Legal. Automates proposal, MSA, and SOW generation, routes documents through internal and external approvals, collects legally binding e-signatures, and syncs signed documents back to the CRM. Standard templates keep customer-facing documents consistent.
Example: a sales-engagement platform. Owner: RevOps; used by SDRs and sales. Runs structured email and call cadences for outbound prospecting, tracks engagement, and syncs activity to the CRM for consistency and efficiency.
Example: a call-recording and analysis tool. Owner: RevOps; used by SDRs and sales leaders. Records and transcribes sales calls, supports coaching and QA, surfaces deal intelligence (next steps, competitor mentions, sentiment), and syncs to CRM records.
Example: a deduplication and enrichment engine. Owner: RevOps only. Keeps CRM data clean through deduplication, normalization, and enrichment, underpinning accurate lead routing, reporting, and territory management.
Example: LinkedIn Sales Navigator. Owner: RevOps; used by sales leaders. Supports targeted prospecting and pre-call research, account monitoring, and outreach, with saved leads syncing to the CRM.
Example: HubSpot. Owner: Marketing and RevOps. Powers campaigns, lead nurturing, scoring, and forms, and syncs lifecycle stages (for example MQL to SQL) to the CRM so marketing and sales stay aligned.
Examples: a work-management platform for onboarding projects (owned by Implementations) and a customer-success platform for health, retention, renewals, and upsell (owned by Customer Success). Both integrate with the CRM so onboarding progress and account health are visible to the wider go-to-market team.
Two ideas hold the stack together: the CRM is the single source of record, and every other tool syncs to it rather than becoming a parallel truth; and each system has one clear owner accountable for its data and workflows. Map your own tools to these categories and the operating model transfers cleanly.