The appointment and the board reshuffle
On July 24, Inbank said Marten Meikop will join as Chief Technology Officer and a member of its management board, effective August 10. The same announcement reshaped the board around him. Ivar Kurvits is being recalled from the management board effective July 31 and will continue as Head of Corporate Development and Strategy, while Chief Risk Officer Evelin Lindvers had her term extended for three years starting August 7. The result is a six-person management board consisting of the chief executive, the finance chief, the commercial and product leads, the risk chief, and now a dedicated technology chief with a formal seat at the table.
The structural detail is the one worth dwelling on. Many banks keep technology a rung below the top governance body, represented through a chief operating officer or a business-side executive rather than a technologist with direct board standing. Inbank is doing the opposite by seating its CTO alongside the CEO, CFO, and CRO as a peer. For a licensed bank, that is a statement about where it believes competitive advantage now lives. It also changes the internal physics of decision-making, because the person responsible for the platform can argue for engineering priorities directly rather than filtering them through a business proxy who may not share the technical stakes.
Who Marten Meikop is
Meikop spent nearly a decade at Pipedrive, the Estonian sales software company, most recently as Director of Engineering Platform leading roughly 100 engineers. Before Pipedrive he held positions at Elion and Proekspert, and he holds a master's degree in information technology from TalTech. That is a platform-engineering pedigree built at a high-growth SaaS company, where the discipline is about building reliable, scalable systems that many teams depend on. Inbank is importing that scale-up engineering culture into a regulated banking environment, betting that the practices that let a SaaS platform grow quickly will transfer to the harder constraints of a licensed financial institution.
Meikop framed his own reason for the move around exactly that tension, saying he was excited to join because Inbank combines the agility of a fintech with the strength of a licensed bank. That sentence captures the strategic bet on both sides. Inbank wants the velocity and platform thinking of a SaaS engineering organization, and it is willing to hand board-level authority to someone who built that discipline elsewhere. The risk in any such hire is the culture gap between shipping software fast and operating under banking supervision, and how Meikop reconciles those two will determine whether the appointment delivers the agility Inbank is buying.
Why a licensed bank promotes technology to the board
Inbank is a fintech with an EU banking license running an embedded-finance platform, which means its product is essentially software that other businesses plug into to offer financing at the point of sale. In that model the engineering platform is the balance sheet's distribution channel. Every merchant integration, every credit decision at checkout, and every deposit flow runs through code that has to be both fast and compliant. When the platform is that central to how a bank makes money, keeping its owner off the top governance body starts to look like a structural liability. Inbank's board change reads as a correction to align authority with where the business actually operates.
This is a governance pattern worth watching beyond Estonia. Financial institutions have spent years talking about becoming technology companies with banking licenses, but their org charts often lagged the rhetoric, leaving technology represented by proxies rather than principals. Inbank giving its CTO a full board seat puts the structure where the strategy already claimed to be. For technology leaders inside larger, slower institutions, it is a useful reference point in the recurring argument about whether engineering leadership belongs in the room where capital allocation and risk appetite are actually decided, or one level removed from it.
The embedded-finance platform under the hood
The numbers explain the urgency. Inbank operates across seven European markets, serves more than 6,200 merchants, and carries over 847,000 active contracts while also collecting deposits, with its bonds listed on the Nasdaq Tallinn exchange. That is a genuinely distributed platform business with real regulatory obligations attached to every market and every contract. Scaling it means keeping a growing web of merchant integrations reliable while satisfying supervisors in multiple jurisdictions. Those are precisely the problems a platform-engineering leader is trained to solve, which is why the profile of the hire lines up so cleanly with the shape of the business Inbank is trying to grow.
For a technology leader running a comparable platform, the interesting question is how Inbank will balance reliability against velocity now that engineering has a direct board voice. Embedded finance lives or dies on uptime and integration quality, because a checkout that fails loses the merchant a sale in real time. At the same time the model only wins by adding markets and merchants faster than competitors. A CTO on the board can make the case for investing in platform durability before it becomes a crisis, which is exactly the kind of unglamorous, long-horizon spending that tends to lose out when technology is represented only through a business proxy focused on the next quarter.
What it signals for fintech org design
The broader lesson sits in how Inbank handled the whole reshuffle as a package. It did not simply add a CTO. It moved an existing board member, Ivar Kurvits, into a strategy-and-corporate-development role, extended its risk chief, and rebuilt the board composition in one coordinated announcement. That signals deliberate design rather than a reactive backfill. The bank decided what capabilities it needed at the top, engineering leadership and continuity in risk among them, and arranged the seats accordingly. Coordinated moves like this are usually a sign that a board is planning around a strategy it can articulate, not patching a vacancy it was caught by.
For CxOs thinking about their own leadership structure, the takeaway is to treat board and executive composition as a design problem tied to strategy rather than a set of individual hiring decisions. If your growth thesis depends on a platform, the person who owns that platform probably belongs in the room where strategy is set. If continuity in risk management is essential to operating under supervision, lock it in explicitly, as Inbank did by extending its CRO alongside the new appointment. The specific titles matter less than the principle: match the composition of your senior body to the capabilities your strategy actually requires.
The roadmap implication
The near-term signal for anyone in embedded finance or regulated fintech is that engineering leadership is climbing the org chart, and the institutions that get there first may move faster on platform investment. Inbank has given its technology chief the standing to fund reliability and scale before they become emergencies, which is a structural advantage in a business where an outage costs merchants sales instantly. Competitors that keep technology one level below the board will find those arguments harder to win internally, and over time that gap tends to show up in uptime, integration quality, and speed to new markets. Structure shapes what gets funded.
The longer arc is about the maturing of the fintech-as-a-bank model. As these companies take on more regulatory weight, the temptation is to let compliance and risk crowd technology out of the top table. Inbank is resisting that by seating engineering as a peer to risk and finance rather than a subordinate function. Whether that balance holds under supervisory pressure is the open question, and it is one every scaling fintech will eventually face. For now, Inbank has made a clear choice about what it values, and technology leaders watching the sector should note both the choice and how deliberately it was executed.
