Zanzarra

Less firefighting.
More moving forward.

Keep your Drupal website working and improving. Get help with bug fixes, critical updates and performance, with ongoing development when your business needs more.

Discuss ongoing support See what we can build
Concept illustration of a server being maintained beside a diagnostic display

Keep today running. Make room for tomorrow.

Separate issues that need attention now from improvements worth planning. A support conversation should cover both.

Issues keep interrupting your team

Troubleshooting and fixes

Investigate reported problems and resolve bugs. A separate site audit can help identify additional issues.

Maintenance is falling behind

Updates and platform upkeep

Critical updates, performance monitoring and deployment workflows keep ongoing maintenance on the agenda.

The improvement list keeps growing

Support beyond maintenance

Discuss new functionality, commerce improvements and Drupal consulting alongside the support workload.

A clear next step.
At every step.

A starting approach to discuss together. The scope and checkpoints should fit your project.

  1. Review the website

    Share the platform, known issues and how the site is maintained today.

  2. Agree priorities and coverage

    Define the support scope, communication and SLA terms before work begins.

  3. Resolve and maintain

    Address agreed issues and maintenance needs in manageable iterations.

  4. Plan improvements

    Keep new requests visible and discuss their priority alongside maintenance.

Meet the people behind the work

Before we start.

Questions worth asking before committing to a project.

Can you support a site built by another team?

Send the website address, Drupal version if known and a summary of the issues. The first step is to understand the existing site and agree what support would involve.

What response time can we expect?

Response times, coverage and escalation are agreed in the SLA. Tell us your operating hours and the business impact of an issue so these requirements are explicit.

Can support include new features?

Yes. Custom development is part of the published support offer. The feature scope and its priority need to be agreed alongside ongoing maintenance.

What needs attention?

Share the issue or the kind of ongoing help you need. Do not include passwords or access credentials.

sales@zanzarra.com

Next: review and send your email. We can use your brief to discuss scope, questions and possible next steps.

I’m looking to… (choose any)

Opens your email app. Nothing is sent or saved automatically.

Prepare project email