Switch language (same page)
Deutsch Einfach erklärt EnglishFreelance · web engineering · software & platforms
Laravel · APIs · architectureWhere 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.
A refreshingly different vibe — less jargon, more personality. Thought through with you, not just shipped over the wall.
Clear thinking · Solid build
How we work
No filler promises — three things you will actually notice in delivery.
Clear milestones and visible progress — you always know where things stand and what happens next.
Laravel, APIs, tests, and sound architecture: tech that holds up in production — not just in a deck.
Concept, architecture, and implementation from one person — the same mind for strategy and the tricky details.
Fit
Especially where your public presence and the underlying tech belong together — from trades and local services to associations, shelters, and law firms. Always with one goal: web and software that stay workable in day-to-day operations.
Craft businesses, driving schools, gyms, equestrian centres, and similar operators: a presence that matches what you do — clear services, enquiries, and contact or booking flows. Built so you can later add calendars, CRM, or industry tools without starting from scratch.
Clubs, federations, animal shelters, and volunteer-driven organisations: trust, membership, donations, and transparency — content that reflects reality instead of a one-size-fits-all club template.
Law firms, tax advisors, coaches, and similar practices: a serious, well-structured presence with client journeys and forms where needed — plus SMB realities like connecting to existing systems, not just a new typeface.
Volunteer · shelters · nonprofit
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
Less theatre, more shippable software — with communication that makes decisions easier.
Structured briefing, clear goals, and a plan everyone understands — so engineering is not stuck waiting on ambiguity.
Laravel, solid APIs, maintainable front ends (Tailwind/Vite). A pragmatic release cadence beats polished vapourware.
Clear boundaries, understandable data models, and releases that do not fall apart — so teams can keep shipping reliably for years.
I own architecture and communication together — especially when business and engineering must align for real.
When the site should fit your brand
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.
Modular · clear · actionable
From a focused relaunch to a larger platform — four areas you can book alone or together. Explained in plain language.
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.
Backlogs, stakeholders, budget, and risks under control. I translate business goals into shippable increments.
On-brand UI, calm patterns, responsive layouts, microcopy — no fluff, real impact.
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
Ongoing dialogue is non-negotiable for partnership and outcomes.
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.
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 compact relaunches and API extensions to longer engagements. If goals, budget, and timing are tangible, we can find a sensible wedge to start.
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.
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?
A short brief is enough — I will reply with clear next steps.