I've had this exact conversation probably eighty times by now. It's Q3, the client is staring down peak season, and the question always shows up in some version of: "Do I have time to fix my tech stack before Q4 gets here?"
Here's the answer nobody wants, and the one I give anyway. It depends.
Stay with me, because "it depends" is not me dodging the question. It's me telling you the honest thing before I tell you the useful thing.
What You’re Really Asking
Before I look at a calendar, I look at the business. Specifically, what it's actually trying to accomplish, because "fix some technology gaps" and "implement a whole new system" are two completely different conversations wearing the same outfit.
Get that part wrong and everything downstream is wrong with it.
Scenario 1: Green Light for Realistic Changes
If a client comes to me wanting to fix problems that have been quietly piling up for months (sometimes years, let's be honest), before Q4 lands, here's what I'm actually checking.
- System stability. Is the stack holding, or is it already on fire? A business in active crisis is a different problem than one that's stable but has simply outgrown its infrastructure. Crisis creates urgency, sure, but it also makes a clean migration harder, not easier. Panic is not a project plan.
- Team bandwidth. Who owns this internally, and what else are they juggling between now and October? I've never once seen an implementation without a named internal owner go well. Doesn't matter how good the partner is. Somebody has to actually drive the thing, and "we'll figure it out as a team" is code for nobody will.
- Integration complexity and data quality. How complex is the integration picture, and how clean is the data sitting on either side of it? A simple stack with clean records is a Tuesday. A tangled stack with years of unresolved discrepancies is a different kind of project entirely, and it will take exactly as long as your worst data problem, not your best intention.
But there's a fourth signal, and it's the one that actually decides everything: are you honest about scope? Will you take a targeted win now and build from there, or are you dead set on getting everything all at once before the holidays hit? I can tell you right now, every business that stalls out in October went in planning for full scope on a compressed timeline. Every time. Without exception.
If your scope is sane, your systems are stable, someone really owns this, and your data isn't a disaster, we're in business. But "in business" doesn't mean rebuilding everything. It looks more like:
- Getting inventory out of spreadsheets
- Putting basic purchase order discipline in place
- Stabilizing the one or two integrations currently causing the most damage
- Cleaning up the data gaps that are actually dangerous, not just annoying
- Killing off the riskiest manual dependency you're carrying
That's it. That's the whole ambition. And it's enough to make Q4 meaningfully less chaotic.
Scenario 2: You’ve Got a Red Light
Sometimes the signals just don't line up, and the honest move isn't to force an implementation and hope for the best. I've watched businesses try that. It does not end with anyone thanking me.
The smarter play is a deliberate holding pattern. Figure out which parts of your current stack carry the most risk and put real manual supports around them for the quarter. Not a fix. A conscious decision to take some risk off the table while you get through peak.
That means actually planning for manual workarounds instead of hoping you won't need them. Name who owns each one. Stop pretending a system change is coming that isn't coming this quarter.
And document the mess now, before Q4 chaos rewrites everyone's memory of what actually happened. Use this window to scope exactly what needs to change while you can still see it clearly.
The bottom line here is simple. Decide now instead of drifting. The businesses that get into real trouble aren't usually the ones who chose to wait. They're the ones who never actually decided anything, kept the conversation open without committing, and wandered into October half-ready. Then volume showed up and told them what that cost.
Choosing to hold steady through Q4 and implement in January isn't losing. It's a decision, made on purpose, with your eyes open. That's the whole game.
Time, Scope, and Q4
Q4 is coming whether you've made a decision or not. Depending on where you land, you're either clear to make some real changes now, or you're better off stabilizing what you've got and holding the line. Either path, done deliberately, sets you up better for next year than drifting ever will.
So if you're the one asking whether there's still time, my honest advice is to spend twenty minutes figuring out which scenario you're actually in before you spend another minute guessing. As a Cin7 partner, that's the conversation Four13 has all the time, and it's usually a lot shorter than people expect.
