The Sellable Package

A Generation prompted by Sean Linehan. Published on May 20, 2026.
A note before you read
This piece is AI generated. I picked the topic and the angle; the words are the machine's. I may or may not agree with what it says, but I found it interesting enough to keep.
Most founders I work with who are doing enterprise sales themselves run into the same decision point at roughly the same time. They've closed some deals, hired their first AE, and now the question is whether to hire a VP Sales right away or to keep running the team for another year so the eventual VP has something to inherit. Both paths can work. What matters more is understanding what you're actually selling to a future VP Sales hire, and how much of that has to exist before they'll take the role and succeed in it.
The framing I find most useful with founders in this spot is to think about your job for the next twelve to eighteen months as building a sellable package for a VP Sales hire. Not the company, the sales function specifically. A strong VP candidate evaluates you the way you evaluated them, and if the package isn't ready, the great ones pass and you end up hiring from the next tier down.
By "sellable package" I mean five concrete things, which the next sections work through one at a time. The five are a proven motion, a second-seller proof point, an operational cadence, a lead generation answer, and a founder-as-operator baseline. Founders consistently underinvest in two or three of these and over-invest in one. Then they're surprised when VP Sales searches stall out.

Diagnosis: what stage are you actually at

Before any framework matters, you need an honest read on where the sales function actually is. A founder I was talking with last quarter had closed twelve deals himself and hired one AE three months ago. He wanted to know if it was time to hire a VP Sales. When I asked about the AE, he said she'd closed one deal so far, with two more in late stage.
The picture there was a founder-led motion with a sample size of twelve, one rep two-thirds of the way through ramp, no documented playbook, and a CRM that the founder kept up by hand. He had a co-pilot. He didn't yet have a team a VP Sales could come in and manage. A VP Sales hired into that situation has to do all the founder's remaining work plus build their own team, and most of them won't sign up for that. The ones who will are usually the ones you don't want.
Most founders I talk to in this position are roughly at one of three stages. The first is founder-only, with maybe an SDR or a CS hire helping out. The second is founder-plus-one-or-two AEs, where you're trying to prove that someone other than you can sell the product. The third is two-or-three AEs producing on quota, with a working motion, where the question of hiring a VP Sales becomes feasible.
Most founders asking the VP Sales question are at stage two and feel like they're at stage three. The gap between those two stages is where most of the work I'm describing lives.

The proven motion

The first thing a VP Sales candidate wants to see is evidence that the motion works. The clearest signal is win rate against qualified opportunities. For B2B enterprise sales, a healthy founder-led win rate from first-meeting to closed-won sits somewhere between fifteen and thirty percent, with deal cycles you can describe with a straight face.
Below fifteen percent, you probably have a product or ICP problem rather than a sales-scaling problem, and hiring more reps will burn cash without fixing anything. Above thirty percent you might be underpriced, or selling only into your warmest network, which is its own kind of trap. Either way, you have to make the call about whether your data actually says the motion works, which requires enough deals in the pipeline to make the percentage mean something. Twelve closed deals is not enough.
The artifact that matters here is a written sales playbook, by which I mean a document rather than a deck. It describes ICP, the qualification questions you ask, the typical objections and how you handle them, the deal stages and exit criteria for each, and the things you say and do at each stage. A founder who is good at selling but cannot write the playbook down has work to do. If it can't be explained and written down, you can't bring on a team yet.

The second-seller proof point

Once you can describe the motion in writing, the next question is whether someone other than you can run it. This is the single most informative thing you can prove before hiring a VP Sales. A VP coming in cold has no idea whether the deals you closed personally were a function of your motion or a function of you being the founder. A second seller who is hitting roughly your win rate against similar accounts answers that question.
I generally recommend two AEs at this stage rather than one. With one, you can't tell if the result is the rep or the motion. Two AEs with comparable backgrounds, going through the same onboarding, working similar territories, give you a real comparison. If both hit reasonable productivity by month four or five, you have a transferable motion. If one hits and one doesn't, you have a hiring or coaching question. If neither hits, the motion still lives mostly in the founder's head and the playbook needs another pass.
Two AEs also creates a manageable management load. One AE who reports to a founder doing four other jobs gets very little attention and develops bad habits in isolation. Two AEs with a weekly 1:1 each, a weekly pipeline review together, and a weekly deal review forces you to actually operate the team. That muscle is what you'll hand to the VP Sales later.
A caveat on the hiring profile for these early AEs. Most founders try to hire senior AEs from name-brand companies, on the theory that experience compensates for the early-stage chaos. In my experience this fails more often than it works. Senior AEs from larger companies are used to inbound pipeline, a working sales operation, and a brand that opens doors. They struggle when none of that exists. The hire that tends to work better is a strong mid-career AE from a company one stage ahead of yours, someone who has lived through the same chaos recently.

The operational cadence

Founders running sales tend to either over-process or under-process. The under-processed version means deals get worked in DMs, the CRM is half-empty, and the founder genuinely has the pipeline state in their head. The over-processed version means a stage-gated CRM with eleven required fields per opportunity that nobody fills in honestly. The middle path is a small set of recurring meetings that produce decisions, backed by a CRM hygiene standard that the team actually maintains.
The cadence I've seen work at this stage has four meetings:
  1. A weekly AE 1:1
  2. Weekly pipeline review
  3. Weekly deal review
  4. Monthly metrics review.
