How Sales Actually Works Inside a Company

Sep 10, 2026 | Blog, Sales at Work

If you work in ops, product, finance, engineering, or customer success, you have probably heard “sales is working it” and still not known what that meant. Deals appear in Slack. Forecast numbers move. Someone asks you for a one-off demo, a custom security answer, or a rush implementation date. You want to help without guessing, or without slowing a real opportunity by jumping in cold.

This article is a mental model for how sales works in a company: who owns what, how a lead becomes revenue, what “pipeline” actually means, how incentives shape behavior, and how non-sales people can collaborate without becoming salespeople. Titles and stages vary by employer. Treat what follows as a common B2B map, not a universal org chart.

You’ll leave able to read a sales conversation the way sales leaders do: as stages, evidence, and risk, not as charm, luck, or mystery.

Sales is a system, not a personality contest

The useful insight for everyone outside the quota team: sales is not a personality contest. It is a system of stages, evidence, and risk transfer.

A deal advances when the buyer’s commitment looks more real and the seller’s risk looks more managed. Non-sales people who learn to speak in stage evidence get better outcomes than people who only ask “when will it close?” Better questions sound like: “What changed since last week?” “What does the buyer still need to believe?” “Who else has to say yes, and have we met them?” Those questions help sales, protect delivery, and keep forecast conversations honest.

If you remember nothing else, remember that.

What sales does in a company (the job in one paragraph)

Sales finds, qualifies, and advances opportunities so the company can exchange a defined offer for a signed commercial commitment. Good sales also shapes deal quality: scope, price, terms, stakeholders, and promises that other teams must keep. Bad sales can still book revenue that creates pain downstream. “What sales does” is therefore both revenue creation and risk shaping for the rest of the company.

Related money context for non-finance readers: how companies make and spend money.

Main roles on a typical sales team

Not every company uses these titles. Some combine roles. Some add overlays (industry specialists, partner managers, renewals reps). Here is a plain glossary of the names you will hear most often in mid-market and enterprise B2B.

Role	Often owns	Rarely owns alone
SDR / BDR (sales / business development rep)	Outreach, qualifying inbound or outbound interest, booking meetings for AEs	Closing large deals, custom pricing, deep product architecture
AE (account executive)	Running the opportunity, discovery, proposal, negotiation, closing	Long-term post-sale relationship in companies with dedicated CS/AM
SE / SC (sales engineer / solutions consultant)	Technical discovery, demos, proof concepts, answering “will it work here?”	Commercial terms and quota (usually)
AM (account manager)	Expanding and retaining named accounts, commercial relationship after the first sale	Brand-new logo hunting (often AE territory)
CSM (customer success manager)	Adoption, outcomes, health, renewal readiness (sometimes shared with AM)	Original prospecting

Illustrative mid-market shape (not a prescription): marketing creates interest → SDRs qualify and schedule → AEs own opportunities → SEs support complex evaluation → legal/finance help on paper → CS/AM take the customer after close. Your company may collapse SDR and AE, skip SE for simple products, or put renewals under CS instead of AM.

Inside sales vs field sales: inside sales usually works remotely by phone, video, and email. Field (or “outside”) sales travels for on-sites, events, and relationship-heavy enterprise deals. Many teams blend both. The distinction is motion and travel, not moral rank.

How a lead becomes an opportunity and then revenue

Think of a path, not a magic trick.

Lead / inquiry. Someone shows interest or fits a target profile. Marketing and SDRs often share this pool.
Qualified conversation. Someone confirms problem, fit, timing, and basic authority (definitions vary; ask your sales ops partner how your CRM defines “qualified”).
Opportunity. The AE opens a deal record with a stage, amount estimate, and next step. This is when leaders start treating it as pipeline.
Evaluation. Discovery, demos, security reviews, pilots, business case work, multi-threaded meetings with more buyers.
Proposal / negotiation. Commercial offer, legal review, procurement, redlines.
Closed-won or closed-lost. Won means the CRM records a win. Lost means it did not. Neither word is the full economic story. See later articles on closed-won vs cash and recognition if your ops team lives in that gap.
Handoff and delivery. Implementation, onboarding, success criteria. Revenue quality often shows up here, months after the celebration Slack message.

