The Weekly Pipeline Plan · Andrew Wesbecher

01 · The Test

A plan you execute, or a checklist you resent.

Every rep I have coached has built a pipeline generation plan at some point. Most of them built it once, for a manager, and never opened it again. The document is not the problem. The difference between the two versions below is whether anything written on Monday reaches a buyer by Thursday.

Plans that get worked

Short, specific, and falsifiable.

Few enough accounts to name from memory

If you cannot list this week's accounts without opening the file, you built a report. Enterprise sellers who run two accounts hard beat enterprise sellers who run twenty accounts politely.

A value hypothesis with a number in it

One sentence tying a pain you can evidence to an outcome you can price. If the number will not survive a CFO asking where it came from, fix it now rather than on the call.

Named humans, above and below the line

Titles are a search filter. People answer phones. Below the line tells you what they run today, above the line owns the budget for changing it.

A goal that can fail

"Learn which model gateway they standardized on" either happened by Friday or it did not. That is a goal. "Make progress" is a mood.

Proof staged before the dial

The customer story is loaded before the first call. Nobody improvises a good proof point live, and the ones invented under pressure tend to be the ones that get repeated back to you in legal review.

Accounts that survive more than one week

The 2026 median cycle on a $100-200K deal is 178 days. Nothing about that number suggests an account deserves one week of attention and then the bin.

Checklists that rot

Long, generic, and safely unmeasurable.

Twenty accounts because the field said twenty

Volume on paper, nothing on the calendar. The list exists to be shown, and it shows well right up until forecast.

Pains copied off the buyer's website

A homepage tells you how a company describes itself to investors. It tells you nothing about what broke last quarter.

"Set a meeting" on every line, every week

An outcome you do not control, written down as a task. Six weeks of that and the plan reads as a record of failure, so the rep stops writing it.

A prospect list of titles with no names

"VP Engineering" is a filter, not a person. You cannot call a filter, and you cannot multi-thread one either.

Research that never leaves the document

Fifteen minutes of intelligence that appears in zero calls, emails or voicemails is fifteen minutes of reading.

A fresh list every Monday

Restarting is not prospecting. The account that ignored you for two weeks is often the account about to answer, and the rep who rotated away never finds out.

The test

Friday afternoon, read Monday's plan. If nothing on it reached a buyer, it was homework. Reps do not abandon planning because they are lazy. They abandon it because the last six plans changed nothing they did.

02 · The Plan

Five fields, filled backward from the meeting.

Most pipeline plans start with a list of accounts and hope a meeting falls out of the far end. Start at the other end instead. Name the meeting you intend to book, then work backward through what has to be true for it to happen. The same five fields every week, in the same order, because the order is what makes a miss legible.

01

The meetingA name, not a title

Who specifically, and why that person this quarter. "VP Engineering" is a search filter. A plan that cannot name the human it is trying to reach is a research project wearing a plan's clothes. If you cannot fill this field, the account is not ready to be on the plan yet, and the honest move is to say so rather than list it anyway.

02

The roomEveryone who can say no

Map the committee before the first dial, not after the first stall. Above the line owns the budget; below the line owns the truth about what they run today. Over 30% of late-stage pipeline sitting single-threaded is a tripwire in the operating system for a reason, and single-threading is decided here, weeks before anyone notices it in a deal review.

03

The gapWhat you do not know yet

Not what you know. What you are missing, written as a question with a name attached to whoever can answer it. Their homepage tells you how they describe themselves to investors. The gap is the thing you can only get from a call, a job post, a changelog or a conference talk, and it is the reason to pick up the phone this week rather than next.

04

The numberTheirs, not yours

Which of their numbers moves, by how much, by when. Written before the call, in the language someone inside the company would use out loud. If you cannot fill in the number, you are carrying a claim rather than a hypothesis, and the difference is audible in the first ten seconds of a cold call.

05

The Friday testOne outcome, pass or fail

The single thing that either happened by end of week or did not. No partial credit, no "made progress." This field is the whole reason the plan is worth building, and section 03 is about why it is almost never "book the meeting."

How many accounts belong on the plan, derived rather than guessed
Input	Where the number comes from	Worked example
Meetings you self-source each week	The capacity model. One per ramped seat, with the BDR carrying the other two.	1
Weeks of work before an account is ready to be asked	Your gate count in section 03. Three gates, roughly a week each.	3
Your account-to-meeting rate	Your own last twenty worked accounts. Not a benchmark, not mine, yours.	1 in 3
Accounts in flight	Weeks of work, times meetings needed, divided by your rate.	9
New accounts entering each week	Accounts in flight divided by weeks of work.	3

Run your own rate through it before you accept the nine. A rep converting one in six needs eighteen accounts in flight and will drown trying to work them properly, which is itself the finding: at that rate the targeting is wrong and adding accounts makes it worse.