The 1:1 is for the rep, not their pipeline. The pipeline review is where you walk each live opportunity and decide what advances or dies. The deal review is where you inspect one or two deals in depth, usually the largest or the ones that just closed or lost. The metrics review is where you set the next month's forecast and look at the leading indicators.
Those leading indicators are the report you want to be looking at every month, and the one a VP Sales candidate will ask for in their interview. The list is roughly pipeline coverage (live qualified pipeline divided by quota, with around 3x as a healthy ratio for the upcoming quarter), win rate by stage, average sales cycle, average contract value, quota attainment per rep, and new logos per rep per period. If you don't have those numbers handy, the VP Sales conversation will stay abstract, and abstract conversations tend to end with the candidate passing.
The other artifact worth building is a one-page sales operating doc that lives next to the playbook. It covers quota, comp plan, territory definitions, deal desk approval thresholds, discounting rules, and stage definitions, and it changes maybe twice a year. New AEs read it during onboarding, and the VP Sales reads it during their interview. The first version is something they'll mostly inherit and modify rather than rewrite from scratch.

The lead generation question

This is the question I see founders dodge most often. Where do the meetings come from? If the answer is "my network and inbound from the podcast I went on," you have a serious problem hiding under the win rate numbers, because that pipeline source doesn't scale and doesn't transfer to new AEs. A VP Sales candidate will figure this out in twenty minutes of diligence, and the good ones will quietly decline.
The early-stage answer to lead gen is usually that AEs do their own prospecting, supported by either a shared SDR or the founder's continued outbound. Asking AEs to source their own pipeline at this stage is reasonable. They have the context, the territories are small, and the volume isn't yet high enough to justify dedicated prospecting headcount. It also keeps the AE close to the ICP, which makes the second-seller proof point more meaningful.
Once you have two AEs hitting roughly half their pipeline through self-sourcing, the next move is to add an SDR. The math is straightforward. An SDR who can set fifteen to twenty qualified meetings a month for two AEs roughly doubles their selling time, and at typical comp ratios will pay for themselves at modest conversion rates. The SDR also lets you test outbound as a scalable channel, separate from the founder's network, which is the data point a VP Sales actually wants to see.
Marketing-sourced pipeline at this stage is mostly noise unless you have a product-led motion or significant content distribution already. Treat it as the VP's problem to figure out later.

Founder-as-operator

The last component is the one founders tend to skip because it feels like it's about them rather than about the sales team. But the founder's relationship to sales, after the VP is hired, is the single biggest predictor of whether that VP succeeds. Founders who never learned sales mechanics try to manage VP Sales by vibes and gut, and the relationship typically breaks within twelve months. Founders who built the operating rhythm themselves can hold a VP accountable to it, recognize when a VP is bluffing about the pipeline, and intervene constructively when deals are off.
This is the strongest argument for not hiring a VP Sales immediately and instead running the team yourself for nine to eighteen months first. You're not just building the team for the VP. You're calibrating yourself on what good looks like so you can pick the right VP and manage them well afterward. The founders I've seen do this well treat their stint as head of sales as a deliberate learning project, with the explicit goal of being able to hire a VP from a position of competence.
The pace of all this matters too. Founders often feel pressure to hire a VP Sales early because they hate sales, or because their board is asking, or because every founder talk they've seen treats hiring a sales leader as the thing that opens up the next phase. The hate-sales founder usually hires too early and the VP fails because the package wasn't ready. The board-pressured founder sometimes hires the wrong VP because they're optimizing for a board narrative rather than a sales outcome.
Twelve to eighteen months of founder-led operation, done deliberately, is almost always the cheaper path.

When this doesn't apply

A few situations break the pattern I've described. If the founder genuinely has prior sales leadership experience and has built a sales team before, the package-building phase can compress to six months or skip the second-AE proof point entirely. They already know what good looks like, and a strong VP can be hired in parallel with the team being built out. This case is rare but it does come up.
If your motion is high-velocity, low-ACV, and transactional rather than enterprise, the framework still applies but the numbers shift. Win rates are lower, deal cycles are much shorter, and you need more reps faster to make the metrics stable enough to interpret. The five components are the same, but the timeframe to get them in place is shorter, often three to six months instead of twelve to eighteen.
If you're selling into a market where deal sizes are very large and cycles run nine to eighteen months, you'll never accumulate enough closed deals to make win rate meaningful before hiring a VP. In that case the second-seller proof point has to be replaced with something else, usually a stage-conversion rate against named-account coverage. A VP Sales hired into that environment has to be evaluated more on prior experience selling at similar deal sizes than on the operating data you can hand them.
And if the company is pre-product-market-fit, none of this is the work. The work is the founder selling and learning. Hiring AEs before you have a repeatable motion is the most common way startups burn cash on the way to nowhere.

A short list of rules

  1. Don't hire a VP Sales until you have two AEs hitting roughly your founder-led win rate against comparable accounts.
  2. Write the playbook before you hire the second AE, not after. The act of writing surfaces the gaps in your motion.
  3. Run a weekly pipeline review and a weekly deal review from the day you have one AE. The cadence matters more than the team size.
  4. Track six numbers monthly: pipeline coverage, win rate, sales cycle, ACV, attainment per rep, and new logos per period.
  5. Make outbound work as a channel before hiring a VP. AE-sourced and SDR-sourced pipeline gives the VP something to scale rather than invent.
  6. Spend nine to eighteen months running sales yourself, deliberately, with the explicit goal of being able to evaluate and manage a VP Sales hire afterward.
Sometimes the company's stage demands a VP Sales before the package is ready. The round won't close without a named hire, or the board has lost patience and wants someone in seat by the next meeting. I don't have a clean answer for that case.
In those cases, the framework above is useful mostly as a diagnostic for how much risk you're taking on with the early hire and how much of the package-building work the new VP will have to do themselves alongside everything else. The best you can do is be honest with the candidate about what they're inheriting, pay them accordingly, and commit to staying close to the sales operating cadence yourself for at least the first six months after they start.
The package gets built either way. The only question is whether you build it before or after the VP arrives, and how much that timing costs you.