The First 90 Days of Outbound: A Founder's Operating Plan

Most founders we work with don’t need more advice about outbound. They need a sequenced operating plan they can follow without having to reinvent it. This post is that plan — a 90-day, week-by-week structure for the first run of outbound at a Seed-stage company.

It assumes you have product, early customers, and a real (if rough) sense of who buys. It does not assume you have a defined ICP, a working sequence, or any of the other artefacts that “running outbound” implies. By the end of week 12, you should have all of them — or a clear, defensible answer for why outbound isn’t the right channel for your business right now.

What the data says about the starting point

Three numbers shape what’s possible.

91% of sales teams missed quota in 2024, which tells you the market is harder than it was three years ago, not easier. Gartner’s most recent buyer research shows that B2B buyers spend just 17% of their purchase time meeting with potential suppliers — and a single rep gets only ~5% of that. So your outbound is competing for a sliver of buyer attention, against twenty other vendors doing the same thing.

But — RAIN Group’s research also finds that 82% of buyers will accept meetings with sellers who proactively reach out, and 71% want to talk to sellers early when looking for new ideas. The buyer hasn’t disappeared. They’ve gotten more selective. The plan below is designed to land in the small fraction of outreach they’ll actually engage with.

Weeks 1–2: Foundations (the unsexy part)

The first two weeks are entirely setup. Resist the urge to start sending. Founders who skip this phase spend weeks 5–8 debugging the setup instead of learning about the market.

Week 1

• Set up a secondary sending domain (don’t send cold mail from your primary).
• Configure SPF, DKIM, and DMARC for the secondary domain.
• Provision 2–4 inboxes per sending domain and start warmup (Smartlead, Instantly, or Mailreach).
• Document your working ICP — two or three sharp segments, not “B2B SaaS 50–500.”
• Write the qualification bar for what a “real” meeting looks like. Without this, week 8 turns into “we booked things but they weren’t qualified.”

Week 2

• Source contacts for segment one only. Don’t try to build all segments at once — segment one is the experiment that informs everything else.
• Verify every contact (ZeroBounce, NeverBounce, or similar). Bounce rate target for the first wave is under 2%.
• Map a buying committee for the top 10 accounts in segment one — five roles per account, two named people per role minimum.
• Write the first messaging matrix: three angles for segment one (a pain-led angle, a trigger-led angle, a contrast-led angle).
• Build a reply-tagging taxonomy you’ll actually use weekly.

Weeks 3–4: First wave + first learnings

The first wave is deliberately small. The goal is not to book a lot of meetings — it’s to validate that the infrastructure works and the direction is right.

Week 3

• Launch sequence to segment one. Volume: ~30–50 contacts per inbox per day across 2–4 inboxes. Total: ~200–400 contacts in the first wave.
• Daily reply triage and tagging. Reply quality matters more than reply quantity at this stage.
• Monitor bounce rate and deliverability daily for the first week.

Week 4

• Mid-wave readout: bounce rate, reply distribution, any signal on which of the three angles is producing better replies.
• Adjust the next wave based on what segment one is telling you.
• Begin sourcing segment two for week 5 launch.

Weeks 5–8: Run the test (the part that produces signal)

By week 5 you should have enough infrastructure and enough first-wave data to run a real test.

Weeks 5–6

• Launch segment two with its own messaging matrix.
• Continue segment one’s second wave, with the angle that worked best.
• Daily reply triage continues. Weekly readout becomes the operating rhythm.
• First meetings are getting booked. Treat each one as a data point — what was the buying context, what objections came up, what would have made them more or less likely to take the call.

Weeks 7–8

• Mid-pilot decision point: which segment is performing, which isn’t, and is the gap big enough to cut the underperformer.
• Begin tracking meeting-to-opportunity rate — the Bridge Group benchmark is ~52.7% for well-run teams. Your number will be lower at week 8 and that’s fine; the directional question is whether it’s heading up.
• Sequence-level conversion comparison — are different angles producing meaningfully different reply patterns?
• Update messaging based on the first 40+ replies.

Weeks 9–12: Verdict + scale plan

The last four weeks aren’t about expanding volume. They’re about producing a defensible answer to “what next.”

Weeks 9–10

• Run the best-performing segment + angle combination at higher volume to validate that the early signal holds.
• Begin probing segment three if segments one and two are both showing signal — otherwise drop it.
• Reply quality should be improving as messaging tightens. If it isn’t, the issue is upstream (targeting, segment).

Weeks 11–12

• Final readout: which segment, which angle, which channel mix produced qualified pipeline. Honest answer, not optimistic framing.
• The three possible verdicts:
  • Scale. The data supports doubling down with more volume, more inboxes, and (eventually) a hiring decision based on evidence.
  • Narrow. One segment works but the rest don’t. Focus there and revisit the others in a quarter.
  • Pause. Outbound isn’t producing economically defensible pipeline at your ACV right now. The honest move is to invest elsewhere for two quarters and revisit.
• Document everything that worked into a playbook a future hire could follow on day one.

“The 90-day mark is the moment most founders should be making the SDR-hire decision, not the moment they should already be six months into one. By week 12 you should know exactly which segment, which message, and which qualification bar — and you should be able to hand all of that to a new rep in writing. If you can’t, you’re hiring against optimism, not evidence.” — Sally Rutherford, Managing Director of Outbound Panda

The 30-minute Friday readout

The operational glue that holds the whole 90 days together is one weekly meeting:

• Sent volume by segment (5 mins)
• Positive reply rate by segment (5 mins)
• Reply quality distribution (5 mins)
• Meetings booked vs. qualified meetings (5 mins)
• One paragraph: “what we learned this week” (5 mins)
• One decision: continue, double down, cut, or replace (5 mins)

Thirty minutes, same agenda every week, different decisions. By week six this meeting is sharper than most internal sales operating reviews. By week twelve, it’s the artefact that lets you make a confident next move.

What this means in practice

The 90-day plan isn’t a guarantee of pipeline — outbound at Seed stage never is. It’s a guarantee that whatever you learn, you learned it on purpose. The teams that come out of the first 90 days with conviction about their motion are the ones that ran the work in this order. The teams that come out unsure usually skipped weeks 1–2 to get to “sending faster,” and ended up sending against a setup that couldn’t produce learning.

Run the order. Trust the cadence. By week twelve you’ll have an outbound system or a defensible reason not to invest in one — both of which are better outcomes than the most common one, which is six months of activity with no verdict.