The plan

Five fields, filled the same way every week, is a system. Five fields filled differently every week is a diary. The value sits entirely in the repetition, because repetition is the only thing that makes a miss legible.

03 · The Gates

You have not earned the ask until you can say three things out loud.

Here is the rule I install first, because it changes behaviour faster than any script. An account stays on the plan until you can say all three of the statements below from memory, in your own words, without opening a tab. Each one is earned on a call, not read off a website. Most reps skip straight to the ask holding none of them, get silence, and diagnose a targeting problem.

Gate one

"They run X for this today, and Y owns it."

Earned below the line, from engineers and platform ICs. A named tool and a named owner. Nobody above the line will tell you this, and half of them do not know.

Gate two

"Y is measured on Z this quarter."

Earned from managers. The metric someone gets promoted or fired against, in their words rather than your category's words. The number you wrote in field 04 gets rewritten after this call, and it gets better.

Gate three

"If they do nothing, here is what breaks, and roughly when."

Earned from either level, and it is the one that survives procurement. A deal with no answer here dies in legal review nine times out of ten, and it dies six months after you stopped being able to influence it.

Now ask

Above the line, holding all three.

A call that opens with what they run, what the team is graded on, and what breaks if nothing changes is not a cold call, and the person on the other end cannot tell it from a referral.

The gates

Three statements, each earned from a human, each checkable on a Friday. Most reps run twelve accounts for one week apiece, hold none of the three on any of them, and conclude that outbound is saturated. It is not saturated. It is ungated.

04 · Build It

Fifteen minutes, most of it not typing.

Fill in five things. The panel builds a research prompt for one account, sized to your motion and carrying last week forward. Paste it into an assistant with web search on, then spend the remaining twelve minutes reading the output like a skeptic and deleting the parts it made up. Nothing here is stored or sent anywhere.

Research prompt · one account

Run it with web search enabled. Everything it returns is a hypothesis until a human confirms it on a call.

An assistant is fast at gathering and confident when wrong, which is a bad combination on a first dial. Make it flag every inference, then cut anything you would not say to the person's face.

05 · The Touches

Nobody replies to a well-written email. They reply to a reason.

The plan tells you who to work. This is what you send them, and in what order. Most outbound training optimises the words, which is the wrong end of the problem: the words are being judged by someone who decided whether to engage before reading a full sentence. What you actually control is the shape of the message, how specific it is, and whether each touch does a different job from the last one.

Two different failures, two different fixes. Rewriting your value proposition does nothing about the first screen, which is where most of your sends die.

01

The open loopOnly works if it is real

An unfinished thought is uncomfortable, and replying is how the reader closes it. Works: "You posted three roles for agent infrastructure last month and none of them mention security. Wondered whether that was deliberate." Fails: "Noticed something about your GTM." If their first instinct is that you noticed nothing, you have spent trust instead of earning attention, and the next four touches inherit that.

02

Proof by specificityOne case beats ten aggregates

"$10M in pipeline for 200 customers" reads as noise, because a stranger's round numbers are unverifiable by design. One named comparable with a before, an action and an after number reads as true, because detail is what lived experience sounds like and vagueness is what invention sounds like. This is the sixty-word customer story from section 02, delivered in writing.

03

Loss that is actually theirsNot your calendar

Fake: three spots left this quarter. Real: a competitive dynamic they already half-suspect. "The teams that sort out agent identity before their first incident get to design it. The ones that wait get to explain it." The tell for manufactured urgency is that the clock belongs to you. Real loss framing puts the clock in their quarter, and they can check it against what they already believe.

04

The shape talks firstBefore a single word is read

Five paragraphs, a header, three proof blocks and a call to action announce themselves as a sales email from across the room. The reader files it before reading it. A short, oddly shaped message cannot be filed that fast, which is the entire point. "Andrew, saw you are standing up an SDR function. Had a thought." No proof, no pitch, no ask. Not because short is better, but because unfileable buys you the second screen.

Five touches, five mechanisms, two channels alternating. This is the touch pattern that carries you through the three gates in section 03.

The cadence, and what each touch has to carry
Touch	Channel	Mechanism	What it must carry that the last one did not
Day 1	Call, below the line	Human contact	One question about what they run. No pitch, no ask, no voicemail longer than fifteen seconds.
Day 2	Email, below the line	Open loop	Something you learned or failed to learn on the call. The email exists because the call happened.
Day 5	LinkedIn, above the line	Specific proof	One named comparable. LinkedIn is where peer claims carry most, so spend the proof point here.
Day 9	Call, above the line	Direct ask	What they run plus what the team is measured on. This is the call that stops sounding cold.
Day 14	Email, above the line	Real loss	The competitive clock, and an honest close-out. Your attention is finite and saying so is not a threat.

