RAGE Frameworks made the paperwork move.

Forty-five days after a quarter ends, an investment report tells you what you owned. It is an oddly patient arrangement for a business concerned with money. In a 2015 account of a Celent case study, RAGE Frameworks described a large American financial institution facing precisely this delay. Its answer began with the incoming paperwork.

The institution’s information arrived from custodians with different systems and smaller funds using spreadsheets and email. Before an adviser could explain performance, someone had to make those inputs agree. The first obstacle sat upstream of the advice: assembling a trustworthy picture of the assets.

RAGE’s LiveWealth standardized those inputs. The company reported that the institution’s client reporting cycle fell from 45 days after quarter-end to same-day or on-demand, alongside 75% operating cost savings. Those are results from one customer account. Their appeal is easy to understand: the report became useful while the conversation was still happening.

For a wealth manager, this is a customer-service problem with a data problem inside it. A consolidated report must include assets held elsewhere as well as those already visible in the firm’s own systems. The fragmented input becomes the customer’s wait. Improving the report therefore requires reaching beyond the reporting screen.

The man who disliked the translation

Founder Venkat Srinivasan came to software through finance. He had taught at Northeastern University and built eCredit, a business concerned with credit and financing decisions. His expertise combined financial judgment with knowledge-based systems and computational linguistics. That combination made him attentive to the distance between deciding how a business should work and getting a computer to do it.

In a 2009 Knowledge at Wharton interview, he described a financial institution that estimated an 18-month rollout for a credit card. RAGE, he said, implemented it in two weeks. Treat that as the founder’s account, rather than a delivery timetable for every bank. The revealing part is his explanation: gathering applicant information, normalizing it and applying the institution’s rules were reusable operations.

“The process is its product.”

Venkat Srinivasan / Knowledge at Wharton, 2009

His objection concerned the repeated translation of a business description into technical specifications and code. RAGE proposed keeping the business process as a live, editable model. Change the rules or flow, and the implementation could change with it. The ambition was to make a working system less resistant to its owner’s next idea.

Reading is only the first step

RAGE’s architecture joined two jobs that are often discussed separately. RAGE AI interpreted information. RAGE Enterprise supplied the operational machinery: aggregation, integration, cleansing, normalization, reconciliation and workflow. A document could enter a process that also managed exceptions, escalations and the action that followed.

That distinction explains its market position. A text extraction tool can pull a number from a statement. A lending operation must also associate that number with the right borrower, standardize it and use it in a controlled decision. RAGE sold an approach spanning those dependencies, with financial-services expertise attached.

By 2016, the product family included LiveSpread for financial statements, bank statements and tax returns; LiveWealth for asset aggregation; and Real Time Intelligence for market, credit and supplier monitoring. KYC and contract-review frameworks addressed other document-heavy work. RAGE emphasized linguistic context, transparency and auditability in describing its AI.

The customer list described in company announcements extended beyond banking to manufacturers, consultants, technology companies and logistics businesses. The common ground was information arriving in inconvenient forms. These were enterprise deployments, sold to organizations with existing systems and operating obligations. The product had to work inside that reality.

A loan with editable rules

At FinovateSpring 2015, RAGE demonstrated LiveCredit. It covered origination, underwriting, booking and servicing. Its product configurator was intended to let financial institutions change financing products, pricing, compliance rules and accounting without programming each change from scratch.

That put RAGE between conventional workflow software, bespoke development and the manual processing those systems often left behind. Its competitive argument was flexibility across a complete business process. Customers still needed to know their lending rules. RAGE offered a way to put those rules to work and revise them.

The commercial model matched the enterprise setting. In January 2016, RAGE described subscriptions for both preconfigured and custom AI solutions. Transaction materials also described managed services. Buying the platform meant buying into an implementation relationship: connecting data, representing policies and maintaining a functioning process.

The distinction between subscription and savings matters. A lower operating bill at one institution does not tell another buyer its software budget or payback period. The business case has to begin with that buyer’s workload, integration effort and cost of reviewing exceptions. Faster reporting is valuable only when the resulting figures remain useful.

The buyer had already tried the partnership

Genpact and RAGE announced a partnership in November 2015. Genpact brought operational knowledge and customer relationships; RAGE brought its automation platform. By the acquisition announcement, they described joint work on management reporting for an insurer and a consumer goods company, plus financial spreading for institutions.

On March 14, 2017, Genpact announced its agreement to acquire RAGE. The purchase closed on April 13. Genpact’s subsequent financial reporting put the consideration at approximately $125.3 million after adjustments. This was an acquisition price, separate from the reported $15 million in growth capital RAGE had raised from Kayne Partners in 2013.

In June 2017, Genpact launched Cora, bringing together capabilities from RAGE, PNMsoft and other acquisitions. Its earnings discussion explicitly placed LiveWealth inside Cora. The earlier partnership had given way to ownership and a broader distribution platform.

Seen this way, the deal joined a specialist’s technical approach to a service company already embedded in business operations. Genpact could bring the capability to more engagements. RAGE’s software gained a home where automating an established process was already part of the commercial conversation.

Start with the waiting

There is a useful discipline to copy here. Pick a decision people already need to make. Follow the incoming information. Measure the delay caused by collection, mismatched formats and reconciliation. Then build the workflow around the answer, including the awkward cases that require review.

That approach depends on accessible information, explicit rules and people accountable for exceptions. When policies are unsettled or inputs cannot be trusted, faster processing can simply move uncertainty along. The lesson of RAGE’s reporting case is practical: intelligence earns its place when the work surrounding it becomes dependable enough for somebody to act.