Sales Organization Design and Workforce Capacity

Introduction

Sales organization design is the deliberate arrangement of sales roles, reporting relationships, territories, customer responsibilities, processes, and resources so that an organization can create customer value profitably. Workforce capacity refers to the amount of selling work the salesforce can perform, expressed through available selling time, skills, coverage, and managerial attention.

These issues are strategic rather than merely administrative. A poorly designed sales organization can create duplicated customer calls, neglected accounts, internal conflict, slow decisions, excessive travel, weak service coordination, and unprofitable growth. A well-designed organization connects corporate strategy with field execution. It answers five practical questions:

1. Who is responsible for each customer, market, product, or activity?
2. How should salespeople be grouped and supervised?
3. How many salespeople are required?
4. Where should they be deployed?
5. How will sales coordinate with marketing, service, finance, and operations?

The most appropriate design depends on customer needs, product complexity, geographic dispersion, channel structure, sales-cycle length, technology, regulatory requirements, and the organization’s strategic priorities. No single structure is universally superior.

Learning Objectives

By the end of this chapter, the learner should be able to:

• compare geographic, product, customer, functional, and matrix sales structures;
• select an organizational structure that fits a firm’s strategy and market complexity;
• estimate salesforce size using workload and productivity approaches;
• deploy salespeople across territories, segments, channels, and activities;
• define sales roles, responsibilities, spans of control, and decision rights;
• design coordination mechanisms with marketing, service, finance, and operations;
• evaluate ethical, technological, and managerial risks in sales organization design.

1. Strategic Foundations of Sales Organization Design

1.1 Structure must follow strategy

A sales organization should implement the firm’s value proposition. A company pursuing low-cost distribution may require standardized territories, efficient routing, inside sales, and tightly controlled processes. A firm selling complex industrial systems may need industry specialists, technical support, account teams, and long-term relationship management. A premium service provider may organize around customer lifetime value rather than geographic proximity.

The design process begins with strategic analysis:

• Market characteristics: number of customers, concentration, growth, buying behavior, and geographic dispersion.
• Offering characteristics: product breadth, technical complexity, customization, margin, and life-cycle stage.
• Customer requirements: service intensity, decision-making complexity, risk, and expected response time.
• Channel strategy: direct sales, distributors, agents, e-commerce, social commerce, or hybrid routes to market.
• Economic constraints: revenue objectives, contribution margins, travel costs, compensation, and available managerial capacity.
• Organizational capabilities: data quality, sales technology, talent, training, and cross-functional maturity.

A useful design principle is alignment. Responsibilities should be assigned to the unit best able to create customer value and control the relevant outcome. For example, a strategic account manager may own the relationship and commercial plan, while operations owns delivery reliability and finance owns credit approval.

1.2 Division of labour and specialization

Sales organizations divide work to improve expertise and productivity. Specialization can occur by location, product, customer type, activity, or a combination of these dimensions. Specialization is beneficial when differences among customers or offerings are substantial enough to justify additional coordination costs.

The central trade-off is between specialization benefits and integration costs. Specialists may understand customers and products more deeply, but customers may face several representatives and the company may experience disputes over ownership. A simple structure is easier to manage but may provide less expertise.

1.3 Principles of sound design

Effective designs generally observe the following principles:

• Clarity: every important customer and activity has an identifiable owner.
• Accountability: responsibility is linked to measurable outcomes and decision authority.
• Customer convenience: the structure should reduce unnecessary contacts and contradictory messages.
• Economy: the expected incremental contribution should justify organizational cost.
• Flexibility: the structure can adapt to new products, segments, channels, and technologies.
• Coordination: interfaces with other functions are explicit rather than dependent on personal goodwill.
• Control: managers can monitor performance without excessive bureaucracy.
• Fairness: territories, quotas, leads, commissions, and opportunities are allocated transparently.

2. Major Sales Organization Structures

2.1 Geographic structure

