The Ashton Solutions Blog - Ashton Solutions

CASE STUDY: Supporting Internal IT, Before and After Growth

Written by Jim Abbott | 11/18/26, 5:15 PM

The Challenge

When a midsized regional law firm first connected with Ashton, its 60-plus employees were already supported by a local managed IT provider that specialized in the legal industry. But despite that industry experience, the relationship wasn’t meeting the firm’s needs. Support followed a rigid structure, collaboration was limited, and projects and tasks often lacked the sense of urgency the firm expected. The firm also found itself working with engineers who didn’t always have a strong understanding of its people, operations, or business needs.

There was another challenge: the firm did not have a dedicated internal IT leader. Technology responsibilities largely fell to the firm administrator, who was balancing IT oversight with the demands of running the firm. Without someone focused solely on technology, the firm needed a partner that could take greater ownership, helping manage vendors, plan for future needs, oversee projects, and provide guidance on infrastructure and security, rather than simply responding when something went wrong.

The Solution

Ashton began with a formal onboarding and documentation process to develop a clear understanding of the firm’s technology environment, operations, and needs. That foundation helped create greater continuity and accountability while giving the firm a technology partner that understood its business, not just its systems.

With no dedicated internal IT leader at the time, Ashton took on a broader role, working with the firm’s technology committee as well as firm administrators, providing both day-to-day support and technology leadership. The relationship included infrastructure management, vendor coordination, cybersecurity guidance,  strategic planning, project support, and access to a deeper team of engineering resources.

As the firm grew, its technology needs became more complex. Due to that growth and complexity, leadership made the decision to invest in an internal IT director who could work closely with attorneys and staff, manage day-to-day operational needs, and focus on the legal applications central to the practice, including docketing and case management systems.

Adding an internal IT director changed the firm’s relationship with Ashton, but it didn’t reduce the need for Ashton’s support. Instead, Ashton’s role evolved. The partnership became a co-managed model, combining the internal IT director’s knowledge of the firm with Ashton’s broader technical resources and expertise.

A Co-Managed Partnership

In the co-managed model, each team has a clear role, allowing the firm to make the most of both its internal IT knowledge and Ashton’s broader resources. Internal IT stays close to the attorneys, staff, workflows, and specialized systems unique to the firm. Ashton provides the broader resources and specialized expertise that would be difficult to replicate with a single internal position, including:

•    Advanced engineering resources
•    Cybersecurity and threat protection
•    Network infrastructure planning and management
•    Backup and disaster recovery
•    User support and escalation
•    Vendor coordination and project implementation
•    Strategic technology consulting

This allows the internal IT director to remain focused on the technology and processes closest to the firm’s daily operations, while still having an experienced team available for security, infrastructure, complex projects, escalations, and strategic  planning.

The Results

For more than seven years, the relationship has continued to adapt as the firm has grown and its technology needs have changed.

What began as Ashton supporting an organization without dedicated internal IT leadership has become a mature co-managed relationship that strengthens the firm’s in-house capabilities.

Today, the firm benefits from:

•    Dedicated internal technology leadership
•    Specialized expertise when needed
•    Less dependence on any one 
•    individual
•    Broader cybersecurity and infrastructure support
•    Additional resources for projects and periods of change
•    The ability to scale its technology resources without building an entire IT department internally

Most importantly, the IT model was able to change along with the business rather than forcing the business to fit a predetermined support model.

Key Takeaway

Adding internal IT can be the next step in a growing organization’s technology strategy. For this firm, growth changed what it needed from Ashton. Instead of owning nearly every aspect of technology, Ashton became an extension of the internal IT team, providing the resources, expertise, and depth that complement what the firm already has in-house. It’s a model that can evolve as an organization evolves, from fully managed IT to co-managed support, while maintaining the knowledge, continuity, and partnership built along the way.