— In closing
If any of this resonates, let's talk.
The best engagements start with a real conversation — not a form.
The best engagements start with a real conversation — not a form.
Each chapter compounds into the next. The through-line: designing feedback loops and shipping systems that survive contact with real operations.
Founded an independent AI automation practice designing and shipping enterprise-grade agent systems — treating AI as core infrastructure, not a surface feature, so operators can cut cost, remove bottlenecks and scale without adding headcount.
Founded and operate an e-commerce brand selling premium digital subscriptions to the Romanian market — full ownership of product, storefront, payments, fulfilment automation, customer experience and growth. A working case study in building and running a digital business end-to-end.
Shipped globally distributed live-service titles at Electronic Arts, owning quality gates that protected launches used by millions of players. Built the operational discipline that now underwrites every AI system I deliver.
Ran an independent coaching practice for seven years — a first business built on personalised programming, measurable outcomes and long-term client retention. The foundation for how I now design systems around real human behaviour.
A mix of formal foundations and a relentless independent curriculum — because the field moves faster than any single institution.
Training theory and practice across twelve disciplines, didactics and applied pedagogy — the foundations of how I now design systems that teach, coach and coordinate people.
Strategic planning, organisational leadership, HR, event operations and sports marketing — the same operating lens I bring to running an AI automation studio.
Bioenergetics, movement analysis, injury prevention and performance testing — a systems view of the human body that shaped how I model complex systems in general.
Certificates of completion across the core web foundations — the baseline layer beneath every product surface I ship today.
Structured self-directed study across model providers, agent frameworks, retrieval and evaluation — kept current with the pace of the field.
End-to-end automation across the platforms that real businesses actually run on — telephony, CRM, calendars, payments and third-party APIs.
Deep focus on production voice agents — latency, turn-taking, tool use and the operational patterns that make voice reliable in real deployments.
Internal training and hands-on practice across global title launches — the discipline of shipping software that millions of people use on day one.
Small-group, high-signal cohorts with practitioners shipping AI in production — a compounding source of taste and pattern recognition.
Deepening the infrastructure layer beneath modern AI products — orchestration, evaluation and scale.
Formal study of the practices that make AI trustworthy in enterprise contexts — evaluation harnesses, guardrails and governance.
Not a checklist. These are the disciplines I reach for when designing systems — grouped by the problems they solve.
Designing production AI agents and automation for real business operations.
End-to-end workflows across the platforms real businesses actually run on.
Multi-provider LLM work with a focus on quality, cost and latency.
Premium interfaces with performance, taste and conversion in mind.
Data-shaped services and reliable third-party integrations.
Enterprise QA discipline shaped by shipping global software titles.
Directing AI as a production medium — video, image and voice.
Positioning, content and community that compound attention over time.
A decade of coaching translated into how I lead teams and clients.
I design and build AI systems for companies that want durable, measurable leverage — not demos. My practice sits at the intersection of automation, applied intelligence, engineering craft and entrepreneurial thinking, and it is guided by one habit: relentless curiosity paired with the discipline to ship.
These are professional commitments, not personality traits. They are the filter I apply to every engagement, decision and line of code.
Every problem is a system. I trace the loops, name the constraints and design where the leverage actually lives — not where it feels obvious.
Small, compounding refinements beat heroic rewrites. I build systems with the seams that make tomorrow's improvements cheap.
Technology is only interesting when it moves a number that matters. I start from unit economics and operator workflows, then design backwards.
I write software as if I'll maintain it in five years — because someone will. Legibility, observability and boring choices where they belong.
Detail is not decoration. It is the signal that tells clients, partners and users the whole system was designed with intent.
A rotating selection of portraits — because behind every system is a person choosing how it should feel.