The work doesn't disappear when we do.
After the build, the automations keep running — until something changes. Support is the safety net: you call, we fix, we evolve, we leave. No retainer creep, no monthly fees you forgot you're paying.
After we ship, what happens?
The question
Most clients ask the same thing at handoff: "what if something breaks?" Or worse: "what if everything works and we never think about it again until it doesn't?"
How Support works
Support exists for that. It's not a monthly subscription you forget about — it's a phone number you call when AI tools shift API behavior, your business changes, or a small enhancement makes sense. You pay for the time we actually spend on your account. Some months that's zero.
What you walk away with.
- 1
Monitoring + alerts. We watch your automations. When something fails — an API change, expired credentials, an unexpected output — we know before your team does, and we tell you.
- 2
Bug fixes. When something breaks, we fix it. Logged time only — no scrambling for a fix-it quote in the middle of a fire.
- 3
AI model updates. When a better model launches (Claude 5, GPT-6, whatever's next), we evaluate and swap it into your automations — usually a 30-minute job that improves quality without you doing anything.
- 4
Tool/API change adaptation. n8n updates, Wrike API deprecates, Google changes auth flow. We keep your automations running through every external change so you don't have to think about it.
- 5
Small enhancements. "Can this also email me when X happens?" "Can we add Slack notifications?" Small asks handled within the retainer, no separate scope/quote.
- 6
Office hours + Slack access. Your team can ping us for AI advice — quick questions, second opinions on new tools, sanity checks on AI policy decisions. We're reachable, not just billable.
The After Picture.
The work doesn't slide back. New tools that fit get integrated; tools that stop earning their keep get cut. When something breaks at 2 AM, you don't wake up — we already know. Your operating model stays sharp without you having to think about it. You stop running the AI; the AI quietly keeps running the business.
Common questions before you book.
Why hourly instead of a fixed monthly retainer?
Because most ongoing support clients use a fraction of what a fixed retainer would charge. Hourly-with-logged-activity means we bill for actual work — not for "being available." The trade-off: we don't promise 24-hour response (we're not a 24/7 managed service). You get senior operator time when you need it. If we work zero hours one month, we invoice zero euros.
What if we never need you and pay for nothing?
Then it sits unused — and you pay nothing. Hourly retainer has no minimum monthly hours — billing follows actual activity. It's a contractual ability-to-call, not a recurring charge. Most clients keep Support active for the value of knowing they CAN call us, not because they're racking up bills. Some months we touch your account for 30 minutes. Other months, not at all.
What does a typical month actually look like?
Usually 1–3 hours/month for a single AI Automations engagement that's stable. More in the first 60 days post-handoff (catching small things). Less after 6 months (system has stabilized). Spikes when a major tool changes — an API deprecates, OpenAI shifts a schema, etc. Every hour is logged with a description so you see exactly what we did.
How it works.
- 1
Eligibility check
Support is for clients who've completed a Map or AI Automations engagement with us. Either you're already a client, or we add Support to a fresh engagement before completion.
- 2
Lightweight contract
Hours-based retainer agreement. No minimum hours per month — billing follows activity. Term commitment varies by engagement size — see contract for cancellation and pause windows. Your automations keep running on whatever we last shipped, regardless of contract state.
- 3
You call when you need us
Our monitoring fires alerts to us, you ping us on Slack or email, or you book a session. We log every hour with a description.
- 4
Monthly invoice
End of month, we send an itemized invoice — hours, what we did, dates. If you worked zero hours with us, the invoice is zero.
Frequently asked.
- What if we want to pause Support?
- Pause windows are set in the contract — typically between engagements. When paused, your automations keep running on whatever we last shipped; we just aren't actively monitoring or making changes during the pause.
- Do you support automations we didn't build?
- No. Support is for systems we've built — we know the architecture, the decisions, what to expect. If you have automations built elsewhere that need maintenance, the right path is a small AI Automations engagement to audit and stabilize them first, then Support.
- Is there an SLA on response time?
- Not a guaranteed SLA — we're not a 24/7 managed service. In practice, response is within hours during weekdays, next-day on weekends, and immediate when we proactively detect a breakage. If you need 24/7 guaranteed response, you need a different kind of vendor.
- How is the hourly rate determined?
- Standard rate for senior operator time. Disclosed in the contract and on the invoice — no markup, no per-task pricing, no surprise fees. We don't charge extra for "emergencies" or for nights/weekends within reason.
Keep the work running.
If we've shipped automations together — or we're about to — Support keeps them evolving. Book a call to add it to your engagement.
Book a call