Amir Wain and the Business of Being Ready

Amir Wain stood in line for lunch with his employees. In his Lahore office, there were few of the decorative assurances that a visitor had arrived in the presence of someone important. The meal was free; waiting his turn apparently came with the position. In a business that sells the machinery behind other people’s money, it was a pleasantly ordinary scene.

That scene, observed in 2019, offers a way into a founder whose subject can otherwise sound forbiddingly abstract. Wain runs i2c, which supplies banking and payment technology. His work concerns what happens behind the card, beneath the app, before the reassuring word “approved” appears. Most customers will encounter the result without learning his name.

The founder in the lunch queue had already spent decades thinking about a problem with a rather personal sting: how to build something that does not require starting over. Custom software, packaged software, payments infrastructure, now artificial intelligence. The tools have changed. His interest in escaping the next unnecessary rebuild has proved remarkably durable.

Arlington, then a classroom of executives

Wain was born in Pakistan and went to the University of Texas at Arlington to study computer science and engineering. Arriving in an unfamiliar country meant learning outside the classroom as well as inside it. His early American jobs included IHOP and Burger King. Even a future chief executive must occasionally begin with somebody else’s menu.

During his last 18 months at college, he and a friend took on custom coding projects. He returned to Pakistan after graduation to be with his parents. By 1986, personal computers offered an opening: businesses could do useful work with an IBM XT and Lotus 1-2-3, provided somebody showed their managers what the machines were good for.

He began teaching a course introducing senior executives to computing. Referrals brought more business. Innovative Private Limited followed in 1987. The first sale, in this telling, required making a possibility understandable. Long before Wain was explaining configurable payment platforms, he was helping people see why they might want to change the way they worked.

The trouble with selling the same year twice

Success in bespoke software carried an awkward limit. Each assignment needed another assignment after it. Wain came to see that being paid for development time gave the business too little benefit from the intellectual property it created. A busy calendar could disguise how often the commercial engine needed another push.

The move into packaged software addressed part of that problem. His earlier company developed FastCash, a transaction-processing platform. Software could be sold to multiple customers. Yet licenses introduced their own complications: installations operated in different technical environments, while new sales still had to be found each year. Maintenance income softened the problem without settling it.

The appeal of software as a service was therefore practical. An ongoing relationship could connect recurring revenue with an ongoing obligation to make the system work. The business model and the customer’s experience became more closely tied together. Wain’s eventual payments company grew from this search for a more durable arrangement.

The progression is useful because it resists the tidy founder legend in which everything arrives fully formed. Wain changed the way he sold software as he learned where the previous model pinched. Staying interested in the underlying problem gave him room to change his answer.

A bank built with movable pieces

At the turn of the millennium, Wain founded i2c. Its organizing idea was a unified platform that could support different financial products and different markets. The architecture would begin with the customer and allow capabilities to be assembled around that relationship. A product launch would not automatically require an entirely separate technological household.

His favored analogy is Lego. A bank needs pieces it can rearrange as circumstances change. The comparison is disarmingly domestic for an industry fond of impressive diagrams. But it identifies a serious design choice: how much of tomorrow’s work can be accomplished by recombining what already exists?

In a 2016 discussion of digital banking, Wain used those building blocks to explain how institutions could respond to changing needs. The attractive part is the freedom to assemble different things. The demanding part is making sure the pieces continue to fit. In payments, experimentation still has to arrive at a working transaction.

The ambition extended beyond cards. By 2024, i2c was pursuing smaller banks and institutions outside the United States for its core banking services. Wain described a chance to consolidate services that a bank might otherwise operate across several platforms. For the founder, expansion meant bringing more of a client’s working day onto the same foundation.

Leave the crystal ball in its box

“I’m not going to be in the prediction business; I’m going to be in the ready business.”

Amir Wain · 2017

Wain offered that formulation in 2017. It is a useful line from someone paid to think about the future. A confident prediction invites a company to commit money and time to one outcome. A configurable system gives it a better chance of responding when customers choose another.

