Working ON Your Business & Setting Your Vision

Introduction

You have made it through the early stage of your managed IT company. You have paying clients, recurring contracts, and a team that can deliver technical work. But if every major ticket, client complaint, renewal decision, and Microsoft 365 change still comes through you, you do not yet own a business. You own a demanding technical job.

To grow, you must move from working IN the business to working ON the business. Working IN means solving escalated tickets, building firewall rules, joining every sales call, and checking every engineer's work. Working ON means designing service standards, improving recurring revenue, hiring leaders, and deciding which markets and services the company will pursue. This shift requires a clear vision and operating values that help your team make good decisions without waiting for you.

The Shift: From Operator to Owner

Working IN the business means you are still the lead technician or emergency dispatcher. You may be the only person who knows how a key client's network is configured, how to recover a failed server, or how to calm an unhappy office manager. This makes you valuable in the short term but makes the company fragile.

Working ON the business means building the machine that delivers reliable IT service without your constant involvement. You create documented onboarding steps, ticket escalation rules, cybersecurity standards, account review processes, and service checklists. You train a service manager or senior engineer to enforce those standards. You also remove yourself from routine approvals by setting clear limits, such as which purchases engineers can make, which incidents require a manager, and when a client issue must reach you.

You are not abandoning technical quality. You are turning your technical judgment into systems that other capable people can follow. The goal is not to make every decision yourself. The goal is to make the right decision repeatable.

Defining Your Vision and Core Values

When an owner steps away from daily tickets, a leadership gap can appear. Engineers may handle the same incident in different ways. Account managers may promise work that is outside the agreement. Salespeople may sell tools the service team cannot support. A clear vision and a small set of operating values prevent this confusion.

Your vision describes where the managed IT company is going. It might be, "We become the most trusted technology partner for professional firms with 25 to 150 employees in our region." This helps the team understand which prospects to pursue, which services to improve, and which clients may not fit.

Core values are practical rules for daily choices. "Secure by default" tells an engineer to require multifactor authentication rather than treating it as an optional upgrade. "Close the loop" tells a service coordinator to update the client after an outage, even when the final fix is not complete. "Own the outcome" tells the team to stay responsible for a problem instead of blaming the internet provider, software vendor, or client employee.

Values should guide hiring, coaching, client selection, and service design. If a candidate avoids documentation, they may not fit a company that values repeatable service. If a profitable prospect refuses basic security controls, the owner must decide whether accepting that account conflicts with the company's standards.

Real-World Example

Consider the owner of a 12-person managed service provider who still reviews every high-priority ticket and personally joins every quarterly business review. The team cannot act until the owner responds, and the owner has no time to improve margins or build a stronger sales pipeline.

The owner shifts to working ON the business by defining a vision focused on secure, predictable IT for growing medical and accounting practices. The company adopts three operating values: secure by default, document before closing, and communicate early. The owner then creates an escalation matrix, a standard quarterly business review agenda, and a checklist for privileged account changes. A service manager becomes responsible for enforcing the process.

Within a few months, engineers can resolve more incidents without owner approval, client updates become more consistent, and the owner can focus on partner relationships, recurring revenue, and hiring. The company is not less technical. It is less dependent on one person.