Agencies

Automation maintenance contracts: what to include and how to justify them

What an automation maintenance contract should cover, what it should exclude, and how to prove to your client every month that it is worth the money.

By Abdellah El Kharraze · · 2 min read

Key takeaways
  • A maintenance contract sells availability, not hours.
  • Four parts: monitoring, fixes, updates, reporting.
  • Write down in black and white what is excluded.
  • The monthly report is what gets the contract renewed.

Delivering a workflow is a project. Keeping it alive is a service. Many n8n and Make providers bill the first and give away the second without saying so, until the day a failure costs them a weekend and a client.

The four parts of the contract

  • Monitoring. Detection of failures, deactivated workflows and silent failures, with a stated response time.
  • Fixes. Restoring existing workflows: expired connection, third-party API change, unexpected data.
  • Updates. For self-hosted n8n, version upgrades and security patches.
  • Reporting. A monthly account of what ran and what was fixed.

What to exclude in writing

Functional changes, new workflows, failures caused by a change the client made, and outages of third-party services. Without that list, every request becomes “maintenance”.

How to set the price

A flat monthly fee per client, based on the number of critical workflows and the promised response time. Avoid hourly billing: it penalises you for being efficient, and the client only sees the months when “nothing happened”.

The report, your best argument

A month with no visible incident is a month in which monitoring did its job. You still have to show it: number of successful executions, incidents detected, average resolution time, trend. Stay factual: write “0 failures detected”, not a promise about the client's revenue.

Nokto produces this report for each client, read-only by link. See Nokto for agencies.

Frequently asked questions

Which response time should I promise?

The one you can keep with your real set-up. Four working hours kept is better than one hour promised and missed.

AE
Abdellah El Kharraze

Founder of Nokto and Owepo, based in Nice, France. Network and security engineer for large enterprises until 2016, then ten years building n8n and Make automations for small businesses.

Your first monitored workflow in ten minutes.

Connect an n8n instance or a Make team: Nokto discovers your workflows, learns their rhythm and warns you at the first anomaly.

14 days free · no credit card · cancel anytime