In 2009, Alfa Life described a small administrative miracle. An application arrived, a medical-information check was ordered, an underwriter received the file, and the administration system recorded it as pending. The whole sequence took less than a minute. Nobody had invented a new kind of insurance. The company had connected the steps that used to keep insurance waiting.
- StoneRiver sold insurers the software behind applications, underwriting, policies, claims and billing.
- Its customer stories turn on a practical problem: work getting stuck between systems and people.
- Sapiens acquired the business in 2017. LifeSuite’s lineage continues as UnderwritingPro.
Alfa’s previous process was manual and sequential. A case needed to move through one person before another could work on it. Its IT director wanted several people to work on the same case, with less paper. StoneRiver’s LifeSuite underwriting system and Life Portraits electronic application tools helped make that possible. The useful innovation was cooperation at the level of the workbasket.
“When agents see the difference in time-to-issue between electronic processing and paper, they all want electronic.”
Allen Foster · Alfa Life · 2009
A company hiding inside the handoff
StoneRiver occupied a part of the technology industry that consumers rarely see. Its buyers were insurance organizations; its users included underwriters, agents and operations staff. A person buying coverage encountered the result, rather than the vendor. The product was infrastructure for promises that an insurer might have to keep for decades.
The portfolio reached across property and casualty, life and annuities, workers’ compensation, reinsurance, and financial compliance. Policy administration kept contracts in order. Billing managed what was owed. Claims software handled what happened when the promise came due. The company’s expertise lay in these particular jobs and the connections between them.
Its life insurance products made the sequence especially easy to understand. Life Portraits illustrated a proposed purchase. LifeApply captured the application and signature. LifeSuite managed underwriting and the new-business case. Sapiens later called those products IllustrationPro, ApplicationPro and UnderwritingPro. The names changed; the sequence remained recognizable.
- 01IllustrateLife Portraits
- 02ApplyLifeApply
- 03UnderwriteLifeSuite
The deadline that slipped
SECU Life wanted members to receive a decision while they were still in the office. Its business model used simplified underwriting. StoneRiver’s customer case study describes an integrated installation of illustrations, electronic applications and automated underwriting, supported by connections to evidence providers.
The first estimate was six months. Production arrived after ten, in October 2013. That is the revealing wrinkle: the implementation timetable gave way before the desired customer experience did. Even buying connected products did not make the installation instantaneous.
Historical implementation timing, as reported in StoneRiver’s customer case study.
The same account reported that 1,700 agents could quote, complete an application and deliver a decision in under 15 minutes. Two underwriters supported the operation. Those figures describe a particular insurer and product model. They are useful evidence of what connected processing could accomplish, rather than a stopwatch guarantee for every insurance application.
Buy the workflow, then test the fit
The ivari case supplies another clue. Its older underwriting tool functioned largely as a notepad. It lacked the workflow and connections the insurer wanted, restricted users, and had no technical support. Paper files moved between desks before being scanned. An underwriting rule could be perfectly sensible while the process surrounding it remained cumbersome.
According to the Sapiens case study, ivari spent approximately a year assessing vendors. Competing presentations did not demonstrate the required workflow and data exchange. Visits to other users helped, and ivari continued its relationship with Sapiens. Before building, the implementation team reviewed business processes, removed redundancies and trained staff in a model environment.
There is a copyable method here: follow an application all the way through the organization before choosing what to automate. Test the connections with real work. Give staff somewhere to practice. A faster decision engine has limited value when the evidence it needs is still waiting elsewhere.
Choosing the scope matters too. ApplicationPro’s product materials describe a standalone electronic application option as well as integration with illustration and underwriting tools. An insurer can address one part of the journey without replacing every core system at once. The trade-off is responsibility for the remaining connections: someone still has to make the whole process work.
The $102 million collection of details
StoneRiver itself came from a corporate rearrangement. In 2008, Stone Point’s Trident IV acquired a majority interest in Fiserv’s insurance businesses. The StoneRiver brand formally arrived in March 2009. This was an established collection of businesses receiving new ownership and a new name.
The broader historical group included activities beyond insurance software. Stone Point describes selling separate business lines and shifting software development toward phases tied to client adoption. That history matters when comparing company figures: the earlier group and the software business later purchased by Sapiens were different scopes.
In February 2017, Sapiens announced the software acquisition for approximately $102 million. StoneRiver brought more than 200 U.S. insurance customers, approximately 500 professionals and estimated 2016 non-GAAP revenue of $80 million. StreamSuite extended Sapiens’ offering for larger P&C carriers; workers’ compensation added another market.
The business model was enterprise software plus the work of making it useful: implementation, integration and continuing support. In P&C, buyers could also consider suppliers such as Guidewire and Duck Creek. StoneRiver’s appeal rested on its insurance-specific portfolio and installed relationships. In 2018, Sapiens combined StoneRiver’s Stream Claims with Adaptik’s policy and billing technology in its broader platform.
For a buyer, that makes the demonstration a starting point. The more useful questions concern what happens after an incomplete application, who receives an exception, and whether existing systems receive the result. Those are the moments when an attractive screen becomes an operating process.
The name recedes. The work continues.
Equitable Life of Canada went live with UnderwritingPro in October 2019. Current Sapiens materials describe configurable rules, evidence connections and automated handling of eligible cases, leaving complex work for underwriters. This distinction matters: a fast path needs suitable products, available data and agreed decision rules.
The ownership story continued too. Advent completed its acquisition of Sapiens in December 2025; an ADIA subsidiary became a significant minority shareholder in 2026. StoneRiver’s lineage now sits inside that larger business. Its enduring lesson is pleasingly concrete. Find the place where a file waits for the next person. Start there.