Building it is the part you already know how to do.

What decides the outcome is three things: how your team works, how fast you take on new technology, and whether the thing you shipped answers a need someone actually has. That is where I come in.

His input has genuinely shaped how we work. He doesn't just advise from a distance. He engages with the real problems, asks the questions that reframe how you see a challenge, and consistently pushes us toward higher standards.

Cosmin-Alin Botoroga · Founder, DATA SWEEP · PhD, Harvard

What founders and CTOs actually call me about

Almost every engagement is one of these three, and the first call is usually about working out which one it really is.

You shipped it
01

How your team works

Every decision routes through one person, and verification quietly replaces trust.

02

How fast you take on new technology

A pilot that impressed everyone and changed nothing.

03

Whether it answers a real need

The roadmap stopped telling you what anyone is actually missing.

It got adopted

1. An engineering culture that holds as the team grows

Teams rarely slow down because the people got worse. Verifying every step is latency. Fearing mistakes is packet loss. I work on what sits underneath: how decisions get made, who owns what, and what happens the first time somebody is wrong in public.

This is the one with no client logo attached, because it is the day job rather than a project. The people who have actually worked for me put it better than I can: 21 of them, on the about page.

2. Taking on new technology faster than the market does

The gap is almost never the model. It is that nobody re-cut the workflow around it and nobody decided what the team stops doing. We pick the few places it pays, score the proposals against something you can argue with, and ship it into the way people already work.

3. Products built around a need, not a roadmap

The hard question is not what to build next. It is whether the thing you are about to add is the thing anyone is actually missing. I have watched a company change what it sells because the data it was already sitting on was worth more than the app collecting it.

Three ways I work

Model A

Fractional, alongside your leadership

Recurring time inside the org. The standing version, for when the problem is how the team works rather than one project.

  • How decisions get made, and who actually owns what
  • Hiring, levelling and the first ninety days
  • Working sessions with your engineering leads, not a report
Model B

One problem, with an end date

A bounded engagement on something specific: an AI adoption program, a product repositioning, a market you have to get into, or the narrative for a raise.

  • An adoption program that survives the pilot
  • Product direction when the roadmap stopped answering the question
  • The investor narrative, pressure-tested the way a partner would
Model C

For funds

The same judgment pointed at your pipeline: can this team build it, what breaks first, and what does fixing it cost.

  • Technical and team diligence on a live deal
  • Benchmarking CEE teams against global standard
  • Portfolio support when scaling stalls

The work

Three companies. One changed how an entire sector buys, one changed how a profession works, and one changed what it sells.

DATA SWEEP Research data · higher education & public sector

From one room of rectors to a fixture in the academic calendar

A research-data startup selling into Romanian higher education. Long cycles, committee decisions, no obvious way in. So instead of working campuses one at a time, we convened the whole market: all 30 top universities' rectors and pro-rectors, plus two ministries, in one room at the Palace of the Parliament.

Alongside it: sharpening strategy, tightening product thinking, and building the narrative for the raise. It stopped being a campaign. It became a channel the company owns.

30Universities convened
2Ministries in the room
5Universities signed
RecurringNow in the academic calendar
Notary.ai Legaltech · regulated profession

The room was the sales channel

A legaltech product that had to be adopted by notaries: a conservative, regulated profession that buys on peer trust and precedent, not on demos. Two months to learn a foreign domain, its legal language, and who actually holds sway in it.

Then we ran the room: a six-hour conference for 200+ notaries, built to explain how AI would change their workflow and to ask them to buy at the end of it. 70% signed up within 48 hours.

6hConference built from scratch
200+Notaries in the room
70%Signed up within 48 hours
2moFrom foreign domain to close

He didn't deliver, he blew it out of the park. After seeing him work, I wouldn't pick anyone else for my critical showcases.

Vlad Bolovan · Founder, Notary.ai
Eldie Elder care · cognitive health

Changing what the company sells

A consumer cognitive-health app for seniors, B2C only. I joined Eldie's Board of Advisors as the company was taking shape. Seniors are an audience where the standard design patterns simply fail, and where accessibility and trust matter more than polish. So we redesigned the workflows end to end, then built product primitives the team could defend: engagement and progress metrics meant to be for brain health what steps are for physical health.

Those metrics generate something more valuable than retention: consented, longitudinal data on cognitive decline. That opened a second business in research datasets and moved the company from B2C-only to B2B. Today it has national TV coverage and partnerships with Romania's largest pharmacy chains.

Aleodor helped us see the product through our users' eyes. No vague opinions, just concrete, prioritized recommendations you can act on the same week.

Teofil Sturzoiu · Founder, Eldie

Why me

Because I am doing this work, not remembering it. By day I lead Stripe's engineering site in Bucharest and own the platform operators use to run risk, compliance, KYC and financial crime.

8,500Operators worldwide on the platform I own
6Jurisdictions in the AML tooling migration
~40%Lower handling time after that migration
~200%Team growth while it was happening

Before Stripe: Snyk, Adobe and Bitdefender. So I have built the culture, shipped the adoption and argued about the roadmap, more than once. That is mostly what you are buying: someone who can tell you which of the three is actually your problem, including when the answer is that you do not need me.

Tell me what you're trying to get adopted

Thirty minutes, no deck needed. Tell me who has to say yes and what keeps stalling. If I'm not the right person, I'll say so on the call and point you at who is.

Takes about a minute. It goes straight to my calendar with your answers attached, so we can skip the discovery small talk.

I take a small number of engagements alongside the Stripe role, usually two at a time.