The True Cost of DIY IT: What Tulsa Business Owners Don’t Factor Into Their Spreadsheets

Somewhere in your budget there is a technology line, and if your business handles IT the do-it-yourself way, it is a comfortable number: software subscriptions, a laptop now and then, and almost nothing for support. No contract, no monthly fee — when something breaks, you fix it, or your office manager does, or the one person who is good with computers puts down their real job and sorts it out. The zero on that spreadsheet is real. The cost is not zero — it is just posted to accounts the spreadsheet does not have.

Who this is for

Owners, presidents, and office managers of Tulsa-area businesses — roughly five to fifty people — where technology is handled in-house, on the side, by someone whose actual job is something else. If that someone is you, read the first line item twice. If you employ a real IT person who is stretched thin, the handoff section covers you.

What counts as DIY IT?

DIY IT is technology handled as a side duty: the owner who sets up every laptop, the office manager who administers Microsoft 365 between payroll runs, the estimator who became “the computer person” because they were willing and capable. These people are usually smart, conscientious, and good at the parts they touch. The problem is not the person; it is structural. IT done on the side gets side-of-the-desk attention, and its most expensive failures stay invisible until the day they are not.

What is the real cost of DIY IT?

Six line items, none of which appear on the spreadsheet.

1. The hourly value of the person actually doing the work

The most expensive IT labor in Tulsa is not a senior engineer. It is an owner’s selling or leading hour spent on a printer. When you handle technology yourself, the labor is billed at whatever your time is worth to the business — the deal not chased, the estimate that went out late. The office-manager version is subtler: every hour spent resetting passwords is an hour their real job absorbs as overtime, backlog, or things quietly not done. There is no invoice because the invoice is paid in the most valuable currency you have.

2. Downtime that lasts longer than it should

Everything breaks occasionally, managed or not. The difference is how long it stays broken. A professional has seen your exact failure many times and starts from a short list of likely causes; a capable amateur starts from a search box. That gap — diagnosis — is where DIY downtime stretches from an hour into an afternoon. And with no monitoring, problems announce themselves at the worst moment: the server that had been logging warnings for weeks fails on invoicing morning.

3. Security debt

This is the one that worries me most: it compounds silently. DIY IT almost never includes patching discipline, monitoring, or a real offboarding process — not because the person is careless, but because those are programs, not tasks, and programs need owned hours nobody has. Updates happen when someone notices. Nobody watches for the sign-in from a country you have never done business with. A former employee’s account stays live because closing it was on a mental list, not a checklist. Then the cyber-insurance application asks in writing — multi-factor authentication everywhere? endpoint detection and response? tested backups? — and there is no honest yes on the page. Every quarter of DIY adds to this debt, and it is repaid at the worst possible exchange rate.

4. The single point of failure you hired

Whatever your DIY person knows — the passwords, the vendor logins, the reason the firewall is set up that odd way — lives in one head. When they are on vacation, your IT department is closed. When they resign, it walks out on two weeks’ notice, and the documentation they always meant to write does not exist. It costs nothing right up until it costs a scramble: locked-out accounts, mystery equipment, a new provider reverse-engineering your own network back to you.

5. Decisions nobody owns

DIY IT can keep the lights on. It cannot own a roadmap. An aging server past warranty, an operating system with an end-of-life date, licensing sprawled across three vendors because each purchase solved that day’s problem — each is a decision, and deferring it is also a decision, with interest. Nobody has hours for planning, so the business drifts into its technology future instead of choosing it, and the bill arrives later as an emergency migration on somebody else’s deadline.

6. The opportunity cost

Add up the hours from line item one and ask what they would have produced pointed at the business. Not what the time costs — what it would have earned. An owner’s week has only a few hours that actually move revenue: selling, leading, pricing, hiring. Spending them on technology substitutes your highest-value work with work you can buy. For most owners this is the largest number on the list — and the spreadsheet will never show it.

When DIY IT genuinely works

Honesty cuts both ways. If you are a handful of people with a simple stack — laptops, Microsoft 365, no server, no compliance obligations, no client data a breach would make existential — and an afternoon of downtime is an annoyance rather than a crisis, DIY can be the right call. Plenty of very small Tulsa businesses run this way sensibly. Even then, do three things: turn on multi-factor authentication everywhere, put files somewhere backed up and test a restore once, and keep a written list of every account and who holds the keys. Those three cost almost nothing and make an eventual handoff cheap.

The crossover signs: how to know it is over

The move from “DIY is fine” to “DIY is costing us” is gradual, so it gets missed. The markers we see most often:

• Technology interrupts work every week — not a bad month, the normal rhythm.
• The owner does IT after hours. If Sunday evening is update night, you are paying weekend rates for the cheapest-looking line in the budget.
• The insurance application needs creative reading. The multi-factor, backup, and monitoring questions cannot be answered truthfully.
• Your DIY person has asked to stop — or started hinting. They usually see the crossover before you do.
• Growth or compliance arrived. New hires, a client security questionnaire, an industry rule that assumes somebody owns IT.
• You had a near miss. The almost-clicked phishing email, the backup that turned out not to exist.

Two or more of these, and the crossover is already behind you.

How to hand it off without losing what they know

The common objection: “Our office manager knows everything about our systems — if we bring in an outside company, all of that walks away.” Done right, the opposite happens. The DIY person stops being the technician and becomes the internal owner of IT: holding the provider accountable, translating between the business and the technical plan, carrying the history behind every odd decision, and sitting in planning reviews as the informed customer. Their knowledge stops being a single point of failure the day it is documented into a shared runbook — the first thing a competent onboarding does — and their hours go back to the job you hired them for. Ask any provider what day-to-day support looks like after the handoff.

If your DIY is further along — a genuine IT person on payroll, stretched thin — the handoff need not be all-or-nothing. A co-managed arrangement keeps the day-to-day work and institutional knowledge inside while adding monitoring, security tooling, escalation depth, and vacation cover. Your person gains a bench instead of losing a job.

What replacing DIY actually costs

Briefly, because we have published the detail: in the Tulsa market in 2026, fully managed IT — help desk, monitoring, patching, security, planning — runs about $100 to $175 per person per month. The tiers, pricing models, and what moves a quote are in our managed IT cost guide; the IT budgeting guide covers the rest of the technology budget. The comparison to make is not that number against zero. It is that number against the six line items above, priced honestly at your hourly value and your tolerance for a bad week.

NSN Management has been Tulsa-owned since 2012, and I have been running Tulsa IT companies since 1999 — long enough to have seen the DIY spreadsheet from both chairs: as an owner making payroll, and as the provider who gets the call when the zero stops being free. If you want real numbers on your own DIY line — your hours, your risk, your deferred decisions — book a Discovery Call. We will price it plainly, and if DIY is still genuinely working for you, we will tell you that too.