Sales Management: Why Sales Leaders Are Constantly Firefighting

Sales management does not start with a dashboard. It starts with a much more basic question:

Is it actually clear how sales is supposed to work in this company?

In practical terms, sales management is the system for directing how sales work gets done: who owns decisions, how opportunities move through the organisation, what information must survive each handoff, and how pipeline, forecasting and performance are measured. Dashboards and KPIs support that system; they do not create it.

Who does what? Who decides what? How is an opportunity handed over? When does the Head of Sales need to get involved? What information has to be in the CRM? What happens after discovery? Who owns what when Sales, Presales, Delivery or Customer Success are involved?

In organisational theory, these are basic questions of organisational structure and workflow design.

In practice, the answer is surprisingly often: “It depends.”

That is where the problem starts.

Organisational structure: Who is responsible for what?

Organisational structure defines roles, responsibilities and decision rights.

In sales, this sounds straightforward. Marketing generates demand. Sales qualifies and develops opportunities. Presales supports technically or commercially complex deals. Management approves exceptions. Delivery takes over won customers.

At least on paper.

In reality, grey areas appear quickly. Who decides whether a lead should be worked at all? Who owns an opportunity when several account managers are involved? When must Presales be involved? Who can change pricing? Who approves individual commitments to a customer? Who owns the forecast? And who makes sure that what was sold can actually be delivered?

If these questions are not answered clearly, they are still answered – just repeatedly and case by case.

Usually by the sales leader.

A leadership role gradually becomes an operational clearing house.

Workflow design: How should a deal move through the organisation?

The second layer is workflow design.

A functioning sales organisation does not need a process because process diagrams look professional. It needs a process so recurring situations do not have to be reinvented every time.

A lead comes in. What happens next?

1. Qualification
2. Discovery
3. Opportunity
4. Solution Design
5. Proposal
6. Negotiation
7. Close
8. Handover.

That is the simple version. The interesting part is what happens between those steps.

What criteria must be met before a lead becomes an opportunity? What information must exist after discovery? When can a proposal be created? When does a deal require technical support? When is management approval required? What information does Delivery need at handover? What happens to lost opportunities?

Many problems that later appear to be “sales problems” originate at exactly these transition points.

Handoffs are the breaking points of the sales system

Handoffs are particularly critical.

Marketing hands over to Sales. An SDR hands over to an Account Executive. Sales hands over to Presales. Presales sends information back to Sales. Sales requests management approval. After signature, Delivery or Customer Success takes over.

Context can be lost at every transition. Often, it is not even defined what information needs to be handed over.

Part of the information then sits in the CRM, another part in email, another in Teams or Slack, and the most important context remains in someone’s head.

As long as everyone keeps talking to each other, this can work somehow. Once volume increases, somebody is absent, the company grows, or several people work on a deal in parallel, it becomes a structural problem.

Processes often exist – people just do not follow them

Many companies have already recognised these problems. So they have defined processes.

There are sales stages. Mandatory fields. Checklists. Approval rules. CRM workflows. Perhaps even a sales playbook.

The problem is that actual sales work operates differently.

People skip steps. CRM data is entered later. Opportunities are created too early or kept open too long. Mandatory fields contain placeholder values because otherwise the system will not let the user continue. Approvals happen through informal messages. Important information stays in personal notes. Exceptions become normal operations.

On paper, there is one process. Operationally, there are several individual versions of it.

Somewhere in the middle sits the sales leader trying to reconcile them.

The sales leader becomes the human operating system

This creates a pattern that can be observed in many growing sales organisations.

The Head of Sales is no longer primarily leading sales. They are continuously operationalising it.

They answer questions. They decide exceptions. They chase missing information. They correct CRM data. They review proposals. They mediate between departments. They remind people about processes. They jump into deals at risk. They explain to management why the forecast is wrong again.

They know which opportunity is genuinely healthy and which one only looks healthy in the CRM.

This creates a paradox: the more experienced and capable the sales leader is, the longer a weak system can continue to function.

They compensate for its weaknesses personally. The organisation initially interprets this as strength. In reality, it creates dependency.

And there is almost no time left for process improvement

This creates another effect that stabilises the problem.

Sales operates under constant performance pressure. The month has to close. The quarterly target is fixed. Proposals need to go out. Customers are waiting. Opportunities need to progress. Management expects the forecast. A strategic deal is stuck. At the same time, information is missing, internal coordination takes too long and the next escalation has already started.

This pressure does not affect only the sales leader. The whole team operates under constant operational pressure.

Account managers are expected to sell. SDRs are expected to create meetings. Presales supports several opportunities at the same time. Leaders have to deliver forecasts and explain target gaps.

Process work therefore competes every day with work that appears to be directly tied to revenue.

In the short term, the customer, proposal or deal almost always wins.

The process workshop is postponed. The CRM will be cleaned up later. Sales-stage definitions can wait until next month. The next handover to Delivery will be better. The playbook will eventually be updated.

But “eventually” rarely arrives.

Operational pressure creates a vicious cycle

The result is a self-reinforcing system:

1. Unclear processes
2. more questions and exceptions
3. more operational work
4. less time for process improvement
5. unclear processes remain.

The longer this continues, the harder it becomes to break the cycle. Eventually the organisation is fully occupied with managing day-to-day operations.

The team develops workarounds. Experienced employees know whom to call for each problem. The sales leader knows the shortcuts. Spreadsheets supplement the CRM. Information moves through chat messages. Individual employees informally hold critical parts of the system together.

