Sales Velocity: 7 Basics No Tool Fixes

Revenue teams are building more this year than ever before. More channels, more sequences, more agents, more segments. Tooling got cheaper and faster, so the number of things you can run at once keeps growing.

And yet, for many teams, the two numbers that matter have not moved: how many first conversations turn into closed deals, and how long that takes.

The cause usually sits one level below the tooling. There are seven questions every revenue organisation has to answer, and no tool answers any of them for you. They are decisions about ownership and focus. This article makes them testable: seven questions, one immediate action each, and a table at the end that shows you which one is still open on your side.

Why more tooling does not replace steering

If your options grow faster than your decisions, you end up paying for tools that run on an unclear foundation. Cost goes up, activity goes up, and the win rate stays where it was. That is not a tooling problem. It is a steering problem that more tooling only makes easier to see.

Manuel Hartmann, Founder and CEO of SalesPlaybook, puts it this way in his LinkedIn newsletter Diary Of A CRO: many people are asking for more AI, and few are getting the basics right. While everyone runs forward, he writes, the foundations quietly rot.

Our position: the cheapest intervention anywhere in the sales process is a decision, not a tool. A clear audience definition makes every campaign after it cheaper. An unclear one makes every campaign more expensive.

The four drivers behind revenue

If you steer on revenue, you steer on the outcome and always learn too late what went wrong. The result is a forecast with no levers: at quarter end you know it did not add up, but not which dial you should have turned in month two.

Revenue is a lagging number. It comes out of four leading drivers, and those are the only ones you can move inside a given week. This is the sales velocity formula, and the multiplication is the point:

• Volume — how many qualified conversations a rep runs per period.
• Speed — how fast a deal travels from first conversation to signature.
• Win rate — how many first conversations end in a close.
• Deal size — how large the average contract is.

Multiplied, they give you revenue per rep. The part most teams miss: the four are connected. Speed is not only speed. It also lifts the win rate.

The reason is not arithmetic, it is the buyer's experience. When things move quickly, trust forms — the buyer feels taken seriously and treated as a priority. The difference is often just two reactions to the same inbound request. One offers a slot in three weeks and announces an internal handover. The other picks up the phone, clarifies the situation immediately, and puts a signable proposal in sight for the next day.

Our own pipeline shows the same pattern from the other side. Deals with a documented LinkedIn touchpoint close at 51 percent, deals without one at 27 percent, and they take 22 days instead of 36. Measured across twelve months in our own pipeline. Faster and more often, together.

Our position: we steer on the four drivers, because those are the only ones that move inside a running week. Revenue is the receipt, not the steering wheel.

Immediate action: take your last twenty closed-won deals and calculate the four drivers once. The weakest of them is your constraint for next quarter.

Who do you solve which problem for?

If you cannot say your promise in a single sentence, you pay for that lack of clarity in every campaign that follows. The result is expensive reach without resonance: ads run, sequences go out, and the reply rate explains nothing. The constraint sits before the campaign, not inside it.

The test is simple. Say out loud who you help, which problem you solve, and what result is there afterwards. If you need two attempts, or if you slide into nouns, the decision has not been made yet.

"Platform", "solution" and "tool" are not changes. They are categories people sort themselves into when they cannot say what is different for the customer afterwards. Hartmann calls this a clarity problem rather than a messaging problem: if you cannot say the sentence with the verb in one breath, no campaign tool will paint over it.

Our position: we build messaging from the customer's result backwards, not from the product category forwards. Every positioning engagement starts with what the customer can do afterwards, not with what the product contains.

Immediate action: write the sentence down. Subject, verb, result. Hand it to three people in sales and ask whether they would say it that way in a first conversation.

What do you deliberately not do?

Running five channels half-heartedly means reaching the depth at which people recognise you in none of them. The result is reach without recognition: plenty of impressions, no demand, and after six months the conclusion that the channel does not work. What did not work was the duration.

Positioning is mostly about saying no. Not "mid-market, enterprise, start-ups, worldwide, every industry", but a choice you can defend: regulated sectors, one size band, one segment, one channel.

Focus has a second axis that breaks more often than the first: consistency over time, counted in quarters and years rather than weeks. One channel you work with discipline for two years beats five channels you try for three months.

For us that channel is LinkedIn, with webinars, articles and a newsletter attached to it. The numbers above come from exactly that decision, held long enough to measure.

Our position: reach is a perseverance problem, not a channel problem. We plan channels in quarters and do not judge them before the fourth.

Immediate action: pause your weakest channel for one quarter and put the time into your strongest. If the choice feels hard, you have too many. How we set this up is described under LinkedIn GTM.

Who owns positioning?

When the decision about audience and promise moves to a role without a view of the whole company, nobody really carries it. The result is claims that do not hold in the market, because they were never tested against product, price and delivery capacity. That gets corrected only when quarterly numbers force it.

