LATEST / 06 OCT
● Sarwaikar’s latest: build the foundation before deploying the agents● From the CIO’s office to the work after closing

People / The servicing years

Anupam Sarwaikar and the Work After the Mortgage

After years running mortgage technology from the inside, Anupam Sarwaikar founded Livegage to tackle servicing. His next question is how much responsibility to hand an AI agent - and what it needs to know first.

Advertisement

A mortgage is sold in a moment and administered for years. Anupam Sarwaikar built a company around the second part. The signatures get the ceremony; the reconciliation gets a spreadsheet. Somewhere in that unequal distribution of attention, the founder of Livegage saw work worth leaving his job to do.

His route into entrepreneurship ran through the machinery he now wants to improve. He had spent years responsible for mortgage technology, with a view across the businesses that make, service and invest in loans. By 2021, he had reached a conclusion about where to take that experience: a separate fintech devoted to residential mortgages.

There is a pleasing inconvenience in this origin story. Familiarity with an industry can make a person comfortable. In Sarwaikar's account, it made him restless. He knew the processes, the people responsible for them and the limitations they worked around. The opportunity was hiding in the jobs everyone already knew needed doing.

The engineer before the founder

Sarwaikar's early work included a token-predictive model for the C programming language, using language compiler theory. Long before the current enthusiasm for language models, his career involved the problem of what comes next in a sequence. His mortgage technology experience subsequently included Goldman Sachs, C-BASS and Black Knight.

At Roosevelt Management Company, he became enterprise chief information officer. His remit encompassed technology for capital markets, servicing, origination and real estate owned management. Twelve years across those operations meant seeing a loan from several institutional angles. A decision that looked tidy in one department could have consequences in another.

He also founded Roosevelt's in-house technology business, Potomac Technologies, and ran it with its own profit and loss responsibility. He grew its team from two employees to 250 over five years. That was an apprenticeship in building an organization as well as software: payroll and customers have their own way of marking homework.

Anupam Sarwaikar in a suit, in the photograph accompanying his Indian Angel Network biography
An earlier chapter, with a tie: the photograph accompanying Sarwaikar's Indian Angel Network profile.

He studied at Samrat Ashok Technological Institute and holds a bachelor's degree in electronics engineering. The technical education and the operating responsibility belong together in this story. He came to the founder's job having already been responsible for systems other people needed to keep working.

A relationship longer than the sale

When Sarwaikar explained Livegage's beginnings in October 2025, he returned to the mismatch between the attention paid to originating a mortgage and the work of servicing it. He described a quarter century in mortgages and more than a decade as an enterprise-wide CIO. The accumulated frustration had become a reason to start again.

His proposed business had an important condition: its products should work around existing systems of record. Customers would still have their core platforms. Livegage would supply additional capabilities, with savings substantial enough to justify another bill. For a founder arguing for fundamental change, that is a practical place to put the ambition.

“My frustration led me to quit my job”

Anupam Sarwaikar, “It's Time,” October 2025

The words are blunt enough to survive without a motivational poster. He was describing a professional decision rooted in a particular market. Servicing was the part of that market he wanted to change, and a fintech was the organization he chose to attempt it.

The distinction matters for understanding his career. Leaving an employer did not mean abandoning the subject that had occupied him for years. It meant taking responsibility for a different kind of answer. A founder must persuade someone else to buy the solution that once existed mainly as a frustration.

What the work actually looks like

The products give that answer some texture. COMPLAI is designed to monitor mortgage servicing compliance, organize loan-level work and identify potential problems before deadlines are missed. Livegage describes countdowns to possible breaches, rule management and automated testing across a portfolio. The intended user has a queue to clear, with consequences attached to the order and timing.

That is a revealing choice of terrain for an AI entrepreneur. A pleasing paragraph from a machine is one thing. A useful warning that lets an employee act before a servicing requirement is missed is another, specific task. The product has to fit the day of the person expected to respond to it.

RECONCAIL addresses investor accounting. Its central process compares the servicing system, cash movements and bank accounts. Livegage offers modules for bank reconciliation, remittance reporting and servicing fee calculations. Think of three accounts of the same financial activity being asked to agree. The drama is quieter than a product launch, but the disagreement still needs an answer.

