01Protect
Maintenance baseline
Document the platform, hosting, accounts, domains, certificates, backups, integrations, dependencies, and recovery path before routine work begins.
A website should not become an abandoned project
Keep the website current, recoverable, and ready for the next change.
Avian Creative Systems provides a defined monthly capacity for maintenance, content updates, monitoring, verification, and prioritized improvements without turning the arrangement into an unlimited support promise.
Typical starting point$100 or $200 monthly
Month-to-month, Care Essentials is $100 for up to 2 total monthly hours and Care Active is $200 for up to 4. As an alternative, prepay 12 months at 20% off: $960 for Essentials or $1,920 for Active. There is no separate onboarding charge. Initial baseline work uses the selected plan's included capacity, both billing choices keep the same monthly allowance, and unused time does not roll over.
01Recoverable baseline
02Visible queue
03Approved changes
The quiet work that protects the public experience
Keep the baseline healthy.
Keep the next decision visible.
Websites drift. Content becomes stale, dependencies change, certificates renew, forms fail quietly, campaigns need updates, and small requests accumulate. A care plan gives those responsibilities a defined place, a monthly capacity, and an approval boundary so the site remains usable without becoming an invisible open-ended obligation.
What the work may include
A complete path.
A bounded scope.
The plan is tailored to the platform and risk. A static site may need release, content, form, certificate, and uptime attention; a CMS may also require backups, core and plugin updates, staging, license awareness, security review, and a more careful regression routine.
02Maintain
Approved monthly changes
Use the included capacity for agreed content edits, page changes, updates, dependency care, form adjustments, and other bounded website needs.
03Watch
Monitoring and verification
Check the important public paths, forms, certificates, visible errors, and release behavior appropriate to the plan; record incidents and follow-up needs.
04Plan
Improvement queue
Maintain a visible list of recommended improvements, distinguish urgent maintenance from optional enhancement, and obtain approval before exceeding the monthly capacity.
Where it becomes useful
Recognizable situations.
Practical responses.
See how ongoing care can create a dependable operating lane for common website needs. Every check, report, coordination task, and change uses the plan's total monthly allowance.
A
Owner without a web administrator
The situation
The business can approve changes but has no one responsible for updates, backups, form checks, or the small technical decisions that follow launch.
What Avian can do
Create a documented baseline, a request and approval path, a recurring check rhythm, and a bounded monthly capacity for maintenance and changes.
What this makes easier
Website responsibilities stop depending on memory, and the owner can see what was completed, what remains, and what requires separate approval.
B
Active site with regular changes
The situation
Services, events, resources, campaigns, and calls to action change often enough that one-off requests create delays and inconsistent pages.
What Avian can do
Use the active plan for a prioritized monthly queue, coordinated content updates, release checks, and a clear overflow estimate when the work exceeds four hours.
What this makes easier
Routine changes have a predictable operating lane while larger initiatives remain separately scoped.
C
CMS with ongoing dependency risk
The situation
Core software, plugins, themes, forms, and licenses require attention, but changing them directly on production could disrupt public pages.
What Avian can do
Maintain backups and staging where available, review dependencies, test approved updates, run regressions, and preserve rollback for changes with meaningful risk.
What this makes easier
Maintenance decisions become evidence-based and recoverable instead of being postponed indefinitely or performed blindly on the live site.
From handoff to responsible stewardship
Know the baseline.
Work from an approved queue.
A care relationship begins with access, ownership, platform, backup, and responsibility mapping. Monthly work is then selected from a visible queue, completed within the included capacity, verified, and reported. Work that exceeds the plan is estimated before it begins.
Baseline
Document the website, accounts, dependencies, recovery path, and critical visitor actions.
Prioritize
Agree on the monthly maintenance and improvement queue before spending the included time.
Maintain
Complete the approved work, use staging or backups where risk requires it, and keep scope visible.
Report
Record completed work, verification, remaining risks, time used, and recommendations for the next cycle.
A website that needs an accountable owner
A strong care plan has a known platform, a recoverable baseline, a clear request path, and a real monthly limit.
This service is appropriate when the site needs regular attention and the business values continuity, documentation, and approval boundaries. It is not 24/7 emergency response or unlimited redesign work.
- No one currently owns routine website maintenance
- Content and campaign changes arrive throughout the month
- A CMS requires staged updates and dependency awareness
- The business wants predictable capacity without an unlimited retainer