Execution is delegable. An agency can build campaigns, a junior marketer can produce content, a freelancer can write sequences. The decision about what is communicated, to whom, with which promise, is not. Nobody except the leadership sees far enough across the company to carry it.

Behind it sits a second ownership question that stays open in many companies: who actually owns the new-business pipeline? Marketing, where the prospecting function often reports? The sales leader? Usually the person who owns both is exactly the one who is missing.

Our position: we delegate execution, never ownership. The positioning decision sits with the managing director, not with a project team.

Immediate action: name, in one sentence, the person who owns the new-business pipeline. If you name two, nobody owns it.

What runs centrally, what runs locally?

If you hand out the definition of the target market locally, you get as many markets as you have people. The result is numbers that cannot be compared and an organisation without a learning curve: everyone works on their own version of the market, so nobody learns from anyone else's results.

The classic failure in new-business acquisition is hiring five people for prospecting and leaving each of them their own stack. What comes out is five variants of the same outreach, five definitions of a good lead, and no basis on which anything could be improved.

The foundation belongs in one place: enrich the target market, segment it cleanly, keep the market message consistent. The work on it belongs with the reps. Hartmann frames the better assignment as a territory rather than an open field — these fifty enterprise, five hundred mid-market or five thousand SMB target accounts are yours, and your job is to work that part of the puzzle. A hunter with a territory, as he puts it, beats a hunter in an open field.

What that looks like in practice shows in the work with node.energy. Target market enrichment runs centrally through Clay, integrated into HubSpot as the system of record. The result is in the case study: 5x more demos with AI-powered outbound on Clay and HubSpot. Not because more people sent more messages, but because everyone worked the same cleanly segmented list.

Our position: markets are defined centrally and worked locally. A rep should work a market cleanly, not invent one on the side.

Immediate action: ask two people to show you their target account list. If the lists differ, market definition is running locally, whatever the org chart says. How we build a central list is described under Pipeline Generation.

Who owns the system everything lives in?

Where responsibility for the central revenue system stays open, nobody maintains it, and the steering from the drivers section loses its data. The result is numbers nobody in the building trusts, and a leadership team that quietly goes back to keeping spreadsheets on the side.

Two failure patterns show up again and again. In the first, the system belongs to everyone, so each person enters whatever they feel like, which is usually very little. In the second, it goes to the sales leader because he is the loudest user. That is understandable and still risky: the best closer is rarely the most structured person, and a system carrying marketing, sales, customer success and reporting at once is more than a sales list.

Hartmann draws the comparison to the other work a company already hands to trained hands: bookkeeping goes to an accountant, contracts to a lawyer, the website to an agency. The central revenue system deserves the same treatment, at least for setup and optimisation.

There is also a buying error that returns reliably: comparing licence prices in isolation. A lower per-seat price looks good until five extra tools are needed to pull the data back into one place. You end up paying for six systems, and the single reliable source of truth is gone anyway.

As a rule of thumb from practice, Hartmann names a size boundary: above roughly a thousand employees an enterprise system usually fits, below that usually HubSpot. That is experience, not a survey, and it does not replace checking your own case.

Our position: the CRM is company infrastructure, not one department's filing cabinet. We settle ownership before the first workflow, not after the first data mess.

Immediate action: name the person who decides on fields, stages and required data. If that person does not exist, that is the first thing to change. How we set such systems up is described under HubSpot CRM.

What do you do with the time you win?

If you put the time automation frees up straight back into automation, you lose exactly the part of the work that builds trust. The result is an efficient process with thinner relationships: more contacts, less attachment, and nothing to stand on in the first difficult negotiation.

The point of automation is not to replace customer contact. The point is to buy time back and then spend it on what a machine cannot do: visiting customers in person, researching deeper, going the extra mile. Not just a one-pager, but a dedicated landing page. Not the quickly written note, but a video you recorded yourself.

The same question applies in account management: does anyone genuinely want to understand what the customer thinks? Calling your best and your worst customer is not a reporting exercise. It is the only method that surfaces the reasons behind the numbers.

From that follows a consequence for hiring into revenue leadership: do not hire leaders who will not do the craft themselves. A marketing lead who will not talk to customers or go to events. A sales lead who will not sell. That sits in the same category as a technology lead who will not write a line of code.

Our position: automation buys time, and we give it back to the conversation. What a machine cannot do becomes more valuable, not redundant.

Immediate action: call your best and your worst customer this week. Not with a questionnaire, with an open question.

The seven questions as a self-test

Walk through the table once and mark the first row you cannot answer in a single sentence. That is your constraint, and it is almost always cheaper to close than the next licence.

Where this article comes from

The seven questions come from an issue of the LinkedIn newsletter Diary Of A CRO by Manuel Hartmann, published on 30 July 2026. The issue works through seven basics; its cover art groups them into five blocks. This article follows the text and adds measured evidence from our own work.

Cover image of the issue from the LinkedIn newsletter Diary Of A CRO by Manuel Hartmann. The figures shown in the artwork are illustrative values from the original design, not SalesPlaybook or client numbers.