Kent Sacia has been working on a problem that rarely earns a standing ovation: getting numbers into a condition where somebody can use them. Before a chart can persuade a room, somebody has to check the records behind it. Before software can simplify a decision, somebody has to untangle the work. There is little glamour in a duplicate entry. There can be considerable trouble in leaving it there.
Sacia joined Milliman in 1996. He went on to found MedInsight and now serves as its chief executive. Across that span, the machinery has changed from mainframes and client/server systems to internet applications, cloud infrastructure and artificial intelligence. His career offers a long view of a familiar business predicament: acquiring more technology is relatively straightforward; making it useful takes rather more patience.
The interesting part is how often his work returns to preparation. Process design, data validation, benchmarks, partnerships, people. These are the things that happen before the polished demonstration. They are also the things a customer encounters after the demonstration has ended and the salesperson has gone home.
A founder with a migration history
Sacia's education connects two places: the University of Washington, where he is a graduate, and Carnegie Mellon University, where he earned a master's degree. His professional qualifications include a Master of Science in Industrial Administration. The combination gives his career a useful frame: technology on one side, the administration of an enterprise on the other.
His work has included redesigning business processes, creating strategic systems plans, moving systems from mainframe environments to client/server arrangements, and managing the development and implementation of large internet-based systems. He has also created multiple commercial software products. That is a career spent dealing with both the machine and the organization around it.
A migration is a particularly revealing kind of assignment. The new system must do something worthwhile while the old business continues to operate. Dependencies that looked minor on a diagram can become everybody's afternoon. Experience across successive generations of systems supplies a perspective that a launch announcement cannot: every new architecture eventually becomes the architecture somebody else must maintain.
In 2000, Sacia launched MedInsight. The product launch gives this story its turning point. A consultant's work was becoming a continuing software undertaking, with the responsibilities that come from having customers return to the same product over time.
The record before the revelation
By 2013, Sacia was talking publicly about a MedInsight business maintaining and processing more than 15 billion records. That figure is a historical snapshot, rather than a current total. Its value here is to show the size of the engineering task at that point in the company's life.
The accompanying initiative concerned data confidence. MedInsight had been developing its Data Confidence Model since 1997. The process combined automated checks with manual work, looking for irregularities as data entered a warehouse and continuing to examine it afterward. The checklist covered inconsistent formatting, duplicate records, relationships between data components, and whether volumes and calculated results made sense.
There is a pleasingly unromantic quality to that list. A duplicate is hardly a philosophical emergency. Multiply the opportunity for duplication across a large system, however, and a modest clerical nuisance becomes an engineering concern. The promise of analysis depends on many such small matters being handled correctly, repeatedly, without demanding a round of applause.
In the 2013 announcement, Sacia connected the scale of the records to the need for sophisticated management techniques. The association is instructive. More data creates a larger obligation to check it. A warehouse can contain a great deal of information and still leave a decision-maker with a perfectly reasonable question about whether to believe the answer.
Buying a wider field of view
In August 2020, Milliman acquired Torch Insight from Leavitt Partners. For Sacia, the attraction was complementary information. MedInsight could help clients analyze their own records; Torch Insight added information about the surrounding market, competition and partner relationships.
Torch Insight's team had linked thousands of data elements from public and proprietary material. The work included cleaning, validating and joining separate datasets. Once again, an expansion in analytical ambition rested on the less theatrical business of making different pieces fit together.
The acquisition adds another dimension to Sacia's career. Building a product involves deciding what to create internally, what to connect to, and what another team has already spent years understanding. Buying complementary capabilities can change the questions a customer can ask. Internal performance looks different when there is a wider environment against which to examine it.
Sacia called the two offerings “incredibly complementary to each other.” The language was enthusiastic; the underlying idea was practical. A clearer picture of one's own organization becomes more useful when the frame includes what is happening outside it. Even a very carefully cleaned window benefits from having something to look at.
Trust acquires a security team
The following year brought a different kind of milestone. In February 2021, MedInsight announced HITRUST certification for its solution. The announcement described more than 300 organizations entrusting it with data. Sacia emphasized the responsibility involved and the continuing work of responding to new threats.
“We are constantly working to advance our security posture as new threats emerge,” he said. The sentence carries a useful refusal to declare the job finished. Certification marks a point of external validation. The work described around it continues beyond that point.
This is another part of a founder's job that tends to be absent from the romantic version. Keeping a software business going involves obligations that expand with adoption. Customers bring expectations about access, protection and continuity along with their technical requirements. The more embedded a product becomes, the less its users can afford to regard it as an experiment.
That continuing responsibility gives the word trust a concrete meaning in this story. It involves records arriving intact, access being managed, and safeguards being examined. The reassuring sentence in a sales conversation needs an organization behind it, with people able to keep doing the necessary work after the conversation ends.
The company gets more company
By June 2023, Sacia was describing an alliance program intended to broaden the reach of MedInsight's work. Microsoft, Databricks and Epic were among the organizations named. Scott Ponder, then vice president of strategic alliances, described partners combining MedInsight capabilities with their own offerings.
For a founder, that changes the shape of the enterprise. Product development includes the connections through which other businesses can use what has been built. A customer may encounter the company's capabilities inside a wider workflow. Cooperation becomes part of how the product reaches the desk where a decision is made.
The next major architecture announcement, in September 2024, made the infrastructure partnerships concrete. MedInsight described a new data lake and warehouse architecture involving Databricks and Microsoft Azure. It also described a move toward a platform-as-a-service approach, giving customers more direct control over customization and their data environments.
The company reported processing that previously took days or weeks being reduced to hours. Those were its stated benefits of the new infrastructure, rather than a universal guarantee for every assignment. More revealing for Sacia's story is the continuity: another generation of technology, another effort to shorten the distance between information arriving and somebody being able to act on it.
For customers, control is an interesting part of that change. A platform that allows people to run their own models creates room for questions its original designers may never have anticipated. The founder's product becomes a place where somebody else can build. That asks a software organization to think about both its own ideas and the working space it leaves for others.
Giving other people the verbs
In February 2026, Iyibo Jack became chief product officer, succeeding Rich Moyer after more than two decades of Moyer's contribution to MedInsight's growth. Moyer would continue at Milliman on other innovation work. Jack had already helped guide MedInsight's product development and cloud migration.
The new remit included the product vision and roadmap, expanding the platform, and embedding AI to improve client experience and productivity. Sacia's endorsement stressed Jack's experience with analytics, machine learning and product innovation. A founder still running the business was placing the next product chapter in the hands of a colleague who had helped build the previous one.
Sacia's public comments about colleagues offer a smaller, more personal detail. Celebrating the team's work on LinkedIn, he wrote: “Proud of our team's deep dedication to product and service excellence!” The wording fits a public pattern of directing attention toward employees and their work. His employee-appreciation post also connected the team to the company's relationship with clients.
Across these episodes, Sacia's career comes into focus through the things he has helped put in place: systems, checks, acquisitions, alliances and leadership responsibilities. The grand reveal in a software demonstration lasts a moment. The work that lets customers return tomorrow has a much longer running time. Sacia has spent decades in that second act.