Every August, somebody on the leadership team says the same thing. "Q3's always slow for us." Pipeline reviews get shorter, the forecast softens a little, and everyone nods as the calendar explains it. The conversation moves straight to Q4 planning without anyone checking if that's actually true.
Here's the problem with that. If you ask the room what specifically makes Q3 slow, most leadership teams can't answer beyond a shrug. Nobody points to a client industry that genuinely shuts down for the summer, or a buying cycle tied to a fiscal calendar. They just know it's felt slow before, so it must be slow again. That's a comfortable answer. It's usually the wrong one.
We call this Reactive Rhythm, one of the five revenue leaks inside our Revenue Rewired framework. Growth activity doesn't run on a rhythm; it runs on attention. When leadership eases off for a few weeks, whether that's summer schedules, a big internal project, or fatigue after a strong Q2, outreach slows, follow-up slips, and content goes quiet. Six weeks later, pipeline reflects it. By then it's easy to call the dip seasonal, because seasonal sounds like something that happened to you instead of something you did.
Most slow quarters that get blamed on seasonality are actually a cadence problem. Before you accept "it's just our slow season," check three things: whether outreach, content, and follow-up volume actually dropped in the weeks before the slowdown, whether anyone can name a real external cause tied to your buyers' calendar, and whether growth sped back up the moment leadership got personally involved again. If the answers are yes, no, and yes, you're looking at Reactive Rhythm, not seasonality. The business consequence matters here. Plan Q4 assuming last year's dip was seasonal, and you'll build the same swing into next year instead of fixing the cadence that caused it.
In consumer businesses, seasonality is real and measurable. Retailers slow down in February. Landscapers slow down in January. There's a calendar reason, and it repeats every year regardless of what the team does.
B2B companies in manufacturing, industrial services, professional services, and construction rarely have that kind of hard seasonality. Buying cycles are longer, decisions involve multiple people, and most purchases aren't tied to a season the way a retail purchase is. So when a B2B leadership team says "Q3's always slow," it's worth asking what's actually driving that. Sometimes there's a real answer, like a client vertical that shuts down in July. Most of the time there isn't, and the real explanation is that the team eased off and nobody noticed until the pipeline showed it.
Before Q4 planning gets built around last quarter's numbers, run this test with your leadership team.
If you're answering yes to the first and third questions and no to the second, you don't have a seasonal quarter. You have a cadence that only runs when somebody's watching.
This isn't a motivation problem, and it's not really an accountability problem either. Most B2B companies never built a growth cadence that survives a busy stretch, so leadership attention became the mechanism that triggers activity. When the CEO gets pulled into a big project, or the sales leader takes two weeks off, or Q2 went so well everyone exhaled, the outreach and follow-up that create Q4 pipeline just don't happen at the volume they need to.
The uncomfortable part is that a strong quarter can hide this just as easily as a slow one does. A great Q2 often means less pressure in July, which means less pushing, which means the exact conditions that produce a "slow Q3." The pattern isn't really about the season. It's about what happens the moment nobody's forcing the pace.
The fix isn't telling the team to work harder in August. It's building a cadence that runs on a schedule instead of on leadership's bandwidth. That means naming the specific activities that produced last year's good quarters, not the vague sense that things were busy, and putting those activities on a calendar that doesn't move just because a big project came up.
It also means somebody other than the CEO owns whether the cadence actually ran that week. If the only way outreach happens is because leadership personally checks in, the system doesn't have a cadence yet. It has a person standing in for one.
For most B2B companies outside a handful of genuinely seasonal industries, a slow quarter is more often a cadence gap than true seasonality. Run the three-question test before assuming the calendar explains it. If outreach and follow-up actually slowed down before pipeline did, and there's no real buyer-side cause, you're looking at Reactive Rhythm rather than a repeating seasonal pattern.
Name the specific activities that created your strongest quarters, not just the feeling that things were busy. Put those activities on a schedule that doesn't depend on leadership remembering to push them, and assign ownership to someone whose job is checking whether the cadence ran, not just whether the CEO got involved that week.
Reactive Rhythm is one of five revenue leaks StringCan tracks inside the Revenue Rewired framework. It shows up when growth activity depends on leadership attention instead of a repeatable cadence, so pipeline surges when someone pushes and flattens the moment they stop. The fix is a cadence that runs independent of any one person's calendar.
Only if you've confirmed it was actually seasonal. If last year's dip was a cadence problem rather than a calendar problem, planning around a repeat just locks the same swing into this year's forecast. Test the cause first, then decide whether Q4 needs more activity or a different cadence.
If the pattern feels familiar, a Growth System Session can help map where revenue is leaking, what's causing it, and what should be fixed before adding more activity.