Open mandate / August 2026London · Edinburgh · Remote / flexible · UK ILRsolodkiy.cv
Founder-operator · product · regulated innovation

Looking for a mandate, not a title.

I want a real problem, a team, a metric and responsibility for the outcome — preferably where product, regulation, trust and new technology collide.

UK Settled Status / ILR · no sponsorship required New Bets / EIRProduct leadershipRegulated fintechIdentity / trustAI × financial infrastructure
IFE-065 (USA)de novo bank licence (PR/US) + de novo fund managalent license (SG)
$25m+capital raised (for ArivalBank.com) + $50m+ for SREDA.Ventures
15+ / 60+direct reports / organisation
500+ / 26business clients / countries
$1bn+transaction volume
01 / I am not looking for somewhere to retire.

Primary ask: a paid senior operating mandate.

I am open to full-time roles, EIR / New Bets, product leadership, special projects and selected hands-on advisory or fractional work where ownership is real.

01 / OWN

A real problem.

Something messy enough that product, economics, regulation and execution have to be solved together — not an “innovation theatre” brief.

02 / BUILD

A small serious team.

I am comfortable being No.1, No.2 or one of several strong owners. What matters is direct responsibility, speed and measurable output.

03 / MEASURE

An outcome, not a title.

Give the unit a customer, a P&L or another hard metric, and the right to scale, re-design or die.

02 / Operating system

Reality-first product building.

I am not a decomposition fetishist. I split systems only when it creates better ownership, observability, economics or failure containment.

Enter

Enter the system, not the deck.

Use the product. Visit the customer. Talk to operators and regulators. Buy the competitor. Try the unhappy path. A presentation tells you what somebody wants to be true; the transaction tells you what is true.

Decompose

Find what the “no” is made of.

Split the first no into hard constraints, soft constraints, incentives, data gaps, operational risk and economics — then ask what must become true for yes.

Customers

Find the customer behind the customer.

Customers often ask for “more horses”. I want the workflow around the request. In regulated finance the user may be the SME, the compliance team, a partner bank — or the regulator consuming your reporting.

Boundaries

Design the failure domain.

A risky unit should be inspectable — and, when necessary, stoppable — without taking the entire machine down. Regulation can be product architecture, not just policy text.

Economics

Find the business hidden inside the cost centre.

Ask whether a support function is actually a platform or future business with its own customer, pricing, capex/opex, P&L and strategic optionality — internal product, subsidiary, JV or spin-out.

Decide

Possible ≠ worth doing.

I enjoy finding a route to “yes”, but I do not confuse solvable with investable. Price the controls, team, capital and opportunity cost — then scale, re-design or kill.

03 / Proof of execution

Arival: from an unpopular wedge to a regulated bank.

The hard part was not simply building software. It was making product, regulation, risk, capital, partnerships and distribution behave as one system.

0 → bank

I did not start by building another digital bank for everyone. We focused on international SMEs, fintech and higher-compliance-complexity businesses — customers mainstream banks often disliked or misunderstood.

  • 01
    Pick a painful wedge. Start narrow enough that the customer has a reason to switch.
  • 02
    Make regulation part of discovery. Understand what the regulator actually fears, not only what the published rule says.
  • 03
    Design for supervision. Reporting is a product surface: make risk visible, explainable and separable.
  • 04
    Build the stack. Front end, middleware, core banking, payments, compliance and partners had to work as one product.
  • 05
    Know when not to build. A route to “yes” is still valuable if the final economics say “not worth it”.
04 / Current frontier & research themes

Learning-by-doing

Since leaving day-to-day bank (and fund) management I have used research, prototypes, hardware experiments, writing and founder conversations as a practical lab for what to build next.

Research / prototypes

Digital identity & trust infrastructure

Reusable regulated identity, assisted verification, multimodal biometrics, delegated authority and trust graphs for humans, organisations, products and AI agents.

Research / experiments

AI infrastructure & sovereign compute

Prosumer AI hardware, local inference, decentralised compute, power/energy constraints and the economics of building AI capacity outside hyperscalers.

Research / public artefacts

Regulated innovation & civic systems

New financial infrastructure, security/civic resilience and institution design — explored through books, prototypes, public research and real-world experimentation.

:: internal project names and domains are intentionally de-emphasised here, these are research/prototype areas + some papers here

05 / Why now

This is a deliberate choice, not a fallback.

I have already been first chair.

I built a venture platform and then a bank. I know the emotional reward and the cost of being No.1. I do not need another CEO title to prove I can sit there.

The next growth curve is listening.

I spent years being the person expected to have the answer. I now want to become materially better at listening and asking inside a strong team whose operating system I did not design.

My strongest craft is product.

CEO work taught me that I can fundraise, hire, manage regulation, boards, operations and P&L. The work I love is taking a messy system apart and rebuilding it into something valuable.

The next conversation

If a problem or team comes to mind,

I would genuinely like to hear about it. I am looking for somewhere to work.