The retainer that keeps the system running.
The Implementation engagement ships the system. The Ongoing AI Support retainer is what keeps it running — coverage scope, response time tier, and SLA level, all custom to the operational cadence you actually run. Built from your implementation artifact, scoped per review, and routed by the founder rather than a SaaS subscription engine. Recurring but custom, not recurring and templated.
Build
From your implementation artifact
Engagement
Recurring, custom-scoped
You leave with
A retainer that fits your cadence
Inquire about an AI Support retainer
We will reply within three business days with a custom retainer shape — coverage scope, response time tier, monthly fee, and the first quarterly review cadence.
Stage 05 · Ongoing AI Support · subscription inquiry.
The retainer is built from your Implementation engagement — start there if the system is not live yet.
What ongoing support covers
The retainer, in four pillars.
- 01
Coverage scope
Three shapes — monitoring and quarterly reviews, model and prompt maintenance, and the full retainer that covers build plus ongoing support. Pick the layer that fits how aggressively your operation changes; move between them as the system matures. Not a SaaS subscription, not a usage meter.
- 02
Response time
A response cadence you actually run — best effort, reply by next business day, or same-day for the systems on the critical path. We agree on the tier during the first quarterly review and revisit it whenever the operating picture changes.
- 03
SLA levels
Written uptime and response windows for the systems on the critical path — what is guaranteed, what is best effort, and the escalation path if something falls outside the window. The retainer is the paperwork; the SLA is the test we run against.
- 04
Governance & compliance
Quarterly reviews on data handling, model drift, and the prompts that wrap them. We document what changed between reviews, what the team did with the system over the quarter, and what is on the list for the next one.
Questions? Email werkbench@polsia.app.
Frequently asked
Before the system goes live.
- 01
Do I need the Implementation engagement first?
Yes — the retainer is built from the implementation artifact, not from a fresh discovery. We need the system we are supporting to already exist in your environment, with the written runbooks and the team that operates it. If you have not done the implementation yet, start there and we will reach back out to support once go-live is behind you.
- 02
Is this a SaaS subscription?
No. There is no usage meter, no monthly minimum, no per-seat fee, and no obligation to renew. The retainer is custom-scoped to your operational cadence — you stop paying when you stop needing us, and the SLA is the test we run against. We do not roll support into the implementation fee, and we do not push you onto a subscription to keep the lights on.
- 03
How is the monthly fee set?
From three inputs and only three inputs: the coverage scope you pick, the response time tier you pick, and the SLA you want in writing. We quote a fixed monthly fee from those three choices — not from a usage meter, not from surprise hour counts — and we revisit the fee at every quarterly review.
- 04
What if we outgrow the SLA?
That is the conversation we want to have. A quarterly review is the right place to escalate the tier, drop a system from the critical path, or end the retainer entirely. We do not auto-renew into a higher tier and we do not penalise a downgrade — the SLA is a written agreement, and a change to it is another written agreement.