In a geographic structure, each salesperson or sales team is responsible for a defined territory. A territory may be a country, region, city, postal zone, or group of accounts within a location.

Advantages include low travel duplication, simple accountability, local knowledge, and efficient routing. Geographic structures are especially suitable when the product line is relatively narrow and customers have similar requirements.

Limitations arise when products are technically diverse or customers require industry-specific expertise. A salesperson may be expected to sell products that require different knowledge, and large strategic customers operating across several territories may receive inconsistent treatment.

Geographic design should not be confused with equal-sized territories. Fair territory design considers opportunity, workload, travel, service requirements, and competitive intensity. Two territories with the same number of customers may have very different sales potential.

2.2 Product structure

A product structure assigns salespeople or teams responsibility for particular product lines, brands, technologies, or solutions. It is appropriate when products require specialized knowledge, serve different markets, or have distinct sales processes.

Advantages include technical expertise, stronger product positioning, focused training, and clearer product performance accountability.

Limitations include multiple calls on the same customer, product rivalry, inconsistent account strategies, and higher selling costs. Customers may become confused if separate representatives promote competing or complementary products without coordination.

Product structures are common in technology, pharmaceuticals, industrial equipment, and firms with broad portfolios. They work best when account planning and contact protocols prevent excessive duplication.

2.3 Customer or market structure

A customer structure organizes salespeople around customer segments, industries, account size, buying behavior, or strategic importance. Examples include separate teams for government, small business, enterprise, healthcare, and channel partners.

Advantages include customer intimacy, relevant value propositions, specialized knowledge of buying processes, and alignment with customer economics. A key-account team can coordinate complex relationships and protect high-value accounts.

Limitations include geographic overlap, increased travel, higher fixed costs, and possible neglect of smaller customers. Segment definitions must be evidence-based; otherwise customers may be assigned arbitrarily or moved frequently between teams.

Customer segmentation should consider potential value, service needs, cost-to-serve, risk, and strategic fit—not revenue alone. A high-revenue customer with excessive discounts and service costs may be less attractive than a smaller but profitable account.

2.4 Functional structure

A functional structure divides selling work by activity. Separate roles may handle lead generation, qualification, new-business acquisition, account management, technical demonstration, renewal, customer success, or sales operations.

Functional specialization can increase productivity because individuals repeat and master a narrower set of activities. Inside sales may qualify opportunities before field representatives invest time. Customer success teams may support adoption and renewal after the sale.

The principal risk is fragmented ownership. Customers may experience handoffs, and employees may optimize their own stage rather than the total customer outcome. Functional structures therefore require service-level agreements, shared customer records, handoff rules, and common performance measures.

2.5 Matrix structure

A matrix combines two or more bases of specialization—for example, geography and product, or customer segment and function. A salesperson may report administratively to a regional manager while receiving product direction from a product manager.

The matrix can provide both local responsiveness and specialist expertise. It is useful when products, markets, and customers are all complex. However, it also creates dual authority, competing priorities, slower decisions, and role ambiguity.

A matrix should not be adopted merely because it appears sophisticated. It requires:

• a documented distinction between solid-line and dotted-line authority;
• agreed decision rights;
• conflict-resolution procedures;
• common planning and CRM systems;
• shared incentives where collaboration is essential;
• senior leadership commitment to cross-functional discipline.

2.6 Comparative overview

3. Choosing and Combining Structures

Managers should evaluate structure using a fit analysis rather than copying competitors. Important diagnostic questions include:

• Do customers prefer one relationship owner or several specialists?
• How much product and industry expertise is required?
• Are customers geographically dispersed or concentrated?
• Does the sales process involve distinct stages with different skills?
• How costly is travel and face-to-face coverage?
• Can the CRM system support shared ownership and accurate attribution?
• Are managers capable of resolving cross-unit conflict?

Many organizations use hybrid designs. For example, a company may use geographic territories for mid-market accounts, a national key-account team for major customers, product specialists for complex solutions, and an inside-sales function for smaller accounts. Hybrid designs are often practical, but they increase the need for clear rules concerning account ownership, lead routing, compensation, and escalation.