This can work for a surprisingly long time. But it does not scale well.

More importantly, it creates constant pressure on exactly the people who would need time to improve the system.

Firefighting is usually a symptom

There are, of course, genuine exceptions in sales. A strategic customer behaves unexpectedly. A competitor changes pricing. A key stakeholder leaves the customer. A complex opportunity requires an unusual solution.

Experienced leadership is necessary for those situations.

The problem begins when predictable situations are repeatedly treated as exceptions.

If the same questions appear every week, they are no longer exceptions. If proposals regularly need correction, it is no longer an individual mistake. If forecast calls are mainly used to discover the real situation behind the CRM data, the organisation does not simply need a better dashboard. If handovers regularly escalate, the people involved are not necessarily the core problem.

The system lacks structure.

Sales management starts before the metrics

Metrics matter. Pipeline coverage, conversion rates, sales cycle, win rate, deal velocity and forecast accuracy can provide valuable management information.

But a metric can only measure what the underlying system produces reliably.

If sales stages mean different things to different people, stage conversion rates become unreliable. If close dates are systematically pushed forward, the forecast deteriorates. If opportunities are qualified differently, pipeline coverage loses meaning. If activity and context are not documented consistently, a better reporting layer does not solve the problem.

The sequence is therefore not:

1. CRM
2. Dashboard
3. KPI
4. Sales Management

It is:

1. Organisation
2. Responsibilities
3. Processes
4. Handoffs
5. Data
6. Metrics
7. Management

Good sales management reduces recurring decisions

A well-managed sales organisation is not one with the maximum number of rules.

The objective is to stop recurring decisions from requiring management intervention every single time.

A salesperson should not have to ask every time when Presales needs to be involved. Presales should not have to discover from scratch which information is missing. Delivery should not need to reconstruct what was promised after the contract is signed. And the Head of Sales should not need personal knowledge of every opportunity for the forecast to work.

The system needs to handle a significant part of this coordination.

Not necessarily through automation. First through clarity.

Four questions quickly show whether sales management works

1. Who is responsible?

Are roles, ownership and decision rights clear?

2. How does the work actually happen?

Not according to the process handbook, but in day-to-day operations.

3. Where are the handoffs?

At which points do responsibility, information or decisions move between people and teams?

4. Where does management repeatedly need to intervene?

The final question is particularly useful. Wherever leaders repeatedly solve the same problems personally, there is often a structural weakness underneath.

The real test: What happens when the Head of Sales is away for two weeks?

A useful test of sales management is not the CRM dashboard. It is absence.

What happens if the Head of Sales is unavailable for two weeks?

Are opportunities still qualified consistently? Do approvals work? Are decisions made? Do handoffs continue? Does the CRM remain reliable? Can management still produce a meaningful forecast? Or do decisions, questions and escalations begin to accumulate?

If sales performance deteriorates significantly without the continuous intervention of a few key people, the organisation does not have a fully resilient sales system.

Part of the organisation still exists in those people’s heads.

Sales management means building a manageable system

The objective is therefore not to help the sales leader become more efficient at firefighting. It is to remove the causes of recurring fires.

That requires organisational structure, workflow design, responsibilities, handoffs and actual working practices to be considered together.

Only then do CRM, automation, reporting and metrics become truly effective.

The result is not a sales organisation without exceptions. The result is a sales organisation where the team is not constantly fighting avoidable operational friction – and leaders can spend their time on genuine exceptions, decisions, coaching and leadership instead of continuously holding the operating system together.

That is the core of effective sales management.

Revenue Architecture: Treat sales as a connected system

This is where Revenue Architecture becomes relevant.

Many sales problems cannot be solved effectively when processes, organisational structure, CRM, data and automation are treated as separate topics. In practice, they are connected.

Unclear responsibility creates a weak handoff. A weak handoff creates missing information. Missing information creates incomplete CRM data. Incomplete CRM data creates unreliable metrics. Unreliable metrics create a weak forecast. Eventually, a sales leader compensates for the entire chain through experience, follow-up and manual intervention.

Revenue Architecture therefore looks beyond individual symptoms to the commercial system behind them:

1. Organisation
2. Responsibilities
3. Processes
4. Handoffs
5. Systems
6. Data
7. Management.

The key question is not only: “Where do we have a problem?”

It is: “What structure keeps producing this problem?”

That is the difference between optimising an isolated process step and working on Revenue Architecture.

Where Wingmen Experts fits

Wingmen Experts works at these interfaces between business, sales, processes and technology.

The objective is not to place another framework on top of the organisation. It is to identify where the existing revenue system creates unnecessary friction, where critical knowledge depends on individuals, where responsibilities and handoffs break down, and where technology merely digitises a weak process.

Sometimes the CRM needs to change. Sometimes the CRM is not the real problem at all.

Perhaps there is no clear opportunity definition. Perhaps teams disagree about what “qualified” means. Perhaps there is no reliable handoff between Sales and Delivery. Perhaps a critical decision depends on the Head of Sales every single time. Or several of these issues reinforce each other.

Meaningful change therefore starts with clarity about the existing system.

The Architecture Clarity Call

If several of these situations sound familiar, the first step does not have to be a large transformation programme.

In an Architecture Clarity Call, we examine where the largest structural friction points in your revenue system are located.

We look at processes, responsibilities, handoffs, systems and dependencies – and identify where the organisation currently relies on manual intervention to keep things working.

The initial objective is clarity:

What is actually the problem, what is merely a symptom, and where is intervention likely to create the most leverage?