Huron makes the complicated work.

The most revealing sentence in a story about enterprise software concerns something wonderfully ordinary: paychecks. In Huron’s account of a Workday implementation at the University of Kansas Health System, Tammy Shepherd says, “Hospital operations continued, and everyone got paid.” It is a useful place to begin understanding a consulting company. Behind the language of transformation sits a practical obligation: change the institution while the institution keeps working.

The work behind the work

The Kansas health system’s trigger was a legacy system approaching retirement. Huron helped select and implement Workday over two years. The published case reports that 18 legacy systems were terminated, producing $2.5 million in annual savings. Those are savings from retiring systems, not a disclosed implementation price or a calculation of net return.

Consider the difference between those measures. A completed installation tells you that software arrived. A retired system tells you that an organization has stopped paying for part of its old way of working. For a buyer, that distinction makes the business case much more concrete.

A company born between institutions

Huron’s origins also concern the relationship between institutions and the people who know how they work. Formed in 2002, the firm began operations with a group composed primarily of former Arthur Andersen partners and professionals, including Gary Holdren. Investors led by Lake Capital supplied equity sponsorship.

The founding argument was independence. Huron’s IPO prospectus explained that a consultancy unaffiliated with an accounting firm could avoid restrictions on selling certain non-audit services to audit clients. It was a structural choice about which problems the new business could accept. The company completed its IPO in October 2004.

Its own controls later became a problem. In 2009, Huron announced a financial restatement and senior management changes. The issue involved accounting for payments redistributed by sellers of acquired businesses. A 2012 SEC settlement imposed a $1 million penalty over reporting, books-and-records, and internal-controls violations. Huron settled without admitting or denying the factual findings. That history belongs in any assessment of a firm selling operational judgment.

Buy the system. Change the work.

Today, Huron operates across healthcare, education, and commercial markets. Its technology work covers enterprise resource planning, customer relationships, financial planning, electronic health records, data, and AI. Strategic technology partners include Microsoft, Oracle, Salesforce, and Workday. In practical terms, a client can hire it to help connect a technology choice to finance, staffing, reporting, and daily workflows.

The competitive field is crowded. Major accounting firms’ advisory practices, specialist consultancies, systems integrators, technology vendors, and internal teams all address parts of these problems. Huron’s proposition combines industry knowledge with implementation and operational support. That combination is useful when a buyer needs several kinds of work coordinated. It still leaves the buyer with a demanding question: which team can deliver this particular change?

The university has a back office, too

Research offers a particularly clear example of Huron’s niche. Scientific work depends on administrative work: proposals, funding, agreements, approvals, and compliance. Huron Research Suite is its own cloud-based software for research administration and compliance. Its research technology practice points to deployments at the University of Virginia and the University of Oregon.

Huron also sells Huron Research Office, a managed services offering incorporating that software. Mission Advance addresses faculty and provider management, funding tracking, and operational transparency at academic health centers. These offerings put Huron inside specialized institutional processes. A university buyer is purchasing help with a particular administrative workload, carrying its own rules and responsibilities.

There is a useful distinction here for anyone buying enterprise technology. The software feature list describes what a tool can do. The operating arrangement determines who will do the work, who will answer questions, and who remains responsible when an exception appears. Huron sells across both sides of that arrangement.

Four ways to send an invoice

Its business model reflects that range. Public filings describe fixed fees, time-and-expense billing, performance-based fees, and software support, maintenance, and subscriptions. Performance fees can depend on agreed outcomes or client-acknowledged savings. A prospective customer should therefore establish the baseline and the definition of success before treating a promised improvement as a budget item.

Huron reported $1.70 billion in total revenue for 2025, including reimbursable expenses, and served more than 2,000 clients worldwide. Its first-half 2026 revenue before reimbursable expenses split was 50% healthcare, 29% education, and 21% commercial. The mix helps explain why hospital operations and university administration feature so prominently in its work.

In June 2026, Huron acquired RelateCare, adding patient access and clinical care coordination capabilities. The acquisition announcement did not disclose terms. This extends the firm’s involvement into activities such as scheduling and triage. In July, Huron raised its full-year revenue-before-reimbursable-expenses guidance to $1.85 billion-$1.89 billion. That range is a forecast.

People are also the capacity behind this model. Huron’s stated values include humility and intellectual curiosity, alongside collaboration and integrity. In September 2026, the company announced its sixteenth consecutive Consulting Magazine Best Firm to Work For recognition, an award based on employee feedback. That is relevant to a buyer because retaining experienced teams matters in a long engagement. It is one signal to consider alongside the proposed team’s record and the contract’s actual commitments.

What survives Monday morning?

The copyable idea is to make continuity an explicit design requirement. Decide which services cannot stop. Assign owners to decisions. Include staff learning and knowledge transfer in the plan. Specify what gets retired. These are practical implications of the operating problems Huron addresses, rather than a guarantee that another organization will reproduce a client’s savings.

The approach needs leaders willing to settle disagreements and teams able to absorb new responsibilities. Where nobody owns the process, another implementation partner can become another layer of coordination. The useful test comes after the launch announcement: can people do the work, understand the system, and keep the institution running?