Building a Tier 1, 2, 3 Ladder Your Techs Can Climb

Published by
Throne of Profit Editorial

Reviewed by
William Hassell
Founder & Chief Editor, Throne of Profit

Most MSPs don't have a technician ladder — they have a pile of tickets and a few people who happen to be better at solving them. New hires get thrown at whatever comes in. Your best engineer, the one who should be handling the hard problems and the project work, spends half the day resetting passwords because that's who the client called. And when a sharp junior tech asks where this job goes in two years, nobody has a real answer, so they leave. A tier structure isn't org-chart decoration; it's the mechanism that routes work to the right skill level, protects your senior time, and gives people a reason to stay and grow.

Without it, every ticket competes for the same attention, seniority gets consumed by trivial work, and career growth is invisible. With it, the routine flows to Tier 1, the complex escalates cleanly, and each tier is a rung a tech can actually see themselves climbing.

   HOW WORK SHOULD FLOW

   ticket in
      │
      ▼
   Tier 1  ── resolve routine ─────────────► closed
      │  (can't resolve in defined window)
      ▼
   Tier 2  ── resolve complex ─────────────► closed
      │  (architecture / root cause)
      ▼
   Tier 3  ── hard problems + projects ────► closed

Owner symptoms

• Your most senior tech is buried in password resets and printer tickets.

• Escalation means "whoever's free" or "interrupt the smartest person in the room."

• Good junior techs leave within a year or two because there's nowhere to go.

Why this happens

Most MSPs grow by hiring generalists and letting the work sort itself out. That works at five clients and breaks at fifty. Nobody defined what belongs at each level, so everything routes by reputation — clients call the tech they like, and tickets escalate to whoever seems smartest rather than through a defined path. There was never a moment where the owner sat down and said "this is Tier 1 work, this is Tier 2, and here's how a person moves between them." So the structure that would protect senior time and create a career path simply doesn't exist, and the same few people absorb everything.

Common mistakes

• Tiers by title only. Calling someone "Tier 2" without defining what work is theirs — so routing doesn't actually change.

• No escalation trigger. Tickets bounce up when a tech feels stuck, not at a defined point, so senior staff get interrupted constantly.

• Senior techs still take Tier 1 calls. The most expensive people keep doing the cheapest work because clients call them directly.

• No path between tiers. A tech can't see what skills move them up, so "advancement" is a mystery and they leave to find it elsewhere.

• Escalating the ticket, not the knowledge. Work moves up and the junior tech never learns why, so they escalate the same thing forever.

Business consequences

When tiers don't exist, you pay senior wages for junior work and lose junior talent before it becomes senior. Your best people are your bottleneck and your flight risk at the same time — buried in routine tickets, with no one coming up behind them. Every departure resets the clock and drains institutional knowledge. The owner who builds a real ladder gets the opposite: routine work handled cheaply and fast, senior time reserved for the problems and projects that actually need it, and a team where people can see two years ahead and choose to stay. That structure is what lets the business add clients without adding chaos.

How experienced operators think about it

They treat tiers as a routing system first and a career ladder second — and understand those are the same thing. The question isn't "who's smart enough to handle this," it's "what's the lowest tier that can resolve this well." Work should live at the cheapest level that does it right, and only rise when it genuinely needs to. That protects the expensive people and forces the definition of what each tier owns. They also see the ladder as retention: a tech who knows exactly what skills move them from Tier 1 to Tier 2 has a reason to grow inside your shop instead of leaving to get a title somewhere else. Escalation, in their view, is a teaching moment — the junior watches the resolution and climbs a little.

Practical actions

1. Define each tier by the work it owns, not by title — a plain list of what a Tier 1, 2, and 3 tech is expected to resolve and what they hand up.

2. Set a clear escalation trigger — a time box or problem type, so tickets rise at a defined point instead of when someone feels stuck.

3. Protect senior time deliberately. Route inbound so Tier 1 catches routine work first; stop clients from dialing your best engineer directly.

4. Publish the path between tiers. Name the specific skills and certifications that move a person up, so advancement is visible and earnable.

5. Make escalation teach. When work moves up, the junior tech sees the resolution, so the knowledge climbs with the ticket.

6. Review routing monthly. Watch what's actually escalating; if Tier 1 is bouncing things it should own, that's a training gap, not a tier problem.

Questions every owner should ask

• If I look at my senior tech's day, how much of it is work a Tier 1 could have handled?

• Does a ticket escalate at a defined trigger, or whenever someone gets stuck?

• Could a junior tech tell me exactly what it takes to reach the next tier?

Frequently asked questions

How many techs do I need before tiers make sense?
Earlier than most owners think. Even with three or four people, you can define what work is Tier 1 versus escalated — the point isn't headcount, it's protecting your scarce senior time and giving people a direction to grow. In a small shop one person may wear two tier hats, but the work should still be sorted by level so your most capable tech isn't the default answer to everything. Formalize the definitions first; add bodies to each tier as volume grows.

Won't a strict tier structure make us slower, with tickets bouncing between levels?
Only if you tier by title without defining the work or the escalation trigger. Done right, it's faster: routine tickets resolve at Tier 1 without ever interrupting a senior tech, and complex ones escalate on a clear signal instead of lingering while a junior struggles. Bouncing happens when the boundaries are fuzzy — so the fix is sharper definitions and a defined trigger, not fewer tiers. The goal is work landing at the right level the first time.

Related articles

• Running a Profitable Managed IT Services Business — the pillar.

• Covering After-Hours IT Emergencies Without Burning Out Your Team — protecting the same senior people off-hours.

• Getting the Owner Out of Answering Every Support Ticket — the owner version of the routing problem.

• Why Jobs Take Longer Than You Quoted — the general estimate-versus-reality gap.

• Where Time Leaks on a Typical Job — where senior time quietly drains.

Every business has more decisions than time

Whether you need help solving one problem, evaluating a major opportunity, or making a company-changing decision, Throne of Profit gives you consulting capacity on demand.

Purchase only the consulting capacity you need and use it across Weekly Focus, Strategic Focus, Financial Focus, and ThinkTank engagements.

Explore Throne of Profit