A managed IT versus in-house IT comparison is useful only when both options cover the same work, risk, service hours, tools, and transition period. Comparing one provider invoice with one employee salary leaves out major costs on both sides and can point to the wrong operating model.
This guide provides an evergreen total-cost-of-ownership worksheet for business decision-makers. It does not publish market price ranges or provide a Rivell quote. For current New Jersey managed service price benchmarks, quote components, and scope factors, use the separate managed IT services pricing page. This page owns the cost-comparison method.
Start with the operating decision, not the price
First define the work the business needs. That may include user support, endpoint administration, network operations, cloud administration, backup, security operations, vendor coordination, procurement, documentation, and technical planning. Rivell’s overview of business IT service types can help identify the categories. The New Jersey managed IT services page describes the recurring service model.
Then decide which operating models deserve comparison:
Primarily in-house
Employees own most day-to-day work. Specialists, projects, tools, and temporary coverage may still come from outside suppliers.
Primarily managed
A provider owns a defined recurring scope. The business retains governance, risk decisions, approvals, budget, and provider oversight.
Co-managed
An internal team and provider divide responsibilities. The model can add specialist capacity while retaining institutional knowledge.
Project or support-only
The business retains the operating model but buys specific projects, escalation assistance, or user support when needed.
Do not force every business into one model. An organization with a capable internal team may need the co-managed IT model. Another may need a defined IT support scope. The comparison should reflect the actual decision.
Normalize scope before comparing totals
Write one requirements sheet and apply it to each option. If the internal model covers business hours but the provider proposal includes evenings and weekends, show the difference as a coverage decision. If one proposal includes security tools and another excludes them, separate those tools instead of treating the totals as equivalent.
| Scope field | Questions to answer | Evidence to collect |
|---|---|---|
| People and locations | How many users, devices, sites, remote workers, shifts, and supported entities are included? | Current inventory, HR roster, site list, device records, and growth assumptions. |
| Service hours | When must requests, monitoring, escalation, and onsite work be available? | Ticket history by hour, business schedule, escalation map, and proposed coverage terms. |
| Technology | Which endpoints, servers, networks, cloud tenants, applications, backup systems, and voice platforms are covered? | Asset list, configuration records, contracts, licenses, and dependency map. |
| Work types | Which tasks are recurring, project-based, approval-dependent, excluded, or billed separately? | Service catalog, responsibility matrix, proposal assumptions, and project backlog. |
| Security and continuity | Who owns access, alerts, incidents, updates, backups, restores, exceptions, and reporting? | Control scope, access model, incident plan, recovery tests, exception log, and reports. |
| Transition and exit | What must be discovered, remediated, migrated, documented, returned, or transferred? | Onboarding plan, remediation list, data-return terms, license ownership, and exit assistance. |
In-house IT total-cost worksheet
Salary is only one labor input. The BLS Employer Costs for Employee Compensation program separates wages and salaries from benefits such as paid leave, insurance, retirement, supplemental pay, and legally required costs. Use current payroll and benefit records when available. BLS data is a benchmark, not a substitute for company records.
For roles not yet staffed, use a consistent occupation and geography. The BLS Occupational Employment and Wage Statistics tables provide current national, state, and metropolitan data. Record the table date, geography, occupation, and wage measure used so the comparison can be reproduced later.
| In-house input | Include | Evidence source | Annual amount |
|---|---|---|---|
| Direct compensation | Base pay, overtime, bonuses, shift premiums, and temporary coverage. | Payroll records or documented hiring benchmark. | Enter company value |
| Employer costs | Benefits, paid leave, insurance, retirement, payroll taxes, and other required costs. | HR and finance records, supported by BLS categories where needed. | Enter company value |
| Recruiting and ramp-up | Search fees, interviews, onboarding, training, certifications, and time to productive coverage. | Recent hiring records and approved training plan. | Enter expected value |
| Tools and platforms | Ticketing, monitoring, endpoint, security, backup, documentation, remote access, and reporting systems. | Vendor contracts, license counts, renewal dates, and internal administration time. | Enter current value |
| Specialists and projects | External engineering, cloud, security, network, compliance, migration, and recovery work. | Invoices, project backlog, and planned capital or operating work. | Enter current and planned value |
| Management and governance | Leadership time, policy work, procurement, vendor management, reporting, and budget oversight. | Role allocation and time records. | Enter allocated value |
| Measured disruption | Documented incidents, coverage gaps, rework, and outage impact attributable to the operating model. | Ticket, incident, payroll, operations, and finance records. | Enter measured value only |
Use the same planning period for each option. If recruiting or platform implementation is a one-time item, show it separately and spread it only when the finance team approves that treatment.
Managed IT total-cost worksheet
A provider proposal can contain recurring fees, one-time work, pass-through licenses, and excluded services. Ask for enough detail to rebuild the number. A low starting fee is not comparable if important systems, users, sites, security work, projects, or service hours are outside scope.
| Managed-service input | Include | Evidence source | Annual amount |
|---|---|---|---|
| Recurring service | Covered users, devices, locations, systems, work types, hours, and minimum commitments. | Proposal, service catalog, assumptions, exclusions, and agreement. | Enter proposal value |
| Onboarding and remediation | Discovery, documentation, access changes, tool deployment, backlog cleanup, and required stabilization. | Onboarding plan, current-state assessment, and remediation schedule. | Enter proposal value |
| Licenses and equipment | Included tools, customer-owned licenses, hardware, taxes, shipping, and pass-through charges. | Bill of materials, license schedule, and purchasing terms. | Enter included and excluded values |
| Projects and exceptions | Migrations, major changes, onsite work, after-hours work, travel, consulting, and work outside scope. | Rate card, project rules, historical demand, and planned roadmap. | Enter expected value |
| Retained internal work | Business approvals, governance, risk decisions, vendor ownership, application ownership, and provider oversight. | Responsibility matrix and internal role allocation. | Enter allocated value |
| Transition and exit | Notice period, data and documentation return, license transfer, offboarding, deletion evidence, and replacement support. | Contract, exit schedule, and transition-assistance terms. | Enter expected value |
| Measured disruption | Documented incidents, service gaps, rework, and outage impact attributable to the proposed model. | Customer records, references, pilot results, and ongoing review data. | Enter measured value only |
The managed IT provider comparison guide helps evaluate provider evidence beyond cost. Use the commercial pricing owner for current price benchmarks, then replace assumptions with a scope-specific proposal.
Calculate the co-managed or hybrid model separately
A hybrid model is not simply the in-house total plus the provider total. Remove work that moves out of the internal team, retain work that stays internal, and add coordination costs only once. The responsibility matrix should identify one accountable owner for each recurring task, approval, exception, and escalation.
Examples of narrower scopes include data backup and disaster recovery, cloud services, VoIP services, and IT infrastructure management. The comparison should include only the services actually under review.
Keep risk evidence separate from assumptions
Do not assign a generic outage or cyber incident cost to every business. Use the organization’s own incident, operations, finance, and recovery records. If evidence is unavailable, label the amount unknown and run a sensitivity range approved by finance rather than presenting a borrowed statistic as fact.
The NIST Cybersecurity Framework provides outcomes that organizations can use to understand, prioritize, and communicate cybersecurity work. It does not prescribe one delivery model. Compare which option can produce the required outcomes, what the business must retain, and how performance will be evidenced.
NIST SP 1305 applies that thinking to technology suppliers. Use it to define supplier requirements, responsibilities, verification methods, information sharing, and contract terms. A provider relationship changes who performs work, but it does not remove customer governance or risk decisions.
Run sensitivity checks before choosing
- Baseline: Use the most supportable current values and the same planning period.
- Growth case: Recalculate for expected users, devices, sites, applications, and service demand.
- Turnover case: Test recruiting, vacancy, onboarding, and knowledge-transfer effects.
- Project case: Add the approved technology roadmap without burying projects inside recurring operations.
- Coverage case: Compare equivalent service hours and escalation requirements.
- Exit case: Include the cost and operational work required to change models later.
Record the source, owner, date, and confidence level for every input. A range is more honest than a precise number unsupported by company records. Revisit the model after major hiring, acquisition, location, application, security, or contract changes.
Use a decision scorecard, not cost alone
| Decision area | Weight | In-house evidence | Managed evidence | Hybrid evidence |
|---|---|---|---|---|
| Total cost and budget fit | Set by leadership | Worksheet and company records | Worksheet and proposal | Worksheet and responsibility split |
| Required coverage | Set by operations | Staffing schedule and escalation | Contracted scope and escalation | Combined coverage map |
| Skills and capacity | Set by roadmap | Role inventory and hiring plan | Named provider roles and availability | Gap and escalation map |
| Security and continuity | Set by risk owners | Control and recovery evidence | Supplier and shared-control evidence | Responsibility matrix and joint tests |
| Control and knowledge | Set by leadership | Documentation and succession plan | Data, access, documentation, and exit terms | Retained ownership plan |
For support escalation assumptions, use Rivell’s IT support tier guide. Verify how a provider defines each tier rather than assuming every organization uses the terms identically.
Managed IT versus in-house cost FAQ
Is managed IT less expensive than an internal team?
Not in every situation. The result depends on equivalent scope, internal compensation, employer costs, tools, projects, coverage, retained work, transition, contract terms, and measured operational impact. Build the worksheet with company records and a current provider proposal.
Where should I find current managed IT price ranges?
Use Rivell’s current New Jersey managed IT pricing guide. This page intentionally owns comparison methodology instead of duplicating commercial price benchmarks.
Should I use a percentage to estimate employee benefits?
Prefer current HR and finance records. When a benchmark is necessary, document the BLS table, period, worker group, and limits. Do not apply a broad average without checking whether it fits the organization.
How should downtime be included?
Use documented incidents and business records. Separate lost production, recovery labor, customer impact, contractual impact, and rework where those values can be supported. Mark unknowns instead of importing a generic number.
What costs are commonly missed in provider proposals?
Onboarding, remediation, excluded tools, projects, onsite work, work outside service hours, retained internal oversight, contract changes, annual adjustments, data return, offboarding, and transition assistance all require review.
When does co-managed IT make sense?
It can fit when the business wants to retain internal ownership while adding specialist skills, support capacity, or a defined operating scope. Compare the retained team and provider responsibilities together, not as two complete models.
Turn the worksheet into a defensible decision
- Inventory the users, devices, sites, systems, tools, service hours, projects, and known gaps.
- Choose the operating models that genuinely fit the business.
- Apply one requirements sheet and one planning period to every option.
- Enter company records before using external benchmarks.
- Separate recurring, one-time, retained, excluded, risk, and exit costs.
- Score cost alongside coverage, capability, security, continuity, control, and exit readiness.
- Document the decision, assumptions, evidence, owners, and review date.
This worksheet is general business decision support. It is not a quote, accounting advice, legal advice, or cybersecurity assurance. Cost treatment, risk valuation, and suitable service scope depend on the organization and should be reviewed by the appropriate financial, legal, risk, and technical owners.
