The question sounds rhetorical, but it isn't. In many companies you hear it asked in two mirror-image versions: when the sale goes well, the credit goes to the salesperson; when it goes badly, the blame goes to the customer \"who doesn't get it\" or to the market \"that has stalled.\" The customer's perception follows the same asymmetry: when satisfied, they say they bought; when dissatisfied, they say they were sold to. Responsibility shifts depending on the outcome, never beforehand.
\nThis article starts from the original question — who really decides in a sales negotiation — and arrives at a less obvious conclusion: the question has no useful answer until the company has defined, before the negotiation, what the salesperson is accountable for and what the organization is accountable for. It is a matter of role design, not of assigning blame.
\nIn the most common picture, the customer is an autonomous decision-maker: they know what they need, weigh the alternatives, and choose. In this view the salesperson is an assistant — they take the order, fulfill it, and collect payment. If the purchase turns out to be wrong, the responsibility lies with whoever made the choice.
\nBut how often does the customer really have the information to decide alone?
\nIn practice, much less often than this picture suggests. Someone buying a window frame doesn't know the materials like someone who has been installing them for twenty years; someone buying management software doesn't know which features will prove critical six months from now; someone who hires a consultant does so precisely because they can't solve the problem alone. If customers were always able to decide well on their own, the competent salesperson would be superfluous: a price list would be enough.
\nSo there is a second picture: the salesperson as a consultant, not an assistant. In this view their job is not to give customers what they ask for, but to understand the problem, select the right solution and — if necessary — steer the customer toward a different option from the one they walked in with. It is the salesperson who, in practice, decides what to propose; the customer decides whether to accept. This is not an ideological picture: it is the central thesis of Neil Rackham's work on complex sales, according to which the most effective salespeople devote the core of the conversation to investigating the customer's problem with questions, not to presenting the product [2].
\nThe two mindsets produce opposite behaviors in the same situation. A customer asks for an expensive product from a certain brand; the salesperson-assistant sells it and closes. The salesperson-consultant, if they know an alternative better suited to the customer's problem, proposes it even at the cost of complicating the negotiation. The first maximizes the transaction; the second takes on responsibility for the customer's result.
\nThe split of responsibility is not the same for every sale. A useful criterion is to distinguish between subjective and objective purchases.
\nWhat is the difference between selling a sofa chosen for its looks and selling a system that has to solve a technical problem?
\nIn the first case — the subjective purchase — the decision depends on taste, preferences, criteria that belong to the customer alone. The salesperson can inform and advise, but the final choice legitimately belongs to the customer, and with the choice most of the responsibility. If, after a year, the customer no longer likes the color of the sofa, it is not the fault of whoever sold it.
\nIn the second case — the objective purchase — the customer buys to solve a specific, measurable problem: a window that insulates, software that handles invoicing, a service that delivers a result. Here the information asymmetry is entirely on the salesperson's side: they know the products, the limits, the alternatives. Economics has studied this condition at least since 1970, when George Akerlof described how markets in which the seller knows much more than the buyer tend to deteriorate — to the point of driving out quality products — if the better-informed party cannot find a way to make its fairness credible [1]. And where there is an asymmetry of expertise, responsibility for the proposal follows expertise. A salesperson who, in an objective purchase, lets the customer choose an unsuitable solution alone is not being neutral: they are simply avoiding the hard part of their job.
\nThis distinction answers half of the initial question: in objective purchases, responsibility for the proposal lies with the salesperson, not the customer. But it immediately opens the next question, the one that concerns the company: responsible for what, exactly? For the proposal or for the outcome? And who decided that?
\nHere the question moves to a different level. Asking \"who is responsible for a sale\" — the customer or the salesperson — assumes that someone has defined, beforehand, what it means to be responsible for a sale. In most companies this definition doesn't exist: there is a revenue target, and the word \"responsibility\" is used as a synonym for \"blame when the target isn't met.\"
\nBut can you be responsible for something that has never been defined?
\nA responsibility, in the organizational sense, is the obligation to answer for something that is under your control. Both conditions matter. If it isn't clear what you answer for, the responsibility is undetermined and gets negotiated after the fact, typically by offloading it onto someone else. If what you are supposed to answer for is not under the control of the person answering for it, it is not a responsibility: it is a lottery with a pre-selected culprit.
\nThe outcome of a single negotiation is not fully under the salesperson's control. It depends on the customer's real budget, on competitors, on decision timelines, on variables that no sales skill fully governs. What is under their control, instead, is the process: how they prepare, what questions they ask to understand the problem, how they build the proposal, how they handle objections, whether and how they follow up. This is what they can and must answer for.
\nSo the initial question is turned on its head: the salesperson is responsible for the sales process, not for the outcome of a single negotiation. And the company is responsible for giving them a process to answer for — defined, taught, observable. A company that hasn't defined its own sales process and then asks the salesperson \"who is responsible for this lost sale\" is asking the wrong question of the wrong person: the first missing responsibility is its own.
\nThe distinction between process and outcome deserves to be made operational, because it is where many companies get confused. It is not an improvised distinction: the marketing literature has formalized it since 1987, when Anderson and Oliver described the difference between sales force control systems based on behaviors (what the salesperson does) and systems based on outcomes (what they produce), arguing that the two approaches tend to generate different sales attitudes and behaviors [3].
\nIf the salesperson is accountable for the process and not the outcome, who owns revenue?
\nThe answer is that outcomes don't disappear: they move to a different level. The single outcome — this negotiation, this customer — is too exposed to chance to be a sensible individual responsibility. The aggregate result over a period — the close rate over a quarter, the average value of proposals, the quality of customers acquired — is instead a legitimate indicator, because with volume random variance shrinks and what remains truly reflects the quality of the process carried out.
\nIn practice, the responsibility of a well-defined sales role is organized on three levels.
\nProcess execution. The salesperson is accountable for carrying out the planned activities in the planned way: qualifying leads according to the agreed criteria, conducting the needs analysis before the proposal, presenting options according to the defined logic, recording progress. This level is entirely under their control, and therefore the responsibility is entirely theirs.
\nQuality of advice. In objective purchases, the salesperson is accountable for having proposed the solution suited to the customer's problem — even when it differs from the one requested — and for having made limits and alternatives explicit. This is the part of the role that distinguishes the consultant from the assistant, and it must be written into the role, not left to individual sensitivity.
\nAggregate results. Over the period, the salesperson contributes to outcome targets that the company sets based on its own track record and its own market. If the process is executed well and aggregate results repeatedly fall short, the information is valuable: it says the problem lies in the process itself, in the price, in the product or in the positioning — that is, in responsibilities that belong to the company, not to the individual.
\nThis architecture has an important side effect: it turns the conversation about results into an analysis instead of a trial of intentions. When it is missing, every sales meeting degenerates into the same dynamic — the company points to the number, the salesperson points to the market — and neither learns anything.
\nDefining the responsibilities of a sales role follows the same logic as any other role in the company — the general method is described in how to define the responsibilities of a role — with a few specific features.
\nWhere do you start, if today the \"sales process\" exists only in the heads of the people who sell?
\nA workable path comes down to four steps.
\nMake the existing process explicit. Before designing the ideal process, it pays to observe the real one: how do the deals that close well start today? Which steps recur? Often the most effective salesperson applies a method they have never formalized. Writing it down — phases, activities, criteria for moving to the next step — is the first act by which the company takes on its share of responsibility.
\nSeparate what is controllable from what isn't. For each phase, distinguish the activities that depend on the salesperson (number of needs analyses conducted, completeness of proposals, follow-up times) from the outcomes that also depend on other factors (signature, amount, the customer's decision time). The former become direct responsibilities; the latter, indicators to read in aggregate.
\nWrite responsibilities into the role, not the person. Responsibility should be assigned to the sales role as such, so that it survives employee turnover and applies in the same way to whoever joins. Sentences like \"is accountable for qualifying leads according to criteria X and Y\" work; \"must deliver results\" doesn't, because it says neither what you answer for nor how it is observed.
\nDefine in advance how performance is evaluated. Who evaluates, how often, looking at which evidence. If this part is missing, everything else remains a writing exercise: a responsibility that no one ever checks is indistinguishable from one that doesn't exist.
\nA sign that the assignment has worked: faced with a lost deal, the company can say which step of the process didn't work — or conclude, just as clearly, that the process was executed well and the outcome depended on external factors. If the only possible analysis is \"the salesperson didn't close,\" responsibilities are not yet defined.
\nThe most delicate point remains: how do you evaluate a person whose work produces outcomes that are only partly controllable?
\nShould a salesperson who did everything right and didn't close be evaluated the same as one who closed by luck?
\nNo — and that is exactly what an evaluation based only on outcomes cannot tell apart. Looking only at the final number, the rigorous salesperson who goes through an unlucky quarter and the sloppy one who ran into two easy customers look indistinguishable, or worse, reversed. Over time, this blindness tends to select the wrong behaviors: it pushes people to force closes, to promise what the product doesn't deliver, to chase today's transaction at the expense of tomorrow's relationship — a dynamic consistent with what the literature on outcome-only control systems has described for decades [3]. The salesperson-assistant described at the beginning isn't born that way by temperament: they are produced by evaluation systems that reward only the immediate outcome.
\nAn evaluation consistent with defined responsibilities looks at three things together: process execution (whether the controllable activities were carried out, and how), quality of advice (whether proposals fit customers' problems, whether acquired customers stay), and aggregate results over the period, read as an indicator to interpret and not as a verdict. When the three levels diverge — process executed well, results missing — the divergence is the most useful information the company can receive about its sales model.
\nThe moment when this evaluation creates value is the periodic conversation between manager and salesperson: analysis of representative deals, discussion of the process, agreement on what to change. For it to work, it needs the same care as any evaluative conversation — describing observed behaviors instead of passing judgment on the person — covered in more depth in how to give feedback to team members.
\nWhat is the difference between process responsibility and outcome responsibility?\nProcess responsibility covers activities under the salesperson's direct control: qualifying leads, conducting the needs analysis, building the proposal, handling follow-ups. Outcome responsibility covers results, which also depend on external factors. The literature on sales force control systems distinguishes the two approaches precisely because they produce different sales behaviors [3].
\nIf the salesperson is accountable for the process, does commission on sales still make sense?\nThe two are not mutually exclusive. A variable component tied to aggregate results over a period remains compatible with responsibilities defined on the process: the critical point is to prevent the outcome of a single deal from becoming the only yardstick, because a system based only on outcomes tends to reward forced closes at the expense of the customer relationship [3].
\nHow do you evaluate a newly hired salesperson who has no aggregate results yet?\nIn the first months, the most sensible level of evaluation is the process: quality of the needs analysis, completeness of proposals, adherence to the agreed steps, learning the product. Aggregate results become readable only when the volume of deals is large enough to reduce the weight of chance — with progressive targets declared in advance, not full targets from day one.
\nShould the salesperson always propose the most suitable alternative, even if the customer asks for something else?\nIn objective purchases, where the customer buys to solve a measurable problem, yes: the asymmetry of expertise is on the salesperson's side, and with expertise comes responsibility for the proposal [1]. In subjective purchases, driven by personal taste, the salesperson informs and advises, but the choice legitimately remains the customer's. The distinction must be written into the role, not left to individual sensitivity.
\nThe initial question — is responsibility for a sale the customer's or the salesperson's? — allows a first-level answer: in subjective purchases the customer decides, and the greater share of responsibility is theirs; in objective purchases expertise is on the salesperson's side, and with expertise comes responsibility for the proposal.
\nBut the most useful answer for anyone running a business sits one level higher: the question is badly framed until the company has defined responsibilities. The salesperson is accountable for the process — preparation, needs analysis, quality of the proposal, management of the negotiation — because that is what they control. The company is accountable for having given them a process to answer for: defined, written into the role, evaluated with criteria set in advance. The single sale, lost or closed, goes back to being what it is: an event to analyze, not a trial.
\nAn organization that has done this work can tell deals lost to bad luck from deals lost to mistakes, evaluates people on what depends on them, and uses aggregate results to improve the model instead of looking for culprits. It is a stance that applies to the sales role as to every other role: first you define responsibilities, then — and only then — does it make sense to ask whose responsibility it is.
\n[1] Akerlof, G. A. (1970). The market for \"lemons\": Quality uncertainty and the market mechanism. The Quarterly Journal of Economics, 84(3), 488–500. https://doi.org/10.2307/1879431 — Foundational reference.
\n[2] Rackham, N. (1988). SPIN Selling. McGraw-Hill. — Practitioner book on selling. It presents the author's proprietary research, never published in a peer-reviewed venue and not verifiable at the primary source: cited for the arguments it makes, not as a source of data.
\n[3] Anderson, E., & Oliver, R. L. (1987). Perspectives on behavior-based versus outcome-based salesforce control systems. Journal of Marketing, 51(4), 76–88. https://doi.org/10.1177/002224298705100407 — Foundational reference.
","headings":[{"level":2,"text":"Who decides what to buy: the customer who chooses or the salesperson who steers?","id":"who-decides-what-to-buy-the-customer-who-chooses-or-the-salesperson-who-steers"},{"level":2,"text":"Subjective and objective purchases: where the customer's choice ends","id":"subjective-and-objective-purchases-where-the-customers-choice-ends"},{"level":2,"text":"Why the question is badly framed: without defined responsibilities there is no one responsible","id":"why-the-question-is-badly-framed-without-defined-responsibilities-there-is-no-one-responsible"},{"level":2,"text":"Process responsibility and outcome responsibility: what it means for a sales role","id":"process-responsibility-and-outcome-responsibility-what-it-means-for-a-sales-role"},{"level":2,"text":"How to assign clear responsibilities to a sales role","id":"how-to-assign-clear-responsibilities-to-a-sales-role"},{"level":2,"text":"Evaluating a salesperson without putting everything on the outcome","id":"evaluating-a-salesperson-without-putting-everything-on-the-outcome"},{"level":2,"text":"FAQ","id":"faq"},{"level":2,"text":"Conclusion","id":"conclusion"},{"level":2,"text":"Sources and references","id":"sources-and-references"}],"tldr":"A deal goes badly: the customer doesn't buy, or buys and then regrets it. Whose responsibility is it? The customer's, since in the end they are the one who signs and pays? Or the salesperson's, who led the conversation, selected the proposals and steered the decision?","tldrItems":null}