A useful governance document is a responsibility matrix. It identifies who is responsible for performing a task, accountable for its outcome, consulted before action, and informed afterward. This is often known as a RACI framework:

• Responsible: performs the work;
• Accountable: owns the final outcome;
• Consulted: provides required input;
• Informed: receives relevant information.

Only one role should normally be accountable for a specific decision, even though several roles may be responsible or consulted.

4. Determining Salesforce Size

Salesforce sizing is an economic and operational decision. Too few salespeople create missed opportunities, slow response, poor service, and burnout. Too many increase payroll, travel, management, and coordination costs without producing sufficient incremental contribution.

4.1 Workload approach

The workload approach estimates the number of salespeople required from customer service requirements and available selling capacity. A general form is:

where:

• N = required number of salespeople;
• W = total annual customer-contact workload, measured in contact-hours or contact-visits;
• C = annual productive capacity of one salesperson in the same unit.

If customers are divided into classes, total workload is:

where:

• Aᵢ = number of customers in class i;
• fᵢ = required contacts per customer per planning period;
• tᵢ = time per contact, including reasonable preparation and follow-up;
• k = number of customer classes.

The equation assumes that contact requirements are sufficiently represented by averages and that customer classes are internally similar. It should be adjusted for travel, administrative work, training, leave, meetings, and opportunity-development time.

A salesperson’s productive capacity can be estimated as:

where:

• D = workable days in the planning period;
• h = available selling hours per workable day;
• p = proportion of available time devoted to the workload being measured.

The units must be consistent. If workload is measured in hours, capacity must also be measured in hours. If workload counts visits, capacity must count visits and include travel assumptions.

Worked example. A firm has 600 Class A customers requiring 12 visits per year at 1.5 hours per visit, and 1,400 Class B customers requiring 6 visits per year at 0.75 hours per visit.

Class A workload = 600 × 12 × 1.5 = 10,800 hours.

Class B workload = 1,400 × 6 × 0.75 = 6,300 hours.

Total workload = 17,100 hours.

Each salesperson has 210 workable days, 6.5 hours potentially available for customer-facing work per day, and 0.60 of that time is assigned to these visits. Therefore:

C = 210 × 6.5 × 0.60 = 819 hours.

Required salespeople = 17,100 ÷ 819 = 20.88, so the firm requires 21 salespeople, assuming fractional capacity cannot be deployed and the service standards are fixed. Managers should test whether travel and geographic clustering make 21 practically sufficient.

4.2 Incremental contribution approach

Workload estimates capacity, but economic analysis tests whether additional people are worthwhile. The incremental contribution of an additional salesperson can be represented as:

where:

• ΔΠ = change in operating contribution or profit;
• ΔCM = incremental contribution margin generated by the salesperson;
• ΔK = incremental employment, travel, technology, supervision, and support costs.

The approach is useful when sales productivity varies by territory maturity, account potential, or salesperson experience. It requires cautious forecasting because expected sales may be affected by competitor action, channel conflict, price changes, and demand uncertainty.

4.3 Capacity is more than headcount

Headcount alone can conceal capacity problems. Managers should examine:

• selling hours versus administrative hours;
• travel time and route density;
• vacancy and turnover rates;
• ramp-up time for new hires;
• product and industry competence;
• availability of technical or presales support;
• lead quality and conversion rates;
• service workload after the sale;
• digital tools and automation.

A smaller expert team may outperform a larger inexperienced team. Capacity planning must therefore integrate quantity, quality, timing, and location.

5. Salesforce Deployment and Territory Design

5.1 Territory design

A territory is a set of customers or prospects assigned to a salesperson or team. Effective territories balance opportunity and workload while minimizing unnecessary travel and conflict. Relevant inputs include:

• current and potential revenue;
• number and type of accounts;
• contact frequency;
• travel distance and accessibility;
• competitive intensity;
• service complexity;
• language and regulatory requirements;
• channel relationships;
• expected growth.

