Replace your IT company
What your IT company should be doing every month
After the agreement is signed, many owners cannot say what happens besides waiting for something to break. If the answer is “they wait for tickets,” you are not getting managed IT. You are getting a help desk with a retainer.
This is the operational list — the work that should run whether or not anyone in the office filed a request. It is how an environment in Southlake, Grapevine, or a second DFW location stays boring on purpose.
Controllers and office managers can use it as a checklist in a quarterly review. If several items have not happened in 90 days, the relationship has already drifted.
Why this matters
Tickets are what you see. The month is what keeps the next ticket from existing. Patching, access reviews, and backup proof do not show up in a satisfaction survey until they fail in public.
For a 15-to-250-person company, this rhythm is cheaper than hiring a department and more honest than a monitoring logo on a slide.
Why the month goes empty
The provider staffs only the queue
If utilization is measured in tickets closed, nobody is paid to look at last month’s backups or last quarter’s admin list.
You never asked for a report you can read
Leadership should get a short picture: what was reviewed, what failed, what is next. A 40-page export is not a picture.
Security is saved for “later”
Later is the insurance form or the incident. Monthly is how MFA, stale accounts, and email forwarding rules stay current.
Business impact of skipping the month
- Unpatched devices become the easy way in.
- Former employees still open email.
- A backup job that failed three weeks ago is discovered during an actual restore.
- Hardware dies with no replacement plan, so the spend is always an emergency.
- Vendors drift. You discover at outage time that nobody has the ISP account number.
What “every month” should include
Security reviews
Look at user access, admin accounts, alerts that actually fired, device protection, and email security. Small corrections every month beat a panic project after a scare.
Patch management
Workstations, servers, and the firmware people forget. Updates address known holes and the crashes you were going to blame on “the network.” Deferring this is how you buy risk on the cheap.
Backup verification
Confirm jobs succeeded, storage is intact, and recovery is possible. At least periodically run a restore you can describe — file, mailbox, or system — with a date. A green check is not a recovery.
User audits
People join, leave, and change roles. Find former staff who still have access, permissions that accumulated, and accounts nobody owns. This is also how Microsoft 365 license counts stop matching the roster.
Vendor coordination
Someone should still know the internet provider, software vendors, security tools, and phones. Without that, accountability fragments the first time two of them disagree.
Technology planning
What is aging out, what security work is queued, what a new office or a hiring burst will need. If the only plan is the ticket that arrived today, you will always be late on budget.
Documentation updates
The environment changed this month. The record should have changed with it. That is what makes the next issue cheaper and the next technician useful on day one.
Recommended solution
Ask your current provider to show the last 90 days of this list. Not a promise — evidence. If they cannot, you are funding a queue.
323 Technologies treats this list as the job, not an upsell. If you need to change who runs it, Replace your IT company is the handoff into that monthly rhythm — not a new portal with the same empty month behind it.
How 323 Technologies helps
From Southlake we run a repeating cycle: review what you have, protect it, improve what is next, then do it again. On-site when DFW buildings need a person. Remote when they do not.
You should be able to ask “what happened last month?” and get an answer that is not a ticket export. If your current company cannot do that, the gap is the relationship, not your staff’s ability to file requests.
Questions
Does every item happen on a calendar month?
Some checks are monthly, some are triggered by hires and exits, some are a restore on a longer cadence. The point is a rhythm you can name — not “we monitor 24/7” with nothing to show.
Will we see a long report?
You should see a short, readable summary: what was reviewed, what is open, what needs a decision. Length is not quality.
Is this included in managed IT or extra?
If it is extra, you are buying break-fix. This work is the core of a managed relationship. Ask what is in the monthly fee in one page.
We already have Microsoft 365. Does that replace this?
No. Microsoft runs the platform. Someone still has to review licenses, access, and whether backups of email and files exist outside wishful retention settings.
What if we have an internal IT person?
This list still applies. We often sit alongside that person so the month does not depend on one vacation or one hero.
How do we start if nothing on this list is happening?
Inventory and backups first, then the monthly cycle. That is the same order as a provider switch — because in practice it is one.
Next step
If the month is empty, the provider is a queue.
See how 323 Technologies takes over an IT relationship and puts a real monthly rhythm behind it — from Southlake, for DFW businesses.
Or call (817) 477-6111