Why Revenue Feels Harder Than It Should
Most businesses don’t have a sales problem. They have a systems problem.
That distinction matters because most revenue problems are diagnosed only after they become visible. Sales misses its number, so leadership asks for more activity. Marketing produces leads that do not convert, so the answer becomes more campaigns. Forecasts miss, so the CRM gets more fields, more reports, more rules, and more oversight. Each response makes sense when you look only at the symptom in front of you. The problem is that the symptom is often the last place the failure appeared, not the first place it began.
Think about a cough. You can take Robitussin and suppress it, and for a while you may feel better. But the medicine does not necessarily tell you why you were coughing in the first place. Businesses do this constantly. They treat the symptom because the symptom is visible, urgent, and easy to name. More leads. More calls. Better follow-up. A new CRM. A better salesperson. A different sales methodology. Sometimes those things help. Sometimes they simply make the underlying problem harder to see.
Zero-Point Selling starts before the prescription. It starts by asking whether we have correctly diagnosed the problem at all.
That may sound obvious, but it is one of the hardest disciplines in business. We are naturally drawn toward solutions because solutions feel productive. They give us something to buy, build, assign, measure, or implement. Problems require us to stay uncomfortable for a little longer. They force us to question whether the thing we think is broken is actually the thing that needs to be fixed.
I have seen this pattern in businesses over and over again. A company says it needs more leads because Sales is not closing enough business. So Marketing spends more money and generates more names. Three months later the pipeline is larger, the sales team is busier, and revenue has barely moved. When we look closer, the real problem is not lead volume. The company has no shared definition of qualification, no reliable handoff, and no standard for deciding which opportunities deserve Sales time. Adding more leads did not fix the system. It poured more water into a bucket with a hole in the bottom.
That is the kind of problem this book is about.
A business is remarkably easy to understand once revenue already exists. A customer bought something. There is an invoice, a cost, a margin, a delivery obligation, and eventually a financial result. Accounting can tell you what happened. Operations can measure what was produced. Finance can examine the P&L. Leadership can look backward and determine whether the organization made or lost money with a level of precision that simply does not exist before the sale.
Before revenue exists, almost everything is less certain. Marketing is attempting to reach people who may or may not care. Sales is attempting to understand people who may or may not buy. Buyers are deciding whether a problem matters enough to act on, whether the seller understands it, whether the timing is right, whether the risk is acceptable, and whether the value is worth the exchange. A significant amount of organizational effort takes place before anybody can point to revenue and say, “There it is.”
I sometimes describe revenue as a luxury post-revenue operators enjoy that Marketing and Sales people toil over. That does not mean Finance, Operations, Customer Success, or anyone else has easy work. It means they are working with something concrete that the pre-revenue organization had to create under uncertainty. Once the sale exists, there are numbers and obligations to manage. Before the sale exists, there are assumptions, conversations, signals, decisions, and probabilities.
Yet many organizations bring far more operating discipline to the work that happens after the sale than they bring to the work required to create it.
That is strange when you think about it. Revenue is the thing the rest of the organization ultimately depends on, but the process that creates revenue is often allowed to live inside individual judgment. One salesperson follows up one way. Another salesperson follows up another. Marketing has one definition of a lead. Sales has another. Leadership looks at the dashboard and assumes the language underneath those numbers means the same thing to everyone. The CRM sits in the middle recording all of it and is somehow expected to turn ambiguity into certainty.
It cannot.
A CRM is a little like a GPS. If you give it the correct destination and the roads are mapped properly, it can be incredibly useful. But if nobody agrees on where you are going, or the map is wrong, a more expensive GPS will not solve the problem. It may simply get you to the wrong place faster. Software can preserve rules. It can automate rules. It can measure whether rules were followed. It cannot create alignment that the organization has never established.
I worked with a company that was convinced the CRM was the problem. The sales team hated using it. Management did not trust the pipeline. Reports contradicted what people said in meetings, and everyone had a slightly different workaround. The first instinct was to reconfigure the software. But when we backed up and asked what “qualified” actually meant, there was no consistent answer. One salesperson thought a good first conversation was enough. Another wanted budget and timing. A manager cared mostly about whether a proposal had been sent. The software was not broken. It was faithfully storing three different versions of reality.
That is not a technology problem. It is a design problem.
Growth can hide that design problem for a surprisingly long time. A founder can compensate for missing process because the entire business still fits inside one person’s head. A great salesperson can create revenue despite poor infrastructure. Referrals can hide weak targeting. Discounting can hide weak differentiation. A few large customers can make an unreliable pipeline look productive. Strong demand can forgive inefficiency because enough opportunity is flowing through the system that some of it becomes revenue anyway.
This is one reason growth is so seductive. We interpret the outcome as proof that the system producing it must be healthy.
But growth does not necessarily validate a system. It puts more pressure on it.
A small business can feel like a pickup truck with too much weight in the bed. For a while, it still moves. You can add another box, then another, then another, and nothing dramatic happens. Eventually the suspension starts to sag, the steering gets sloppy, and every bump in the road feels worse than it used to. The problem did not appear the moment the truck started struggling. The problem was there earlier. The extra weight simply made it visible.
What once required one person now requires coordination between several. What used to be remembered now has to be documented. What used to be resolved in a conversation now has to survive a handoff. The company adds people, tools, meetings, workflows, and reports, and each addition creates another place where meaning can be lost. The organization becomes busier at exactly the same time leadership begins feeling less certain about what is actually happening.
The natural response is to push harder.
That response makes sense because effort is one of the few things leaders can see and influence immediately. Ask for more calls. Produce more content. Hire another salesperson. Add another dashboard. Require more fields in the CRM. Schedule another pipeline meeting. Increase the marketing budget. These actions create movement, and movement feels like control.
But motion and progress are not the same thing.
You can run faster on the wrong road.
You can automate a bad rule. You can measure an activity that has little relationship to buyer movement. You can hire talented people into an environment that makes success unnecessarily difficult. You can build a beautiful dashboard that reports numbers no one actually trusts. The system can become more sophisticated while the underlying logic stays just as weak.
One client blamed its sales team for poor follow-up. From leadership’s perspective, the conclusion was obvious: the reps needed to be more disciplined. When we looked at the process, the picture changed. Contact records often lacked useful phone numbers or direct emails. Ownership was unclear. Nobody had defined what qualified for follow-up, what the timing should be, or what information needed to be captured first. Leadership believed it had a people problem. In reality, it had created a relay race without clearly marking where the baton was supposed to be handed off.
Could the salespeople have worked harder? Certainly. But working harder would not have fixed the handoff.
That is why I am cautious when organizations immediately blame people. Sometimes people are the problem. Sometimes they lack skill, urgency, judgment, or willingness. But before we conclude that, we should make sure the system has given them a reasonable chance to succeed. If the process is unclear, the information is missing, the ownership is ambiguous, and the tools add friction, demanding more effort may simply make everyone more frustrated.
This is a central idea in Zero-Point Selling: rule out the system before blaming the person.
Another is just as important. Marketing and Sales have to become more interested in the buyer’s problem than they are in their own solution. Uri Levine, co-founder of Waze, popularized the idea of falling in love with the problem rather than the solution. That principle belongs naturally inside revenue creation because sellers become attached to what they sell, marketers become attached to what they want to say, and businesses become attached to the tactics they already know how to execute.
The buyer has no obligation to care about any of that.
The buyer cares about their world.
Their problem. Their goal. Their constraint. Their risk. Their opportunity. Their version of what is not working.
That does not mean the buyer always understands the root cause correctly. In fact, a great deal of selling begins because they do not. Someone says they need more leads when the real issue is weak qualification. They say they need a CRM when the real issue is that nobody follows the same process. They say the sales team needs more training when the team may be operating without clear definitions, useful information, or a trustworthy pipeline.
The job is not to immediately correct them. If someone walks into a doctor’s office saying, “My knee hurts,” the doctor does not begin by arguing that the knee is not the real problem. They ask questions. They examine what is happening. They look for what caused the symptom. The patient has to arrive at a credible diagnosis before they will trust the treatment.
Marketing and Sales work the same way.
The buyer’s language is the entry point. The deeper diagnosis is the destination.
That is also how this book will work. I am not going to hand you twenty-seven chapters of answers in the Introduction. We are going to work through the problem in sequence because sequence matters. If I explain everything now, I would be doing the same thing I am telling you not to do in Sales: prescribing before we have earned the diagnosis.
We will begin with growth because growth is where many businesses become convinced their system works. Then we will look at effort, technology, and language, because those are the places organizations usually reach when growth becomes harder to manage. From there we will work backward from revenue, examine how people move toward becoming customers, and distinguish activity from evidence. Only then will we move into Marketing, Sales, pipeline, loss, CRM, automation, AI, measurement, and continuous improvement.
Along the way, I am going to challenge some assumptions.
A Lead may not be what your CRM has taught you to think it is. A Discovery Call is not necessarily evidence that discovery happened. More pipeline is not automatically better pipeline. A Closed Lost deal is not automatically a bad outcome, and a Closed Won deal is not automatically a good one. More data is not always more useful. More automation is not always more efficient. A salesperson saying they feel good about a deal is not the same thing as evidence that the buyer has moved.
We will get to those ideas when they become useful.
For now, the important thing is to understand what Zero-Point Selling is trying to accomplish.
It is not a closing technique. It is not a script. It is not a CRM implementation methodology, although CRM matters deeply to the system. It is not designed to replace Sandler, MEDDPICC, EOS, Continuous Improvement, or every other framework a business may already use. Those systems solve important problems at different layers of an organization.
Zero-Point Selling is an operating architecture for the work of creating revenue before that revenue exists.
It asks what needs to be true, what needs to be known, what work needs to happen, who should own it, what evidence demonstrates progress, what technology should support it, and how the organization learns when the outcome does not happen. The operating sequence is intentionally simple: Strategy, then Process, then People, then Technology. We will unpack that later. For now, it is enough to understand that ZPS does not begin with software or tactics. It begins with clarity.
Clarity about the problem. Clarity about the buyer. Clarity about what happened. Clarity about what happens next.
The purpose is not to eliminate human judgment. Selling is human. Marketing is human. Relationships are human. Buyers do not move through a perfectly linear sequence because we put stages in a CRM. They hesitate, change their minds, involve other people, delay decisions, misunderstand problems, discover new constraints, and occasionally surprise us.
The purpose of a system is not to remove that humanity. It is to create something closer to guardrails on a mountain road. The guardrails do not drive the car. They do not decide where you are going. They simply make it easier to move with confidence without every mistake becoming catastrophic. Good revenue systems should work the same way. They should support judgment, make the work easier to see, and reduce the number of times people have to reinvent basic decisions.
That is ultimately what this book is about.
It is not about selling harder. It is not about collecting everything. It is not about automating everything. It is not about turning people into machines.
It is about understanding the system that exists before revenue, making enough of that system visible to manage it intelligently, and then improving it based on what actually happens rather than what we hope is happening.
The first obstacle is that success itself can make a broken system difficult to see. A company can grow while carrying weaknesses that will not become obvious until more weight is placed on them. Revenue can increase while coordination deteriorates. Activity can expand while predictability declines. The organization can look healthier from the outside while the people inside it feel increasingly dependent on heroics just to keep everything moving.
That is where we begin.
Because before we can build a better revenue system, we have to stop assuming that growth is proof the one we already have is working.