Clear responsibilities
We agree on who administers each service and how incidents are reported. Access and dependencies have an owner.
Base · Continuity
Website maintenance and technical support
Keep what you have built useful every day.
Hosting, email, maintenance and support with a defined scope. We organise ongoing care for your website or system so you know what is maintained, who is responsible and how it is reviewed.
The craft of connecting the pieces.Código Palanca
The starting point
Launch was one step. Keeping it running needs attention.
A pending update, access details nobody can find or a form whose messages stop arriving. We review the operational foundation and agree on the tasks it needs to keep working.
Planned maintenance
We define reviews and updates around the system. Every change needs to account for its dependencies and a recovery method.
Continuity you can check
We identify what needs monitoring and how to verify backups and recovery. Operations can be assessed rather than left to assumptions.
From the objective to concrete work
What we can work on with you.
Base supports what Calicata builds. We can also assess an existing system after reviewing its condition, access and whether it can realistically be maintained.
Define my next stepReview of the current foundation
An inventory of the hosting, domain, email, applications and access involved. Identification of needs and dependencies.
Agreed maintenance
Updates and checks for the included components. The plan is adapted to WordPress or the system being maintained.
Hosting and email
Configuration or operational support where included in the service. We define providers, responsibilities and applicable conditions.
Support and recovery
Agreed channels, hours and incident handling. The proposal defines the scope of backups, restoration and checks.
Availability, channels, hours, response times and included tasks are agreed in each proposal. New features and work outside routine maintenance require a specific scope.
Código Palanca applied to your project
Decide. Build. Check.
We start with an inventory and a review of the current state. With that information, we propose a continuity plan and distinguish initial fixes from recurring maintenance.
We review what needs to be maintained
We check the state of the system, its documentation and the services it relies on. We identify gaps before taking on maintenance.
We agree on how to support it
We define recurring tasks, channels and responsibilities. We distinguish maintenance, incidents and new features.
We maintain and reassess
We carry out the agreed tasks and review relevant changes to the system. New requirements are assessed under their own scope.
Before you start
Questions about Base.
Decisions worth clarifying before building.
Do you maintain WordPress sites built by another agency?
We can assess this after reviewing the code, plugins, hosting and access. If fixes are needed first, we explain them before agreeing on maintenance.
Does support include round-the-clock availability?
Channels, hours and response times are specified in the proposal. The website does not offer universal availability for every system or service arrangement.
Are backups included?
They are defined in the plan: what is backed up, where, how often and how recovery is checked. Having a backup and being able to restore it both need verification.
What happens if I need to add a feature?
We review its scope and how it relates to maintenance. A new feature is treated as development work so it can be estimated and validated separately.
Let’s discuss your next step
Let's keep what you have built working.
Tell us about your system and what you need maintained. We will review its condition and the care it requires.