The rule underneath the table: no mechanism repeats, no channel runs twice in a row, and every touch carries something new. A sequence where touch four is touch one with "just circling back" on top is not persistence. It is a rep confirming the buyer's original read.

Diagnostic: what your numbers are telling you
What you see	What is broken	What to change
Low opens, low replies	Screen one, before the message is even open. Sender, subject, preview text.	Change the shape of the subject line, not its cleverness. Try statements and fragments instead of questions and hooks.
Good opens, low replies	Screen two. You got read and gave them nothing to do about it.	Rebuild around one mechanism instead of around a value proposition.
Replies, but hostile ones	The opener wrote a cheque the body did not cash.	Make the body deliver exactly what the hook implied. An open loop that resolves into a generic pitch is worse than no loop.
Replies, no meetings	The ask is too heavy for a first exchange.	"Worth ten minutes?" rather than "book a 30-minute call." Replying should cost less than ignoring.

Before you send

Five checks. Any one failing sends it back.

Does it look different from the last ten they got?

If the shape is familiar, the content will not get read. Rewrite the structure before you touch the words.

Does the first line open something the message does not immediately close?

If sentence one hands over the whole point, there is nothing left for a reply to do.

Is there one piece of information only someone who looked would have?

Not their funding round. Everyone has their funding round. Something from a job post, a changelog, a talk, a repo.

Is the urgency theirs or yours?

If the clock belongs to your quarter, cut it. It reads as a clock belonging to your quarter.

Is replying cheaper than ignoring?

A yes or no question clears this bar. A calendar link does not.

What I would not do

Advice that circulates and should not.

Deliberate typos to seem human

This gets recommended constantly. To a CISO evaluating whether you are careful enough to trust with runtime access, a typo does not read as human. It reads as careless, and it is the first thing they will quote to a colleague. Get the same effect honestly by writing something only their situation could have produced.

Fake threads and false re-sends

"Re:" on a first contact, or "bumping this up," when no prior message exists. It works exactly once per person and it costs you the account plus whoever they forward it to.

Manufactured scarcity

Three spots left, pricing goes up Friday, my calendar is filling. Every senior buyer has seen it hundreds of times and it marks you as junior in one line.

Volume as a substitute for a reason

Sending the same message to two thousand people does not make it work at scale. It makes the failure bigger and burns the domain you will need next quarter.

The touches

Five touches that each do a different job is a sequence. Five touches that each say "just following up" is a rep teaching a buyer to ignore them, one message at a time. The second is far more common, and it is the actual reason most people think outbound stopped working.

06 · The Week

Where the fifteen minutes sit.

The plan is worth building only if the week is built around it. Five moves, in order, on the same operating cadence as the rest of the playbook.

01

Monday, before the inbox

Same six fields, same fifteen minutes. Run the prompt on anything new. Carry forward every account still climbing the ladder, and write this week's goal for each one before you look at a single email.

02

Verify with a human before you build on it

The first call is a check on the research, not a pitch. One below-the-line conversation will confirm or kill more of the plan than another hour of reading ever does.

03

Tuesday to Thursday, work it out loud

The pain, the hypothesis and the proof point belong on the phone this week, not in the file. A dial that opens with a name and a reason is not a cold call, and it does not sound like one.

04

Friday, five minutes, honest

Did each goal land. Did anything from the document reach a buyer. Then keep one thing that worked and cut one thing that did not, in writing, so Monday starts from evidence rather than memory.

05

Roll the accounts, not the list

Accounts leave the plan when they convert or when they have failed a goal three weeks running. Everything else stays and gets the next rung. A plan that fully turns over every Monday is a plan nobody is working.

The cadence

Fifteen minutes on Monday, one self-sourced meeting a week, 49 weeks. That is the third of the three meetings a ramped seat needs, and it is the only one nobody else can book for you.

07 · The Rerun Problem

Forty-nine weeks of evidence, or one week run forty-nine times.

Two reps do the same volume for a year. One is measurably better in December than they were in March and can tell you exactly why. The other is running week one on repeat with fresh logos in it. The difference is not effort and it is not talent. It is three pieces of unglamorous administration, and every rep I have coached who got sharper had all three.

01

One named variable, chosen on MondayWritten down before the week starts

The opener, the persona, the channel, or the offer. One of them, named in advance, and section 05 is where each of those levers actually lives. Change four things and a better week teaches you nothing, because you cannot say which change earned it. This is the first rule reps break, and they break it in the week after a bad week, which is precisely the week the evidence matters most.

02

A Friday gate that a real number has to clearAnd the old version kept

