Maintenance and support
Updates, backups, small edits, and a named person when something breaks, under a written boundary.
What you get
- A named person who answers when something breaks.
- Updates and backups done on a schedule, under a written boundary.
- A monthly price you can put in the budget, and stop when you need to.
Where it goes wrong
After launch, the vendor disappears or every request becomes a new quote. Updates stop on the Drupal or WordPress site, and the maintenance plan that was promised never starts. The form stops sending in the busy week and nobody notices for days.
What we do
- Security and platform updates on a schedule.
- Backup checks, with restore tests where the agreement includes them.
- Monitoring, and a look when the site stops answering.
- Small edits on the Keep it current plan and above: a staff name, a PDF, a date on an existing form.
- One named person to write to: Leonardo Calado.
How it runs
The agreement says what a month includes and what it leaves out. Requests go into one queue, ordered by urgency. New sections, new integrations, and campaigns are scoped separately. The same boundary is on the pricing page. You can leave at any point with the site, the content, and the accounts.
Who this fits: Associations, Nonprofits, Small businesses, Community organizations. Prices are on the pricing page.