evoyo.la
Services
Maintenance & Ongoing Development
For projects that are running and should keep running. No ticket-system overhead — a direct line, clear agreements.
Currently taking on new projects
The starting point
A finished project still needs ongoing care: dependencies age, PHP and Laravel versions change, new requirements come up. Many small businesses don’t want ticket-system overhead or an agency with long turnaround times for that — they want a direct line to someone who already knows the codebase or gets up to speed quickly.
How I approach it
-
Stock-take of the current stack and open issues before ongoing support begins.
-
Clear agreement on how requests are handled — directly, no ticket-system detour, with realistic response times.
-
Regular updates and monitoring so problems surface before they become an outage.
What you get
- A project that stays current — dependencies, PHP/Laravel version, security patches.
- A direct point of contact instead of a ticket system with rotating handlers.
- New features that build on the existing architecture instead of undermining it.
Matching case studies
Gutz Intern
Internal club app for Gutzkowclub e.V.: member management, shift scheduling, credit system, messaging.
View case study "Gutz Intern" →Gutzkowclub e.V. — Website
Public website of Dresden’s oldest student club (since 1964): program, drinks menu, history, contact.
View case study "Gutzkowclub e.V. — Website" →Frequently asked questions