Mike Wolfel and the Work Between the Screens

Consider the customer who walks into a bank carrying a loan offer. The letter is real. The offer is real. Yet the employee at the desk cannot find its terms in the software meant to serve the customer. One system knows the person. Another knows the account. Somewhere in the back office, a third system remembers the letter. The banker begins the ritual of tabs, passwords and polite delay.

Mike Wolfel likes examples of this sort. They are modest enough to sound almost comic, and ordinary enough to be expensive. A customer should not need to understand the architecture of a bank in order to use one. A banker should not have to perform digital archaeology to answer a straightforward question. Yet the modern bank, polished on the outside, can still resemble a row of locked rooms behind the counter.

Wolfel is the CEO and CTO of Savana, a financial-software company in Malvern, Pennsylvania. His job titles place him in both the boardroom and the engine room. The combination fits a career spent worrying about the distance between an institution's promise and its machinery. His central idea is easy to describe: connect the core systems, employee tools, workflows and customer channels so that they act as parts of one operation. The execution requires years, patience and an uncommon affection for process maps.

“A simple customer address change can turn into a logistical nightmare.”Mike Wolfel, on the cost of disconnected bank systems

The education of a systems thinker

Wolfel did not study computer science. He studied economics at Penn State, earning a bachelor's degree in 1990. It is tempting to treat that as a detour before a technical career. It may be the straightest line in the story. Economics asks how information, incentives and scarce resources move through systems. Software architecture asks much the same question, though the arguments are conducted with interfaces, rules and data.

By 1991 he was chief technology officer at Novacom. Business development at Identitech followed in the late 1990s. Then came three years in which he ran Wolfel Consulting Group while working as a consultant and software architect for GMAC Commercial Mortgage. The overlap is revealing. He was learning the trade from both sides: how complicated financial work is performed and how technology is sold as the cure for it.

At Epitome Systems, where he served as senior vice president and CTO from 2003 to 2009, the vocabulary of the later Savana years came into focus: business process management, case management, content and automation. These are not technologies that excite dinner parties. They are the means by which work remembers what happened before, knows what must happen next, and notices when a rule has been ignored.

A company changes its center of gravity

Wolfel joined Savana in 2009 as CTO and executive vice president of strategy. For its early customers, the company built workflow solutions that stitched together disconnected product lines and systems. The work began close to the problem: individual processes, individual institutions, specific seams. Over time, those seams revealed a larger pattern. Banks did not merely need another point solution. They needed an operational layer capable of making many useful but isolated systems cooperate.

He became president and CTO in 2019, then CEO and CTO in August 2022. The promotion came in the same month as a major funding round that gave Savana room to expand product development and its market reach. By then the company had worked with early adopters long enough to turn bespoke lessons into a broader platform. Wolfel described the investment as validation of both the strategy and the system's value. More importantly, it funded the unromantic work of making the architecture usable across more banks and credit unions.

The five-week figure carries the argument better than a brochure. During the Paycheck Protection Program, Savana launched a new loan-servicing experience in less than five weeks after changing its user-experience development approach. Wolfel said the method had dramatically accelerated time to market. The point was not merely that a team had worked quickly during a crisis. Reusable processes and a flexible experience layer made speed less dependent on heroics.

The bank behind the banking app

Much of digital banking's public competition takes place on glass. Apps become cleaner, buttons move, balances appear a little faster. Wolfel's argument begins when the customer leaves the app and calls for help. Does the call-center employee know what the customer just attempted? Can a branch worker continue a process begun online? Do the same rules govern an assisted transaction and a self-service one?

If the answers are no, a beautiful interface has decorated a fragmented institution. The customer experiences the fracture as repetition: explain the problem again, provide the information again, wait while another employee opens another application. The employee experiences it as uncertainty. The bank experiences it as manual work, inconsistent controls and missed opportunities.

Savana sits in that missing middle. Its banking APIs do more than move data. They carry the logic, permissions and sequence of a process across cores, third-party tools and channels. A banker can see customer context in one place; a customer can move between self-service and assistance without the process forgetting its history. The company calls this orchestration. In plainer English, it means the bank's software has learned to pass the baton.

Renovation without the wrecking ball

Wolfel is careful about the romance of replacement. Some banks need a new core. But a core conversion alone does not reconcile the systems that have accumulated around it. Each was added for a reason, often to launch a product or meet a new customer expectation. Years later, the additions can resemble an apartment with too many extensions and a light switch nobody dares touch.

He describes two paths. A bank can attempt a big-bang conversion, replacing the core in one consequential move, with the risk and ecosystem rework that entails. Or it can renovate progressively, accepting a period in which customer and account data may be divided across old and new cores. Neither path is a shortcut. In Wolfel's telling, the crucial decision is to define the complete end state before optimizing one channel in isolation.

“Having a clear vision of the full end-state ... is the critical consideration.”Mike Wolfel, on planning a bank transformation

That view shaped Savana's work with Woodforest National Bank, whose conversion reaches from the core through the call center, back office and branch. Wolfel called the project near the outer edge of Savana's usual implementation timetable. It is a revealing admission. The salesman's instinct is to make transformation sound brisk. The architect knows where the walls are load-bearing.

He also refuses to blame the core for every institutional frustration. Legacy cores were extended because banks needed them to do more. Point solutions solved immediate problems. The chaos emerged from success without coordination. Wolfel's prescription is an operational layer that allows those investments to participate in common processes, while leaving room for the underlying systems to change.

Intelligence with a memory

Wolfel's more recent public thinking turns toward active intelligence. He has argued that bank experiences should use customer behavior and context to surface useful actions, much as familiar consumer services recommend relevant material. Yet his version of intelligence is grounded in continuity. A recommendation is of little value if the banker cannot see it when the customer asks a question, or if an assisted channel cannot continue what a digital channel began.

This is why his future of banking still contains branches and call centers. The pandemic forced institutions to improve digital access, but it also exposed how much operational work remained. Wolfel observed that the transformation agenda widened from the consumer interface toward next-generation cores and more efficient internal systems. Digital did not abolish the human channel. It raised the cost of making that channel ignorant.

The aspiration is a bank with memory: one that recognizes the customer, preserves the thread of an interaction and gives employees enough context to be useful. Savana's current platform extends that idea across personal and business banking, account opening, servicing, case management, communications and multi-brand operations. It is technical scope in service of a social courtesy: nobody should have to introduce themselves twice to their own bank.

The dignity of invisible work

There is no cinematic moment when orchestration succeeds. A workflow routes correctly. A permission is respected. A banker sees the relevant history. A customer changes an address and goes on with the day. Infrastructure is praised mostly in its absence, when the ordinary becomes an ordeal.

Wolfel has arranged a career around those quiet moments. The economics graduate became an architect; the architect became an operator; the operator kept the architect's title after becoming chief executive. Across the changes, the problem remained stubbornly consistent. Financial institutions contain decades of decisions, technologies and obligations. The task is not to pretend that complexity away. It is to keep complexity from becoming the customer's burden.

A bank should feel like one bank. In Wolfel's world, that sentence is less a slogan than a very long to-do list. Somewhere near the top is the customer with the loan letter, still waiting for the systems in front of the banker to agree.