Should a Los Angeles business choose co-managed or fully managed IT?
Axus helps Los Angeles businesses choose by assigning responsibility first. For a 25-person team with an internal IT owner, co-managed support can cover defined gaps. Fully managed IT suits a business ready to delegate daily operations. Both need written ownership, escalation rules, and a named business decision-maker; headcount alone does not settle the choice.
The practical difference is who does the work and who coordinates it. Fully managed IT delegates the agreed day-to-day technology work to a provider. Co-managed IT splits that work between your internal team and the provider. Neither label tells you enough about a particular contract.
Before requesting proposals, ask your internal IT person what takes their time and where they need help. An owner may see a support backlog; the person handling it may see undocumented applications, delayed approvals, or a missing specialist. Those problems call for different scopes.
Start with a responsibility table
The table below is an illustrative ownership model, not an Axus contract. Its purpose is to make the division of work visible. Replace each example with named owners and confirm who covers absences.
| Work | Co-managed example | Fully managed example | Business responsibility |
|---|---|---|---|
| Everyday employee support | Internal team first; provider handles agreed overflow | Provider receives and owns requests | Tell staff where to ask for help |
| Device maintenance | Provider runs agreed maintenance; internal team approves exceptions | Provider runs agreed maintenance and reports exceptions | Fund necessary replacements |
| Application changes | Internal owner coordinates with vendor; provider supports infrastructure | Provider coordinates technical escalation with vendor | Approve workflow and commercial changes |
| Security alerts | Provider investigates agreed alerts and escalates | Provider investigates agreed alerts and escalates | Name an incident decision-maker |
| Backup recovery | Provider performs assigned tests; internal owner reviews results | Provider performs agreed tests and reports results | Set recovery priorities |
| Technology planning | Internal lead and provider prepare the plan together | Provider prepares recommendations | Approve budget and priorities |
Security, backup, and application responsibilities deserve particular attention. Two teams can each believe the other is checking something. Give each recurring activity one accountable owner, even when several people contribute.
When co-managed IT fits
Co-managed IT can work well when an internal person understands the business and needs more capacity or a particular skill. They might own application workflows while a provider handles agreed maintenance, monitoring, backup tasks, or support overflow. The arrangement can preserve close contact with employees while adding help where it is needed.
It also requires coordination. Your internal team needs time to maintain shared documentation, review unresolved work, approve changes, and work through disagreements. Keeping an internal employee does not automatically make a co-managed arrangement effective; the work must fit their available time and authority.
Ask about shared ticket visibility and documentation. If employees can contact either team, agree on how tickets enter one visible process. Otherwise, the same issue may be worked twice or passed back and forth without anyone taking responsibility.
When fully managed IT fits
Fully managed IT can suit a company without an internal technology team, or one whose leaders want an external provider to coordinate the agreed operational work. Employees need a clear support route, while management needs reports that explain outstanding issues and decisions.
The business still retains responsibilities. Someone must approve spending, authorize access, communicate employee departures, set priorities, and decide how much disruption a change can tolerate. Delegating technical work does not remove those decisions.
Confirm the depth of application support. A provider can manage the devices, identities, network, and vendor escalation around an application without owning its source code or business workflow. If an application is central to operations, name its business owner and software vendor in the service plan.
Compare total cost without assuming a discount
Do not assume co-managed IT costs half as much because two teams share the work. A narrow specialist service can require substantial effort; an internal salary remains in your budget even when some tasks move to a provider.
Use the same accounting period and count each cost once:
Co-managed annual budget = retained internal employment costs + provider fees + separate tools + projects and hardware.
Fully managed annual budget = provider fees + retained business administration costs + separate tools + projects and hardware.
The managed IT pricing guide uses $100 to $250 per user per month for planning, not a binding quote or a co-managed rate card. At 25 users, that is $2,500 to $6,250 monthly or $30,000 to $75,000 annually for the modeled recurring amount. Get a separate written scope for the actual division of responsibilities.
Test the arrangement before you sign
Use a tabletop discussion with both teams. Suppose an employee loses access to a business application while your internal IT lead is away. Who receives the request, checks identity, contacts the vendor, approves changes, and tells the employee what happens next?
Repeat the exercise for an after-hours incident. Confirm coverage hours, response priorities, notification rules, and any additional fees. This discussion is more useful than assuming every urgent issue follows the same process.
During onboarding, request a documented list of systems, access owners, open problems, and handoff dates. Agree how responsibilities can change if your company hires an IT lead, opens another office, or changes applications. Review what happens to tools and documentation at the end of the agreement.
Put your ownership model on paper
Compare Axus co-managed IT with managed IT services. Bring your current division of work to a scope discussion, or call (310) 676-4440. The useful proposal is the one that assigns the work your business needs done and leaves everyone clear about their part.