Wise turned a visible customer problem, the cost and opacity of moving money across borders, into an infrastructure problem. Under co-founder and chief executive Kristo Käärmann, the company has built local payment connections, licences, treasury operations and software that aim to move money without relying on one slow international transfer for every customer transaction.

The durable part of the model is not a memorable fee comparison alone. Transparent pricing creates a promise, while payment and compliance infrastructure determines whether the company can fulfil it at volume. For founders, Wise is a useful study in making an operational system part of the product rather than treating it as back-office work.

A personal friction became a measurable proposition

Wise was founded in 2010 around the difficulty and cost of moving money between countries. The company’s current leadership page identifies Käärmann as co-founder and chief executive. The role matters because Wise remains founder-led while operating as a listed, regulated group.

The proposition can be stated in terms a customer can test: the fee, exchange rate, amount received and expected arrival time. That makes trust more concrete than a broad promise of disruption. It also creates operational pressure. If the price is visible, failures, delays and hidden dependencies become easier to notice.

A payments founder can learn from that specificity. The strongest early claim is one the product can calculate and the customer can verify. Marketing then becomes an explanation of the operating advantage, not a substitute for it.

The public sources reviewed here describe the founding problem but do not identify Wise’s first credible customer or show how that customer was acquired. Later customer totals cannot fill that gap. A publishable founder profile still needs contemporaneous or independently confirmed evidence about the first customer relationship.

Local connections change the route of a transfer

Traditional cross-border payments may pass through correspondent banks and several systems before reaching the recipient. Wise’s model uses locally held funds and payment-system connections where permissions and infrastructure allow, matching flows so that money can often be paid out locally rather than sending the same funds through a full international chain.

That description should not be simplified into a claim that money never crosses borders. Treasury positions, settlement, liquidity and regulatory requirements still have to be managed. The company needs enough volume and forecasting to balance flows, and it needs arrangements for currencies or corridors where direct access is limited.

Wise’s Platform mission update for the second quarter of 2026 describes work on direct connections, partners, speed, cost and coverage. It is a company source, so its performance measures should be read with the stated definitions. The important operating idea is that each new connection can change cost and control, while also adding integration and compliance work.

Transparent pricing depends on cost discipline

A company cannot promise a visible low fee indefinitely if its unit cost is unknown. Cross-border payments incur payment-system, banking, compliance, fraud, support and treasury costs. Prices also need to reflect difficult routes rather than hide their cost inside another customer’s transaction.

Wise’s public pricing shows the customer the fee before a transfer and separates that fee from the exchange rate. Its pricing page varies by route and product, which is more informative than describing one universal price. Founders should take the principle rather than copy a number: show the customer what they pay, then build the operations that keep the promise viable.

Transparency creates another commercial discipline. A product team can measure whether infrastructure investment reduces a fee, shortens delivery or improves reliability. That connects technical work to a customer outcome and makes prioritisation easier to explain.

Scale comes from consumers, businesses and infrastructure customers

Wise serves people and businesses directly, and Wise Platform allows other institutions to use parts of its network. Those routes have different sales, integration and risk profiles. A consumer can begin with a single transfer, while a bank or large company may require procurement, security, operations and regulatory review.

The company’s FY26 results reported support for 19 million people and businesses moving $243 billion during the year. Those are company-defined operating measures and should be read with the financial statements. They still illustrate why infrastructure utilisation matters: a network built for one customer relationship can support another product or partner when permissions and service levels align.

For a founder, the lesson is to separate distribution from infrastructure. Selling through a partner may extend reach, but it also makes the product dependent on the partner’s interface and customer relationship. Direct customers provide clearer feedback, but acquiring them can be expensive. A combined model needs to show how both sides strengthen the same operating core.

Regulation is embedded in the route

Payments regulation is not one global permission. Wise operates through different regulated entities and licences, and the customer’s contracting entity can change by market and product. Know-your-customer checks, sanctions controls, safeguarding, complaints and reporting shape the speed and cost of a transfer.

The company’s regulatory disclosures describe the entities and authorities across markets. This is useful for customers, but founders should also examine the underlying regulator records and current terms. Expansion requires a legal and operational map before it becomes a product launch.

London contributes access to payments expertise, financial institutions, regulation and international talent. The network itself is not confined to London. Its value comes from local connections and teams across markets, which means a London-founded company must organise beyond its home city.

Founder control and public governance coexist

Wise’s leadership page identifies Käärmann as chief executive, while its governance structure includes a board and independent directors. Its September 2026 voting-rights announcement explains that his exercisable voting rights are capped at one vote below 50 per cent while he remains chief executive, with a lower cap if he ceases to hold that role. Founder control can support a long investment horizon, but public shareholders also need clear rights, oversight and succession arrangements.

The useful question is not whether founder control is inherently good or bad. It is whether governance allows challenge while preserving accountability for a coherent mission. Infrastructure businesses make investments whose customer benefit may take years to appear, yet regulated operations cannot depend on personal conviction alone.

Founders should specify which decisions require board oversight, which measures test the mission and how control changes if a founder’s role changes. Formal design becomes more important as the company holds more customer trust and operates across more jurisdictions.

What payments founders can apply

Start with a promise the customer can observe. Map every system, entity and partner needed to fulfil it. Measure price, speed, completion, error and support by route. Treat each local connection as an investment with a defined customer and cost effect.

Build regulatory and treasury work into product planning. A new currency is not complete when the interface accepts it. The company needs liquidity, reconciliation, controls, customer communication and a failure process. These capabilities may be less visible than the app, but they determine whether the product deserves trust.

Finally, decide whether the company is a direct product, an infrastructure provider or both. Each route changes sales, margins, service levels and ownership of the customer experience. Wise’s public record shows how one operating network can support several routes, but it does not remove the need to manage their conflicts.

Limits of the public evidence

Wise’s reports and product pages are primary company sources. They describe the company’s measures and account of its infrastructure, but they do not independently establish the experience of every route or customer. Public filings aggregate operations and cannot show the economics of each payment connection.

This draft needs independently verified first-customer evidence, an independent payments-operator perspective and a current customer case that can verify cost, speed and integration. It should also recheck Käärmann’s role, regulatory entities and reported FY26 measures immediately before publication. The evidence supports a clear conclusion: Wise made infrastructure and transparent pricing mutually dependent. It does not prove that the model is identical across every market.

Reporting by Shoreditch Talk