> ## Content Index
> Fetch the complete content index at: https://notes.jasonjhonson.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# If I can sell it, why can’t you?
- URL: https://notes.jasonjhonson.com/if-i-can-sell-it-why-cant-you/
- Published: 2026-10-29T16:49:16.000Z
- Updated: 2026-10-29T16:49:16.000Z
- Description: Why can the founder sell the product when the sales team can’t? The answer may be less about sales execution and more about whether customers care about the problem, believe in the solution, and trust the product to deliver.
- Author: Jason Jhonson
- Tags: GTM, sales, Product Marketing

### Moving from founder selling to scaling a GTM team

There is nearly always a moment in a growing technology company when the founder looks around the room and says “Why am I the only person who can sell this?”

The company has customers. People have paid real money. Prospects have told the founder the product is amazing. Investors have called it a game changer and breakout growth is right around the corner. The founder can sit down with a customer and somehow get a deal across the line. Then the company hires salespeople, gives them roughly the same sales deck, teaches them to describe the same product, points them at the same kinds of companies, and the deals do not happen with anything like the same frequency.

So the company starts fixing things. The salespeople need better training. The pitch needs work. Marketing needs to explain the product more clearly. The website needs a new headline. The deck needs another slide. And there is likely truth in all of those explanations - this is a new GTM function so there is no reason to believe we’re going to be great at this out of the gate. But there is likely another reason that companies are much less comfortable considering: the founder may not actually have proven that the product can be sold in the way the company thinks it can.

### What the founder is really selling

I sometimes ask the company to imagine the founder has a clone. The clone knows everything the founder knows about the company and the product, has exactly the same personality, uses the same presentation and says exactly the same things. Now make one of them the CEO and the other an account executive. Would customers react to them in exactly the same way?

Probably not, because when a founder of a new and exciting tech company is selling, the customer is likely buying a lot more than the software that exists today. They may be buying access to the person who controls the roadmap, confidence that problems will get fixed, a relationship with an innovative company, some ability to shape what gets built next, or simply the energy and conviction of the person who created the thing. The founder can also change the sale in real time, adjusting the vision, reframing the problem, promising something that is not quite (and maybe not nearly) in the product yet, or connecting what the customer says to something the company might become.

Then the founder hands a salesperson the current product and a PowerPoint presentation and wonders why conversion falls.

From inside the company, the founder and the salesperson may appear to be selling the same thing. From the customer's perspective, they aren’t. That’s not to say that founder sales are illegitimate or that they don’t count. Early companies need founders to sell, and those conversations are often how the company learns what it should become. But a founder closing five deals proves something different from a sales team repeatedly selling a stable product to a defined customer. The second is a much higher bar, and it is what makes scalable growth possible.

### Before the product, there is the problem

One reason companies misdiagnose this transition is that they start too quickly with the product. Technology companies are usually quite good at proving that their products do what they say they do. We can process this much data. We can model this more accurately. We can automate this workflow. We can reduce the time required for this task.

All of that might be true, and the customer can believe every technical claim you make and still not buy. There is an earlier question: do they care about this problem enough to prioritize solving it?

That is not the same as asking whether they agree the problem exists. Almost every executive would like to grow faster, reduce costs, build better software, serve customers more effectively and make better decisions. Those are easy problems to get agreement around because they are so broad that almost everyone wants them solved. They are also so broad that almost no individual product can credibly solve them.

Tell a CEO that you can make the company more profitable and you are describing something they desperately want. You have not yet described a problem they believe your product can solve. It is a little like asking me whether I would buy a time machine. Of course I would. I just do not believe you have one.

Useful problems tend to be nested inside larger ones. A company wants to reduce operating costs. Customer service is too expensive. Too many customer interactions require a human agent. A meaningful subset of those interactions could be handled another way. Now we are getting somewhere. The problem is still connected to something the organization genuinely cares about, but it is specific enough that someone owns it, people are spending money against it, and a product might credibly make a difference.

The first job of selling is to create energy around a problem worth solving. Then the product has to deserve the energy you created.

### You can see when the energy is there

