Brian O’Neill had a prospective customer who could not believe the price. The software was free, O’Neill explained. The customer remained unconvinced. In a business accustomed to invoices for sending invoices, this apparently required a personal visit.
O’Neill drove out and went through the office’s existing bill, line by line. By his account, it was paying $8,700 a month to send claims electronically. The same batch through Office Ally would cost $2.75, covering eleven claims that still needed to go on paper. The difference was large enough to make suspicion understandable. A bill that small might reasonably be mistaken for a printing error.
The episode captures his particular talent. He could write software, but he could also sit beside a skeptical customer and explain a bill. The technical proposition and the sales proposition belonged together. He wanted an office to try the service, see the arithmetic and keep using it.
His wager was that a useful service could earn its money from another participant in the transaction. Getting that arrangement to work would occupy much of his professional life. It began with an engineer asking friends a fairly ordinary question: how did they get paid?
An engineer discovers the post
O’Neill grew up in Ohio, earned a computer science degree and moved to California at twenty. His working life took him through defense contractors and large companies. IBM was his last Fortune 500 employer. Consulting assignments had given him a view of the machinery behind business operations, including the places where that machinery seemed to have stopped advancing.
Conversations with doctor friends brought one problem into focus. They mailed forms to insurers, then waited for a check or a rejection. The intervals they described could stretch from twenty to ninety days. For someone accustomed to moving information through computers, a payment process dependent on envelopes was a curious survival.
He hired contract programmers to develop electronic submission software. The design also checked entries for mistakes before they could become rejected claims. He founded Office Ally in 2000, offering the software free to the submitting offices. His first customer was St. Joseph’s IPA in Orange, California.
The attraction was straightforward: less retyping for the organization receiving the claim, fewer avoidable mistakes along the way and a shorter route through the paperwork. O’Neill had found a business problem with two ends. Solving it required both to connect.
The retirement account becomes the runway
He had written the software before securing the commercial agreement. That sequence put his own judgment, and then his own money, on the line. O’Neill said he cashed in his 401(k) and initially committed about $500,000. The funding came with an unusually personal measure of risk: savings accumulated for later life were paying for a new company.
A friend made the introduction to St. Joseph’s. O’Neill recalled demonstrating the processing of 500 claims in five minutes, work he said had occupied a five-person team for a day. Demonstration mattered because a prospective customer could watch the proposed improvement happen. The argument had a stopwatch.
Office Ally reached break-even in June 2003, he said. He also described a landlord being puzzled by the absence of a borrowing history when checking the company’s credit. O’Neill’s explanation was that he had never borrowed from anyone except himself.
That small rental anecdote gives the financing story its human scale. Running without outside loans had consequences even when the business needed something as ordinary as office space. Financial independence could produce an awkward pause on an application form.
A personal stake before a national network.
A quarter at the other end
At the start, St. Joseph’s paid twenty-five cents per claim. The office submitting the claim could use the service free; the receiving organization paid to avoid work in its own operation. The amount was small, but it applied to a task repeated many times. O’Neill had aligned the charge with a place where he believed the savings would be visible.
There was patience inside that arrangement. St. Joseph’s remained his only customer for roughly six months. The next customers followed, but the beginning was one relationship that had to function. A network starts with the rather unglamorous requirement that its first connection actually work.
By 2010, O’Neill described substantial word-of-mouth growth. About half of new business arrived that way, and the company was adding roughly 1,200 practices a month. He reported approximately $300,000 in revenue for 2001, $1.5 million for 2002 and $2.5 million for 2003. His forecast for the base business in 2010 was at least $19 million.
Those numbers describe different stages of a company learning to repeat its first transaction. The forecast was an expectation at the time, rather than a later audited result. Even with that distinction, the progression shows why the little charge at the receiving end deserved attention.
More desks, same practical questions
Growth acquired a physical address. O’Neill moved the company to Clark County, Washington, in 2009. Early the following year, its east Vancouver call center employed 76 people in sales and customer service, with about 22 software developers working in Irvine, California. He was talking about larger quarters and additional hiring.
The split is revealing: software development in one location, the people helping customers in another. The company’s work included persuading offices to adopt the service and supporting them once they had done so. A working connection still needed someone to answer a question about it.
O’Neill’s ambitions extended into other administrative tasks. Appointment reminders and checks on payment details were among the products he discussed in 2010. There was a consistent interest in moments when an office had to repeat a task, wait for information or correct something that should have been right the first time.
Asked what he intended to do with the business, he said: “I enjoy solving problems and that is what we are doing.” It is a plain description of an occupation, and a useful explanation of why a programmer might keep finding more work after the original program was finished.
“I enjoy solving problems and that is what we are doing.”Brian O’Neill · 2010
The blue-ink exception
Electronic business did not mean the end of paper. O’Neill described an enrollment process that required him to sign forms in blue ink before they were mailed for approval. The person selling a faster route through administration still had to pick up a pen.
He said approval could take six to eight weeks, with more than sixty percent of the forms his company submitted being rejected. These were his descriptions of the process in 2010. The details matter because they locate his frustration in an actual sequence of actions: prepare, sign, post, wait, correct, repeat.
Blue ink makes an excellent supporting character in a software story. It is cheap, familiar and capable of holding up an expensive system. O’Neill could automate one stretch of a transaction and still encounter a manual requirement farther along. His complaints were those of a builder whose work depended on organizations beyond his own control.
That tension helps explain the persistence in his career. A successful demonstration could establish that something was possible. Adoption required people, agreements and procedures to move as well. The computer could finish its part while everyone else was still finding the right form.
Twenty-one years, then a handover
On December 20, 2021, Francisco Partners announced its acquisition of Office Ally. The company was then processing approximately 25 million claims a month for more than 720,000 providers, with 4,000 payers in its nationwide network. The recurring transaction had become a substantial operation.
The announcement also marked O’Neill’s retirement. Chris Hart would become CEO as the transaction closed. After twenty-one years of building the company, its founder was handing responsibility to a successor with a different set of resources behind him.
O’Neill’s statement emphasized the employees’ part in the result and the opportunities ahead for the business. It was a fitting place to put the emphasis. The original software and the first sales demonstrations had grown into an organization serving a network far beyond its first customer in Orange.
The acquisition supplies a clear ending to his operating chapter. It also changes the meaning of the early financial gamble. Money taken from a retirement account helped fund a business he would eventually leave on retirement. Between those two events lay the daily work of making the arrangement hold.
What people kept
In August 2025, Office Ally announced O’Neill’s passing. Its tribute remembered his generosity, adventurous spirit and ability to bring people together. It also pointed to his support for Habitat for Humanity and Wounded Warriors. The company assembled photographs of him with colleagues and at a community building project.
People responding remembered humor and early conversations as well as the company. Jonathan Henderson recalled morning meetings in O’Neill’s Laguna Beach office and help getting his own billing business started. Such memories put a person back into a story that could otherwise disappear behind transaction volumes.
The company shared a line it attributed to O’Neill: “It’s not about the things you have, it’s about the experiences.” Beside the photographs, it reads as an invitation to count differently. A company can be measured in claims processed and customers connected. The people who knew its founder also remembered what it was like to spend time with him.
There is room for both accounts. One follows a computer scientist from Ohio into a business built around repeated, practical improvements. The other stays with the conversations, jokes and shared work. O’Neill made his living helping information get where it needed to go. Some of what people kept was considerably harder to put on a form.
