By the third week of September the school routine has settled. Backpacks by the door, lunches made the night before, everybody out of the house on time.
The families that used the window in August are cruising. The ones that did not are still improvising at 7:40 every morning.
Same season, two very different mornings. The difference was a short list run at the right moment.
Your business has that window right now. Q4 starts in a few weeks, and September is the last stretch where you get to prepare instead of react.
Check whether your team agrees on the Q4 priority
Ask three people what the company's top priority is between now and December 31. If you get three answers, that is much better to learn in September than in November.
Most owners assume an alignment they have never actually verified.
Write down what has to happen before the year closes. Which revenue targets, which client commitments, which projects cannot slip. Then say it to the whole team, because assuming they already know is how it goes sideways.
What should a business review before Q4 starts?
Four things. Whether the team agrees on the top priority, what technology costs land in the next ninety days, whether responsibilities quietly shifted over the summer, and whether the recovery plan still matches how the company actually runs. None of it takes long in September. All of it gets harder in November.
Find the technology costs before they find you
Technology expenses show up at the worst possible time, usually because nobody went looking for them.
Pull the list now. Which warranties, licenses, and renewals land in Q4. Which machines are slow enough that people have started mentioning it. Which security or compliance items got pushed in the spring and never came back.
Knowing the number in September is a budget conversation. Finding out in November is an emergency purchase at whatever price is available that week.
Most business computers are worth replacing somewhere around four to five years, and sooner if the warranty has expired on a machine somebody depends on daily. The trigger is rarely a failure. It is the minutes your team loses waiting, plus the odds that the replacement decision gets made during an outage instead of during a budget cycle.
How far ahead should a business plan technology spending?
A rolling twelve months works for most organizations in the 10 to 250 employee range. You want to know which renewals, warranties, and refresh cycles land in each quarter before that quarter starts. The goal is to make the decision on your own schedule instead of during an outage.
Confirm the team you have is the team you think you have
Summer changes teams quietly. People take leave, someone new starts, a responsibility shifts in a hallway conversation and never gets written down.
By September you can have a team that looks identical on paper and works differently in practice.
Ask directly. Does everyone know what they own right now? Did anything move while someone was out? Is there a task that still belongs, on paper, to a person who stopped doing it in June?
Unclear ownership does not resolve itself once Q4 gets busy. It becomes the expensive kind of surprise.
How do role changes create technology risk?
When responsibilities move without being written down, access usually does not move with them. The person who left the role often keeps their old permissions, and the person who took it over gets access granted in a hurry with more than they need. Both surface later as problems, and both are simple to correct if somebody checks.
Clear the small items you have been living with
https://www.cisa.gov/audiences/small-and-medium-businesses/secure-your-business
Every business has the list that never reaches the top. Old user accounts nobody turned off. Documentation that stopped matching reality two system changes ago. A process everyone agrees is broken and nobody has scheduled time to fix.
These are easy to live with in September and expensive in November.
Pick two. Handle them while you still have the breathing room.
Why do inactive user accounts matter?
An account belonging to a former employee still holds whatever access it had on their last day: email, files, sometimes a vendor portal or a banking system. It is also the account nobody watches, because nobody expects it to be used. Turning them off is one of the shortest security tasks on any list and one of the most commonly skipped.
Ask one preparedness question
September is National Preparedness Month. Most of what gets written for it aims at households and storms, and the business version usually gets skipped.
One question is enough for now. If something disrupted operations tomorrow, would your team know what to do in the first hour?
A confident yes is a good answer. A pause is a better one, because you found it in September rather than during the thing itself.
If the pause is real, there are five questions worth putting in front of your leadership team, and the whole conversation takes fifteen minutes.
Put a real agenda in front of your IT provider
A good IT provider sees more than your open tickets, but only if you hand them something to work with.
Use September for a conversation that is not about a ticket:
- Where the business is headed in Q4 and what technology has to support it
- Risks and gaps that nobody has formally owned
- Hardware, software, and security decisions that should land before year end
- Whether the recovery plan is current, and whether anybody has tested it
The organizations that get the most from an IT partner treat it as a business relationship rather than a support line. This meeting is where that difference stops being a slogan.
What should be on the agenda for a quarterly meeting with an IT provider?
Business direction first, technology second. Cover what the company is trying to do next quarter, what is coming due, which risks have no owner, and whether the recovery plan has been tested recently. If the whole conversation is about open tickets, it was a support call rather than a planning meeting.
The bell already rang
The families with the smoother September handled the important things before the rush, not during it.
Your window is narrower than theirs, and it is open right now.
A complimentary 15 minute Technology Confidence Score call gives you a clear picture of where your systems stand today, along with your score out of 100. Schedule at 10dtech.com/Tech_Confidence_Score. Albany, Corvallis, Eugene, Bend: 541-243-4103. Portland, Salem: 971-915-9103.
Frequently Asked Questions
What should a business review before Q4 starts?
Four things. Whether the team agrees on the top priority, what technology costs land in the next ninety days, whether responsibilities quietly shifted over the summer, and whether the recovery plan still matches how the company actually runs. None of it takes long in September. All of it gets harder in November.
How far ahead should a business plan technology spending?
A rolling twelve months works for most organizations in the 10 to 250 employee range. You want to know which renewals, warranties, and refresh cycles land in each quarter before that quarter starts. The goal is to make the decision on your own schedule instead of during an outage.
How do role changes create technology risk?
When responsibilities move without being written down, access usually does not move with them. The person who left the role often keeps their old permissions, and the person who took it over gets access granted in a hurry with more than they need. Both surface later as problems, and both are simple to correct if somebody checks.
Why do inactive user accounts matter?
An account belonging to a former employee still holds whatever access it had on their last day: email, files, sometimes a vendor portal or a banking system. It is also the account nobody watches, because nobody expects it to be used. Turning them off is one of the shortest security tasks on any list and one of the most commonly skipped.
What should be on the agenda for a quarterly meeting with an IT provider?
Business direction first, technology second. Cover what the company is trying to do next quarter, what is coming due, which risks have no owner, and whether the recovery plan has been tested recently. If the whole conversation is about open tickets, it was a support call rather than a planning meeting.