Opens are not a result. Clicks are not a result. A subject line that lifts opens by reading more like spam has made things worse while showing you a green number. The honest gate is meetings booked, and one stage later, the 16% that turns meetings into qualified opportunities. Whatever fails the gate gets reverted, which only works if you kept the previous version, so keep it.

03

A log that outlives your memory of the weekWritten, not remembered

What you changed, why you expected it to work, what happened. Three lines. Without it you re-run the same experiment in different words for a quarter and call it persistence, and every dead opener, dead persona and dead account has to be discovered twice. This is why the plan is a document, and why accounts roll forward instead of resetting each Monday.

Where the week stops compounding, and what it looks like on a calendar
Failure	On a rep's calendar	The fix
Two tests, one channel	Two subject lines hitting the same inbox pool in the same week. Both numbers are noise.	One experiment owns one audience slice at a time.
Fake wins	Opens, clicks, and "a lot of good conversations." Nobody has ever forecast on a good conversation.	Grade on meetings and pipeline, every time.
Effort instead of experiment	Reply rate flat for three weeks, so the answer is more of the same, sent harder.	Change what is being tested, not how loudly.
No paper trail	Nothing written down, so the only memory of the account is how the rep feels about it.	Log the change, the reason, and the result.

The difference

An assistant can propose a hundred variants a week. It cannot tell you which one deserves to survive, because that call is a business number and the number is yours. Four quarters of keeping the winners and cutting the rest does not give a rep better instincts. It gives them a longer log, which beats instincts.

08 · The Stack

Cost per token is the wrong unit. The arithmetic going around is also wrong.

Section 07 says a week only compounds if you can afford to run the research behind it. This is that number. The idea circulating right now is that the most expensive model is secretly the cheapest, because it finishes analytical work in one pass while a cheaper model needs four rounds of correction. The idea is right. The multiples attached to it, in the version I keep getting sent, are not, and they are wrong in the direction that sells you something.

What is being claimed, and what is true

The claim: the top model costs five times what Opus costs and twenty-five times what Sonnet costs, so it had better be worth it.

Actual published rates on 27 July 2026: Fable 5 is 2x Opus 5 and 5x Sonnet 5 at its introductory rate. Not 5x and 25x. Whoever is quoting those multiples is comparing against a rate card that does not exist, and the inflated version conveniently makes a $20 agency line item look like a bargain.

The correction matters because it changes the answer. At 2x, the frontier tier is a reasonable default for hard analysis. At the claimed 5x, it would be a luxury you ration. Anthropic's own guidance is to start with Opus and step up only when you need the ceiling.

Published rates per million tokens, verified 27 July 2026
Model	Input	Output	Where it belongs in a GTM stack
Haiku 4.5	$1	$5	Classification and enrichment at volume. Tagging, deduping, routing, anything you would have written a regex for.
Sonnet 5	$2	$10	Copy. Drafting, variants, rewrites. Introductory rate through 31 August 2026, then $3 and $15.
Opus 5	$5	$25	The default for analysis you will act on: account research, campaign diagnostics, competitive reads.
Fable 5	$10	$50	The ceiling. Long context in one pass, no human checking the middle of it.

Rates change. Check the published pricing page before you build a budget on this table, and treat the date above as the expiry.

One question decides it, and it is not "which model is best." It is what a wrong answer costs you.

01

The three levers that beat model choiceCaching, batching, output length

Prompt caching cuts input cost by up to 90% on the stable part of a prompt, which for GTM work is most of it: your ICP, your positioning, your proof points, last week's history. The Batch API halves both directions when the work is not urgent, and a Monday research sweep is not urgent. Every current tier holds a five to one output-to-input ratio, so the fastest way to cut a bill is to stop asking for prose you will not read. Get these three right and the model you picked matters much less than the debate suggests.

02

The compliance footnote nobody postsAsk before you build on it

The frontier tier carries 30-day data retention and is not available under zero data retention agreements. If you sell into security or regulated buyers, and you are pushing prospect data, call notes or anything resembling customer information through it, that is a procurement conversation before it is a cost conversation. I have watched a deal stall for six weeks over less. Check it against your own DPA before the pilot, not during the security review.

03

Where the real money goesNot the tokens

A month of the research in section 04, run properly across a full target list, costs less than one dinner with a prospect. The expensive line in outbound has never been the model. It is the seat: a ramped AE at full cost, spending three of five days on accounts that were never going to buy. Cheap research that improves targeting pays for itself before the token bill is worth opening. Argue about the seat, not the tier.

The route

Route by what a wrong answer costs. A redraft, use the cheap tier. A call with a buyer you get one shot at, pay for the pass that does not need checking. Most teams have this exactly inverted: premium models writing emails a human rewrites anyway, and the cheapest available model deciding who is worth calling.

Three meetings a week. One of them is yours.