Bring me the decision you are stuck on
I’m Satyam. Most of what I am paid for is talking people out of the expensive version.
Book a discovery callThe work
fourteen years, six countries
-
2026
Identity resolution from under 50% to over 70%
US
-
2025
Core Web Vitals from 40 to 95, in two passes
Spain
-
2020–22
Three car portals as one, six million visits a month
Netherlands
-
2014
Co-founded hyperlocal delivery, a decade early
India
Most platforms do not fail on the code. They fail on a decision nobody wrote down, made a year before anyone noticed.
How I decide
Where I usually disagree with the plan
Five calls I have made often enough to have a rule for.
-
On the rewrite
Read the system before changing it
I have recommended one full rewrite in fourteen years. The other twelve times it was three files nobody had measured.
-
On adding AI
AI only where it earns its place
Search or ranking? A model helps with one. The other is a catalogue where half the fields are wrong, and inference does not fix a wrong field.
-
On building with agents
Build with agents, ship AI carefully
I direct agents and review what comes back, every day, on my own platforms and on client work. The review is the job either way.
-
On hiring
Say what the choice costs in month six
Three hires is often the right call. It is also a slow quarter, and that half gets left out of the plan. Both halves go in writing.
-
On the margin
The margin note is the job
Not a deck about the work. Me, in the repository, saying which line is wrong and why. It is why I take few engagements at a time.
Engagements
Three ways in
The first one runs a week or two. You find out whether I am worth paying for before you commit a quarter to it.
-
Advisory and architecture
A week or two reading the system, ending in a written answer: what to build, what to defer, and whether the rewrite you are considering is really a rewrite.
Best for Anyone about to sign off on a rewrite, or about to defer one for the wrong reason.
-
Product Partner
I work with you in the repository: scope, architecture, implementation, and review. A small team and short loops. Nothing goes in that production cannot carry.
Best for Founders and technical leaders who want senior engineering judgment while the product is being built, not only after it ships.
-
Modernization
Target the highest-friction areas: tests, boundaries, build and release paths, and the parts everyone is afraid to touch.
Best for Teams slowed by fragile code, unclear architecture, weak tests, or delivery paths that have become too risky to change confidently.
Who
Who you would be working with
I'm a fractional CTO and hands-on engineering partner, fourteen years across automotive marketplaces, regulated banking, crypto gaming, retail pricing, data and identity, secure operational software, hyperlocal delivery and mobile apps. I stay in the work: architecture decisions, code reviews, and the calls where trade-offs need senior judgment.
Some of it runs through companies rather than contracts: Saxena Holdings B.V., which I founded in 2020, Weird.io, which I co-founded, and MHG Companies in the US, where I head technology. I carry two engagements at full weight, two days a week each, and longer relationships continue alongside them at a lighter cadence.
Based in the Netherlands.
Director, Saxena Holdings B.V.
Start with
thirty minutes.
Thirty minutes. Bring the plan, the constraint, or the argument you keep having.