Specific incidents
Forms that stop sending, visible errors, functions that fail, problems after an update or behaviour that used to work correctly.
Technical Website Support
We step in when an existing website shows an error, a function stops responding or you need a specific technical adjustment. One-off support is designed to solve a specific need; monthly maintenance is a different service.
It is corrective or one-off work on an existing website. First we identify what is happening, then assess the scope, and only then work on the problem that genuinely needs solving.
Forms that stop sending, visible errors, functions that fail, problems after an update or behaviour that used to work correctly.
Small changes to blocks, behaviour, links, forms or functionality when they do not require a redesign or a new development phase.
The same incident can come from code, a plugin, hosting, configuration, an API or permissions. We review the cause before applying unnecessary changes.
The service fits when there is an identifiable problem and you need someone to review and resolve it without necessarily taking out recurring maintenance.
We do not assume the first symptom is the cause. A website can show the same error for very different reasons, so the intervention starts by understanding the context.
We need to know what is failing, since when, what should happen and whether anything changed immediately before the problem appeared.
We check the platform, hosting, plugins, code, integrations and other related elements to identify the likely source of the incident.
If it is a one-off correction, it is handled as support. If we discover a structural problem, a badly deteriorated website or a larger development need, we explain it before expanding the work.
We apply the solution with the lowest reasonable risk, verify the affected journey and confirm that the specific incident has been resolved.
If the failure reveals a lack of updates, backups or periodic review, we may recommend maintenance, but one-off support does not require you to take it out.
It depends less on the sector than on how much the incident affects day-to-day work. Even a simple website may need support if a form, booking or contact route stops working.
When forms, calls to action, landing pages or commercial pages are part of lead generation.
Plugins, themes, updates and compatibility can cause incidents that need a one-off review.
Websites built with HTML, CSS, PHP, JavaScript or Laravel may require diagnosis and corrections to specific functions.
We can also review them as long as there is sufficient access and the technology is within an environment where we can work safely.
Tell us your situation and we will help you identify the next practical step.
One-off support is used when there is a specific incident, error or adjustment. Maintenance is a recurring, preventive service that includes scheduled reviews, updates, backups and other tasks defined in the plan. If you only need to solve one specific problem, you do not need to take out monthly maintenance.
Yes, in many cases. First we need to review the technology, condition of the website and available access. If we find a badly deteriorated foundation, major incompatibilities or an environment where we cannot work safely, we explain that before making changes.
It can include small adjustments related to the incident or a specific need. A redesign, new pages, broad content changes or new functionality would be assessed as different work.
Yes, when the cause and scope allow a safe intervention. We review which update, plugin, theme or configuration is related to the failure and assess whether it should be corrected, replaced or restored.
We do not offer a 24/7 service. Incidents are handled according to availability and priority during reasonable business hours. If a website needs monitoring and technical continuity, it is worth considering a maintenance service appropriate to that risk.
It depends on the incident, the time needed to diagnose it, the technology and the scope of the correction. Before expanding an intervention or turning it into a larger piece of work, the problem and the work required are explained.
Not always. An incident can be resolved while an underlying cause remains, such as lack of maintenance, outdated software, hosting, plugins or project decisions. If we identify a risk of recurrence, we explain it so you can decide whether preventive work makes sense.