The reconciliation problem / simplified
Servicing
records
Cash
movements
Bank
accounts
↓ Compare transactions ↓
Investigate the exceptions
Three versions of the money story. RECONCAIL is designed to bring them into agreement.

There is a recognizable thread here: direct a person's attention toward the items that require judgment. An accounting team should be able to spend time investigating a mismatch. A compliance team should be able to deal with an approaching problem. Software earns its place when those working decisions become easier to make.

Data integration sits underneath both ambitions. Livegage's ENLAIT offering combines mapping, warehousing, analytics and reporting. Its stated purpose includes making scattered information available consistently across departments. That may sound like supporting work, until a report depends on a field another system has named differently. The plumbing gets interesting the moment the tap fails.

VAIDA, the company's mortgage-focused natural language processing engine, supplies another part of the foundation. Livegage describes training it to interpret documents, guidelines, regulations and internal procedures. The company associates its name with the Sanskrit word for knowledge. In this business, knowledge has a rather practical destination: the next action on a loan.

The people who recognize the problem

Sarwaikar's recruitment choices extend the same argument. In August 2025, Livegage appointed Michael Blair chief operating officer. Blair had held operating leadership roles at LoanCare, Cenlar and KeyBank. His responsibilities at Livegage included product suites for servicers and investors, client outreach, and an implementation center of excellence.

Implementation is an unglamorous word with a large job. It covers the distance between a product someone agrees to buy and a tool employees can use. Giving that work to an experienced operator fits Sarwaikar's insistence that mortgage knowledge belongs inside the company building the technology.

Blair's own account of joining Livegage dwells on work he had done in servicing: compliance, documents, investor accounting and exception management. He describes having participated in modernization efforts within servicing businesses and wanting to address familiar constraints from a different position. The founder and the operator arrived at the company carrying overlapping professional questions.

The advisory board announced in July 2025 adds other perspectives. Its members included Matthew Chua, Jack Navarro, Kira Vanderwert, Matthew Whalen and Ike Suri. Their experience spans mortgage investing, servicing, company building and fraud prevention. A mortgage business involves several parties looking at the same asset with different responsibilities; the board reflects that variety.

The connections also put Sarwaikar's venture in a recognizable professional world. His argument has to make sense to people who have run servicing operations and evaluated mortgage investments. They know what a handoff costs. They know that a feature is only part of the answer when several organizations must exchange information and money.

An investor's interest in what changes

There is another angle to his professional life. Sarwaikar is an individual member of Indian Angel Network. His stated interests include disruptive technologies and their potential effects on the American mortgage and financial markets. They also include social impact investing and human capital development across economies.

During his Potomac and Roosevelt chapter, Potomac had a presence in New York, Mumbai and Indore. The business connected technology development across those cities before Livegage became his central public role. His interest in new technology was already connected to established financial institutions and to the question of what technology could change.

It is tempting to turn every founder's earlier experience into a perfectly straight road. Careers rarely oblige. Here, the continuity is concrete enough without that convenience: technical work, enterprise responsibility, a technology business inside an investment organization, and then an independent company serving a market he knew.

First, give the agents a floor

By October 6, 2026, Sarwaikar was writing about deployment order. He reported a team of more than 200 mortgage technologists and said Livegage products ran at organizations managing over a trillion dollars in mortgage balances. Those are his descriptions of the business's scale, rather than figures for Livegage's own assets or revenue.

October 2026 / founder-reported team200+mortgage technologists at Livegage

His essay's more interesting detail is the sequence. Rules and document understanding come first; operational products provide the next layer; agents follow. He describes agents taking tasks from shared work queues, with human involvement where regulation touches a loan and autonomy limited to task types the client releases.

There is a former CIO's concern running through that account: someone will eventually ask why an action happened. An agent needs an answer grounded in the work it was authorized to do. The excitement of automation does not remove the need for an intelligible record.

Sarwaikar has spent much of his career close to that question of responsibility. His founder's project gives it a new setting, but the standard remains familiar. When a loan needs attention, a payment needs matching or a requirement needs meeting, someone has to know what happens next. He has chosen to build a business there.

Follow the work