An IT services firm juggles three businesses at once. There is the ticket business, reactive support, things that broke and need fixing today. There is the project business, planned work with a scope, timeline, and deliverable. There is the retainer business, recurring revenue from clients who expect you to just keep things running.
Each business has a different margin profile. Each has a different operational rhythm. Most firms run all three with one workflow and wonder why margins keep compressing.
Tickets Are the Low-Margin Engine
Ticket work pays the bills but rarely builds the business. A billable hour of ticket work is a billable hour of reactive time. No leverage. No recurring value beyond the hour itself.
Which is why ticket operations have to be ruthless on efficiency.
A clean ticket workflow covers: - Single intake channel, portal, email, or phone, all feeding one queue - Auto-triage by priority, P1 outages, P2 degradations, P3 normal, P4 requests - SLA clock that starts the moment a ticket is created, not when a human sees it - First-touch target, 15 minutes for P1, 1 hour for P2, 4 hours for P3 - Assignment by skill and availability, not by whoever picks up first - Resolution notes that feed a knowledge base, so the same issue resolves faster next time
The firms that let tickets sit in email inboxes are the firms whose techs spend 30 minutes figuring out context before they start solving. Multiply that across 100 tickets a day and you are paying for a full-time employee who does nothing but context-switch.
Projects Need a Real Gate
Project work is where IT firms either make money or lose shirts. Good projects have a clear scope, a realistic timeline, and a change order process. Bad projects are open-ended, and the firm eats every variance.
The gate between "proposed" and "in flight" matters more than anything downstream.
Before a project kicks off: - Scope document signed, not just emailed - Assumptions listed explicitly, what is in, what is not - Resources assigned with capacity confirmed, not just planned - Change order process agreed in writing, including pricing - Kickoff meeting scheduled with all stakeholders - Acceptance criteria defined for every deliverable
Skip any of these and the project will hemorrhage time. Usually the one that gets skipped is the change order process. Which means every scope change becomes a negotiation, and half the negotiations end with the firm eating the work.
The Retainer Trap
Managed services retainers are the dream revenue line. Predictable, recurring, high-margin. In practice they are the easiest way to lose money in IT services.
Here is how the trap works. You sign a client on a retainer for a fixed monthly fee for unlimited support within a defined scope. First month, they use 10 hours. Second month, 15 hours. By month 6, they are using 40 hours a month and you are working at a loss.
The fix is usage transparency from day one. - Every retainer has a stated hour range - Every ticket logs time against the retainer - Monthly reports show usage vs. range - When usage exceeds range for 2 consecutive months, a pricing conversation happens - Clients see the data, not a surprise invoice
The Three Workflows Need Different Rhythms
Ticket work runs on minutes and hours. Project work runs on days and weeks. Retainer relationship management runs on months and quarters.
Build three separate rhythms: - Daily standup for ticket queue, 15 minutes, focused on P1 and P2 status - Weekly project review, 60 minutes, focused on active projects and blockers - Monthly retainer review, per client, 30 minutes, focused on usage, satisfaction, upsell
Billing Has to Match the Work
Build billing into the workflow, not onto it: - Every ticket has a billing category, retainer, project, T&M, warranty - Time logs require a category, cannot be saved without one - Weekly time reports flag anything unbilled or miscategorized - Monthly billing runs on a fixed date - Unbilled work over 30 days old triggers a review
Firms that tighten billing hygiene typically recover 5 to 15 points of margin that was already earned but never collected.
Knowledge Compounds or It Evaporates
Every ticket resolution contains knowledge. A knowledge base is not a nice-to-have. It is a firm asset.
Build the habit: - Every ticket over 30 minutes requires a resolution note - Every recurring issue gets a documented runbook - Every client has a documented environment map - Every new tech goes through the knowledge base in their first 30 days
That is what separates a $2M IT shop from a $20M one. Same talent. Cleaner ops.