Thinking Like a Business Owner

Understanding the Capitalist Mindset

In Managed IT, the “Capitalist Mindset” is simple: spend your time on decisions that move revenue and reduce risk, and let your team handle the work that keeps client systems running. A veteran way to do that is the 80% Rule.

The 80% Rule means:
- If someone on your team can perform a task to about 80% of your personal standard, you don’t need to own it.
- You set clear expectations, give them the tools, and let them deliver—then you review outcomes.

This is how you scale an IT services business. If you’re the person approving every ticket, reviewing every onboarding checklist, and double-checking every invoice detail, your capacity becomes the limit. The business can’t grow because you’re always busy.

#

Why the 80% Rule?

In IT Services, perfectionism looks like redoing tickets you didn’t need to touch, rechecking the same documentation, or insisting every change request goes through you “just in case.” The problem is not quality—it’s speed.

When you demand 100% from yourself and your team, you create:
- Micromanaging (team members wait for you)
- Delays (tickets sit idle)
- Higher stress (people stop moving quickly)
- Slower onboarding (clients feel the business is sluggish)

Managed IT is already complex. A CEO/owner who reviews every command they don’t need to can’t scale. But a leader who trusts trained techs to operate within defined boundaries can grow without chaos.

Example from Managed IT: You personally review every Microsoft 365 security change before it’s applied. Even small things—like adding a security group or enabling MFA for a pilot group—take days because you’re in a meeting. Meanwhile, the rest of the team is blocked. The client sees “proactive support” as “waiting support,” and churn risk rises.

The Importance of Delegation

Delegation in Managed IT isn’t just handing off tickets. It’s handing off ownership of outcomes.

Effective delegation looks like:
- The tech owns the troubleshooting path
- The tech owns the update to the documentation
- The tech owns the client communication within agreed rules
- The supervisor reviews for quality—not for every detail

That creates accountability. Your team doesn’t just “do tasks.” They learn what “good” looks like in your service delivery.

Example from a good delegation model: A senior technician runs your weekly endpoint health review and posts findings in your internal dashboard. You only step in for exceptions: repeated malware detections, persistent patch failures, or clients missing required reporting windows.

The Role of Trust in Leadership

Trust doesn’t mean “no standards.” It means your team has the confidence to act because standards are written, training is done, and the escalation path is clear.

When trust is real:
- Techs don’t hesitate to start
- They document and escalate properly
- Clients get faster responses
- You stop being the “approval bottleneck”

Example from a common MSP reality: A client asks for a minor change—like setting up a new user and granting access to the correct shared drive folders. If every request requires your personal approval, the client experiences delays and you experience constant interruptions. If your team knows the access standard and the documentation rules, that same request can be handled quickly.

Implementing the 80% Rule

1. Identify Tasks to Delegate
- List what only you do today.
- Focus on recurring work: standard onboarding steps, Tier 1 triage, routine patch cycles reporting, access provisioning, and template-based client updates.
- Keep only the work where you’re truly needed: exceptions, major contract issues, escalation decisions, and major financial review.

2. Empower Your Team
- Write the “80% standard” in plain terms.
- Provide the playbooks and access needed to execute.
- Give authority boundaries: when they can act immediately, and when they must escalate.

3. Monitor and Adjust
- Review outcomes weekly: ticket aging, first-response quality, documentation completion, and escalation reasons.
- Give feedback on patterns, not micromanaged details.
- If quality is off, tighten standards and training—not “back to you for everything.”

Example from MSP scaling: You implement a documented onboarding checklist. Your tech team completes onboarding to the checklist and records proof (screenshots, RMM status, backup verification). You only perform a spot-check on the first 3 onboarding cases each month and for any client with special compliance needs.

Conclusion

The Capitalist Mindset in Managed IT is strategic delegation with clear standards. The 80% Rule helps you stop being the bottleneck, build a team that can execute reliably, and grow without sacrificing service quality. The goal isn’t to do less—it’s to do what only an owner should do.