A sales cycle is the time and sequence from serious pursuit to decision. Cycles vary because buyers vary: deal size, number of stakeholders, regulated industries, custom work, and competitive bake-offs all stretch or shrink the path. Do not treat a friend’s “our deals close in two weeks” story as a benchmark for your company. Ask your team how this segment usually behaves, and treat averages as local folklore until sales ops shows you real internal data.

Marketing, sales, and customer success: who owns which stretch

A simple ownership map for the customer journey:

Marketing often owns awareness, demand generation, content, events, and early lead capture. Success looks like interested people and clear handoff criteria.
Sales often owns converting qualified interest into a commercial commitment. Success looks like pipeline that turns into bookings with terms the company can fulfill.
Customer success / delivery often owns making the customer successful after the sale and protecting renewals and expansion. Success looks like adoption, outcomes, and healthy accounts.

Handoffs are where companies leak trust. If marketing passes “leads” that sales will never call, or sales sells a vision delivery cannot staff, the customer feels the seam. Good collaboration means shared definitions (what is a qualified lead?), shared notes (what was promised?), and shared timing (when should CS join before the signature?).

What “pipeline” means in practice

Pipeline is the set of open opportunities a sales team is actively working, usually visible in a CRM as rows with stage, amount, owner, and dates. Leaders obsess over it because pipeline is the near-term story of future revenue before it is booked. Hiring, capacity, and spend plans often lean on whether that story looks thin, healthy, or inflated.

Pipeline is not the same as a marketing funnel. A funnel often describes volume moving through awareness and interest. Pipeline usually means named deals with owners and stages. For how to sit in a review without theater, see pipeline / status meetings.

Healthy pipeline talk sounds like: stage, evidence, next step, risk, and what changed. Unhealthy talk sounds like: “it’s looking good,” with no buyer evidence and a close date that slips every Friday.

How salespeople are usually compensated (and how that shapes behavior)

Most quota-carrying sellers earn a mix of base salary and variable pay (commission, bonus, or both) tied to bookings, revenue, or other targets. Exact plans differ widely by company, segment, and role. SDRs may be paid on meetings or qualified opportunities. AEs may be paid on closed business. AMs may be paid on retention and expansion. Do not invent “typical” commission rates in your head; ask how your partners are measured if you need to interpret urgency.

Incentives shape behavior in predictable ways:

End-of-quarter urgency is often real because variable pay and quota periods are real.
Discount pressure can rise when a close date matters more than margin.
Custom promises can appear when a seller needs a win and delivery pain is someone else’s problem later.
Sandbagging (holding deals back) or over-optimism can both show up when forecast politics meet compensation.

None of that makes sales “greedy.” It makes sales human under a scoreboard. Your job as a partner is to make the right deal easy: clear product limits, fast security answers, honest capacity, and early escalation when a promise would break the company.

Meetings and rituals non-sales people should expect

You may be invited to some of these. You do not need to attend all of them.

Pipeline review. Inspect open deals, risks, and next steps. Best when exception-based, not a full tour of every green row.
Forecast call. Translate pipeline into what leaders believe will actually close in a period. Finance listens closely because hiring and spend ride on trust in that number. For adjacent planning language, see budget vs forecast vs actual.
Deal desk / deal review. Cross-functional check on nonstandard pricing, legal terms, or delivery risk before a big commitment.
QBR (quarterly business review). Sometimes internal (team performance), sometimes customer-facing (account outcomes). Ask which one you are walking into.
Win/loss or deal retrospective. Learning loop after outcomes. Useful when blame is banned and evidence is welcome.

If you are asked into a customer call, clarify your role: expert, listener, or decision-maker. Ambiguous guests create awkward silence or accidental commitments.

Where non-sales roles create friction or acceleration

Friction patterns

Slow security or legal responses that stall a real evaluation
Product silence when a buyer asks a hard “will you roadmap X?” question and nobody owns the answer
Ops giving a date that sales treats as a promise without capacity math
Finance surprises on discount or payment terms late in negotiation
Engineers jumping on calls without context and inventing scope live

Acceleration patterns

