Co-managed IT for architecture businesses pairs your internal IT staff or tech-savvy team member with an external managed service provider who handles specialized tasks like CAD/BIM optimization, 24-7 monitoring, cybersecurity, and disaster recovery. This model typically costs $75 - $150 per user per month and allows your firm to retain control over design software configurations while offloading network management, security patches, and after-hours emergencies to experts who understand architecture workflows.
Why Do Architecture Firms Choose Co-Managed IT Over Fully Outsourced Support?
Many Salt Lake City architecture practices already employ someone who manages software licenses, troubleshoots Revit crashes, or coordinates with consultants on file-sharing protocols. That person knows your rendering pipelines, understands which BIM families your team relies on, and has relationships with software vendors.
Co-managed IT preserves that institutional knowledge while adding enterprise-grade infrastructure your internal resource cannot deliver alone. Your in-house contact remains the first point of escalation for design software questions, but when a server fails at 9 PM before a permit submission deadline, a 24-7 helpdesk with one-hour emergency response takes over.
The model also solves the expertise gap. A single internal IT person cannot stay current on zero-day vulnerabilities, manage complex Azure backups, optimize network switches for 500 GB rendering file transfers, and still have time to help an architect recover an unsaved SketchUp model. Co-managed IT fills those gaps without forcing you to hire a second full-time employee.
Scott, an engineering professional whose firm uses co-managed services, noted: "911 IT's services allows us to focus on our core business by effectively and safely managing our security for our cloud-based services, such as Microsoft Office365, Atlassian, GitLab, NextCloud, and more, including virus and cybersecurity protection on our computer system connected to our network."
Co-managed IT works best when roles are clearly defined - your team owns design decisions, the MSP owns infrastructure reliability.
What Specific Tasks Does the MSP Handle in a Co-Managed Arrangement?
The external provider typically assumes responsibility for proactive monitoring, patch management, cybersecurity, and backup verification. For architecture firms, this means real-time alerts when a workstation's GPU temperature spikes during a rendering job, automated patching of Windows and third-party software outside business hours, and nightly verification that your 2 TB project archive actually completed its backup cycle.
Cybersecurity becomes a shared function. The MSP deploys endpoint detection and response tools, manages firewall rules, conducts quarterly phishing simulations, and monitors dark web exposure for compromised credentials. Your internal contact handles user permissions within project management platforms like BIM 360 or Procore, while the MSP ensures those platforms are protected by multifactor authentication and encrypted connections.
Disaster recovery planning shifts entirely to the MSP. They document your recovery time objectives, test restore procedures quarterly, and maintain offsite replicas of your file server. When a flood damaged a Salt Lake City firm's server room, their co-managed provider had them operational from cloud backups within four hours.
The MSP also handles vendor coordination for hardware failures. If a workstation's NVMe drive fails, the provider manages the warranty claim, coordinates the replacement, and restores the user's profile from backup - tasks that would otherwise consume half a day of your internal person's time.
911 IT provides 24-7 IT monitoring and helpdesk support with one-hour emergency response times, ensuring architecture firms never lose productivity during critical project phases.
How Do Architecture Firms Structure the Division of Responsibilities?
Successful co-managed relationships begin with a responsibility matrix that defines who owns each IT function. A typical architecture firm arrangement assigns design software installation, license management, and CAD/BIM troubleshooting to the internal contact, while network infrastructure, security operations, and backup management belong to the MSP.
Communication protocols matter. Most firms establish a shared ticketing system where end users can submit requests to either party. The internal contact triages design software issues directly, while infrastructure problems automatically route to the MSP. Weekly sync calls between your internal resource and the MSP's vCIO ensure both parties stay aligned on upcoming projects, such as a new hire onboarding wave or a server refresh.
Escalation paths must be crystal clear. If your internal person cannot resolve a Revit performance issue within 30 minutes, they escalate to the MSP's co-managed IT team, who can analyze network latency, storage I/O bottlenecks, or memory allocation problems. Conversely, if the MSP detects unusual outbound traffic suggesting a compromised workstation, they immediately notify your internal contact to verify whether it's a legitimate large file upload to a consultant.
Documentation becomes a shared asset. The MSP maintains network diagrams, IP address schemes, and disaster recovery runbooks in a centralized portal your internal person can access anytime. Your internal contact documents design software configurations, custom scripts, and plugin dependencies in the same system, ensuring continuity if either party changes.
- Define ownership boundaries: Create a responsibility matrix listing every IT function and assigning it to either internal staff or the MSP.
- Establish communication channels: Deploy a shared ticketing system with clear routing rules for design software versus infrastructure issues.
- Schedule regular sync meetings: Weekly calls during onboarding, then monthly check-ins to review tickets, upcoming projects, and capacity planning.
- Document escalation procedures: Define time thresholds for escalating unresolved issues and emergency contact protocols for after-hours crises.
- Centralize documentation: Maintain network diagrams, software configurations, and disaster recovery plans in a shared portal accessible to both parties.
This division allows architecture firms to scale IT capabilities without doubling headcount.
What Does Co-Managed IT Cost for a Typical Architecture Practice?
Industry pricing for co-managed IT ranges from $75 to $150 per user per month, with architecture firms typically landing in the $100 - $125 range due to specialized software support needs. A 12-person firm with high rendering demands and strict backup requirements might pay $1,400 monthly, while a 25-person practice with multiple offices and complex network infrastructure could invest $3,000 monthly.
Pricing models vary by scope. Some MSPs charge per user, covering all workstations, servers, and network devices under a flat rate. Others use a hybrid model: a base fee for infrastructure management plus per-user charges for helpdesk access and security tools. Architecture firms should clarify whether CAD/BIM performance optimization, rendering farm management, and large file transfer troubleshooting are included or billed separately.
Additional costs often include cybersecurity add-ons ($25 - $75 per user monthly for advanced threat detection), VoIP phone services ($20 - $40 per user monthly), and project-based work like office network buildouts ($150 - $250 per hour). A firm migrating from on-premise file servers to a cloud-based project management system might incur a one-time $8,000 - $15,000 project fee on top of monthly co-managed fees.
Compare this to hiring a second full-time IT employee. A qualified network administrator in Salt Lake City commands $65,000 - $85,000 annually plus benefits, totaling $80,000 - $105,000. For a 20-person firm, co-managed IT at $2,000 monthly ($24,000 annually) delivers enterprise-grade infrastructure, 24-7 coverage, and specialized architecture software expertise at roughly one-quarter the cost of another hire.
Jessie, who runs a restoration business, praised the personalized approach: "Every time I call, they know exactly who I am and have my file pulled up in front of them ready to help. They are always in a good mood when helping me - even when my needs are super difficult - and they always get the issue solved very quickly."
Co-managed IT delivers predictable monthly costs without sacrificing the personalized service small architecture firms require.
Which Salt Lake City Providers Offer Co-Managed IT for Architecture Firms?
Salt Lake City's architecture community has access to several regional MSPs with co-managed capabilities, though few specialize in CAD/BIM optimization and rendering infrastructure. Verified local providers include Executech, Wasatch I.T., Nexus IT Consultants, INTELITECHS, ProLink IT, and Qual IT, each serving professional services firms with varying levels of architecture-specific expertise.
When evaluating providers, architecture firms should prioritize those with documented experience supporting Revit, AutoCAD, SketchUp, Rhino, and rendering engines like V-Ray or Enscape. Ask whether the provider has optimized network storage for large BIM files, configured workstations for GPU-accelerated rendering, or supported digital plan submissions to Salt Lake City Building Services Division.
National MSPs occasionally pitch Salt Lake City firms, but architecture practices benefit more from regional providers who understand Utah's building code submission systems, have relationships with local consultants, and can dispatch on-site technicians within an hour for hardware emergencies. A firm in Sugar House doesn't need a provider with offices in 40 states; they need someone who can be on-site before lunch when a workstation fails the morning of a planning commission presentation.
911 IT explicitly lists CAD, BIM & Engineering Software Performance as a core service offering, positioning them to handle architecture firms' specialized needs alongside managed IT services, cybersecurity, and data backup. Founded in 2004, 911 IT serves businesses across Utah, Wyoming, and Arizona with 24-7 helpdesk support and one-hour emergency response times - critical for architecture firms facing project deadlines.
The provider's flat-rate, transparent pricing and 100% satisfaction guarantee address common pain points architecture firms experience with break-fix IT companies that bill hourly and lack accountability. Their proactive monitoring approach prevents the 4 PM Friday server crashes that derail weekend rendering schedules.
For architecture firms, the right co-managed partner combines infrastructure expertise with genuine understanding of design workflows - not just generic business IT support.
How Do You Transition from Break-Fix IT to a Co-Managed Model?
Most architecture firms begin with a break-fix arrangement: calling a technician when something breaks, paying hourly, and hoping problems resolve quickly. Transitioning to co-managed IT starts with a network assessment where the MSP documents your current infrastructure, identifies security gaps, catalogs software licenses, and maps data flows.
The assessment typically reveals unpatched servers, workstations without endpoint protection, backups that haven't been tested in months, and network switches running firmware from 2019. The MSP presents a remediation roadmap with prioritized fixes: critical security vulnerabilities first, then backup verification, followed by performance optimizations for CAD/BIM software.
Onboarding takes 30-60 days. The MSP installs monitoring agents on all devices, configures backup jobs, deploys security tools, and integrates with your existing systems. Your internal IT contact receives training on the MSP's ticketing system, documentation portal, and escalation procedures. During this phase, both parties handle issues collaboratively until workflows stabilize.
Communication is essential. Weekly check-ins during the first quarter ensure nothing falls through the cracks. Your internal person might discover the MSP's automated patching schedule conflicts with overnight rendering jobs, prompting a schedule adjustment. The MSP might notice your file server is approaching capacity and recommend a storage upgrade before it impacts project work.
After 90 days, most firms settle into a rhythm. Routine infrastructure tasks happen invisibly in the background, your internal contact focuses on design software support, and end users experience fewer interruptions. The MSP's quarterly business reviews provide data on system uptime, security posture, and capacity planning - metrics that help you make informed IT investment decisions.
Debbie, who worked with 911 IT across multiple offices, shared: "No matter the issue(s) that we encountered with our computers your entire staff was always very helpful and outstanding reflections of your Company. I worked with various computer representatives and everyone wanted to make sure we were satisfied customers." The firm successfully restored several years of email after complete deletion and corruption - the kind of disaster recovery that validates the co-managed investment.
Transitioning to co-managed IT transforms IT from a cost center that drains time into a strategic asset that enables growth.
Why 911 IT Is the Right Co-Managed Partner for Salt Lake City Architecture Firms
Architecture firms need an IT partner who understands that a crashed Revit session 30 minutes before a client presentation is not a minor inconvenience - it's a business emergency. 911 IT's one-hour emergency response time and 24-7 helpdesk ensure your team gets help when it matters, not the next business day.
Their explicit focus on CAD, BIM & Engineering Software Performance distinguishes them from general business IT providers who treat AutoCAD like any other application. 911 IT understands the difference between optimizing a workstation for Excel and optimizing one for rendering a 200 MB Revit model with real-time ray tracing.
Flat-rate, transparent pricing eliminates the break-fix model's unpredictability. You know your monthly IT cost in January, which makes budgeting for the year straightforward. The 100% satisfaction guarantee means if the service doesn't meet expectations, you're not locked into a punitive contract.
With a South Jordan office at 1124 South Jordan Parkway, 911 IT provides local presence for on-site support when remote troubleshooting isn't enough. They've served Utah businesses since 2004, building deep familiarity with regional building codes, local consultant ecosystems, and Salt Lake City's digital plan submission requirements.
For architecture firms weighing co-managed IT, the decision ultimately comes down to partnership fit. Do you want a provider who sees you as ticket number 4,872 in a queue, or one who knows your firm by name, understands your project cycles, and treats your deadlines as their own? 911 IT's testimonials consistently highlight personalized service, proactive communication, and genuine partnership - exactly what architecture firms need when technology must fade into the background so design can take center stage.
If your current IT arrangement leaves you troubleshooting network issues when you should be refining elevations, it's time to explore Salt Lake City IT support built for architecture workflows.
Frequently Asked Questions
What is the difference between co-managed IT and fully managed IT?
Co-managed IT splits responsibilities between your internal IT resource and an external MSP, with your team handling design software and the MSP managing infrastructure, security, and backups. Fully managed IT outsources all technology functions to the provider. Architecture firms with existing IT staff typically choose co-managed to preserve institutional knowledge while gaining enterprise-grade infrastructure and 24-7 support coverage.
Can co-managed IT support multiple office locations?
Yes, co-managed IT providers manage network connectivity, cloud services, and security across multiple offices from a centralized platform. For architecture firms with satellite offices or remote employees, the MSP ensures consistent security policies, reliable file access, and unified communications regardless of location. 911 IT serves businesses across Utah, Wyoming, and Arizona, providing regional coverage for multi-office firms.
How quickly can a co-managed IT provider respond to emergencies?
Response times vary by provider and service level agreement. 911 IT guarantees one-hour emergency response for critical issues like server failures, ransomware attacks, or network outages that halt productivity. Non-emergency requests typically receive same-day response during business hours. Architecture firms should verify emergency response commitments before signing a co-managed agreement, especially if project deadlines create time-sensitive IT needs.
Does co-managed IT include CAD and BIM software support?
It depends on the provider. General business MSPs often exclude design software support, treating CAD/BIM as specialized applications outside their scope. 911 IT explicitly includes CAD, BIM & Engineering Software Performance as a service offering, covering performance optimization, troubleshooting, and infrastructure tuning for Revit, AutoCAD, and rendering applications. Clarify software support scope during contract negotiations to avoid gaps.
What happens if my internal IT person leaves the company?
A strong co-managed relationship includes comprehensive documentation of your systems, configurations, and workflows maintained by the MSP. If your internal person departs, the MSP can temporarily assume their responsibilities while you hire a replacement, then train the new hire on your environment. This continuity protection is a key advantage of co-managed IT over relying solely on internal staff.
