The functions of sales, prospecting through retention, and what each actually requires from the CRM.
Sales organizations run across 9 distinct functions: prospecting (finding), qualification (filtering), discovery (understanding), proposal (specifying), negotiation (agreeing), close (committing), onboarding (activating), retention (keeping), expansion (growing). Each function has workflow, metrics, roles, and CRM requirements. A CRM that covers each function natively performs materially differently from one that assumes functions happen in separate tools.
The functions-of-sales framing is useful for CRM evaluation because functions have distinct requirements that generic sales CRM assumptions flatten. The six issues below are the function gaps that drive sales teams to add separate tools rather than running full lifecycle on one platform.
Prospecting lives in separate tool
Outreach runs in prospecting tool, not the CRM.
Prospecting (list building, outbound sequencing, engagement tracking) commonly runs in separate tools (Outreach, Salesloft, Apollo, Reply.io). The prospecting activity never flows cleanly to the CRM. Contacts drift between tools; conversation history fragments. Strkr's native prospecting primitives bring outbound into the same system as pipeline.
Qualification criteria vary by rep
Each SDR qualifies differently.
Qualification criteria vary across SDRs when the framework (BANT, MEDDIC, firm-specific criteria) is not codified in the CRM. The handoff from SDR to AE is inconsistent because qualification depth varies. Strkr's qualification framework configurable at firm level enforces consistent qualification across SDR team.
Discovery notes live in Zoom
Discovery findings do not reach proposal.
Discovery call findings commonly live in call recording (Zoom, Gong, Chorus) and personal notes. The findings do not flow to proposal building, stakeholder tracking, or pain-point retention. Strkr's discovery primitives bring findings into deal record where subsequent functions can access.
Proposal workflow is tool
PandaDoc or Proposify lives separate from deal.
Proposal workflow commonly runs in separate tools (PandaDoc, Proposify, custom document systems). The proposal content fragments from deal context. Pricing math diverges from deal record. Strkr's native proposal primitives bring proposal into deal record.
Close handoff drops context
Sales-to-onboarding handoff loses context.
Close-to-onboarding handoff commonly drops context: commitments made during sales, stakeholder relationships, risks the AE flagged, timeline expectations. The onboarding team re-discovers context the AE already knew. Strkr's unified record preserves context across handoff.
Retention and expansion are reactive
Churn signals surface only at renewal.
Retention and expansion commonly operate reactively: churn signals surface at renewal conversation rather than weeks earlier, expansion opportunities appear at renewal planning rather than ongoing attention. Strkr's account health rollup and expansion-trigger workflows surface signals proactively.
The nine functions covered
Nine sales functions with Strkr primitives.
Each sales function has workflow, metrics, roles, and CRM requirements. The nine capabilities below cover primitives Strkr ships natively for each function.
Prospecting
List building, outbound sequencing, engagement tracking.
Prospecting primitives support list building (ICP filtering, territory assignment, source attribution), outbound sequencing (multi-touch cadences, channel coordination, personalization at scale), engagement tracking (reply detection, meeting booking, interest signals). The prospecting runs native rather than in separate Outreach or Salesloft overlay.
Qualification
Codified framework with criteria enforcement.
Qualification primitives support codified frameworks (BANT, MEDDIC, firm-specific criteria) with criteria enforcement on SDR workflow. Qualification depth is consistent across SDR team. Qualified-opportunity handoff respects firm standards. Handoff quality is measurable rather than variable.
Discovery
Call findings on deal record.
Discovery primitives support call recording integration (Zoom, Gong, Chorus with transcript sync), finding extraction (Strkr AI drafts key points from transcripts), stakeholder mapping (attendee identification, role tagging, sentiment tracking), pain-point retention. The discovery findings flow to subsequent functions natively.
Proposal
Template library with CRM-linked pricing.
Proposal primitives support template library (firm-specific templates by proposal type), CRM-linked pricing (opportunity pricing flows to every proposal reference), scope-from-discovery (discovery notes feed scope narrative), dynamic security addendum, tracked-change review, native e-signature workflow. The proposal runs native rather than in PandaDoc overlay.
Negotiation
Exception tracking with approval workflow.
Negotiation primitives support exception tracking (pricing exceptions, SLA commitments, contract term variations), approval workflow (VP approval for threshold exceptions, legal review for standard-term variations), redline tracking (customer redlines with reviewer attribution), approval audit trail. The negotiation retains defensible record.
Close
E-signature workflow with CRM state transition.
Close primitives support e-signature workflow (multi-signer sequencing, order enforcement, signer attribution with timestamp), CRM state transition (opportunity move to signed state), document attachment (signed version attaches to opportunity automatically), forecast reconciliation (committed revenue vs signed revenue). The close completes sales motion with defensible record.
Onboarding
Sales-to-success handoff with context retention.
Onboarding primitives support handoff workflow (stakeholder context, commitments made during sales, risks the AE flagged, timeline expectations), onboarding checklist (firm-specific onboarding steps, milestone tracking, stakeholder engagement), health signal activation. The handoff retains sales context for customer success.
Retention
Account health rollup with at-risk alerts.
Retention primitives support account health rollup (usage signals, engagement patterns, support ticket patterns, stakeholder changes), at-risk alerts (threshold triggers, CSM intervention workflows), renewal workflow (renewal timeline, renewal probability, renewal conversation preparation). The retention runs proactive rather than reactive.
Expansion
Opportunity triggers with cross-functional workflow.
Expansion primitives support opportunity triggers (usage thresholds, feature-request patterns, stakeholder change signals, customer success flags), cross-functional workflow (CSM flags opportunity, AE engages, sales ops configures expansion deal), expansion attribution. The expansion motion is systematic rather than ad-hoc.
Who runs which functions
Six roles with distinct function responsibilities.
Sales functions have role ownership that varies by team structure and firm size. The six roles below describe common ownership patterns with Strkr capability that supports each role's functions.
SDR / BDR
Prospecting and qualification.
SDR/BDR team owns prospecting (list building, outbound sequencing, engagement tracking) and qualification (criteria enforcement, opportunity handoff). The SDR workflow runs on cadence execution with engagement signal detection. The handoff to AE is measurable rather than variable.
Account executive
Discovery, proposal, negotiation, close.
AE team owns discovery (call findings, stakeholder mapping, pain-point retention), proposal (template-based drafting with customer-specific content), negotiation (exception tracking, approval workflow coordination), close (signature workflow). The AE workflow runs on deal record as single source of truth.
Sales engineer / solutions engineer
Discovery technical depth and proposal technical scope.
Sales engineer team supports discovery (technical requirements gathering, architecture conversation, feasibility assessment) and proposal (implementation plan, technical scope, migration approach). The SE workflow runs on deal record alongside AE with collaborative primitives.
Sales operations
Qualification, proposal, negotiation support.
Sales ops team supports qualification (framework configuration, reporting), proposal (pricing math, configurator consistency, template maintenance), negotiation (exception approval workflow, audit trail). The ops workflow runs on admin surface with governance discipline.
Customer success manager
Onboarding, retention, expansion identification.
CSM team owns onboarding (handoff reception, milestone tracking, stakeholder engagement), retention (account health monitoring, at-risk intervention, renewal conversation), expansion identification (opportunity flagging). The CSM workflow runs on same account record as AE with role-specific perspective.
Sales leadership
Function metrics and coaching across all functions.
Sales leadership (sales manager, VP of Sales) owns function metrics (SDR productivity, AE conversion, CSM retention), coaching (rep-level pattern coaching across functions), forecast across functions (SDR pipeline generation to AE close to CSM renewal). The leadership workflow runs on cross-function dashboards.
What makes function coverage defensible
Six properties of full-lifecycle CRM.
Full-lifecycle CRM coverage distinguishes from sales-only CRM through properties that span handoffs and cross-function workflows. The six properties below describe what defensible function coverage looks like.
Context preservation across handoffs
Handoff retains upstream context.
Context preservation means SDR-to-AE handoff retains qualification context, AE-to-CSM handoff retains sales context, CSM-to-AE handoff retains renewal context. The retention eliminates re-discovery tax and dropped-ball failures. The discipline distinguishes full-lifecycle CRM from handoff-by-email approach.
Shared account record
Same record from role perspectives.
Shared account record exposes same record from role perspectives: SDR sees prospecting view, AE sees deal view, CSM sees health view, finance sees invoice view. The shared record eliminates system drift and supports cross-function conversation.
Function-specific metrics
Function has measurable outcomes.
Function-specific metrics measure function outcomes: SDR productivity (qualified opportunities per week), AE conversion (stage advancement, close rate), CSM retention (renewal rate, expansion rate). The metrics support function-level coaching and function-level resource allocation.
Cross-function workflow automation
Upstream event triggers downstream action.
Cross-function workflow automation triggers downstream actions from upstream events: SDR qualifies opportunity triggers AE calendar invite, AE closes deal triggers CSM onboarding workflow, CSM flags expansion opportunity triggers AE engagement task. The automation respects function boundaries while enabling coordination.
Function-aware reporting
Cross-function analyses supported natively.
Function-aware reporting supports cross-function analyses: SDR source to close rate correlation, AE deal pattern to CSM retention correlation, CSM intervention to renewal outcome correlation. The reporting runs native rather than requiring BI tool joins across separate systems.
Permission alignment with roles
Permissions respect function responsibilities.
Permission alignment matches permissions to function responsibilities: SDRs see prospecting data without financial data, CSMs see health data without sales commission data, finance sees invoice data without coaching notes. The alignment supports role-appropriate visibility.
Head-to-head
Strkr full-lifecycle vs sales-only CRM plus tools stack.
Sales-only CRMs typically require separate tools for prospecting (Outreach, Salesloft), proposal (PandaDoc, Proposify), customer success (Gainsight, ChurnZero), and expansion tracking. The comparison below is Strkr's full-lifecycle coverage against the typical sales-CRM-plus-tools stack.
Feature
Strkr
Sales CRM + separate tools
Prospecting
Native cadences, engagement tracking
Separate Outreach/Salesloft tool
Qualification
Codified framework native
Varies by rep without enforcement
Discovery
Call findings on deal record
Separate call recording tool
Proposal
Native with CRM-linked pricing
Separate PandaDoc/Proposify tool
Negotiation
Exception tracking with approval
Email thread with attachments
Close
Native e-signature with CRM state transition
DocuSign with manual update
Onboarding handoff
Context-preserving handoff workflow
Separate CS tool with sync
Retention
Account health rollup native
Separate Gainsight/ChurnZero tool
Expansion
Trigger workflow across functions
Manual identification process
Cross-function reporting
Native joins
BI tool with sync pipelines
How teams use Strkr
How teams run full-lifecycle sales on Strkr.
The common thread across teams running full-lifecycle sales on Strkr: function handoffs had been dropping context, and tool stack had been accumulating sync maintenance. The playbooks below are motions on customer accounts.
95-rep SaaS consolidating stack
Replaced sales CRM + 5 tools with Strkr in 16 weeks.
A 95-rep SaaS team replaced sales CRM plus 5 tools (Outreach for prospecting, Gong for discovery, PandaDoc for proposal, DocuSign for close, ChurnZero for retention) with Strkr during 16-week migration. The full-lifecycle consolidation eliminated sync-lag between functions and reclaimed roughly 32 hours per week of ops-lead time previously spent on reconciliation. The cross-function reporting supported coaching conversations that separate-tools stack had not supported.
A mid-market SaaS team's renewal rate improved by roughly 11 percentage points after implementing context-preserving sales-to-CSM handoff on Strkr. The CSM team gained visibility into sales commitments, stakeholder relationships, and risks the AE had flagged. The first-30-day onboarding conversation ran on sales context rather than re-discovery.
Proactive retention
Account health rollup replaced reactive renewal.
A growth-stage team with churn problem replaced reactive renewal with proactive retention using Strkr's account health rollup. The signal patterns (usage drops, engagement decreases, ticket volume spikes) surfaced at-risk accounts weeks ahead of renewal conversation. The CSM team intervened on at-risk accounts rather than reacting at renewal. The churn rate declined by roughly 28 percent across two quarters.
Systematic expansion
Expansion trigger workflow attributed to expansion revenue.
A SaaS team implemented expansion trigger workflow on Strkr: CSM flags expansion opportunity when usage threshold or feature-request pattern triggers, AE receives engagement task with account context, sales ops configures expansion deal from template. The systematic expansion attributed to roughly 18 percent of quarterly new ARR, which exceeded prior ad-hoc approach.
Function-level coaching
Cross-function metrics drove coaching focus.
A sales leader at a 80-rep team used cross-function metrics on Strkr to drive coaching focus: SDR source correlation to close rate identified highest-value prospecting patterns, AE discovery depth correlation to CSM retention identified highest-value discovery patterns. The coaching focus shifted rep development to highest-leverage behaviors.
The functions of sales, prospecting through retention, on one CRM instead of a stack of tools.
Start a 14-day trial with the full-lifecycle configuration enabled: prospecting with cadences and engagement tracking, qualification with codified framework, discovery with call findings on deal record, proposal with CRM-linked pricing, negotiation with exception approval, close with e-signature workflow, onboarding with context-preserving handoff, retention with account health rollup, expansion with trigger workflow across functions.
Sales organizations run across 9 specific functions: prospecting (finding target buyers through list building, outbound, engagement tracking), qualification (filtering opportunities through framework like BANT or MEDDIC), discovery (understanding buyer needs through call findings and stakeholder mapping), proposal (specifying scope and pricing in formal document), negotiation (agreeing terms through exception approval and redline tracking), close (committing through e-signature workflow), onboarding (activating customer through sales-to-CSM handoff), retention (keeping customer through account health monitoring), expansion (growing account through trigger workflow). Each function has roles, metrics, and CRM requirements.
Who owns which function?
Ownership varies by team structure. Common patterns: SDR/BDR owns prospecting and qualification; AE owns discovery, proposal, negotiation, close; sales engineer supports discovery and proposal technical depth; sales ops supports qualification, proposal, negotiation across functions; CSM owns onboarding, retention, expansion identification; sales leadership owns function metrics and coaching across all functions. For smaller teams, roles merge (AE handles prospecting through close, CSM handles onboarding through expansion). For larger teams, functions split further (specialist AEs for segment, dedicated expansion team).
Can we run full-lifecycle sales on one CRM?
Yes. Strkr is designed for full-lifecycle coverage with primitives for each function. The full-lifecycle model eliminates tool stack (prospecting tool, proposal tool, customer success tool, expansion tool) and sync maintenance between tools. For teams with sophisticated requirements in function (enterprise prospecting at scale, complex customer success workflows), specialist tools remain reasonable. For most mid-market and growth-stage teams, full-lifecycle CRM beats tool stack on TCO and handoff quality.
Function-level metrics: prospecting measured by qualified opportunities per SDR per week, source conversion rates; qualification measured by criteria adherence, SDR-to-AE handoff quality; discovery measured by stakeholder depth, pain-point specificity; proposal measured by assembly time, win rate per template; negotiation measured by exception rate, approval cycle time; close measured by signature cycle time, close rate per stage; onboarding measured by time-to-first-value, milestone completion rate; retention measured by renewal rate, expansion rate; expansion measured by trigger-to-expansion conversion, expansion attribution. The metrics support function-level coaching and resource allocation.
How does the expansion function work?
Expansion function identifies expansion opportunities through trigger workflow: CSM flags opportunity when usage threshold, feature-request pattern, stakeholder change, or customer success signal triggers. The AE receives engagement task with account context. The sales ops configures expansion deal from template. The expansion motion is systematic rather than ad-hoc, which drives measurable expansion revenue attribution. For teams at scale, dedicated expansion team may own function; for smaller teams, AE handles expansion within primary account book.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
We use cookies.
Essential cookies keep the site working. If you accept, we also enable Google Analytics
so we can see which pages help and which don't. Reject to opt out entirely. Details in our
Privacy Policy.
