We installed a CRM, but the numbers did not move. I hear this constantly. The cause is almost always the same: the CRM has become an application that a staff member operates. Someone manages contacts, sends emails, and looks at the pipeline screen. That is where it stops.
- Using and designing are different things
- Why only the CEO can do it
- Until now there was a technical wall
- AI removed the technical wall
- A case where losses turned into profit
- What designing actually means in practice
- Now is the time to lean into CEO dependence
- There is nothing wrong with a hands-on CEO
- The first step you can take today
Using and designing are different things
Using means entering data, sending emails, and learning what the buttons do. Designing means deciding which metrics to watch, when to act and toward whom, and which pipeline will raise the win rate. These are two entirely different activities.
The data inside a CRM contains everything about how a company sells. Which customer moved and when, which message they responded to, where the deal stalled. Reading that structurally and designing the next move is what a CRM is actually for.
In most companies, however, that design work is left to a staff member. In some companies nobody does it at all. Selling is the hardest and most important activity a company performs. Leaving its design to the staff level is like handing the heart of the business to a new hire.
The insidious part is that the problem stays invisible. When the numbers weaken, it gets explained away as a bad economy or strong competitors. Years pass without anyone recognising it as a design problem.
Why only the CEO can do it
Sales design is company strategy itself. Which market to pursue, which customers to prioritise, where to invest. These are the CEO’s decisions.
A staff member cannot decide to drop a customer. They cannot decide to change a price band. Design is a chain of exactly those decisions. Even at executive level it is difficult; in practice it takes the CEO.
This is less about ability than about authority and field of view. Deciding that a metric does not need to be watched is a strategic judgment, and only the CEO can make it.
Until now there was a technical wall
Even so, it used to be hard for a CEO to do this personally. Salesforce demands specialist knowledge; HubSpot configuration is complex. So CEOs handed the work to IT staff or outside vendors.
What happens when you hand it off? You explain the requirements, wait weeks, and repeat “that is not quite it.” Meanwhile the market moves. A lag opens up between the CEO’s judgment and its implementation.
Worse, outside vendors know nothing about your strategy, your market, or your customers’ voices. What they know is the feature set of their own tool. So the design becomes “this feature is convenient, let us use it.” It never becomes a design built around how your company wins.
The same structure applies when it is left to internal staff. Tools should be designed to fit the company’s strategy, but instead the strategy gets squeezed into whatever the tool happens to do. If the direction is wrong, the harder everyone works, the further off course the company goes.
AI removed the technical wall
AI has changed that structure. By speaking to AI in plain language, you can now change HubSpot settings, analyse data, and rebuild a pipeline.
When the CEO says “I want to see this weekly,” AI builds that view. When the CEO says “I want to move while interest is high, so tell me which deals have stalled,” AI configures that mechanism. The CEO’s judgment becomes part of how the company sells, the same day.
The point worth emphasising is this: use AI not as an efficiency tool, but as a foundation for externalising thinking, improving judgment, and designing. AI organises the sales strategy in the CEO’s head, gives it structure, and helps implement it.
A case where losses turned into profit
Here is a company we support. For a long time it managed selling through a CRM and stayed in the red. The CRM was there, and the numbers never improved.
The core problem was that yield across the pipeline was not being managed. Customers were genuinely interested, yet they were not moved to the next phase while that interest was still high. A staff member entered data, a staff member read the reports, a staff member acted. But that person had neither the authority nor the field of view to see where deals were dropping and change the response.
What changed was that the CEO began using AI to work out which metrics to watch. At which stage is the yield falling? Are we moving interested customers to the next phase before their interest cools? The CEO raised those questions and worked out the answers together with AI.
The company moved into profit. What changed was not the product or the market. It was that the CEO became the designer.
What designing actually means in practice
It is not difficult. It starts with putting into words the customers your company can win. What industry, what size, what problems make a customer need your product most?
Once the CEO sets the target, AI classifies those customers inside the CRM, assigns priority, and designs the order of approach. The CEO decides direction; AI implements.
Next comes deciding which metrics to watch. Win rate, average days to close, the distribution of loss reasons. What you look at determines what you act on.
Last comes deciding where to invest. Which channel to push, which customer segment to give up, when to add people. AI can organise the data and lay out the options, but the CEO decides.
Now is the time to lean into CEO dependence
People ask whether having the CEO design everything is dangerous key-person dependency. What if the CEO is out of action?
My answer is direct: right now is exactly the time to lean into it. Before AI, there was a limit to what one person could do, so the work had to be spread out. That is no longer true. The CEO’s judgment now takes shape directly, so it should not be diluted.
On top of that, the order matters. The CEO designs, AI structures that design, and it gets implemented in the CRM. What is implemented can be operated by staff. Design belongs to the CEO, operation to the team. Once a design is written down and structured, it can be handed over.
The most dangerous key-person dependency is a design that exists in nobody’s head. “This is just how we have always done it” is what cannot be handed over.
There is nothing wrong with a hands-on CEO
Today’s management orthodoxy says the CEO should watch the big picture and leave details to the team. Micromanagement is bad, delegation matters, and so on.
But in a small or mid-sized company, a CEO caring about the details of selling can decide whether the company lives or dies. Post-war Japanese founders sold the product themselves, talked to customers themselves, improved the product themselves.
As companies grew, pressure emerged that said it was undignified for a CEO to do such work, and sales design fell into a place where nobody owned it. What AI changed is that structure. Without a large organisation, the CEO can design the CRM, read the data, and build the automation. The need to keep hiring simply to act on your own ideas has fallen.
It has become a time when a CEO is allowed to speak up about details and care about them.
The first step you can take today
Start by putting into words the customers your company can win. Who needs your product most? Then talk to AI about it: “This is what we sell. Help me think about which customers we should prioritise.”
Inside that conversation, the metrics you should watch will surface. So will the pipeline you should design, and what belongs in your CRM.
Becoming the designer is not about learning a tool. It is about working out how your company wins at selling. Selling is the heart of a business. I would like to see CEOs take its design back.

Comments