A CTO With a Board Seat
Inbank, an Estonian fintech with a European banking license, named Marten Meikop chief technology officer on July 24, and it did something many of its peers still hesitate to do. It placed him on the Management Board, effective August 10. For a company that lends across seven markets and answers to bank supervisors, that placement carries weight. The person who owns the technology roadmap will now sit where capital, risk, and strategy get decided. We read this as a deliberate statement that engineering choices at Inbank are governance questions that reach beyond delivery details handed down from the boardroom to a separate technical function.
The timing matters. Embedded finance platforms are under pressure to ship faster while regulators sharpen their expectations on operational resilience and third-party risk. Inbank chief executive Priit Poldoja framed the hire around scale, saying Meikop "brings extensive experience in building cross-border technology platforms and leading large engineering organisations." That description reads as a response to a specific problem. A lender operating in multiple jurisdictions cannot let each market build its own stack. The CTO seat on the board is the mechanism Inbank has chosen to keep platform strategy and banking accountability in the same room.
What Meikop Brings From Pipedrive
Meikop joins from Pipedrive, the Estonian sales software company, where he spent close to a decade and most recently served as Director of Engineering Platform, overseeing roughly 100 engineers. Before that he worked at Elion and Proekspert, and he holds a Master of Engineering in information technology from TalTech. That background is heavy on platform engineering and organisational scale rather than banking, which tells us Inbank wants a builder who can standardise infrastructure and run large teams. The CTO he becomes will be judged on how well a SaaS-style platform discipline transfers into a regulated lending environment.
Meikop himself pointed to the tension he is stepping into. He said he was drawn to Inbank because it "combines the agility of a fintech with the strength of a licensed bank." That combination is the hard part. Move too fast and you invite regulatory and operational fragility. Move too slowly and merchants leave for a competitor that ships. For CTOs watching from adjacent sectors, the interesting question is whether a leader trained in high-velocity SaaS delivery can hold that line inside a balance sheet business. Inbank is betting the platform instincts travel well.
The Board Seat Is the Real Signal
We spend a lot of time debating whether the CTO belongs in the C-suite. Inbank answered by putting the role on the Management Board, the body that carries legal and regulatory accountability at an EU-licensed bank. That is a stronger commitment than a title. It means technology tradeoffs on resilience, data, and vendor concentration get argued at the level where the company is answerable to supervisors and bondholders. Inbank's bonds trade on the Nasdaq Tallinn exchange, so the governance around technology decisions is visible to the market rather than buried in an internal reporting line.
For readers structuring their own leadership, this is a useful reference point. A board-level or executive-committee CTO changes what the role can actually do. Budget authority, veto power over risky architecture, and a direct line into risk and audit stop being favours the CTO has to negotiate. They become part of the mandate. Inbank did not invent this pattern, though it applied it in a regulated setting where the stakes are concrete. If your platform decisions increasingly carry regulatory consequences, the reporting line is worth revisiting before the next incident forces the question.
Why Cross-Border Platforms Are the Pressure Point
Inbank operates an embedded finance platform across seven European markets, working with more than 6,200 merchants and managing over 847,000 active contracts. Those numbers explain the emphasis on cross-border platform experience. Every additional market adds regulatory variation, payment rails, language, and settlement complexity. A CTO who lets that sprawl calcify into seven bespoke systems will spend years and budget untangling it later. The mandate implied by Meikop's hire is consolidation and reuse, building shared services that behave consistently no matter which merchant or market touches them.
This is the same discipline PE-backed SaaS leaders recognise from serial acquisitions. Growth by geography or by deal produces a patchwork, and the technology leader's core job becomes standardising it without freezing the roadmap. Inbank's choice of a platform-engineering specialist over a banking technologist suggests it sees its hardest problem as an architecture and scale problem. For our readers weighing similar hires, the lesson is to match the CTO's background to the actual bottleneck. Inbank concluded that its bottleneck sits in platform consolidation, and it hired accordingly.
The Quiet Reshuffle Underneath
The appointment came with a board change that is easy to overlook. Ivar Kurvits was recalled from the Management Board effective July 31, though he stays with the company as Head of Corporate Development and Strategy. Rotating a leader off the board while keeping their expertise elsewhere is a clean way to make room without losing institutional knowledge. It also tells us Inbank wanted a technology voice in that seat specifically, enough to reshape board composition to get one. The swap frames the CTO hire as a structural decision rather than a routine backfill.
We flag this because the surrounding governance moves often reveal more than the headline appointment. A company that merely wanted a competent CTO could have hired one and left the board alone. Inbank chose to change who sits at the top table. That choice raises the visibility and the accountability of the technology function in one step. For leaders reading the tea leaves on their own organisations, watch what gets rearranged around a hire. The reshuffle is where the company shows how seriously it takes the mandate it just handed out.
What It Means for Your Roadmap
Inbank's move lands as a small but clear data point in a larger shift. Regulated and PE-backed businesses are pulling technology leadership closer to the centre of decision-making, because platform, data, and resilience choices now sit on the critical path to both growth and compliance. If you run technology at a company facing multi-market complexity or supervisory scrutiny, the structural question is whether your role has the authority to match its accountability. Inbank answered that with a board seat. Your answer may differ, but the question is now unavoidable.
The practical takeaway is to align the hire, the mandate, and the reporting line before the pressure hits. Inbank matched a platform-engineering leader to a consolidation problem and gave him governance standing to act on it. That coherence is worth copying even if the specifics do not fit. When your next senior technology hire arrives, decide in advance whether they are a delivery lead or a decision-maker, and build the structure to match. The gap between those two definitions is where most technology mandates quietly fail.