If I go to a concert and the crowd is dead, the performer does not get to stand on stage and blame the audience (well they often do, but that doesn’t make the situation better). Maybe it is the wrong crowd. Maybe the band was booked into the wrong room. But deciding that everyone would love the music if only they understood it better is not particularly useful while you’re standing on the stage. The performer has to create some energy, and when that happens the crowd starts returning it. The band gets more energetic because the crowd is energetic, the crowd responds to the band, and around it goes.

![](https://storage.ghost.io/c/ec/41/ec4178b6-0a2a-4b63-a5d1-a95a2fdc0a72/content/images/2026/10/Singer.png)

Selling works in much the same way. You know you are creating energy around a problem when the customer starts contributing some of their own. They tell you how the problem shows up inside their company, what they have already tried, and which workarounds they hate. They ask what you have seen other companies do. They bring another executive into the conversation. They want your opinion. At that point you are not simply presenting a problem. You are becoming someone they believe understands it and can help.

Most established sales methodologies recognize some version of this. Good selling begins to resemble consulting. You have talked to enough companies with this problem to have a useful point of view about it. The customer brings their lived experience, and you bring pattern recognition from seeing the problem elsewhere. That conversation is much stronger evidence than someone telling you your demo is interesting.

Even that engagement is not enough, though. People have lots of problems they genuinely intend to solve someday. The trouble is that the fourteen problems above yours on the list will take precedence forever. The stronger question is what the customer is already sacrificing to solve it. Are they spending money? Assigning people? Maintaining an ugly internal workaround? Is an executive measured on it? Does it appear in a budget, operating plan or board discussion? Are people spending hours every week compensating for it? Organizations reveal the hierarchy of their problems through the resources they assign to them.

It is possible to walk into a sales meeting, persuade someone they have a problem they didn’t previously care about, create urgency around it and change the company's priorities enough to make a sale. It is also one of the hardest possible foundations for a repeatable sales motion. If the market does not yet believe the problem matters, establishing its importance may be the work of branding, category creation, thought leadership, customer evidence and repeated exposure over time. Asking an individual salesperson to manufacture a new organizational priority and then sell the solution to it in the same conversation requires too many cognitive leaps and the people you’re selling to don’t have the time and energy for it.

Ideally, you know there is energy around the problem before you need the product to prove anything. You can learn a surprising amount about that before the product is even finished.

### Problem fit, solution fit and product fit

I have started to think about this as three different kinds of fit.

![](https://storage.ghost.io/c/ec/41/ec4178b6-0a2a-4b63-a5d1-a95a2fdc0a72/content/images/2026/10/Three-Step-Product-Market-Fit-Journey.png)

The first is **problem fit**. Does this customer care enough about this specific problem to spend scarce attention on it? Not “Do you have this problem?” and not “Would solving this be good?” Do they lean into the conversation? Are they already trying to solve it? Does it compete successfully for resources against everything else they could be doing?

If not, you may have the wrong customer, the wrong framing of the problem, or a problem the market has not yet learned to prioritize. That last condition is not necessarily permanent. Problem-market fit can be built.

But building it is a different kind of work.

Political persuasion is an interesting example. You rarely change someone's behavior by dropping a completely unfamiliar idea into their head in a single conversation. You connect a new argument to something they already believe, repeat it, give it credible messengers, make it socially familiar, and gradually increase its importance. Markets can work the same way. Thought leadership, category creation, customer stories, analyst influence, peer evidence and repeated exposure can turn a tolerated condition into a problem people believe deserves action.

That is very different from asking a salesperson to walk into a meeting, convince someone that a previously low-priority issue is suddenly urgent, persuade them that your approach is the right solution, and then close the deal. It can happen, but it is an expensive foundation for a repeatable sales motion.

So the absence of problem-market fit does not necessarily mean stop. It means being honest about the job in front of you. You are still creating demand to solve the problem, not simply capturing demand for your solution.

The second is **solution fit**. Once the customer cares about the problem, do they believe the kind of intervention you are proposing makes sense? This is a place technology companies often skip. They prove that the technology works without proving that doing what the technology does is the right way to solve the customer's problem.

A customer can believe that your software does what you say it does and still not believe that doing that is the right way to solve the problem. That is not necessarily a product failure. It may be a failure to establish the logic connecting the problem to your proposed solution.

This is where the questions should start to change. How would this work here? What would it replace? What are the tradeoffs? What new problems would it create? Who would need to be involved? What would implementation require? Why is this approach better than hiring people, changing our process, building something ourselves, buying an incumbent product or simply living with the problem? If the customer cares about the problem but does not want to investigate your way of solving it, you have learned something important before the demo even begins.

Then comes **product fit**. The customer cares about the problem and accepts that your approach is a sensible way to solve it. Now they want to know whether your actual product is good enough. This is where demonstrations, pilots, technical proof, customer references, implementation plans and economics become useful.

Customers will tolerate remarkably imperfect products when the first two kinds of fit are strong. They routinely put up with rough interfaces, missing features, manual processes and awkward implementations when they badly want the outcome and believe this is the right path to getting it. There are also countless beautifully designed products that I would not adopt if they were free. Some I would not adopt if you paid me.

The price of a product is only one part of what it costs a customer. It also costs attention, implementation, training, integration, political capital, change management and another thing somebody has to own. If the problem does not matter enough or the solution does not feel compelling enough, zero dollars can still be too expensive.

### Give the customer some credit

Believing that you know your customers’ needs better than they do or that they just aren’t understanding how wonderful your product is shows a fundamental lack of respect. There are two kinds of respect that matter here. The first is respecting the customer's attention. Your product is almost never the center of their world. Even if the problem matters, they have a company to run, employees to manage, customers to serve and a dozen other, often very human things, competing for exactly the same hour you want them to spend thinking about you.

The second is respecting their ability to understand.

When a customer does not engage, it is comforting to conclude that they simply did not get it. We need a better slide. We need a sharper headline. Marketing needs to explain it differently. There can be truth in that, but customers are usually pretty smart, and often they understood you perfectly well. You just didn’t make them care. And sometimes ‘I don’t understand’ is an easier thing for a customer to say than ‘I’m not interested enough to keep working at this.’

Positive and negative feedback have a dangerous asymmetry inside growing companies. When a prospect loves the idea, it confirms the founder's belief that the product is great. When another prospect does not react, it confirms the belief that the messaging needs work. The product wins either way.

Companies can spend months circling this problem, changing language over and over, because “we have not explained our product correctly” is much more comfortable than “maybe this problem is not important enough to these customers.” There are only so many ways to describe something. At some point persistent difficulty generating energy is the evidence you need.

### From improvisation to something repeatable

Founder selling is often a kind of improvisation. Every conversation is different. The product shifts a little, the problem shifts, the promise shifts, and the story changes based on what the person across the table says. That is useful while a company is learning. It is not yet a scalable commercial system.

The transition is about holding more things constant. Can we sell roughly the same thing, to the same kind of customer, against the same problem, using the same basic proposition, repeatedly? Can someone other than the founder do it? When the founder leaves the room, does the customer still move from problem to solution to product?

That is much closer to the evidence a company needs before it begins hiring a large sales organization around supposed product-market fit.

Only then does another problem become dominant: can you reliably get this proposition in front of enough of the right customers at the right moment? Distribution has always involved intermediaries. Analysts, journalists, search engines, partners and other institutions shape how customers discover and understand products. AI agents and large language models are becoming another one, and potentially a very strange one. Increasingly, a customer may begin forming a view of both the problem and the available solutions before ever encountering your website or talking to a salesperson.

That creates a whole new set of questions about how companies become understood by the market. I want to come back to that separately in a future essay.

For now, when something is not selling, resist the urge to jump right into fixing the deck. Ask where the energy disappears. Do customers care enough about the problem (and how have they shown you that)? Do they believe your approach is the right way to solve it? Does the product actually deliver against what you sold? And can all of that still happen when the founder is no longer in the room?

Those are different problems, and you probably want to know which one you have before you hire another head of sales.