A crisp one-pager on limits (“we can do A; B needs a SOW; C is not available”)
Named owners for security questionnaires with a turnaround norm
Product joining only when the question matches their decision rights
CS previewing onboarding reality before the contract is signed
Written notes after every multi-team customer meeting: decisions, promises, open risks

What to ask a sales partner before you join a customer conversation

Use a short pre-brief. Five minutes saves a bad call.

What stage are we in, and what evidence got us here?
What does the buyer still need to believe after this meeting?
Who is in the room on their side (role and power)?
What are we not allowed to promise?
What is the exact ask of me (demo, expert answer, listen-only)?
What happens if they ask for a custom thing: who decides live vs offline?
What should I do if I disagree with something said in the room (Slack the AE? speak up?)?

If the AE cannot answer stage and evidence, you are not late to the party; you are early to a fuzzy one. Help them clarify before you put the company on speakerphone.

Enterprise vs SMB vs self-serve (high level)

Motions differ. The words below are directional, not laws.

Self-serve / product-led: Buyers try or buy with little human sales touch. Sales may still help larger accounts or expansions. Cycle friction is often product UX, pricing page clarity, and support, not multi-threaded negotiation.
SMB sales: Smaller deal sizes, fewer stakeholders, shorter paths, more volume per rep. Custom work is usually limited on purpose.
Mid-market / enterprise: More stakeholders, security and procurement, longer evaluation, heavier SE involvement, and higher cost of a bad handoff. Multi-threading (relationships with more than one buyer) matters because one champion is not a company decision.

When someone says “just close it like the last deal,” check segment. Process that works for a five-seat SMB signup can break an enterprise security review.

What good collaboration with sales looks like week to week

Good collaboration is boring in the best way:

You know who your AE/SDR partners are for your area.
You have a shared place for deal context (CRM notes, a deal channel, a brief doc).
You respond to real late-stage risk faster than to vague “can you hop on a call?” fishing.
You speak in evidence: changes, beliefs, blockers, owners.
You protect the customer from conflicting messages across marketing, sales, and delivery.
You escalate early when a request would create undeliverable scope.
You celebrate clean wins, and you also study messy wins so they do not become the template.

Week to week, that looks like short Slack clarity, occasional deal reviews, and almost never a surprise custom promise discovered after signature.

A plain RACI for a live deal (illustrative)

Use this as a conversation starter with your sales lead; adjust to your company.

Activity	Sales (AE)	SE	Product	Legal/Finance	CS/Delivery
Qualify and run process	A/R	C	C	C	I
Technical fit / demo	A	R	C	I	C
Commercial terms	A/R	I	C	C/A (policy)	C
Security packet	A	R/C	C	C	C
Delivery date commitments	A	C	C	I	A/R
Post-sale success criteria	C	C	C	I	A/R

R = responsible (does the work), A = accountable (owns the outcome), C = consulted, I = informed. Labels are illustrative.

FAQ

Is sales the same as marketing?

No. Marketing usually creates demand and early interest. Sales usually converts qualified interest into a commercial commitment. In small companies one person may wear both hats; the jobs are still different.

Why does leadership care more about pipeline than about my project status?

Pipeline is a leading story about near-term revenue. Project status matters too, but unpaid or unbooked work does not fund the plan the same way. Connect your project language to revenue risk or capacity when you need airtime in a revenue meeting.

Should I ever say no to joining a sales call?

Yes, when you have no brief, no decision rights, or the ask is “just vibe with the customer.” Offer a written answer or a scheduled expert slot instead of a cold join.

What if sales promised something we cannot deliver?

Escalate with facts, not blame: what was promised, to whom, in what channel, and what delivery can offer instead. Involve the AE and a manager early. Quietly “making it work” trains the system to oversell again.

Do all companies use SDRs and AEs?

No. Many startups combine roles. Some product-led companies have few quota sellers. Learn your local map before you assume a title means the same thing it meant at your last employer.

Soft next reads on All Things Workplace

If your team is building deeper sales literacy next, natural follow-ons are pipeline stages in plain English, quota and forecast for finance partners, and the sales-to-CS handoff checklist: same system lens, sharper zoom.