October 2, 20264 min readpipelineoutboundstrategy
Q4 Started Yesterday. Your Pipeline Didn't.
The uncomfortable arithmetic of the last quarter: what you actually need in the funnel today to close anything by December 31.
By Scrappy Team
It is October 2nd. There are 90 days left in the year, and roughly 61 of them are working days once you take out weekends and the stretch between Christmas and New Year when nobody signs anything.
That is the real number. Not 90. Sixty-one.
Work backwards, not forwards
Most teams plan Q4 forwards: here is what we will do in October, then November, then December. That hides the problem. Plan it backwards from the close date instead and the picture changes immediately.
Take a deal that needs a 45-day cycle from first reply to signature — modest, for anything with a procurement step. For that deal to close by December 31, the first reply has to land by November 16. Not the first email. The first reply.
Now add the part everyone forgets. Cold outreach does not get a reply on the first touch. A sequence that works is four to six touches over two to three weeks. So the first email in that sequence has to go out around October 27.
Which means the list it draws from has to exist, be enriched, and be validated before then. You have about three weeks to build it.
The volume question
Here is the arithmetic nobody enjoys. Work out your own numbers rather than borrowing anyone else's, because reply rates vary enormously by market — but the shape is the same for everybody:
deals needed
÷ win rate (opportunity → closed)
÷ meeting-to-opportunity rate
÷ reply-to-meeting rate
÷ reply rate
= contacts you need in the funnel
Each division multiplies the number at the top. Four divisions by rates well under one is how "I need three deals" becomes "I need several thousand verified contacts", and it is why teams that start Q4 outbound in November are not actually running Q4 outbound. They are running Q1.
Where the quarter is usually lost
Not in the sending. In the three weeks before it.
Bad data burns your sending reputation at the worst possible time. Bounces hurt most when you are sending more than usual, which is exactly what Q4 means. A list that bounces at 8% in October will have your December mail landing in spam, and no amount of good copy recovers from that. Validate before you send, not after.
A list built in a hurry is a list of the wrong people. The fastest way to waste three weeks is to send a perfect sequence to contacts who were never going to buy. Narrower and smaller beats broader and bigger in a compressed quarter, because you cannot afford the second attempt.
Enrichment that happens by hand does not happen. If finding each contact's role, company size and email takes a person five minutes, a thousand contacts is twenty working days. The quarter is gone before the first email sends.
What to do this week
- Fix your close date assumption. Ask what actually closed in the last two quarters and how long it took. Use that number, not the optimistic one.
- Build the list now, send later. The list is the long pole. Everything else can be written while it builds.
- Validate before the first send. Deliverability is the one mistake that compounds across the whole quarter.
- Cut the segments you cannot service. A smaller list you follow up properly beats a larger one you abandon at touch two.
The honest version
If your Q4 number depends on new outbound pipeline and you have not started, December is already decided. That is not a reason to skip it — it is a reason to start this week and let the pipeline land in January, which is a genuinely good quarter to have full.
The teams that have a strong Q1 are the ones building their list in October. That has always been true. It is just easier to see on October 2nd.
Scrappy builds and validates lead lists from the sources you point it at, so the three weeks above become an afternoon. Start with 100 free credits.
Keep reading
A JavaScript Dialog Looks Exactly Like a Frozen Tab
Every CDP command on the tab times out, CPU is at zero and the screen shows a normal page. Before you call it a hung renderer, rule out a native dialog.
proxiesYour Proxy Provider Replaced the IP. Your Config Still Has the Old One.
A static residential IP was replaced overnight, the old address answered 407, and every login pinned to it failed. What we changed so it cannot recur.
browserpuppeteer.connect() Hangs Forever. Here Is Why, and How to Tell.
A puppeteer connect that never resolves while raw CDP answers instantly is usually one target that never attached, not a dead browser. How to tell.