About

A principal full-stack system builder for B2B platforms.

Connected digital platforms for B2B companies.

I design and build complex B2B websites, content platforms, internal applications, and digital infrastructure by connecting business understanding, full-system technical judgment, AI-assisted implementation, and direct accountability.

Discuss your project See how I work

Perspective

The role I fill

I can move between levels

Leadership needs a defensible direction. Marketing needs content ownership. Operations needs workflows that do not depend on manual coordination. Developers need architecture that can actually be built.

I stay close to implementation

The same person who maps the platform also makes the technical decisions and can build the foundation directly. That keeps strategy tied to what will work in production.

I specialize without narrowing the problem too early

Next.js and Payload CMS are highly visible in my work, but they support the platform decision. The first question is what the organization needs the system to own.

Principal-led, by design

I started in marketing and sales before becoming a full-stack developer. That combination helps me translate business problems into data, workflows, interfaces, and production software, then explain technical decisions in terms of cost, risk, ownership, and business impact.

I work with a maximum of three active clients at a time. That limit keeps me directly involved in discovery, architecture, implementation decisions, and rollout.

Visual and interaction design is handled in collaboration with Katharina, where design depth is relevant. I remain accountable for the platform architecture, technical decisions, integration model, and delivery path.

I learned full-stack application development before modern AI coding tools became capable. The experience of building, breaking, recovering, deploying, and operating real systems now becomes pattern recognition for client projects. AI increases my implementation speed, but judgment and production responsibility stay with me.

Patterns

The engagements I am usually brought into

Complex website rebuilds where content, migration, integrations, and ownership all matter
CMS migrations where the platform decision affects teams and workflows beyond marketing
Multi-site or multi-brand programs that need shared infrastructure without forcing one monolith
Internal teams that need senior architecture direction on Next.js, Payload CMS, caching, permissions, infrastructure, or migration sequencing
AI and automation requests that expose a deeper knowledge, workflow, or system-boundary problem

Specialization

Next.js and Payload CMS remain the specialist stack

I use Next.js and Payload CMS when the platform needs structured content, custom workflows, access control, database ownership, integrations, and a frontend that can evolve with the organization. The stack supports the business system; it does not replace the business reason to build.

Next.jsPayload CMSTypeScriptNode.jsPostgreSQLDockerQueuesCachingIntegrationsAI-assisted delivery

Philosophy

Practical platform principles

Define ownership before implementation.
Keep systems separate when separation is the better architecture.
Make content models reflect real operations, not only page designs.
Treat migration, governance, and launch as architecture problems.
Use AI where the foundation gives it meaningful leverage.

How this differs from the delivery process

This page explains my professional perspective and credibility. The delivery model, phases, communication style, and engagement modes are covered on How I Work.

Talk through the system behind the project.

A discovery call is the quickest way to decide whether the issue is a rebuild, migration, advisory need, or wider platform discovery.

Discuss your project

A principal full-stack system builder for B2B platforms.

Connected digital platforms for B2B companies.