He returned to the point in a 2021 interview about financial innovation. An industry can dismiss an unfamiliar idea until demand makes dismissal expensive. His stated approach was to have the capacity to support a new use case when it arrived. Curiosity becomes more valuable when the machinery can act on it.

He also draws a commercial distinction between invention and innovation. A new idea has to become something people will use and a business can deliver. In his discussions with Karen Webster, innovation belongs alongside a company’s operating skills, rather than being entrusted to a separate laboratory and admired from a safe distance.

There is a restrained sort of ambition here. It makes fewer demands on anyone’s ability to guess correctly. It makes considerable demands on the quality of the preparation. Being ready sounds modest until one considers the engineering required to remain ready for a long time.

Pakistan was part of the design

Wain’s global outlook has coexisted with a substantial commitment to engineering in Pakistan. In a 2015 interview, he addressed prospective customers’ concerns about operating there directly, including questions about retaining staff. His argument was that competition for talent in Silicon Valley could itself create considerable risk. Geography deserved examination, rather than an automatic verdict.

The same conversation described a founder who responded to uncertainty by preparing for problems. There is a practical connection between that temperament and the platform he wanted to build. Both require asking what might go wrong before the reassuring sales presentation has finished.

His work beyond i2c includes chairing the Wain Foundation. At the University of Sargodha, the foundation agreed to support the Waheed Wain Incubation Center financially and professionally, with expertise from i2c. The university supplied space. Wain wanted the center to stand comparison with incubators in Silicon Valley.

The arrangement gives his interest in entrepreneurship a physical address beyond his own business. Students need somewhere to test a venture, access to experienced people, and help turning an idea into work that somebody values. Providing those conditions is a concrete extension of a career that began by showing executives what a computer could do.

The small humiliation of a declined card

In March 2026, Wain spoke with Peter Renton about a moment familiar to anyone whose payment has failed: the authorization decision. The discussion considered how more context could help institutions handle that encounter, balance fraud prevention with unnecessary declines, and preserve a customer relationship at the point when it becomes uncomfortable.

That is an unusually human test for a technical architecture. A customer experiences the interruption, while the institution has to decide whether it is protecting the account or frustrating its owner. Better information matters because the same short refusal can conceal very different circumstances.

By then, Wain’s conversations also included AI agents acting for customers. In a November 2025 discussion with Samee Zafar, he explored agentic AI, tokenization and digital assistants. His emphasis remained on what a business wanted to accomplish. A technology acquires a purpose when it can take care of a task that matters to somebody.

That interest also appears in his other roles. Wain chairs the board of xiQ, an AI sales and marketing platform, and is a limited partner in venture funds focused on business applications of AI and machine learning. The applications differ from payments, but they keep him close to questions about turning information into useful action.

Who answers when the agent acts?

The public recognition arrived too. In June 2026, Wain received a Silver Stevie in the AI Leader of the Year category at the American Business Awards. In July, i2c announced his recognition as Fintech Leader of the Year in Juniper Research’s Future Digital Awards for Fintech & Payments.

His own reaction to the Stevie was characteristically guarded. On LinkedIn, he expressed skepticism about trophy posts, then explained why independent judging made this recognition worth sharing. He credited the team and clients. The acknowledgment took up less room than the people behind it.

In September 2026, his discussion of autonomous systems included an admission that i2c was still piloting the approach. He described redesigning its software development process, while treating the authority given to agents as a decision requiring limits. Reversibility and the consequences of an error were central to that judgment.

“You can’t blame it on the agent,” he said. “You have to take the responsibility.”

Amir Wain · 2026

This is where Wain’s long argument about readiness becomes especially interesting. Software that can act needs a company willing to answer for the action. The founder who began by helping managers understand their computers is now asking how much work managers should let computers perform. After nearly four decades of building businesses, he is still occupied with the terms on which people trust the machine.