A national hospitality company with more than 90 hotel properties across major U.S. business and leisure markets needed a better way to manage onsite IT support across its portfolio. The company had a significant presence in dense city markets and, in many cases, operated multiple properties within the same metro area.
Its onsite IT support model relied on full-time technicians covering clustered properties in markets such as Boston, New York, Washington, DC, Atlanta, Dallas, Los Angeles, and San Diego. That structure gave each market dedicated coverage, but it also created a costly operational problem. Too much paid technician time was being lost to travel between properties. Urgent issues were harder to handle when the assigned technician was already at another hotel. And with annual spending on full-time onsite IT technicians and third-party support reaching $1.423 million, leadership needed a more flexible model that could improve responsiveness without adding headcount. The company’s public market footprint shows the kind of clustering that makes this problem expensive: Boston 7 hotels, New York 7, Washington, DC 11, Atlanta 9, Dallas 8, Los Angeles 9, and San Diego 5.
Cartennas helped the company replace a travel-heavy technician model with a more flexible onsite IT support structure built around property-level dispatch, on-demand onsite response, and centralized coordination across clustered city markets. Instead of forcing service requests through one technician’s daily route, the company could direct onsite IT support where it was actually needed, when it was needed. That shift reduced wasted paid time, improved emergency responsiveness, and cut annual support spend by 59%, from $1,423,000 to $583,430, generating $839,570 in annual savings.
Key Outcomes
- 59% reduction in annual onsite IT support and third-party support spend
- $839,570 in annual savings
- Annual support cost reduced from $1,423,000 to $583,430
- Less paid technician time lost to travel between clustered properties
- More flexible response to urgent onsite issues without expanding headcount
- Centralized dispatch coordination across multiple hotel markets
Customer Snapshot
Industry: Hospitality
Business Type: Hotel ownership, investment, and management company
Portfolio Scale: More than 90 hotel properties
Geographic Reach: Major U.S. business and leisure markets
Representative Cluster Markets: Boston, New York, Washington, DC, Atlanta, Dallas, Los Angeles, San Diego
Annual Support Spend Before Cartennas: $1.423 million
Services Delivered: Onsite IT support
Previous Support Model: Full-time onsite IT technicians covering property clusters, supplemented by third-party support
The Challenge
The company needed to support a large hotel portfolio spread across major U.S. markets, often with multiple properties inside the same city. In those clustered markets, full-time technicians were assigned to groups of hotels and moved between properties as issues came up.
That looked workable on paper. In practice, it wasted money and slowed support.
A meaningful portion of paid technician time was being spent in transit rather than resolving issues onsite. If one hotel had a pressing problem, support could be delayed because the assigned technician was already at another property. In hospitality, that matters more than it does in many other industries. Front-desk systems, connectivity, point-of-sale devices, back-office hardware, guest-facing technology, and operational endpoints all sit close to revenue, guest experience, and day-to-day property operations.
The company’s problem was not a lack of support staff. The problem was that too much support capacity was tied to movement between properties instead of work performed at properties.
Leadership needed a support model that could do four things at once:
- reduce wasted paid time
- improve response to urgent onsite issues
- support clustered city markets more efficiently
- avoid solving the problem by simply adding more headcount
Why the Previous Model Was Not Working
The previous structure relied on two expensive layers at the same time: full-time onsite IT technicians assigned to hotel clusters and third-party support used to fill gaps.
That model created four clear weaknesses.
Paid labor was being diluted by travel
The company was paying for skilled onsite IT support, but too much of that paid time was being consumed by technicians driving between hotels. In dense city clusters, even short inter-property trips added up. Across a national portfolio, that became a structural cost problem, not just a scheduling inconvenience.
Urgent issues had to wait on technician location
When one technician was responsible for multiple properties, the real bottleneck became physical location. If that person was already at another hotel, a high-priority issue at the next property had to wait. That meant the company’s response capability was often limited not by technical ability, but by routing and travel time.
Cluster coverage was rigid
A technician assigned to several hotels cannot be in two places at once. When issues overlapped across properties, support availability became uneven. One hotel could be covered while another waited, even though both were in the same market.
The default answer was more spend
As the portfolio grew and markets became more complex, the obvious answer under the old model was to add more full-time coverage or spend more on third-party support. But that would have raised fixed cost without fixing the core inefficiency: too much of the support budget was being spent on coverage structure rather than productive onsite work.
With annual onsite IT technician and third-party support spend already at $1.423 million, leadership needed a better operating model, not just more of the same.
The Cartennas Solution
Cartennas replaced the travel-heavy support structure with a more flexible onsite IT support model centered on on-demand dispatch, city-market coverage, property-level response, and centralized coordination through the Cartennas platform.
The shift was operationally simple but financially meaningful.
Instead of relying so heavily on full-time technicians driving between hotels throughout the day, the company could request onsite support based on actual property need. Cartennas gave the business a way to separate service delivery from one technician’s physical route and availability.
The Cartennas platform added a centralized dispatch layer across the hotel portfolio. Service requests no longer had to stay inside separate market routines or depend on whoever happened to be covering a property cluster that day. Intake, triage, dispatch coordination, status visibility, and escalation could all be managed through one platform. That gave the company a more organized way to route onsite IT support across multiple city markets.
That centralization mattered. Leadership gained one place to see open needs across properties, coordinate response across clustered hotels, and reduce the friction that comes from managing support through a mix of technician assignments and fragmented third-party activity.
That change helped the company in five practical ways.
1) Property-level dispatch instead of route-based support
Support no longer depended as heavily on whichever technician happened to be assigned to a cluster. Cartennas made it possible to send onsite help to the hotel that needed it, rather than forcing every issue through a travel sequence.
2) Less technician time lost to non-productive movement
By reducing dependence on inter-property travel, more paid support time could be used for actual onsite work. That improved labor efficiency immediately.
3) Better handling of urgent issues
Urgent onsite problems no longer had to wait as often for one assigned technician to finish at another property and drive over. Cartennas gave the company a more flexible way to respond when guest-impacting or operationally sensitive issues came up.
4) Reduced reliance on overlapping support layers
The company no longer had to lean as heavily on a mix of full-time technicians plus ad hoc third-party support to maintain service levels. Cartennas provided a more coordinated alternative across clustered markets.
5) Scalability without headcount expansion
Most importantly, the company improved support coverage without having to expand internal headcount.
How Cartennas Delivered
Cartennas supported the company through an onsite IT support structure designed specifically for multi-property city clusters.
That mattered because the company’s market profile was exactly the kind of environment where travel-heavy technician models break down: multiple hotels in the same city, overlapping service needs, and a support burden spread across major business and leisure markets.
Cartennas improved delivery in five specific ways.
Coverage moved closer to actual demand
Instead of making one technician’s daily movement the center of the support model, Cartennas let the company direct onsite IT support where demand actually existed at the property level.
Urgent issues became easier to isolate and handle
When a property had an urgent issue, response no longer depended as heavily on whether the assigned cluster technician was already across town at another hotel.
Support spend became more productive
The company’s support budget was no longer carrying the same level of travel waste. More of every support dollar could go toward actual onsite service activity.
National scale became more manageable
Because the company operated across major U.S. markets, the real issue was not just one city. It was repeating the same inefficient support pattern across a national footprint. Cartennas gave leadership a cleaner operating structure that could work across clustered markets without requiring a parallel increase in full-time staffing.
Dispatch became centralized instead of fragmented
The Cartennas platform helped centralize dispatch execution across the portfolio. Instead of handling service coordination market by market, the company could manage intake, routing, status tracking, and escalation through one operating layer. That made it easier to prioritize urgent issues, coordinate response across clustered hotels, and keep dispatch from becoming fragmented as portfolio complexity increased.
Business Impact
59% lower annual support spend
The clearest result was financial.
The company reduced annual onsite IT technician and third-party support spend from $1,423,000 to $583,430.
That is a savings of:
$1,423,000 × 0.59 = $839,570
This was not a marginal improvement. It was a structural reduction in support cost driven by a better operating model.
Better use of paid support time
Before Cartennas, a meaningful share of paid labor was being absorbed by travel between hotels. After the change, more paid support time could be used for productive onsite work. That improved labor efficiency without requiring more headcount.
Faster response for urgent onsite issues
By reducing dependence on one technician’s location and route, the company improved its ability to respond when urgent issues affected hotel operations, guest-facing systems, connectivity, or staff workflows.
More scalable support across clustered city markets
The old model naturally pushed leadership toward hiring more full-time technicians as complexity increased. Cartennas gave the company a more flexible alternative. That made support across clustered markets more scalable without repeating the same fixed-cost pattern.
Centralized dispatch visibility and control
Beyond labor savings, the company gained a more centralized dispatch structure. That made it easier to coordinate service activity across multiple hotels, track open issues across markets, and manage onsite response through one platform instead of relying so heavily on separate technician coverage patterns and fragmented support workflows.
What Changed
Before Cartennas, the company’s onsite IT support structure relied heavily on full-time technicians covering groups of hotels within each city market, with third-party support filling gaps. That created local coverage, but it also wasted paid time, reduced emergency flexibility, and made the model expensive to scale.
With Cartennas in place, the company moved to a more flexible onsite IT support structure built around actual property demand rather than technician movement.
Instead of spending $1.423 million annually on a travel-heavy mix of full-time technicians and third-party support, the company reduced annual spend to $583,430 and saved $839,570. More importantly, it did so while improving flexibility, centralizing dispatch, and avoiding headcount expansion.
About the Customer
This customer is a national hospitality company operating more than 90 hotel properties across major U.S. business and leisure markets. Its public market profile shows extensive experience managing multiple clustered hotels in the same city, which is exactly the type of operating environment where inter-property technician travel becomes costly and hard to scale.