Equal sales potential is not always the objective. A new strategic market may justify an intentionally underdeveloped territory, while a mature territory may need greater coverage to protect existing revenue.

5.2 Deployment choices

Salespeople may be deployed through:

• field sales for complex, high-value, or relationship-intensive opportunities;
• inside sales for efficient remote engagement and qualification;
• specialist overlays for technical, legal, or industry expertise;
• partner or channel managers for indirect distribution;
• customer success or renewal teams for post-sale value realization;
• digital self-service for low-complexity transactions.

The best deployment often follows customer economics. High-potential accounts justify higher-cost coverage; low-potential accounts may be served through inside sales, automated communication, partners, or self-service.

5.3 Account ownership and conflict prevention

Every account should have a clear primary owner, even when a team serves it. Policies should specify:

• who owns the account record;
• who receives credit for revenue;
• how leads are assigned;
• how cross-sell opportunities are shared;
• what happens when an account operates across territories;
• how disputes are escalated;
• how inactive or unassigned accounts are reviewed.

Compensation plans can either reinforce or undermine these rules. If only individual bookings are rewarded, employees may hide information or resist collaboration. Shared credit, team measures, and strategic-account incentives may be appropriate when selling is interdependent.

6. Roles, Responsibilities, and Spans of Control

6.1 Core sales roles

A contemporary sales organization may include the following roles:

• Sales development representative: identifies and qualifies potential opportunities.
• Account executive or territory representative: develops opportunities and closes business.
• Key-account manager: coordinates the commercial relationship with strategically important customers.
• Product or solution specialist: provides technical expertise and supports complex opportunities.
• Channel manager: recruits, enables, and governs intermediaries.
• Customer success manager: supports adoption, retention, expansion, and realized value.
• Sales operations analyst: manages data, forecasting, territory planning, compensation administration, and performance reporting.
• First-line sales manager: coaches representatives, allocates resources, reviews pipeline, and manages performance.
• Sales director or regional leader: translates strategy into plans, budgets, talent systems, and cross-functional priorities.

Role descriptions should state outcomes, authority, boundaries, required capabilities, key interfaces, and performance measures. Titles alone do not establish accountability.

6.2 Span of control

Span of control is the number of direct reports assigned to a manager. A narrow span permits closer coaching but adds managerial layers and cost. A wide span reduces layers but may weaken coaching and oversight.

The appropriate span depends on:

• salesperson experience and independence;
• complexity of products and sales cycles;
• geographic dispersion;
• frequency of coaching required;
• quality of sales technology and reporting;
• volatility of the market;
• degree of standardization;
• administrative burden on the manager.

There is no universally correct numerical ratio. A manager supervising experienced, geographically concentrated representatives with standardized processes may handle more direct reports than a manager supervising new hires selling complex systems. Span should be evaluated through coaching quality, decision speed, employee development, and performance—not by a fixed benchmark alone.

6.3 Decision rights

Decision rights should be explicit for pricing, discounts, credit terms, contract exceptions, account reassignment, lead acceptance, service commitments, and forecast changes. A salesperson may recommend a discount, but finance may approve credit exposure and a sales manager may approve commercial terms within limits.

Clear authority reduces delay and protects the organization from unauthorized commitments. It also supports ethical conduct by preventing employees from making promises that operations cannot deliver.

7. Coordination Across Functions

Sales performance depends on a system of interdependent functions. Coordination should be designed into routines, data, incentives, and governance rather than left to informal communication.

7.1 Sales and marketing

Marketing commonly manages market insight, segmentation, positioning, campaigns, content, brand, and lead generation. Sales converts opportunities, supplies field intelligence, and provides feedback on customer objections and competitor activity.

Coordination mechanisms include:

• a shared definition of a qualified lead;
• service-level agreements for lead follow-up;
• common segmentation and account data;
• joint campaign planning;
• closed-loop reporting from opportunity to outcome;
• regular revenue or pipeline reviews;
• shared measures such as accepted leads, conversion, pipeline quality, and customer value.

