At nine in the evening, the question sounds reasonable. What should the business do tomorrow? Jack O'Hara has described the work required to answer it: collect information from seven systems, put it into Excel, add the organization's business rules, then perform the analysis. Tomorrow is approaching while the evidence is still being assembled. The spreadsheet, that faithful office companion, has become rather demanding company.
The scene is an example O'Hara uses to explain his business. It also provides a useful way into his career. He spent years responsible for technology inside large organizations before founding Translucent AI in 2024. His concern is the interval between an event and the moment someone can understand its financial consequences. A report can be carefully prepared and still arrive after the decision it was meant to inform.
There is a human scale to that interval. Someone has to gather the files, reconcile the figures, and explain why two apparently respectable totals disagree. Someone else is waiting to approve an investment or revise a plan. O'Hara's company is built around shortening that wait. The interesting part of his story is how much of his preparation happened before he had a company to pitch.
Eight years on the inside
His executive career included a regional CIO role at Mount Sinai, followed by service as CIO and later Chief Transformation Officer at Springfield Clinic. At ChenMed, he became Chief Information Officer. His public career biography describes eight years as a technology executive before Translucent, including leadership of more than 300 people across product, engineering, and AI at ChenMed. He also rebuilt that organization's financial claims system.
Those jobs put him on the receiving end of a difficult request: make the systems agree well enough for people to run the business. The titles changed, but the work connected technology with operations. A chief information officer has to consider what happens after a piece of software is installed. A transformation role adds another question: whether the organization actually works differently because of it.
In June 2024, O'Hara won the South Florida Enterprise ORBIE Award as ChenMed's CIO. The category covered organizations with more than $1 billion in annual revenue. It was recognition for his work as an executive, before Translucent's later funding announcements gave him a different public identity. In his acknowledgement, he credited people who had supported him and people who had challenged him. Both groups made his thank-you list.
He holds an MBA from Cornell University and a second graduate degree from Weill Cornell. The combination fits a career spent moving between business requirements and technical implementation. Degrees and job titles describe his preparation; the claims-system rebuild gives that preparation a concrete object. Before selling a new approach to financial information, he had been responsible for making an existing one work.
A company, then a larger cheque
Translucent began in 2024. Max Jones is its co-founder and heads operations. By August 2025, the company had announced a $7 million seed round, with NEA, Virtue, FPV Ventures, and Redesign Health among its backers. In March 2026 came a $27 million Series A led by GV, with NEA, Virtue, and FPV participating. The two announced rounds added up to $34 million.
Seven months separated the seed announcement from the Series A announcement. That is a compact financing calendar, though a funding calendar only records one kind of progress. The money gives the company resources to develop its product and expand its team. Its usefulness will be judged in the ordinary working hours of the people who subscribe to it, when a financial question needs an answer.
The company sells subscription software that connects information and automates financial analysis. Its current product includes views of workforce costs, profit and loss, budgets, forecasts, and contract economics. The ambition is to let a finance team investigate a change without first constructing the entire evidence trail by hand. O'Hara has moved from managing technology for one organization to trying to make a repeatable product for many.
That change brings a different test. Inside an organization, a useful workaround can depend on the person who knows where everything lives. A software company must turn enough of that knowledge into a service that another team can use. A tidy interface is the visible part. Beneath it lies the less photogenic work of connecting information and preserving its meaning.
Hiring people who have already started something
O'Hara has offered an unusually specific account of the team he wants around him. In a public post, he said more than 30 percent of Translucent's team were former founders, and about 80 percent of its leadership were former founders. Those were his figures at the time of the post, rather than a permanent description of the company. His stated preference was for people comfortable with ambiguity, speed, and responsibility from beginning to end.
A former founder brings experience of a particular inconvenience: a problem does not disappear merely because it belongs to another department. In a small company, responsibility can reach well past the edge of a job description. O'Hara's hiring comments suggest that he values people willing to follow a task through the awkward middle, when the plan is incomplete and the next step requires judgment.
He described building the team as one of the most rewarding parts of his job. That is a revealing emphasis from someone whose public business is automation. The people still matter enough to be a subject in their own right. His account of hiring places ownership beside technical skill, which is sensible for software expected to help other people make consequential decisions. A tool can produce an answer; a team has to stand behind the work.
“Focus relentlessly on solving a real, urgent problem for your customers.”Jack O'Hara
The code reviewer gets a desk
By August 2026, O'Hara was describing how Translucent used AI within its own operation. Its engineers had created a marketplace of specialized internal agents, organized around the roles of engineering, delivery, and sales. Each group received tools shaped around its work. This was a practical account of adoption: several teams, several kinds of tasks, and software arranged accordingly.
He also singled out an internal code reviewer as a favorite. He described it examining a change from multiple angles and bringing the results together in a way comparable to a senior engineer's review. His description focuses on the process of examining work, rather than simply generating more of it. For a company building analytical software, reviewing the product is an apt place to spend attention.
The detail connects with his earlier executive experience. Leading a large technical team and building tools for a smaller one both require decisions about how work moves. An engineering task, a delivery task, and a sales task have different constraints. Organizing agents by role acknowledges those differences. It also makes the company's internal use of AI easier to picture than a broad statement about becoming more efficient.
What a number needs to mean
O'Hara's writing in the summer of 2026 moved beyond the speed of reporting. In July, he argued that finance leaders needed a broader revenue strategy: a way to connect investment choices, contracts, capacity, and operational performance. Collecting money already earned and deciding how future revenue will be created require different kinds of attention. He wanted finance teams involved earlier in the decisions that shape the result.
He also described valuable financial expertise as an understanding of how the parts of an organization interact. The concern is familiar from his software brief. Information can be available in separate departments while its significance remains difficult to assemble. An analyst may know which question to ask because of years spent learning the connections. Keeping that understanding useful across an organization is part of the work he wants finance leaders to address.
In August, he made a related argument about expenses. Reading a cost line on its own can produce an incomplete decision, because that expenditure may also support revenue. Workforce costs provide a straightforward illustration. The relevant question can include what additional capacity earns alongside what it costs. Cutting a number is easy to describe; deciding whether the business is better off requires a fuller view.
Taken together, the essays show a founder concerned with context as well as calculation. Faster reporting is useful when the report helps someone understand the choice in front of them. A precise figure with the wrong frame can send attention in the wrong direction. O'Hara's writing asks finance leaders to consider the relationships behind the ledger, and to judge their function partly by the decisions it helps people make.
An October test, and an afternoon at the ballpark
On October 7, 2026, O'Hara announced a financial-intelligence partnership between Translucent and the University of Texas Medical Branch. The planned work spans financial reporting, performance management, and planning. It takes the company's proposition into another large organization, where information must become useful across different parts of the enterprise. An announced deployment is a new assignment, with the practical work still to do.
The partnership gives his earlier arguments a place to be tested. Can reconciliation consume less time? Can a shared view support a better planning conversation? Can an analyst spend more attention interpreting a result? Those are the questions suggested by the brief, rather than results established by the announcement. They keep the story close to the work O'Hara set out to change.
He has supplied one lighter detail about life in New York. Asked for his favorite spring destination around the city, he chose baseball at Yankee Stadium. It is a pleasingly specific answer from a founder whose working vocabulary includes forecasts and root causes. An afternoon at the ballpark offers numbers, arguments about performance, and the possibility that everyone will disagree about what the manager should do next.
O'Hara's next business chapter rests on a less leisurely version of that problem. He wants people to understand the numbers while there is still time to act. After executive roles, an award, two funding rounds, and a growing software company, the question remains close to the late-evening example he uses to explain it all. Tomorrow is coming. How much of tonight should be spent assembling the answer?