The everyday problem
Your website does not end at the contact button.
Someone understands your offer, sends an enquiry or books an appointment. What happens next? I design the path through to the workflow behind it, connecting the first impression, mobile experience and enquiry management.
Design, content and technology are developed together. Contact paths, search metadata and loading behaviour are part of the work from the beginning. Booking, customer accounts and integrations connect the website to the process behind it.
What we will work on together.
The scope follows your project.- 01
Explain your offer
Custom design with clear structure and contact paths
- 02
Make it easy to use
Responsive development, accessible controls and technical SEO foundations
- 03
Connect the next step
Booking, content, accounts or integrations that fit the business
From my work
See what this looks like in practice.
Salon website with booking and CRM
A salon website that does the front-desk work.
From choosing a look to booking an appointment: stylist selection, accounts, vouchers and AI previews in one flow.
- Book against real availability
- Self-service accounts and vouchers
- Compare and preview new looks
- Next.js
- TypeScript
- MongoDB
- +3
Product website and licensing backend
The product starts on the website and continues on the desktop.
The path from a first site visit to an installed app connects accounts, a trial, subscriptions, device pairing and updates.
- Connect accounts and installations
- Subscriptions with verified webhooks
- Pair devices and deliver updates
- Next.js 15
- TypeScript
- MongoDB
- +3
Agency site with project enquiries
A clearer story for the agency. A simpler path to contact.
Services, case studies and a self-assessment lead to relevant enquiries. A modular structure connects design and operations.
- Connect services with case studies
- First-party minimal-data measurement
- Extend pages through modules
- Next.js 16
- React 19
- TypeScript
- +3
Our first conversation
What should happen after the first visit?
You do not need a finished technical specification. Your idea, an example or a look at the current workflow is enough to start.
Let us talk it through- 01
What should a visitor understand and do next?
- 02
Which content, features and existing systems are involved?
You might also be wondering:
Felix SchumannAI automation engineerName it, I build it.
If something here looks like the problem you have, write to me. A short description of what is not working is enough to start.
