What You Must Own as the Business Owner
When the Pensacola manufacturing company owner retired, the business nearly died because nobody knew where the software licenses were documented.
Last updated: March 20, 2026
The Pensacola manufacturing company owner spent 28 years building his business. When he retired, his son took over and found a mess: software licenses scattered across personal emails, vendor contracts in the owner's desk drawer, passwords on sticky notes, and $40,000 in annual software subscriptions nobody could account for.
Three months of unraveling. $12,000 in penalties for lapsed licenses. A software vendor who held the only copy of custom configurations and wanted $8,000 to release them.
The technical work—the actual IT management—wasn't the owner's job. But ownership of the technology strategy, the vendor relationships, and the documentation? That was his job. And he never did it.
Here's what you, as the business owner, must own. Not do—but own.
What You Must Own (Even If You Delegate)
1. The Vendor Relationships You need to know:
- Who provides your internet, email, software, and support
- What you're paying for each
- Who the contact person is for each vendor
- What happens if you need to leave a vendor
You don't need to understand the technical details. You need to know the business relationship.
2. The Budget Technology is a business expense. Someone has to decide how much to spend, on what, and when.
If you delegate the IT budget entirely to an IT person or MSP, you may find yourself paying for things you don't need, missing things you do, and having no visibility into what's happening.
3. The Risk Decisions Should we have a second internet connection? Do we need off-site backup? Are we spending enough on security?
These aren't technical questions. They're business risk questions. Your IT person advises. You decide.
4. The Access to Critical Information Who has the passwords? Where is the documentation? If you were hospitalized tomorrow, could someone run your business?
This doesn't mean you need to know every password. But you need to know where they're stored and have access to them.
5. The Approval on Major Changes Moving to a new software platform, changing vendors, hiring an IT consultant—these are business decisions. Your IT person makes recommendations. You approve.
What You Can Delegate
Day-to-day technical decisions. Your IT person decides whether to patch a system now or after hours. That's their job.
Technical implementation. They set up the network, install the software, configure the backup. That's their job.
Troubleshooting. When something breaks, your IT person figures out why and fixes it. That's their job.
Vendor management (technical side). They deal with your ISP about an outage. They manage software vendor technical support. That's their job.
What you cannot delegate: The consequences. If technology fails, it's your business that fails. Your customers who leave. Your employees who can't work. That's why you own it.
What This Costs
Your time: 2-4 hours/month minimum for technology oversight. More if your IT situation is complex.
Quarterly business review with IT: $125-$225/hour, 2-4 hours per quarter. Worth it to stay informed.
Documentation system: $5-$10/month for a password manager like LastPass or 1Password Business.
MSP or IT consultant: What you're already paying. Make sure you get regular reporting and quarterly reviews.
What Can Actually Go Wrong
Thinking "I have an IT guy" means "it's handled." Having an IT person doesn't mean you're protected. You need to ask questions, review reports, and understand what you're paying for.
Not knowing what you own. Software licenses, hardware, cloud subscriptions. If you can't list them in 10 minutes, you don't have visibility.
No documented succession. What happens to your technology access if you die? If you're incapacitated? This is morbid but necessary.
Approving changes you don't understand. "We need to migrate to a new platform." Why? What does it cost? What happens if we don't? What are the risks? You need enough information to make a business decision.
Letting vendors talk to your IT person without you. Ever. You should be copied on significant decisions, even if you delegate the technical review.
Vendor Questions (Copy/Paste)
1. Can you provide a monthly report that shows what we spent, what you worked on, and what needs attention?
2. Can you give me a written summary of our current technology environment, including all vendors, costs, and key contacts?
3. Do you offer quarterly business reviews where we discuss strategy, budget, and roadmap?
4. What happens to our documentation and configurations if we end our relationship?
5. Can you train me on what I need to know to make good decisions, without drowning me in technical details?
Minimum Viable Implementation (Do This Today)
-
Make a list of every technology vendor you pay. Internet, email, software subscriptions, IT support. Pull it from your bank statement.
-
Find out where your passwords are stored. If you don't know, this is today's emergency.
-
Ask your IT person for a 30-minute briefing. What do we have? What works? What needs attention? What's coming up?
-
Read one report from your IT person this month. If you're not getting reports, ask for them.
-
Set a recurring 30-minute calendar slot every month for "Technology Oversight." Review what's happening, approve what's needed, ask questions.
When to Hire Help
Hire now if:
- You can't list your top 5 technology vendors in the next 5 minutes
- You don't have a relationship with anyone who manages your IT
- You've had technology problems that cost you money and you didn't see them coming
- You're making significant technology decisions without enough information
You have this handled if:
- You know your vendors, costs, and key contacts
- You get regular reporting from your IT person
- You understand the risks and have made conscious decisions about them
- You have documentation that someone else could use to run your technology
Related Reading
7 min · Intro
Who Owns the Code, Data, and Accounts?
A Gulfport engineering firm paid $200,000 for software they thought they owned. They were wrong. Don't make the same mistake.
5 min · Intro
Hardware Basics: What Your Computer Actually Needs
A Pensacola print shop owner lost $8,000 in revenue because his 6-year-old computer couldn't handle print queue management during a busy tourist season.
6 min · Intro
How to Build a Risk Register That You'll Actually Use
A Destin real estate office lost 3 days of deals when their email went down—because nobody had written down who to call.
5 min · Intro
How to Spot Systems About to Break Before They Do
A Mobile seafood wholesaler found out their server was dying the hard way—at 5 AM on a Saturday when the entire order system crashed.
5 min · Intro
Single Points of Failure: The One Thing That Can Shut You Down
One dead router. Four hours of downtime. $12,000 in lost revenue. This is the story of why single points of failure matter.