What Results to Expect From an Outbound Agency in the First 90 Days

What the marketing pages promise, and why that's not the whole clock

I'm Hlib Storchak. I build and run outbound systems for B2B founders and sales teams, 2000+ meetings booked for B2B clients, and one of the most common calls I get is from a founder three or four weeks into an agency engagement asking whether something is broken. Usually nothing is. They read a homepage that said "meetings in two weeks" and a signed contract that started the clock, and now they're comparing a marketing sentence to their actual calendar.

Agency onboarding pages are not lying, exactly. SalesHive's own process page states plainly that its model runs "first call to booked meetings in weeks," and lays out a four-phase build: kickoff and playbook in week 1, list building and validation in weeks 2 to 3, campaign launch in weeks 2 to 3, with first qualified meetings arriving within 1 to 2 weeks of that launch (SalesHive, "Our Process"). Belkins states an even tighter number for the paperwork side: 5 business days from kickoff call to launch, needing about 5 hours and 2 calls of a client's time, with appointments "very often" appearing in the first week of partnership, though the same page is careful to add it can't guarantee that (Belkins, client-facing onboarding page). Both of those are real numbers from the agencies' own sites, not invented ones. What they describe, though, is time to first meeting, not time to a meeting count you can build a forecast on. Those are different clocks, and conflating them is where most of the week-3 panic calls come from.

Before kickoff: what you owe them before the clock starts

The fastest timelines above assume you show up to kickoff with an answer to three questions: who is your ICP, what is the offer, and which domains or mailboxes are you sending from. If any of those three is still being debated internally, add that debate time before the agency's clock even starts, since no amount of agency speed fixes an ICP that changes mid-onboarding. This is the single biggest lever a client controls, and it's also the one most often skipped in the sales process, because "we'll figure out targeting together" sounds collaborative on a call and costs two extra weeks in practice.

Days 1 to 5: onboarding and the ICP sign-off

This is the part that genuinely can move at the pace agencies advertise, because it's mostly information transfer, not execution. Expect a kickoff call, a written ICP and offer sign-off, and access handovers (CRM, any existing domains, brand assets). Belkins' 5 business day figure and SalesHive's week-1 phase both live here. If this stage drags past a week and a half, the more common cause is an internal approval bottleneck on the client side, someone in marketing or leadership needs to sign off on messaging, than anything the agency is doing slowly.

Weeks 1 to 2: the part no marketing page slows down for

Cold email needs warmed sending domains before it can go out in volume without landing in spam, and warmup is a fixed clock, not a negotiable one. SalesHive's own phase breakdown names domain warming specifically as a week-1 activity running in parallel with the playbook build, which is the right sequencing: warmup should start on day one, not after copy is approved, since waiting to start it stacks two clocks in sequence instead of running them side by side. If an agency's timeline has warmup starting after list building and copy are done, that's a sequencing choice that adds a week or two for no real reason, and it's a fair thing to ask about before you sign.

Weeks 2 to 4: lists, copy, and launch

List building, verification, and copy drafting happen here, and this is where quality and speed genuinely trade off against each other. A rushed list built purely to hit a launch date arrives with more bad emails and weaker targeting than one given an extra few days to verify against your actual ICP criteria. SalesHive frames weeks 2 to 3 for the playbook and TAM build and weeks 3 to 4 for list building, validation, and launch, which puts real send volume starting somewhere around week 3 to 4 for a clean run. That lines up with what I see running accounts myself: campaigns that launch in week 2 to "hit the timeline" almost always need a list correction in week 3 anyway, which costs more calendar time than doing it right the first time would have.

When the first real meeting actually lands

Once send volume is live, the honest range for a first meeting is 2 to 4 weeks after launch, not from kickoff. Add that to the 2 to 4 weeks of onboarding and setup above and you land on roughly weeks 4 to 8 from contract signature to first meeting for a typical B2B ICP, later than the headline "meetings in two weeks" framing suggests, because that framing usually measures from launch, not from kickoff, and doesn't always say so. A first meeting inside week 2 or 3 is possible and does happen, usually when the ICP is narrow, the offer is well understood already, or the list has some warm signal in it (an existing pipeline, a known event, a referral network) rather than a completely cold new list. Treat a fast first meeting as a good sign, not the baseline you should expect on every account.

