The first 90 days of business development, week by week

Ninety days is long enough to build something real and short enough that nobody has stopped watching. Both facts shape what you should do with it.

The first ninety days of a business development function get planned badly for a structural reason: the person doing the planning wants evidence quickly, and the only evidence available quickly is activity. So the plan fills with activity, the activity gets reported, and at day ninety there is a lot of it and no pipeline worth forecasting.

Harvard Business Review's description of Michael Watkins' The First 90 Days puts the stakes directly: "Missteps made during the crucial first three months in a new role can jeopardize or even derail your success." The framing that follows is built to avoid the specific misstep of mistaking motion for progress.

This applies whether the ninety days belong to a new hire, a founder deciding to take business development seriously, or an existing team restarting after a quiet period.

Days 1 to 30: learn the losses, not the pitch

The instinct in month one is to learn the product and start reaching out. Learn the product, certainly. But the higher-value study is the deal history, and specifically the deals that did not close.

Read every lost opportunity from the past year and sort them by where they died: no response at all, response then silence, interest but no budget, budget but no decision, or lost to a named competitor. Those five buckets have completely different fixes, and the distribution tells you what the next sixty days should be about. A pile of "no response at all" is a targeting and message problem. A pile of "budget but no decision" is a completely different problem living at the end of the funnel.

Month one should also produce a written description of the buyer that generates names nobody has contacted yet, and a short list of the sources those names come from.

Days 31 to 60: one channel, worked properly

The temptation at day thirty one is to open every channel at once so that something works. This reliably produces too little of each to learn from any.

Pick one channel and give it enough volume to produce a readable result. If it is outbound email or LinkedIn, that means a consistent weekly volume held steady for four weeks rather than a burst followed by silence. Our note on what LinkedIn outreach actually allows is worth reading before you set volume targets, because the platform's own limits decide what is achievable before your effort does.

The output of month two is not meetings, although meetings are welcome. It is a rate: how many attempts produce one conversation. Without that number nothing downstream can be forecast, and with it almost everything can be estimated.

Days 61 to 90: build the forecastable pipeline

Month three is where pipeline becomes the metric, because it is the first month where the number means anything. Pipeline in month one is a number about optimism. Pipeline in month three, built on a known conversion rate from a channel that has run for four weeks, is a number you can defend.

This is also the month to fix stage definitions, because the pipeline is now large enough for sloppy definitions to hurt. A stage should be defined by something the buyer did, not by how the seller feels. "Sent proposal" is an event. "Interested" is a mood. Our guide to building a B2B pipeline you can actually forecast works through the stage definitions that hold up.

Period	Primary output	Wrong metric
Days 1 to 30	Loss analysis and buyer definition	Meetings booked
Days 31 to 60	Attempts-to-conversation rate	Channels opened
Days 61 to 90	Forecastable pipeline	Total activity volume

The activity trap, stated plainly

Activity is the easiest thing to produce and the easiest thing to report, which is exactly why it becomes the default measure. Two hundred emails sent is a real number and it feels like work, and it can coexist with zero progress.

The corrective is to insist that every activity number is reported alongside its conversion. Two hundred emails and four replies is a message problem. Two hundred emails and forty replies and no meetings is a different problem entirely, sitting one step later. The raw number on its own hides which of those you have.

This is the same confusion that shows up in marketing, where an increase in a number gets reported as growth without anyone asking whether it changed the business. Khaled Badr's piece on what growth actually means, and why not every increase counts makes the distinction well, and it transfers directly to business development reporting.

What to write down as you go

Ninety days produces knowledge that evaporates if nobody records it. Three documents are worth maintaining from week one:

• The objection log. Every objection heard, verbatim, with what was said back and whether it worked. This becomes the training material for the next person.
• The disqualification list. The characteristics that made a prospect a waste of time. This is worth more than the ICP, because it is built from evidence rather than aspiration.
• The channel ledger. What was tried, at what volume, over what period, with what result. It prevents the same failed experiment being run again in six months by someone who was not there.

What ninety days cannot do

It cannot close a long sales cycle. If your typical deal takes six months from first contact, a ninety day plan that promises closed revenue is promising something the calendar forbids, and the honest version of the plan says so at the start rather than explaining it at the end.

It also cannot fix a positioning problem. If the loss analysis in month one keeps returning "they did not think they needed this", no amount of outbound volume in months two and three will change the answer. That finding is a genuinely useful output of the ninety days even though it is not the one anybody wanted, and acting on it beats grinding through another quarter of attempts.

The plan above is deliberately modest about what arrives when. A function that reaches day ninety with a known conversion rate, a defensible pipeline and three written documents is in a strong position, even if the revenue line has not moved yet. A function that reaches day ninety with a large activity number and none of those things has spent a quarter and learned nothing.