For eight years, the storage system did its job. No failures. For a government agency running a consolidated data center, that ought to have been the happy ending. Instead, the agency wanted a replacement. The equipment was dependable; the cost of continuing with it was the problem. That distinction is a good place to meet e360.
- e360 designs, installs, and runs enterprise IT, from virtual desktops to cloud infrastructure and security.
- Its customer work joins technical decisions to budgets, governance, and everyday operations.
- The lesson to borrow: define the constraint before choosing the platform.
The consultancy helped the agency evaluate HPE GreenLake, which brought a consumption-based storage model into its own data center. The published account describes networking trouble during deployment, resolved with equipment HPE supplied without charge. Even a functioning storage system, it turns out, exists inside a larger system of contracts, networks, and budgets.
The machine works. Does the arrangement?
The agency expected savings of as much as $10 million at its then-current usage rate. That was an estimate, without a stated time horizon. The revealing detail is the purchasing logic: installed capacity, room for demand spikes, and a different pattern of payments. The hardware could stay on premises while the economics changed around it.
e360 occupies that intersection. It helps enterprises assess their technology, buy and integrate systems, migrate workloads, secure access, and operate the result. Healthcare organizations, government agencies, financial firms, and manufacturers all appear in its market. Customers include Yamaha, QuidelOrtho, and Ensign Services. These are organizations with existing applications and obligations. Starting over is rarely the assignment.
The company began in 1988 as an application-training business started by Mike Strohl’s father. After his death, Mike and Matthew General took over in 1994. Today they are CEO and COO. The company’s history emphasizes employees with more than two decades of service. Training, long relationships, and complicated systems make a fairly coherent family tree.
Yamaha changes the room behind the desktop
At Yamaha Corporation of America, the pressure came from growing demand, rising costs, and an increasingly cumbersome virtual desktop environment. Moving to the cloud also meant introducing a platform the organization was not yet accustomed to using. Users still needed their familiar applications. IT needed a design it could support.
e360 combined Citrix Cloud with workloads in AWS, spread across multiple availability zones in one region. Locality mattered: most users were in Southern California. Autoscaling adjusted instance counts to utilization. According to the Yamaha case study, applications required no refactoring, users experienced fewer interruptions, and performance-related support calls fell. Buying specialized hardware gave way to paying for operating capacity.
The transferable idea is quite practical. Preserve what users need while changing the machinery behind it. That approach depends on applications that can move without major rewrites, appropriate network performance, and active management of consumption. A different workload or geography could require a different architecture. Yamaha’s design answers Yamaha’s constraints.
An editorial reading of the customer projects: three questions to ask before approving the purchase.
Then somebody has to read the bill
Cloud consumption changed e360, too. In an interview with CRN, Strohl described the investment, mistakes, and persistence involved in moving from traditional infrastructure resale into cloud work. Customers were struggling to understand their spending. Engineering skill alone could not explain the financial consequences.
“It’s learning to speak a new language.”
Mike Strohl, on the shift to cloud and FinOps, speaking to CRN
The business model helps explain his concern. Strohl described revenue from cloud consumption, other services, managed services, and marketplace sales. Where e360 controls customer contracts, billing becomes part of the relationship. FinOps, the discipline of managing cloud spending, brings finance into decisions that might once have belonged mostly to technical teams.
QuidelOrtho illustrates the organizational side. Its growing AWS use supported new products, including services collecting data from diagnostic devices. The company wanted broader visibility into governance and quicker decisions. e360 ran stakeholder workshops and helped establish a Cloud Business Office with a charter and foundational policies. The reported outcome was wider involvement among business, development, and technology teams. Here, the deliverable included an agreement about how people would decide.
The price of replacing yesterday
Anaheim offers a less abstract view of the money. An April 2025 city staff recommendation selected e360 for a proposed replacement of a phone system installed in 2001. Its pricing table listed $1,692,366 for year one and $276,408 annually in years two through five. These were proposal figures for a citywide project.
The city requested contingency funding partly because documentation for the old system was sparse. That is the unglamorous inheritance of enterprise technology: uncertainty accumulates alongside equipment. Buyers can copy the discipline of separating implementation, equipment, recurring licenses, and support, then asking which unknowns could move each number.
A place between the vendors
e360’s position rests on working across suppliers, including AWS, Microsoft, Google Cloud, Citrix, and HPE. Its managed services add ongoing monitoring, contractual service levels, and an optional co-management arrangement. In June 2025 it announced recognition as Citrix’s 2024 North America Technical Partner of the Year, evidence of a specific technical relationship.
Its security practice covers identity and access management, threat detection, risk, and compliance, alongside AI governance. For a buyer, this makes the selection question more specific: which responsibilities belong together, and which should stay inside the organization? The breadth matters only when it produces clear ownership across those boundaries.
The same operating concerns now appear in its AI Engineering practice: governed data, custom applications, deployment, and monitoring. Buyers should expect to participate, supply internal owners, and define measurable goals. An adviser can design the process; the organization must use it. Eight-year-old storage, cloud desktops, and AI applications all eventually face that very human test.