Weeks 6 to 9: from a trickle to a number you can plan around

This is the stretch that marketing pages skip entirely, because there's no clean sentence for it. One or two meetings in week 5 tells you almost nothing about whether you'll get eight or ten a month by week 10. This is where A/B tests on subject lines and openers run their course, where the list gets segmented once early replies show which sub-segment is actually responding, and where deliverability either holds as volume ramps or starts showing cracks that need a domain-health fix before they compound. None of this is a sign anything is wrong. It's the actual work of turning "it can work" into "here is roughly how many meetings next month looks like," and it takes real weeks, not a weekend of tweaking.

Day 90: what "predictable" should actually look like

By day 90, you should be able to answer four questions with real numbers instead of guesses: roughly how many meetings a month is this producing, which segment of your list is driving most of them, what's your current reply rate and how does it compare to when you launched, and is deliverability holding steady or degrading as volume has scaled. If you can answer those four with data instead of a shrug, the program has actually ramped. If the answer to any of them is still "too early to tell" at day 90, either the launch was delayed somewhere in the first 60 days, or the account isn't being run with enough rigor to have generated an answer, and both are worth raising directly with whoever runs your account.

The stated timeline vs the realistic one, side by side

The mistake I see most often at week 3

The mistake I see most often when I take over a mid-ramp account is a client who benchmarked the whole engagement against the fastest number on the agency's homepage, then treated week 3 with zero meetings as proof the program had failed, right when list building and warmup were still legitimately in progress. That reaction usually triggers one of two bad moves: pressuring the agency to launch early on an unverified list, which produces worse deliverability and a slower real ramp, or churning the engagement at week 4 or 5, right before the stretch where most accounts actually start producing. The fix isn't blind patience either. It's agreeing on the specific week-4 and week-8 checkpoints before you sign, so a slow start has a defined moment to get flagged instead of a vague sense that something feels off.

Pace red flags, not scope red flags

This is deliberately narrow: it's about timing signals, not the broader vetting checklist (references, contract terms, who does the work) that belongs in a different conversation before you sign. Three pace-specific signals are worth watching once you're inside the first 90 days:

• Still "warming domains" past day 30 with no launch date given. Warmup should be measured in weeks, not months, once it's actually started. A moving target here usually means it started later than agreed.
• A burst of meetings in week 2 or 3, then near silence by week 6. This pattern often means the first batch came from a small warm slice of the list (existing relationships, inbound-adjacent contacts) rather than the cold process actually working, and the real cold number hasn't shown up yet.
• Flat or declining meeting count from week 6 to week 10 instead of climbing. A healthy ramp trends up through roughly week 9, even if it's a small number of meetings. Flat or falling in that window, with volume held constant, is a signal to ask about list exhaustion or a deliverability issue before day 90 arrives.

A cost model: what a slow ramp actually costs you

Here's a way to put a number on a delayed ramp, built on assumptions you should replace with your own. Assume a $5,000/month retainer and a target of 8 meetings a month once ramped, so a rough cost-per-meeting target of $625 at full pace. If the program is still producing 2 meetings a month by week 10 instead of the 6 to 8 a healthy ramp should show by then, you've effectively paid close to $2,500 per meeting for that stretch, four times the target rate, without that alone telling you whether the program is broken or simply still ramping on schedule. The number only becomes a decision point once you compare it against where the timeline sections above say you should be: if week 10 output looks like a normal week 5, you likely have a launch-delay problem worth raising, not a program-failure problem worth cancelling over.

Run this with your own retainer, your own meeting target, and the week-by-week benchmarks above as the yardstick, not a fixed percentage. The exercise is less about the exact dollar figure and more about forcing a specific "is this on pace for week X" comparison instead of an anxious general feeling that it's taking too long.

FAQ