AI workflow maintenance and optimization
Maintenance, quality tuning, and improvement work, with someone accountable when the output looks off.
Why AI workflows need maintaining
An AI workflow is not something you install and leave. Ordinary changes move its output.
New client types arrive with documents laid out differently.
The workflow was tuned on what came before.
Suppliers change their forms.
Extraction that was reliable starts missing a field.
The team starts using it for adjacent work.
Work it was not tested on.
Model providers release updates.
Output that was consistent shifts in tone or structure.
Your own standards change.
What counted as a good draft last year is not what you want now.
None of these stop it working. They move the output gradually — from reliable, to occasionally needing an edit, to needing a careful check every time. At that point people quietly return to doing the work by hand, and the conclusion becomes that AI did not suit the business.
Maintenance is what prevents that.
Three levels of AI workflow support
| Lite | Standard | Advanced | |
|---|---|---|---|
| Covers | A single workflow | A sequence several people depend on | Workflows the business runs on |
| Fixes and quality tuning | Included | Included | Included |
| Monthly written check-in | Included | Included | Included |
| Monthly review call | — | 45 minutes | 45 minutes |
| Quality sample review | — | Monthly | Deeper, tracked over time |
| Continuous improvement work | — | Minor changes | Against a prioritized backlog |
| Performance reporting | — | — | Monthly |
| Multi-team support | — | — | Included |
| Quarterly review | — | — | Included |
| Response priority | Standard | Standard | Priority |
Outside this engagement
- New workflows — quoted as implementation work.
- Rebuilds and redesigns.
- Out-of-hours or on-call response.
- Unlimited changes.
Anything outside scope is quoted before the work is done, never after.
Terms
Monthly and rolling. Thirty days’ notice either side. Hours reset monthly and do not carry over. Available after an implementation. Move between levels at any point, effective the following month.
If several months pass with little to do, we will say so and suggest moving down a level.