Sales looks like persuasion from the outside. Inside a company, most cross-functional pain is language and handoffs: people debate deal strategy with the wrong words, then surprise Delivery or Customer Success at “closed-won.” This hub teaches shared language for collaboration, not closing scripts.
This is the How Sales Works function hub. Use it if you are in product, marketing, CS, ops, finance, or HR and you touch deals; if you just joined a sales team and need a map; or if you manage a team that sits next to revenue. For a narrative overview, start the cluster with How sales works in a company after Module 1.
We do not invent win rates, cycle times, or quota attainment norms. Your company’s methodology and CRM definitions win.
Who this hub is for
Stay here if you need pipeline vocabulary, stage concepts, forecast categories, or cleaner requests into sales time.
Use stage hubs instead if you need new-hire runway (New Hire), IC scope (Individual Contributor), first-line management habits (New Manager), or portfolio leadership (Director / VP).
Sibling hubs: money language on Finance for non-finance managers, people routing on How HR works, interface design on How departments work together.
The insight: shared language for handoffs, not persuasion training
Position sales literacy as shared language for handoffs. The mandatory first module is a pipeline vocabulary card: stage concepts, who owns each handoff, and what “commit” versus “upside” means in meetings. Non-sellers who skip this card create noise in forecast reviews and broken delivery starts.
Module 1 (mandatory): Pipeline vocabulary card
Copy into a one-pager. Fill with your CRM labels where they differ.
Stage concepts (names vary; learn the idea)
| Concept | Plain meaning | Typical handoff owner (confirm locally) |
|---|---|---|
| Prospecting / outbound or inbound start | Finding and qualifying early interest | SDR/BDR or AE, depending on motion |
| Discovery | Learning problem, stakeholders, and fit | AE (often with SE support) |
| Solution / evaluation | Mapping product to need; demos, proofs | AE + SE / solutions |
| Proposal / commercial | Pricing, terms, paperwork path | AE (+ deal desk / finance as designed) |
| Negotiation / legal | Terms, security, procurement | AE + legal/security partners |
| Closed-won / closed-lost | Terminal outcomes in the CRM | AE owns CRM hygiene; CS/Delivery own post-won start |
| Handoff to Delivery / CS | Turning a won deal into a successful start | Named handoff owner (AE, CS, implementations) |
Deep dives: Sales pipeline stages explained, What closed-won means, Sales to delivery / CS handoff.
Commit vs upside (meeting language)
| Term | Plain meaning in many forecast cultures | What non-sellers should not do |
|---|---|---|
| Commit | Deals leadership treats as expected to land in the period (definition is company-specific) | Do not “help” by re-categorizing someone else’s deals in the meeting |
| Upside | Possible upside beyond commit; higher uncertainty | Do not treat upside as promised revenue in your plans |
| Pipeline | Open opportunities in stages | Do not confuse pipeline dollars with closed revenue |
| Funnel | Often a marketing or conversion view; related but not identical to CRM pipeline in every company | Ask which view the slide uses |
Ban list for this hub: invented win rates, average cycle lengths, and stage conversion “standards.” If you need an example timeline for training, label it fictional and methodology-agnostic.
Fill-in for your company
- Our stage names: __
- Who updates stage in the CRM: __
- Who runs forecast call: __
- Who owns CS/Delivery handoff checklist: __
- Where security/legal enter: __
Read next after Module 1: How sales works in a company.
Module 2: Sales glossary
| Term | Plain meaning |
|---|---|
| Opportunity | A tracked deal in the CRM with a stage and usually an amount and close date. |
| AE | Account executive: often owns pursuing and closing opportunities. |
| SDR / BDR | Sales/business development roles focused on early pipeline creation (titles vary). |
| SE | Sales engineer / solutions engineer: technical discovery and demos in many B2B motions. |
| CS / AM | Customer success / account management: post-sale value and expansion (design varies). |
| MEDDIC / BANT | Optional qualification frameworks some teams use. Definitions only; not universal policy. |
| Quota | A target assigned to a seller or team for a period. |
| Forecast | Expected results versus quota/plan; Finance cares because it feeds company planning. See Quota, forecast, why Finance cares. |
Module 3: Who owns this deal stage? decision tree
- Early interest, no discovery yet? Usually SDR/BDR or AE inbound owner. Ask sales ops who routes leads.
- Active discovery or evaluation? AE owns the opportunity; SE supports as designed.
- Commercial proposal? AE; involve deal desk/finance if your company requires it.
- Security, legal, procurement? AE coordinates; specialists own their reviews.
- Closed-won handoff? Follow the handoff checklist; CS/Delivery owns successful start criteria.
- Forecast category debate? Sales leadership / AE owns categories; non-sellers ask clarifying questions, they do not overwrite.
Module 4: Pipeline-meeting observer worksheet (non-sales)
Use when you attend a forecast or pipeline review as a partner.
- Meeting goal today (forecast accuracy, deal help, risk): __
- Stages I heard: __
- Commit vs upside moments I noted: __
- Where my team was asked for help: __
- Risks that are product / ops / legal, not “try harder”: __
- One follow-up I will send async (owner, date, artifact): __
- What I will not do (no re-forecasting others’ deals): __
Module 5: Cross-functional request template to sales
Fields only. Keep it short.
- Requesting team / person: __
- Deal or segment context (CRM ID if any): __
- Decision or artifact needed from sales: __
- By when (real deadline): __
- What we already tried: __
- Impact if late (customer / launch / revenue plan): __
- Single thread owner on our side: __
For discovery etiquette as a non-seller: Discovery calls for non-sales.
Ordered read-first paths by audience
Complete Module 1 first.
Path A: Non-sales collaborator (product, marketing, CS, ops, finance, HR)
- How sales works in a company
- Sales pipeline stages explained
- What closed-won means
- Sales to delivery / CS handoff
- Discovery calls for non-sales
- Quota, forecast, why Finance cares if you sit in planning
Stage CTA: IC hub for influence without authority; How departments work together for interface cards on recurring handoffs.
Path B: New seller (AE / SDR / SE)
- Module 1 with your CRM admin or manager
- How sales works in a company
- Sales pipeline stages explained
- Company methodology docs (always win over blogs)
- Sales to delivery / CS handoff before your first won deal
- New Hire hub if access and orientation are still noisy
Path C: Manager / director touching revenue conversations
- Path A through forecast literacy
- Finance for non-finance managers Module 1 so commit language meets budget language cleanly
- Director / VP hub if portfolio interfaces are the real job
Sample start (no invented metrics)
Illustrative: A product manager joins forecast reviews. They complete the vocabulary card, learn which stage names match the CRM, and stop asking “why isn’t this closed?” on upside deals. They use the request template for roadmap proof points instead of side chats during the call.
Role differences from an outsider’s view (orientation)
Titles and splits vary. Rough orientation only: SDR/BDR create and qualify early pipeline; AEs own opportunities through close; SEs handle technical depth; CS/AM own post-sale outcomes and sometimes expansion; sales ops/enablement own systems and process. Ask for your org chart’s real RACI.
Failure modes when partners misunderstand pipeline language
- Treating pipeline as cash in the bank
- Surprising Delivery on closed-won with missing scoping
- Debating persuasion tips instead of handoff quality
- Pulling sellers into meetings without a decision or artifact
- Inventing cycle-time “norms” in planning docs
When to use this hub vs. company methodology
Use this hub for shared vocabulary and pathing. Use your company’s sales playbook, CRM, and compensation docs for how you are measured. If those conflict with a blog definition, the company wins.
CTA: stage hubs and sibling function hubs
Stage hubs: New Hire · Individual Contributor · New Manager · Director / VP
Sibling function hubs: How HR works · Finance for non-finance managers · How departments work together