get the motion out of your head before you hire

I work with B2B founders at the 5 to 100 person stage who are still personally running their sales motion. The single most expensive mistake I watch them make has a polished name on it. They call it a bad hire.

Here is the shape of it.

A founder closes the first fifteen customers themselves. No deck that survives contact, no process written anywhere, just a founder who knows the product cold and can tell within ten minutes whether a buyer is real. Revenue gets to a couple of million. Then it flattens, because the founder is the constraint. There are only so many calls in a week.

So they hire. Usually someone senior. Someone with a logo on their CV and a number they hit three years running. The pitch to themselves is reasonable: this person has sold before, they will bring their playbook, they will take selling off my plate.

Four months in, the new rep is underwater. Pipeline they sourced is thin. The deals they did touch stalled at exactly the points the founder would have pushed through. The founder watches a forecast slip and reaches the obvious conclusion. Wrong hire. Let them go, try again, this time screen harder.

The hire was not the problem.

Here is what actually happened. The founder had a working sales motion. It just lived entirely in their head. Which deals to walk away from, what the buyer's real problem was underneath the stated one, when to stop talking, when a verbal yes was real and when it was politeness. Every one of those judgments was running. None of them was written down.

An experienced AE executes a system. They do not author one. That is not a knock on the rep. It is what the role is. You hand a good AE a defined motion and they run it faster and more consistently than you can. You hand them a vacuum and ask them to reconstruct, from scratch, the instincts you built over fifteen deals and a decade in the category. They cannot. Nobody could. You are not testing whether they can sell. You are testing whether they can read your mind.

What you handed them was a CRM full of fields and no method for filling them. Stages with names but no definition of what makes a deal actually move from one to the next. A pipeline that looks like a pipeline and is really a list of conversations that have not died yet.

So before you write the job spec, do this.

Take your last five closed-won deals. For each one, write a single sentence: what did the buyer believe was true before they spoke to you, that was no longer true after your first real conversation? That sentence is your diagnostic motion. It is the most valuable thing you own and it is almost certainly nowhere on paper. If you can answer it cleanly for fewer than three of the five, the thing you are about to hand a new rep does not exist yet in any form they could inherit.

That is the work that comes before the hire. Not screening harder. Externalising the motion you already run, so the person you bring in has something to stand on.

This is what a revenue operating system is, at founder scale. Not software. The motion itself, written down well enough that someone other than you can run it. The qualification logic. The two or three questions that separate a real opportunity from a friendly one. What a committed next step looks like, and how you check it actually happened rather than taking the rep's word.

That last one is the part almost nobody installs. Plenty of founders can describe their motion. Far fewer inspect it: check what the buyer actually committed to, and whether it happened, instead of trusting what the rep wrote down. Describing the motion is the easy part, and the part anyone can copy. Inspecting it is the part a new rep can't fake and a competitor can't reproduce.

Get that out of your head and onto a page, and the senior hire you were about to fire becomes the senior hire who finally has room to be good.

There is a version of early hiring that works, and it is worth naming, because the comments will name it if I do not. If you have genuinely run the motion enough times that you can teach it in an afternoon, hire. If you are hiring someone explicitly to co-author the system with you, a builder rather than an executor, hire. The pattern that fails is the specific one: hiring an executor to inherit a motion that was never made inheritable, and calling the result a personnel decision.

The founders who get this right are not better recruiters. They sequence it differently. System first, then headcount. The hire lands on something instead of into nothing.

I write about this three times a week on LinkedIn. This week, each post takes one piece of this further: the rep who could have been good, what to actually look for before you hire, and why "hire a senior AE" is usually the wrong first move.