Marketing should not be judged only by lead volume, and sales should not be judged only by short-term bookings if the strategy depends on long-term customer value.

7.2 Sales and customer service

Sales promises influence service workload, installation, complaint volume, and retention. Service teams should be involved when proposed solutions have delivery, training, maintenance, or support implications.

A formal handoff should record customer objectives, contractual commitments, implementation requirements, risks, contacts, and escalation procedures. Customer feedback should return to sales and product teams so that recurring problems are addressed systematically.

7.3 Sales and finance

Finance supports pricing discipline, profitability analysis, credit assessment, revenue recognition, collections, and incentive governance. Sales requires timely information about margins, customer credit status, payment behavior, and approved commercial terms.

Finance and sales should jointly define discount authority and approval thresholds. A sale that increases revenue but destroys contribution margin or creates unacceptable credit exposure is not necessarily a successful sale.

7.4 Sales and operations

Operations determines capacity, inventory, production schedules, delivery feasibility, and service levels. Sales forecasts must therefore be sufficiently accurate and timely for planning. Operations should communicate constraints clearly, while sales should avoid making commitments beyond approved capacity.

Integrated business planning, shared forecasts, exception reporting, and documented promise dates reduce the risk of over-selling and customer disappointment.

8. Technology, Data, and Artificial Intelligence

Customer relationship management systems support account ownership, contact history, opportunity stages, forecasting, workflow, and performance analysis. Technology improves coordination only when data definitions, adoption expectations, and governance are clear.

Artificial intelligence may assist with lead prioritization, next-best-action recommendations, call summaries, forecast risk detection, territory analysis, and administrative automation. However, AI outputs are not inherently objective or accurate. Managers should evaluate:

• data quality and representativeness;
• privacy and consent requirements;
• bias in lead scoring or opportunity allocation;
• explainability of recommendations;
• human review for consequential decisions;
• cybersecurity and access controls;
• whether automation reduces or merely relocates work.

AI should augment professional judgment, not remove accountability. Customers should not be misled about automated interactions, and sensitive information should be processed only under appropriate legal and organizational controls.

9. Illustrative Case: Meridian Industrial Solutions

Background

Meridian Industrial Solutions sells energy-monitoring equipment and maintenance contracts to factories, hospitals, and large commercial buildings. It has grown from one regional product line to three product families across four countries. Its salesforce consists of regional representatives, product specialists, and a small customer-service team.

Problem

Customers complain that several Meridian representatives contact them independently. Product specialists pursue opportunities without informing regional representatives, while service staff receive incomplete information about installation requirements. Forecast accuracy is poor, discounting varies widely, and large national customers receive inconsistent treatment. The managing director must decide whether to add more salespeople or redesign the organization first.

Analysis

The company’s problems are not primarily a headcount shortage. They arise from overlapping product and geographic responsibilities, unclear account ownership, weak handoffs, and inconsistent approval rights. A purely geographic structure would improve ownership but might not provide sufficient technical expertise. A purely product structure would intensify duplication.

Approach and solution

Meridian adopts a hybrid design:

1. Regional representatives become primary owners of standard accounts.
2. A national key-account team manages customers operating across multiple regions.
3. Product specialists become overlay resources with defined engagement rules and shared opportunity credit.
4. Customer service participates in a documented pre-commitment review for complex installations.
5. Marketing and sales agree on lead definitions, acceptance times, and campaign reporting.
6. Finance establishes discount and credit approval thresholds.
7. The CRM system records one account owner, specialist involvement, next actions, and handoff status.
8. Territory workload is recalculated using customer classes, contact frequency, travel, and service complexity before hiring decisions are made.

Outcome

After two planning cycles, Meridian reports fewer duplicate calls, faster technical response, improved forecast visibility, and more consistent pricing. The company adds specialists in two high-growth industries but does not increase general territory headcount until workload evidence demonstrates the need. The result illustrates that organization design can release capacity before additional recruitment is required.

