I help founder-led teams make the right technical decisions before they become expensive mistakes.

Most founders don’t need another engineer.


They need someone who can see the entire machine — business model, team, processes, architecture, infrastructure, and code — and tell them what will work, what won’t, and what will cost them six figures later.


I’ve been building systems since I was 9.
For the last 25 years, I’ve operated across every layer myself — from electronics firmware, backend and frontend web systems, cloud pipelines to machine learning, infrastructure & server architecture (DevOps) to product architecture.


But the real edge isn’t the code.
It’s the founder lens.


I’ve built companies, run teams, carried P&L responsibility, and operated real products in the field.


I understand the cost of slow shipping, broken releases, angry clients, and technical uncertainty — not from theory, but from living it.


That’s why founders want me in before they greenlight big features, redesigns, AI coding workflows, or architectural changes.


They want certainty, not “we’ll see.”

Where I’m different

Most technical advisors specialise in one area.


I specialise in the intersection where everything meets:

  • business objectives

  • engineering architecture

  • developer workflow

  • operational risk

  • infrastructure reliability

  • ML-powered intelligence

  • real-world delivery constraints

I look at the system the way a founder must — not from one discipline, but from all of them at once.


This lets me spot the hidden risks that teams miss, redirect bad decisions early, and design a clear, reliable path forward.

Founder Lens + Deep Technical Range

I’ve spent years working across domains that rarely meet under one roof:

  • firmware, CAN bus, and LTE-modem integration
  • backend architecture and multi-tenant SaaS
  • cloud ingestion pipelines for real-time systems
  • Kubernetes + DevOps for production systems
  • ML modelling and event detection
  • real-time frontend/UI for high-volume data applications
  • security, governance, and AI coding workflows

This isn’t “multi-domain engineering.”


This is end-to-end system design — the kind that prevents rewrites, accelerates teams, and lowers the technical risk founders carry.

What founders reach out to me for

  • technical certainty before major decisions

  • fixing or preventing architectural drift

  • speeding up slow engineering teams

  • reducing release chaos and silent tech risk

  • bringing order to AI-assisted coding

  • stabilising production environments

  • designing systems that scale without rewriting

  • guiding teams through complex features safely

Sometimes I advise.


Sometimes I architect.


Sometimes my company executes under my direction.


But the outcome is always the same:


clarity, stability, and predictable shipping.

Remoted

Before consulting, I spent two years building Remoted — a full end-to-end IoT platform:

  • custom hardware and power systems
  • embedded firmware
  • LTE Cat-M modem stack
  • OTA updater
  • CAN bus event pipeline
  • multi-tenant backend
  • ingestion engine receiving 10+ signals/sec/asset
  • TimescaleDB-based time series engine
  • Kubernetes production deployment
  • ML models for idling and movement
  • full React frontend with real-time map
  • ...

I built this stack solo — the kind of system mid-sized companies routinely spend €1–€2M failing to deliver.


This is the depth I bring to technical decisions:


I’ve lived through every layer of a real, production-grade platform.

Who I work with

Mostly DACH-region SaaS founders and technical CEOs who:

  • need certainty before scaling

  • can’t afford multi-month detours

  • want clarity on architecture decisions

  • want to avoid six-figure mistakes

  • run teams without senior technical leadership

  • are moving fast but can’t risk breaking their system

If you’re moving into a complex feature, scaling the team, expanding your product surface, or feel the architecture drifting — that’s when you bring me in.

If you want certainty before you commit people, time, or budget, let’s talk.

Most founders reach out when they’re about to make a technical decision they don’t want to get wrong — a feature expansion, architectural change, development team processes, or anything that could create a six-figure rewrite later.


If that’s where you are now, schedule a short Quick Match call now and we'll decide together if it makes sense to move forward.


This initial call is free of charge. 

BOOK A QUICK-MATCH CALL