Phase 04: Phase 2: Plan & Model

Freelance IT Pricing: Hourly, Retainer, or Per-Device, and When to Use Each

3 min readUpdated September 2026

Hourly billing punishes you for getting faster at your job, which is exactly backwards for a skilled technician. The pricing models that actually build a sustainable freelance IT practice reward expertise and predictability instead, and most successful solo providers end up on a managed-retainer or per-device model within their first year even if they started hourly. Getting this wrong in either direction costs you: underpricing burns you out chasing volume, while overpricing without the positioning to justify it simply loses you the deal.

READY TO TAKE ACTION?

Use the free LaunchAdvisor checklist to track every step in this guide.

Open Free Checklist →

Know Your Real Floor Before You Quote Anyone

Add up every fixed monthly cost: RMM and PSA tooling (roughly $2-4 per managed device per month plus a base platform fee), liability and cyber insurance ($800-2,500 per year), software licenses you resell or use for delivery, vehicle costs if you do on-site work, and your own required take-home pay. Divide by your realistic billable hours per month, usually 90-120 for a solo operator once you account for sales, admin, and non-billable travel, not the 160+ hours a full-time job implies. That number, typically landing between $65 and $95 per hour of true cost for a solo generalist and higher for specialized cybersecurity or compliance work, is your floor. Quoting below it means every additional client makes you poorer, not richer.

The Three Models That Actually Work, and Where Each Fits

Hourly, at $75-150 depending on specialization and market, works for one-off projects like a network redesign or a server migration where scope is genuinely hard to predict upfront. Fixed-project pricing works for well-defined work like a 20-user Microsoft 365 migration, where you quote a flat fee based on your estimated hours plus a 15-20% buffer for the unknowns that always appear. Managed retainers, priced per user ($99-250/month) or per device ($30-75/month) for ongoing monitoring, patching, help desk, and a defined response SLA, are what actually builds recurring revenue and business value, because a buyer of your practice later is paying for predictable revenue, not for you personally answering the phone.

Build in Tiers So the Retainer Isn't a Take-It-or-Leave-It Decision

A single flat retainer price forces every prospect into a yes-or-no decision, and you lose the ones who think they need less than what you're offering. Structure three tiers: a basic monitoring-and-patching tier, a mid-tier adding help desk and a 4-hour response SLA, and a premium tier adding a security stack (endpoint detection, phishing training, backup verification) and a monthly strategy call. This also creates a natural upsell path: a client on the basic tier who has a security incident is now a warm conversation for the premium tier, rather than a cold pitch.

Review and Raise Prices on a Schedule, Not by Accident

Without a deliberate review cadence, most freelancers let retainer prices sit flat for years while their costs, skill level, and demand all rise, which quietly erodes real margin even as revenue looks stable. Set an annual review date for every retainer client, and evaluate three things: has your tooling or insurance cost increased, has the client's device or user count grown without a corresponding price adjustment, and has your market rate for new clients moved up since you signed them. A 3-7% annual increase tied to a specific, named improvement (an added security feature, expanded coverage hours) is far easier for a client to accept than a larger, unexplained jump every few years, and it keeps your existing book from quietly becoming less profitable than your newest clients.

A Worked Example: The Same Client, Three Pricing Models

Consider a 12-person office needing ongoing support. Billed hourly at $95, a typical month might run 8-10 hours of tickets plus troubleshooting, landing at $760-950, but with no revenue in a quiet month and a spike in a bad one, so your income swings with their luck. Priced as a per-user retainer at $150/user/month, that same office generates a predictable $1,800/month regardless of ticket volume, smoothing your cash flow and rewarding you for keeping their systems stable enough that tickets stay low. Priced as a flat project fee for a one-time server migration instead, quoting 25 estimated hours at $95 plus a 20% buffer comes to roughly $2,850, paid in a deposit plus completion structure rather than after 25 hours of unbilled risk. The retainer model wins on predictability for ongoing work; project pricing wins on capturing the full value of defined, one-time engagements.

Don't Let One Client's Rate Become Your Anchor

Early clients, especially the first two or three who take a chance on a brand-new freelancer, often get a lower rate as a reasonable trade for being willing to go first. The risk is letting that early rate quietly become your default mental anchor for every client after, even once your track record, tooling, and confidence have all improved. Treat your rate as something that should trend upward with your evidence of reliability, not stay pinned to what felt fair to charge in your first month.

Take this further

Get a personalized AI Advisor

Premium answers from your own workspace, up to 150 questions a day, and lets you start threads in the Founder Forum. $15 a month or $144 a year, with a 7-day free trial.

Want an AI CTO to take this on?

Taj on MeetMyCXO helps with your tech stack, tools and build decisions. Plans start at $49 a month with a 7-day free trial.

FREQUENTLY ASKED QUESTIONS

Should I ever go back to pure hourly billing once I have retainer clients?

Keep hourly available for genuinely one-off, out-of-scope work (a data center relocation, a one-time compliance audit) even after you build a retainer base, but bill it at a premium, often 25-50% above your standard hourly rate, since it's disruptive to a schedule built around predictable retainer work.

How do I raise retainer prices on existing clients without losing them?

Give 60-90 days' written notice, tie the increase to a specific added value (a new security tool, expanded coverage hours) rather than presenting it as a bare price hike, and expect to lose 5-15% of clients on any meaningful increase. That attrition is normal and usually still net-positive on revenue.

What's a realistic minimum retainer size to bother taking on a client?

Most solo providers set a floor around $300-500 per month; anything below that rarely covers the fixed overhead of onboarding, monitoring, and periodic check-ins relative to the time it consumes, even if the per-device math looks fine on paper.