My position is simple. An IT services firm that only sells projects is a job with overhead, not a company. You land the work, deliver it, invoice it, and start prospecting again. The income stops the day you stop selling. An IT services owner recurring revenue plan fixes that by changing what you sell, how you price it, and how you deliver it. Most owners who try this copy a software company’s subscription model. That is the wrong template. You sell people’s time and judgment, not a product with near-zero delivery cost.
This article lays out the plan we recommend. It follows the order we install in every business through our S.C.O.R.E. operating system: sales and marketing first, then controlled delivery, then operational data. I will say where I think most advice is wrong, and I will name real client work from our records where it applies. Client results here are reported by the client or our team. They are not audited.
Project-only IT work fails for three reasons
First, you cannot forecast. You have no idea what March looks like in January. Hiring becomes a guess. Marketing budget becomes whatever is left over. Planning becomes a wish.
Second, delivery does not scale. Every new client needs discovery, scoping, a proposal, and custom setup. Your best technicians spend half their week in pre-sale work instead of billable work.
Third, retention has no structure. When the project ends, the relationship goes quiet. A holiday card is not a reason to keep paying you. In my view, the churn in project-only firms is a business model problem, not a service quality problem.
The usual answer is to sell more projects. That treats the symptom. A recurring revenue plan treats the cause.
What most advice gets wrong about recurring revenue
The common advice is to productize your services into fixed packages. Bronze, Silver, Gold. That sounds clean. It ignores how IT work behaves. A dental office with five workstations and cloud email is not a law firm with 40 users, an on-premises file server, and compliance rules. Force both into one $500 plan and you either over-deliver and lose margin or under-deliver and lose the client.
The second mistake is thinking recurring revenue means you stop doing projects. Wrong. Recurring contracts create the base. Projects become expansion revenue sold to clients whose environment you already know. You are not replacing projects. You are changing who you sell them to and when.
The third mistake is borrowing pricing from software companies. A software company sells a product with almost no cost per extra user. You sell expertise delivered by humans with limited hours. You cannot put a monthly fee on what you used to bill hourly and call it done. I will be blunt: the firms we assess that do this are usually working more hours for less money than before.
One more thing most advice skips. Our position is that revenue is not the whole scoreboard. Growth has to be judged next to margin, cash, capacity, and what the owner takes home. We wrote about this in why growth can destroy profitability, and it applies double to a managed services shift, because every contract you sign adds fixed delivery cost.
The four revenue streams a managed IT plan should carry
We recommend building the plan around four income types. Each one behaves differently on predictability, margin, sales cycle, and churn. The table below is our view of how they compare. It is a planning aid, not industry data.
| Revenue stream | What it is | Predictability | Margin | Churn risk |
|---|---|---|---|---|
| Managed services | Monthly contracts for monitoring, patching, helpdesk, and security, priced per user or per device | High | Depends on scope discipline | Low when scope is clear |
| Co-managed IT | A monthly retainer to back up a client’s internal IT person with strategy, vendor management, and escalation | High | High | Medium |
| Project work | Migrations, upgrades, and implementations sold to existing managed clients | Low | High, because you already know the environment | Not applicable |
| Technology resale | Licenses, cloud hosting, backup, and security software billed monthly at a markup | High | Thin | Low |
Managed services is the foundation. Co-managed IT fits companies that have one IT person and need a bench behind them. Project work becomes higher margin once you already know the network. Resale is thin margin but it compounds as the client base grows. Our recommendation is a target where most of your revenue comes from the first three within about two years. That is a goal we set with clients, not a benchmark.
Price from your cost, not from your competitor
Pricing is where most owners leave money on the table. They anchor to what the shop down the street charges or to what they think the market will bear. Neither number tells you what you need to earn.
Start with your fully loaded cost per technician per month: salary, taxes, benefits, training, software seats, insurance, and a share of overhead. Divide by the hours that technician can actually bill. That is your cost per hour. Add the margin you need. Now you have a floor.
Here is a worked example with made-up numbers so the math is clear. Say your fully loaded technician cost is $85 per hour and you want a 40% margin. You need about $141 per hour in realized revenue. If a typical user on your main plan consumes 1.2 support hours a month, that user has to bring in about $170 a month before you add tooling, monitoring, and admin time. If your price per user is well below that, the contract loses money on day one, and no amount of volume fixes it.
This is not theory for us. At 518 Floor Care, a small owner-operated business, our coach John Brunty listened first and then brought in Kristy Faulk to review the books. The owner was busy but the business did not make money. The client’s own words:
“He even brought in a colleague Kristy to look at my quickbooks and we determined that my pricing model was not right and that I was not making the profit percentages I needed to run my business. With the help of a new spreadsheet and John’s guidance I was able to turn things around and now I am profitable and free of debt.”
518 Floor Care, client testimonial
That is a floor care company, not an IT firm, and it is one client’s report. The margin figures are not something we publish. But the pattern is the one I see most often in service businesses: the owner is working hard and the price is wrong. One spreadsheet and the discipline to use it on every quote changed that business. Build yours before you sign another contract. Our post on pricing strategy for consulting services walks through the same logic for advisory work.
Two more pricing rules. Price by risk, not just seat count. A 20-person law firm that bills by the hour loses more in an outage than a 40-person wholesaler, and its price should reflect that. And bundle. Separate line items for monitoring, patching, helpdesk, and backup invite price shopping. One plan with everything inside it communicates value and lets you shift margin between components as your costs move.
Write the contract so scope protects margin
The contract is where owners give away the farm. Three parts matter most.
Scope
Define what is in and what is out. “Unlimited support” wins the sales call and destroys the margin. We recommend a plain list. Included: remote support for covered devices during business hours, monthly patching and monitoring, security event response by defined severity, and a quarterly business review. Not included and quoted separately: onsite visits beyond a set number, after-hours emergency work at a higher rate, end-user training, and hardware procurement. Ambiguity creates scope creep. Scope creep kills profit.
Term
Here I want to be honest about our own model. Accountability Now runs its core coaching month to month. Our position is that we should earn the relationship every month, and a long commitment is no substitute for useful progress. So why do I recommend a 12-month initial term for managed IT? Because your onboarding is expensive. You document the network, deploy agents, migrate the client onto your stack, and test backups. If the client leaves in month three, you lose money. The term protects that investment. After year one, move to a 90-day notice. And hold yourself to our standard anyway: the service should be good enough that the client would stay without the term.
Response times and rate increases
Tie service levels to plan tiers. We recommend four severity levels, from business-down events with a one-hour response target down to routine requests handled in a weekly cycle. Give the lowest plan the lowest two levels only. That creates a natural reason to move up. Then write in an annual rate increase of a few percent tied to your published rate card, with 60 to 90 days of notice. Your labor, licenses, and insurance go up every year. If your contract does not, your margin shrinks every year.
Track four numbers and let them change decisions
The Operational Data stage of S.C.O.R.E. is short on purpose. Manage the business with a few numbers that change decisions, not a dashboard nobody reads. For a managed services firm I recommend four.
Monthly recurring revenue. Stripe’s guide to MRR and ARR defines MRR as the predictable revenue you generate each month from clients who pay on a recurring basis, and breaks it into new, expansion, churn, and contraction. Track all four parts. A flat MRR number hides a firm that is adding clients and losing them at the same pace.
Net revenue retention. Take last year’s client cohort. What share of that revenue do you still have today after churn, downgrades, and upgrades? Above 100% means your existing clients are growing faster than they are leaving. Below it means you are filling a leaking bucket.
Lifetime value against acquisition cost. Total sales and marketing spend divided by new clients gives you cost to acquire. Average monthly revenue per client, times months they stay, times gross margin, gives you lifetime value. Compare the two. If a client costs $3,000 to win and returns $7,200 in margin over three years, the economics are workable but tight, and either retention or sales cost has to improve.
Technician utilization. What share of technician hours are billable or client-facing? Pick a target range and hold it. In my experience, a shop far below its range is overstaffed, and a shop far above it is about to lose people.
Put those four on one page with one owner each and review it weekly. At Gardeners Center, our coach BenJoe installed a weekly scorecard meeting with a short list of numbers, each with an owner, then coached the team to run it without the owners. The engagement record reports work got done faster, problems surfaced in the meeting instead of in a crisis, and the owners stepped out of daily operations. No hours saved were measured. The point is the habit, not the software.
Sell the contract, not the ticket
Project selling is transactional. Contract selling is a different skill, and it is the part of the plan owners resist most. I spent years as a Chief Revenue Officer before I started this firm, and the lesson that carried over is that the sales process has to be designed, not improvised.
Stop giving away free assessments. Charge for a 30 to 60 day discovery engagement where you audit the environment, document the risks, and propose a roadmap. A paid assessment makes you an advisor. A free one makes you a proposal factory. At the end, present two options: fix the immediate problems as a one-time project, or fix them as part of onboarding and maintain everything monthly. Show the cost of break-fix over three years next to the monthly fee. Let the client do the math.
Offer a 90-day pilot with a modest discount and clear success measures. State the pilot goals in writing. At day 90, review them together and decide. Then keep the quarterly business review on the calendar for the life of the contract. It is where you reinforce value and where expansion work surfaces: new locations, security upgrades, compliance needs.
One client record worth naming here. An IT and eLearning company left a public review of our work in December 2023. The work was staffing support and lead generation. The client reported 40% year-over-year sales growth. That is a single client-reported result, it is not audited, and the client stayed anonymous. I include it because sales growth in an IT firm came from fixing the sales system, not from a new tool. If you need someone inside your business to build that system, that is what our fractional CRO service is for.
Build delivery so the team can run it without you
Selling monthly contracts is one thing. Delivering them at a profit is the Controlled Delivery stage of S.C.O.R.E., and it is where most owners break. Three pieces have to be in place.
A remote monitoring and management platform that feeds tickets into your service automation system. Without it, you are doing break-fix work with a subscription label on it. Alerts should create tickets. Manual ticket entry is waste.
A standard technology stack. Pick one business-class hardware line, one firewall vendor, one backup product, and one productivity suite. When a client wants something outside the stack, price the exception into the contract or walk away. Supporting 40 different setups kills margin and traps knowledge in one technician’s head.
Documentation the team owns. Every client needs a network diagram, an asset list, and runbooks for common work, stored where any technician can find them. When our COO Michelle Markland served as fractional COO at Laridium, a manufacturing and fulfillment company, she built the operating system across sales, production, and shipping with the team, not for them. The client said she “made sure they were ours.” That is the standard. Documentation that only the owner or one senior tech understands is not documentation. It is a liability.
Two habits protect this. Every request becomes a ticket, no exceptions, no quick favors. And track time per client even though you bill monthly. If one client on a mid-tier plan consumes three times the hours of a similar client, either they need a project to fix the root cause or they are abusing the scope. Raise the rate or fix the cause. Do not let good clients subsidize bad ones.
Fix billing and accounting before you scale
Automate the invoice. Bill on the same day every month, charge by ACH or card, and send receipts and reminders without a human touching them. Require electronic payment in the contract. Net 15, not Net 30. Suspend service at 30 days past due. A client who does not pay is a client who is about to leave.
Learn the revenue rule. Sage’s guide to SaaS accounting explains that under ASC 606 you recognize revenue as you deliver the service, not when you bill or collect. Its example is a $1,200 annual subscription recognized at $100 per month over 12 months. If you bill a client a year up front, the cash is yours but the revenue is earned month by month. That matters for taxes, for your financial statements, and for what the business is worth if you ever sell it. Work with a CPA who understands subscription accounting.
Look hard at your software costs while you are in there. At Buckingham & Routh, a professional services firm, Michelle moved the client to new accounting software as part of a larger rebuild. The engagement record reports about $10,000 per month saved on accounting software, which is about $120,000 on an annualized basis. That annualized number is arithmetic on a monthly figure. A full year of net savings and the migration costs were not recorded. I use it because it shows the size of waste that can hide in a tool stack nobody has questioned in years.
Keep a reserve. Recurring revenue is more stable than project revenue. It is not guaranteed. Our post on why cash flow beats growth makes the case for holding several months of operating expense in cash, and a managed services firm with fixed technician payroll needs that cushion more than most.
Convert the clients you already have
Do not abandon your project clients. Convert them. Sort the list into three groups: high-value clients who buy often, occasional buyers with a good relationship, and one-off clients with little engagement. Spend most of your effort on the first group. The third group probably will not convert, and that is fine.
Make the offer time-limited. Something like: we are moving to a managed services model, and clients who transition by a set date get the onboarding fee waived and their first-year rate locked. An open-ended offer does not create a decision. For long-term clients who push back, hold their current project rates for six to twelve months if they sign, then move them to your standard tiers.
Start with one converted client, not a perfect plan
This is a 12 to 24 month rebuild of pricing, contracts, delivery, sales, and finance. I will not tell you what it does to revenue, because I do not have an audited number and neither does anyone else selling you a course on it. What I can tell you is the order that works. Get one paying client onto a monthly contract with a real scope and a price built from your cost. Run the four numbers on it. Fix what the numbers show. Then convert the next one.
The owners who wait for certainty will still be grinding out project quotes in two years. The ones who convert one client this quarter will have data. Data beats certainty. If you want the full method behind that order, our business coaching page explains how S.C.O.R.E. is installed from left to right.
Frequently asked questions
What is an IT services owner recurring revenue plan?
An IT services owner recurring revenue plan is a written plan for moving a firm from one-time project income to monthly contracts. It covers what the firm sells each month, how it prices that work, what the contract includes, and which numbers the owner tracks. The goal is income that continues when the owner stops selling.
Should an IT services firm stop doing project work?
An IT services firm should keep project work but change who it sells projects to. Monthly managed services contracts become the base, and migrations, upgrades, and implementations become expansion work sold to clients the firm already serves. Accountability Now's position is that projects for existing clients carry less scoping risk than projects for strangers.
How should a managed IT provider price a monthly contract?
A managed IT provider should start with its fully loaded cost per technician hour, add the margin it needs, and then set the monthly price per user or per device. Competitor rate cards show what others charge, not what the provider needs to earn. Accountability Now recommends building a pricing spreadsheet and using it on every quote.
Does a managed services contract need a 12-month term?
A managed services contract usually benefits from a 12-month initial term because onboarding, documentation, and stack changes cost the provider real money up front. Accountability Now runs its own core coaching month to month and earns the relationship each month, so a term is a business decision, not a rule. The term should cover the onboarding investment, and the service should be good enough that clients would stay without it.
What is monthly recurring revenue for an IT services business?
Monthly recurring revenue, or MRR, is the predictable revenue a business generates each month from clients who pay on a recurring basis. Stripe's guide to MRR and ARR breaks it into new, expansion, churn, and contraction components. For an IT services firm it includes managed services contracts, co-managed retainers, and monthly software resale, but not one-time project fees.
How is revenue recognized on an annual managed services contract?
Under ASC 606, revenue on a managed services contract is recognized as the service is delivered, not when the client is billed or pays. Sage's SaaS accounting guide gives the example of a $1,200 annual subscription recognized at $100 per month over 12 months. An IT services owner who bills a year up front should work with a CPA who understands subscription accounting.
Which metrics matter most for a managed services business?
Accountability Now recommends four metrics for a managed services business: monthly recurring revenue, net revenue retention, the ratio of client lifetime value to acquisition cost, and technician utilization. Each number should have one owner and should be reviewed in a short weekly meeting. A metric that never changes a decision is not worth tracking.
How do you move existing project clients to monthly contracts?
To move existing project clients to monthly contracts, sort the client list by how often and how much each client buys, then focus conversion effort on the top group. Offer a time-limited incentive such as a waived onboarding fee, and consider holding legacy rates for a set period for long-term clients who sign. Open-ended offers with no deadline rarely convert.
This article was drafted with AI research and writing tools, then rewritten and fact-checked by the Accountability Now team against our own client records and Google’s published guidance. Client results are reported by clients or our team and are not independently audited unless stated.
