Ongoing care
Keep useful things
working well.
Defined support for systems we can maintain, with clear time allowances and responsibilities.
A technical check and bounded content changes.
Scroll to explore
Support with
a clear boundary.
Care is for an accepted system we can maintain. Agree the baseline, access and recovery responsibilities before a plan starts.
These are proposed plans, not active service agreements. The allowance includes the check itself, and additional work needs a written quote.
When and how
Proposed support channel: an agreed email address, Monday–Friday, 09:00–17:00 UK time, excluding public holidays. Proposed acknowledgement within two working days; this is not a resolution guarantee.
One monthly check and the stated minor-change allowance. Unused time does not roll over. Access, maintainability and recovery must be established first.
What sits outside the plan
New features, emergencies, compromised-system recovery, third-party outages, unlimited support and 24/7 monitoring are excluded.
Software, hosting, domains, storage and AI/API usage are separate costs. Extra work requires a written quote before it starts.
Discuss ongoing care ↗Questions about care
Can I add care to any existing system?
Care starts with an accepted system that Brivendale can maintain, not simply a request to cover any setup. We need to establish the baseline, permitted access and backup or recovery responsibilities first. The published plans are proposals, not active service agreements. Their actual scope and operating terms must be agreed before a plan starts.
Does the monthly allowance include the check itself?
Yes, in the proposed plans. Website care allows up to 45 minutes for a monthly check plus 30 minutes of minor content changes. Automation care allows a 30-minute check plus one hour of minor workflow changes. Brain care allows a 45-minute health or backup check plus two hours of minor changes. Unused time does not roll over.
Would care cover new features or an emergency?
The proposed care plans exclude new features, emergencies, compromised-system recovery, third-party outages and round-the-clock monitoring. Their allowance is for the stated check and minor changes. Additional work needs a written quote before it begins. A monthly check should not be understood as a promise that every problem is prevented or that emergency cover has been arranged.
How quickly would a care issue be fixed?
The care page describes proposed acknowledgement arrangements, not a guaranteed fix time. Before a plan starts, the agreement needs to identify the contact route, support hours and response arrangements. Resolution depends on the issue and agreed scope. The proposals do not include unlimited support or continuous monitoring, and a reported unresolved finding must not be presented as fixed.
What should I confirm before agreeing to recurring care?
Confirm the maintained system, monthly cap, included checks and changes, required access and recovery responsibilities. Also agree billing, duration, renewal and how the arrangement can end; those terms are not created by viewing a proposed plan. Hosting, domains, software and AI or API usage remain separate. Any extra work needs its own prior written quote.
Bounded care with clear responsibilities
The proposed monthly plans show bounded checks and minor-change allowances. Responsibilities and actual operating terms must be agreed before a plan starts.