Fast clarity instead of endless workshops
Structured briefing, clear goals, and a plan everyone understands — so engineering is not stuck waiting on ambiguity.
Freelance · web engineering · software & platforms
Laravel · APIs · architectureIdeas become software that scales.
Where I shine: solid backends and heavily automated workflows — with UIs that explain themselves in daily use. Good tools rarely need a manual.
The focus is demanding web development and line-of-business software: APIs, permissions, integrations, and front ends built to a high standard. Public sites and relaunches are often part of that — but not the only profile. Marketing channels such as paid search (SEA) only as an add-on when they can be implemented cleanly on the engineering side. Delivery is usually Laravel & PHP: sound architecture, tests, CI/CD, and production-minded releases.
Web engineering · Laravel · PHP
APIs · data models · Ops-light
IT project leadership
UI/UX · design systems
Tests · quality · performance
Backends and automation at the core — interfaces that stay intuitive; public sites and relaunches when they fit the product story.
Clear thinking · Solid build
How we work
Clarity, quality, one steady point of contact
No filler promises — three things you will actually notice in delivery.
-
Predictable rhythm
Clear milestones and visible progress — you always know where things stand and what happens next.
-
Engineering with substance
Laravel, APIs, tests, and sound architecture: tech that holds up in production — not just in a deck.
-
One counterpart
Concept, architecture, and implementation from one person — the same mind for strategy and the tricky details.
Volunteer · shelters · nonprofit
Pro bono work when it is the right fit
Animal welfare matters to me — I am glad to help shelters and similar nonprofits when it fits: websites, small apps, or finance prep pro bono, scoped honestly and based on capacity.
Volunteer projects →Why working with me feels safe
Highlights you can feel in delivery
Less theatre, more shippable software — with communication that makes decisions easier.
Engineering you will still like tomorrow
Laravel, solid APIs, maintainable front ends (Tailwind/Vite). A pragmatic release cadence beats polished vapourware.
Architecture instead of short-term tinkering
Clear boundaries, understandable data models, and releases that do not fall apart — so teams can keep shipping reliably for years.
A partner, not a “resource”
I own architecture and communication together — especially when business and engineering must align for real.
When the site should fit your brand
Not an off-the-shelf theme with your logo But typography, colour, and UI shaped around you
Whether it is a compact one-pager, a larger multi-page site, a corporate presence, or editorial surfaces — the point is not page count, but a coherent system: instead of catalogue looks, you get aligned typography, colour, spacing, and components — where design and engineering work together and stay maintainable day to day.
- Components and UI rules that stay consistent, documented, and extensible — for you and your team.
- Semantics, accessibility, and performance budgets from day one — not a late rescue pass.
- Shipped for real stacks: Laravel, Vite, Tailwind — maintainable and versionable, without opaque page builders.
Modular · clear · actionable
How I can help
From a focused relaunch to a larger platform — four areas you can book alone or together. Explained in plain language.
Software & web development
Backends, APIs, and line-of-business software with Laravel & PHP: data models, permissions, integrations, tests, deploy pipelines, Vite/Tailwind front ends. Strong automation and understandable UIs — maintainable code, pragmatic releases.
IT project leadership
Backlogs, stakeholders, budget, and risks under control. I translate business goals into shippable increments.
Web design & UX
On-brand UI, calm patterns, responsive layouts, microcopy — no fluff, real impact.
After launch & measurability
Iteration, observability, and meaningful metrics once you are live. Optional and clearly scoped: technical foundations for organic discovery or e.g. SEA — only when integration stays clean and marketing does not dominate the engineering brief.
FAQ
Short answers — when you need to decide quickly
Ongoing dialogue is non-negotiable for partnership and outcomes.
Why is steady communication so important?
Software is shaped in conversation: goals, risks, fast decisions, and transparent progress keep quality and dates under control. I prefer a clear communication rhythm (short syncs, agreed written channels) — remote, hybrid, or on-site.
Do you work remote, hybrid, or on-site?
Yes — Germany-wide remote, hybrid around Hanover, or targeted on-site days. What matters is a dependable rhythm: steady touchpoints and clear ways to reach each other.
From what project size does working together make sense?
From compact relaunches and API extensions to longer engagements. If goals, budget, and timing are tangible, we can find a sensible wedge to start.
Is your focus simple marketing sites or serious engineering?
The focus is demanding web development and line-of-business software: APIs, authorisation, integrations, and front ends built to a high bar. Public sites and relaunches are often part of that — but not the only story. Marketing channels (e.g. SEA) only as extras when the technical implementation can stay clean. I am especially strong on robust backends and high degrees of automation; surfaces should be as self-explanatory as possible.
What does a typical intro call look like?
Short, concrete, no pitch theatre: goals, risks, stack, timeline. You leave with next steps and an honest feasibility read.
Shipping serious software or a complex web build?
Let’s talk about your next chapter
A short brief is enough — I will reply with clear next steps.