The Last Five Weeks: How to Close Q2 and Not Start Q3 Empty
There's a pattern that repeats for almost every operator at the end of every quarter. The last few weeks are consumed by delivery — finishing projects, closing loose ends, keeping clients happy. The pipeline work that should have been running in the background quietly stops.
June 30 arrives. Q2 numbers look fine, maybe even good. But July 1 starts with a nearly empty pipeline. The work you closed in Q2 means you've been heads-down for six weeks and haven't had a real outreach conversation since April.
This is not a motivation problem. It's a systems problem. And the last five weeks of Q2 — right now — are the exact window where the right moves compound into a strong Q3 start.
The Two Jobs That Have to Run Simultaneously
At the end of a quarter, operators are trying to do two things that feel incompatible:
- Close what's already in motion. Active conversations, warm leads, deals that have been "almost ready" for three weeks. These need consistent follow-up, timing, and a clear close push.
- Build the Q3 pipeline. New outreach, fresh contacts, content going out to the market. This takes time and energy you don't have when you're also closing Q2.
Most operators can only do one. They pick closing Q2 (sensible, the money is real) and sacrifice pipeline building. Then Q3 starts with a 6–8 week lag before new outreach converts to conversations.
The operators who consistently have a warm Q3 start figured out how to run both motions — not by working more hours, but by separating the work that requires human judgment from the work that can run on schedule.
The Five-Week Sprint — Week by Week
| Week | Close Q2 Work | Build Q3 Work |
|---|---|---|
| Week 1 (now) | Audit: which deals are actually closeable before June 30? | Launch new outreach batch — 40–60 fresh contacts, ICP-matched |
| Week 2 | Reactivate warm leads who went quiet in March–April | Second touch on Week 1 outreach; start content for June |
| Week 3 | Close push: demo + decision deadline for active deals | Third touch; surface who responded and book calls |
| Week 4 | Final follow-ups on stalled deals; accept "not now" explicitly | New batch live; first responses from Week 1 contacts converting |
| Week 5 (last week of June) | Q2 close: contracts, invoicing, final client confirmations | Q3 pipeline already seeded — 8–15 warm conversations in play |
This is not a heroic schedule. It's five weeks of consistent parallel motion — the close work happening in the foreground while the pipeline build happens on schedule in the background.
What Has to Be Off Your Plate for This to Work
The reason most operators can't run both motions simultaneously isn't willpower. It's that the background work — research, sequencing, drafting follow-ups, running content — requires the same mental bandwidth as the close work.
When every GTM task requires you personally, you can't run two tracks at once. Something gives. It's always the pipeline build.
The Compounding Effect of Running Both Tracks
When you keep the pipeline build running through close mode, something counterintuitive happens: you close Q2 better, not worse.
The operators who go completely heads-down into delivery get desperate in the last two weeks. They try to rush deals, push too hard, miss timing cues. The ones who know Q3 is already seeded can close Q2 deals on the right terms — patient, confident, not chasing.
The pipeline you build in weeks 1–3 of this sprint won't convert to revenue until August. But by August, everyone else who went heads-down in June will be scrambling through the summer with an empty funnel. You'll be running demos on leads that have been warming for 8 weeks.
"Every time I focused completely on delivery for 6–8 weeks, I'd come up for air and there was nothing in the pipeline. I kept treating it like a temporary problem. It wasn't temporary — it was structural. The month-on-month variability was coming from the fact that I couldn't do delivery and pipeline at the same time." — Operator, 9-person consultancy
What This Looks Like in Practice
- Q2 close mode = pipeline completely pauses
- Outreach stops for 6–8 weeks
- Content cadence drops off during delivery pressure
- July 1 starts with near-empty funnel
- Q3 is slow July, frantic August, catch-up September
- Pattern repeats every single quarter
- Q2 close mode = close work in foreground, pipeline build in background
- Outreach running on schedule while you close deals
- Content goes out twice a week automatically
- July 1 starts with 8–15 warm conversations already in play
- Q3 July = converting pipeline built in May/June
- Each quarter feeds the next instead of starting over
The One Thing to Do This Week
If you're an operator heading into the last five weeks of Q2 and you haven't started the Q3 pipeline build yet, this week is when it has to start. Not next week.
The math is simple: a contact you reach out to today, with a 35–60 day close cycle, converts to a meeting in mid-June and potentially closes in late July. A contact you reach out to in mid-June doesn't convert until September. You've lost two months of Q3 runway.
The outreach batch that starts this week is the Q3 pipeline. Every week you delay is a week of Q3 revenue you won't see until October.
Want to see how Sandbox runs the Q2 close + Q3 pipeline build simultaneously?
We'll walk through the exact workflow: what gets delegated, what you keep, how the parallel motion actually runs in practice.
Book a 15-minute walkthrough →
Or email directly: rob@sandboxgtm.com