Learning points

• Headcount cannot compensate for unclear ownership.
• Hybrid structures require explicit governance.
• Technical specialists should support, not compete with, account owners.
• Cross-functional handoffs are part of the customer experience.
• Capacity analysis should precede recruitment.

10. Challenges, Ethics, and Best Practices

10.1 Common challenges

Sales organization redesign can generate anxiety, political resistance, territory disputes, temporary productivity loss, and employee turnover. Historical account ownership may conflict with the new strategy. Managers may manipulate data to protect territories or quotas. Reorganization may also create customer confusion if communication is poorly planned.

A responsible transition includes stakeholder consultation, pilot testing, transparent criteria, training, customer communication, and review of unintended effects. Performance should not be judged during a short transition period without recognizing ramp-up and reassignment effects.

10.2 Ethical and governance issues

Important ethical risks include discriminatory customer allocation, manipulation of quotas, concealment of customer information, misrepresentation of product capability, excessive surveillance of employees, and incentive systems that encourage unsuitable sales.

Governance should ensure:

• fair and documented territory allocation;
• truthful customer communication;
• protection of personal and confidential data;
• approval of commitments that affect delivery or safety;
• separation of duties where financial risk is material;
• accessible complaint and escalation channels;
• audits of compensation and account-credit practices.

10.3 Best-practice design cycle

A practical design cycle is:

1. Diagnose strategy, customers, offerings, channels, and current performance.
2. Map required customer activities and service standards.
3. Compare alternative structures and estimate coordination costs.
4. Define roles, decision rights, territories, and interfaces.
5. Estimate workload, capacity, and economic contribution.
6. Pilot the design in a representative market or segment.
7. Train employees and configure systems.
8. Measure customer, financial, employee, and operational outcomes.
9. Correct unintended consequences and review the design periodically.

A sales organization should be treated as a living operating system. Market changes, acquisitions, digital channels, product innovation, and customer concentration can make an once-effective structure unsuitable.

Chapter Summary

Sales organization design aligns selling work with strategy, customer requirements, product complexity, and economic capacity. Geographic structures offer efficient local coverage; product structures provide technical expertise; customer structures support segment intimacy; functional structures improve activity specialization; and matrix structures combine dimensions at the cost of greater coordination complexity. Hybrid designs are often appropriate but require explicit account ownership and decision rights.

Salesforce sizing should consider workload, productive capacity, incremental contribution, travel, capability, ramp-up, and service requirements. The workload approach estimates required headcount by dividing total contact workload by one salesperson’s productive capacity, provided that units and assumptions are consistent. Deployment decisions should match coverage cost with customer potential and buying complexity.

Roles must specify outcomes, authority, interfaces, and measures. Span of control depends on complexity, experience, dispersion, and coaching needs rather than a universal ratio. Coordination with marketing, service, finance, and operations should be supported by shared data, service agreements, handoff processes, integrated planning, and aligned incentives. Technology and AI can improve capacity and insight, but they require data governance, privacy protection, human oversight, and ethical accountability.

Key Terms

Sales organization design: The arrangement of sales roles, responsibilities, reporting relationships, and processes.

Workforce capacity: The amount of productive selling work a salesforce can perform.

Geographic structure: Organization based primarily on territory or location.

Product structure: Organization based on product line, brand, or solution.

Customer structure: Organization based on customer segment, industry, or account type.

Functional structure: Organization based on selling activities or process stages.

Matrix structure: Organization combining two or more bases of specialization.

Hybrid structure: A design combining different organizational bases for different markets or activities.

Territory: A defined group of customers or prospects assigned to a salesperson or team.

Workload approach: A method of estimating salesforce size from required customer work and available capacity.

Productive capacity: The time or activity volume a salesperson can devote to specified work.

Span of control: The number of direct reports supervised by a manager.

Account ownership: Formal responsibility for coordinating a customer relationship.

Key-account management: Coordinated management of strategically important customers.

