Key takeaways
- A retainer is not “we’ll fix it if it breaks.” It is monitoring, fixes, improvements and reporting.
- Insist on response-time targets, a named owner and a monthly report you actually receive.
- If a vendor can’t tell you what they watch and how fast they respond, that is your answer.
Why most software dies after launch
The launch is a milestone, not the finish line. The moment software goes live it starts to drift: dependencies age, integrations change, data grows, models get upgraded, and the business it serves keeps moving. Without someone tending it, a system that worked beautifully in month one is limping by month nine. The usual story is not a dramatic failure, it is slow neglect, until one day it breaks and nobody remembers how it works.
The five things a real retainer covers
When you read a support proposal, look for these five. If any are missing or vague, push until they are specific.
1. Monitoring
Someone, or something, watches the system around the clock: uptime, errors, queue depth, and for AI, accuracy and cost. You should be able to see a live status, not find out from an angry customer.
2. Fixes with a response-time target
When something breaks, how fast does work start? A real retainer states it: critical issues in hours, minor ones in days. “Best effort” is not a target.
3. Improvements, not just patches
Good partners ship small improvements every month, not only emergency repairs. The software should be a little better in month six than it was at launch.
4. Security & updates
Dependencies and platforms get patched on a schedule, before they become a breach. For AI, that includes re-evaluating after every model upgrade.
5. A monthly report you actually get
One page: what we watched, what we fixed, what we improved, and the metric that matters to you. If you never see a report, you are not really on a retainer.
The test is simple. Ask a vendor: what do you monitor, how fast do you respond, and what will I receive each month? Hesitation is the answer.
Weasel words to avoid
“Ad-hoc support,” “available on request,” “best-effort maintenance,” and “we’ll bill by the hour when needed” all mean the same thing: nobody is actually responsible. They are fine for a brochure site; they are dangerous for software your business runs on.
How retainers are priced
A fair retainer is sized to what is being kept live: the complexity of the system, the volume it handles, and how fast you need issues resolved. It should be a predictable monthly number, not a surprise invoice. Expect it to scale with the surface area being supported, and expect the value to show up as uptime and saved hours, not just a line of cost.
In short
Building software is the easy half. Keeping it alive, secure and improving is where the value compounds, or quietly leaks away. That is exactly why we build and then run what we ship, instead of handing over files and disappearing.