Overlay specialist: A specialist who supports primary account owners without replacing ownership.

RACI: A responsibility framework identifying responsible, accountable, consulted, and informed roles.

Service-level agreement: A documented commitment defining responsibilities, timing, and performance expectations.

Incremental contribution: Additional contribution generated after additional costs are considered.

CRM: A system for managing customer information, interactions, opportunities, and activities.

Decision rights: Explicit authority to make specified decisions or approve actions.

Review Questions

Short Answer Questions

1. What is the main purpose of sales organization design?
2. State one advantage and one limitation of a geographic sales structure.
3. What does span of control mean?
4. Why should account ownership be explicitly defined?
5. Name two mechanisms for coordinating sales and marketing.

Long Answer Questions

1. Compare geographic, product, customer, functional, and matrix structures. Explain the circumstances in which each may be appropriate.
2. Explain the workload approach to salesforce sizing, including its assumptions and limitations.
3. Discuss how sales should coordinate with customer service, finance, and operations.
4. Explain why hybrid structures can be effective and why they also create governance challenges.
5. Evaluate the role of CRM and artificial intelligence in sales capacity management.

Analytical / Application Questions

1. A company has a broad product portfolio, geographically dispersed customers, and several national accounts. Recommend an organizational structure and justify your choice.
2. Using the workload approach, calculate required salespeople for 400 customers requiring 10 annual visits of 1.25 hours and 900 customers requiring 5 annual visits of 0.8 hours. Assume each salesperson provides 750 productive hours annually. State any rounding decision.
3. A sales team is exceeding revenue targets but generating delivery failures and customer complaints. Diagnose the organizational and coordination causes and propose a corrective design.

Multiple Choice Questions with Answers

Question 1

Which sales organization structure primarily assigns responsibility according to location?

A. Geographic

B. Product

C. Functional

D. Matrix

Correct Answer: A. Geographic

Question 2

A major advantage of a product structure is that it provides salespeople with stronger:

A. Territory equality

B. Technical expertise

C. Credit authority

D. Administrative independence

Correct Answer: B. Technical expertise

Question 3

In the workload approach, required salespeople are estimated by dividing total workload by:

A. Annual revenue

B. Average account value

C. One salesperson’s productive capacity

D. Total marketing expenditure

Correct Answer: C. One salesperson’s productive capacity

Question 4

A responsibility matrix identifies the person who owns the final outcome as:

A. Responsible

B. Accountable

C. Consulted

D. Informed

Correct Answer: B. Accountable

Question 5

Which structure is most directly associated with dual authority?

A. Geographic

B. Customer

C. Functional

D. Matrix

Correct Answer: D. Matrix

Question 6

A salesperson has 200 workable days, 6 hours per day available for a task, and devotes 50% of that time to the task. What is the annual capacity for that task?

A. 300 hours

B. 400 hours

C. 600 hours

D. 1,200 hours

Correct Answer: C. 600 hours

Question 7

Which practice best reduces conflict between product specialists and account owners?

A. Allowing both to contact customers without coordination

B. Removing all product specialists

C. Defining engagement rules and opportunity-credit policies

D. Assigning every product specialist a separate finance role

Correct Answer: C. Defining engagement rules and opportunity-credit policies

Question 8

Which function is most directly concerned with credit assessment and revenue recognition?

A. Finance

B. Marketing

C. Customer service

D. Sales training

Correct Answer: A. Finance

Question 9

A wide span of control generally means that a manager has:

A. Fewer direct reports and more layers

B. More direct reports and fewer layers

C. No responsibility for coaching

D. Authority only over marketing

Correct Answer: B. More direct reports and fewer layers

Question 10

Which statement best describes responsible use of AI in sales management?

A. AI outputs should automatically determine all territory decisions

B. AI eliminates the need for data governance

C. AI should augment judgment with human oversight and privacy controls

D. AI recommendations are always unbiased

Correct Answer: C. AI should augment judgment with human oversight and privacy controls