# Launch checklist vs retainer checklist for AI-built websites

A launch checklist answers one question: is this site safe to show a client today? A retainer checklist answers a different one: will we notice when it gets worse next month? Agencies that treat those as the same document keep shipping [AI-built sites](https://devlog.apogeewatcher.com/ai-built-sites-core-web-vitals-regressions-after-the-padlock) that look finished on Friday and feel slow after the next content prompt.

The launch pass is short, human, and often honest. Forms work. Mobile layout holds. Analytics fires once. Someone ran PageSpeed Insights on the homepage and pasted a green-ish score into Slack. The retainer pass is calendar-shaped: named URLs, dated lab runs, field context when CrUX exists, and a named owner when Largest Contentful Paint or Interaction to Next Paint moves. AI builders make the gap wider, because a successful afternoon QA does not survive an unsupervised redesign of the hero or a new chat widget.

What follows is a side-by-side for agency teams and freelancers who ship AI-assisted sites into retainers. For what automated monitoring means in plain terms, see [What Is Automated Web Performance Monitoring?](https://apogeewatcher.com/blog/what-is-automated-web-performance-monitoring?utm_source=hashnode&utm_medium=referral&utm_campaign=launch-vs-retainer-checklist-ai-sites). For why agencies outgrow manual checks, see [Why Agencies Need Automated Performance Monitoring in 2026](https://apogeewatcher.com/blog/why-agencies-need-automated-performance-monitoring-in-2026?utm_source=hashnode&utm_medium=referral&utm_campaign=launch-vs-retainer-checklist-ai-sites).

## What a launch checklist is for (and what it is not)

A launch checklist is a gate before the custom domain goes live. Typical rows cover critical journeys (home, contact, booking or checkout), forms and email delivery, broken links, mobile layout, basic accessibility, SEO tags, analytics, and a one-off Lighthouse or PageSpeed Insights pass on home and the conversion URL. The job is binary enough for a ship decision: ship, fix, or delay.

It is not a monitoring plan. Passing once does not create history, budgets, or alerts. It also does not prove field Core Web Vitals for real users; CrUX needs traffic and time. Launch QA can include a lab score, but that score is a photograph of one URL on one day, not a retainer obligation.

For AI-built sites the launch list still matters. Builder previews lie; the published origin is what clients open. Forms, redirects, and consent banners deserve a human pass even when the model wrote the templates. The mistake is stopping there and calling performance “done.”

## What a retainer performance checklist covers

A retainer checklist assumes the site is already live and somebody will keep watching it. The useful rows look more like operations than launch day:

- Named URL set (home, conversion path, one or two templates that change often)
- Scheduled lab tests on a fixed cadence (weekly is enough for many small retainers; denser where deploys are frequent)
- Field context when PageSpeed Insights or Search Console shows CrUX for the origin or URL
- Budgets or plain thresholds on LCP, INP, and CLS that a human can explain
- Alert or review ritual with a named owner (Slack channel, weekly standup line, or report pack)
- Change log of what shipped since the last green period (theme edit, tag manager, AI prompt, plugin)

That list is the monitoring half of automated web performance work: schedules, history, thresholds, and a person who acts. It is deliberately boring. Boring is what survives a portfolio of AI-assisted client sites.

## Side-by-side: launch afternoon vs weekly monitoring

| Question | Launch checklist | Retainer checklist |
| --- | --- | --- |
| When | Once before go-live (and after big launches) | On a calendar after go-live |
| Pass condition | Journeys work; no blockers; one lab sanity check | Trends hold; regressions get a ticket |
| Artefact | Checkbox list / QA notes | Dated runs, budgets, alerts, monthly proof |
| Owner | Launch engineer / PM | Account or performance owner on the retainer |
| AI risk it catches | Broken forms, missing tags, obvious layout | Hero swaps, new widgets, script creep after prompts |
| Stops when | Domain is live | Never; cadence continues |

Both lists can share a few URLs. They should not share a single “done” checkbox. Launch says the site can open. Retainer says you will notice when it softens.

## How AI-built sites break the gap between the two

AI builders and agent workflows accelerate the launch list. They also accelerate post-launch drift. A prompt that replaces the hero image, injects a booking iframe, or adds a chat script can clear launch QA and still move LCP, CLS, or INP within a week. Cookie banners and marketing tags often arrive after the padlock, which is after the launch checklist closed.

Teams that only re-run the launch list after every prompt waste time on binary gates that already passed. Teams that never leave launch mode miss the regressions that show up as “the site feels slower” emails. The retainer checklist is the cheaper habit: keep the same URLs on a schedule so the next prompt has a before-and-after, not a memory of Friday’s green score.

Agencies feel this first. One AI-built brochure site is manageable as a spot check. Ten clients with weekly content prompts are not. That is the same scaling story as any portfolio without schedules: manual honesty that does not fit the calendar.

## How to hand off from launch QA to a monitoring loop

A practical handoff after go-live usually looks like this:

1. The launch checklist stays in the project folder as the ship record.
2. Three to five URLs move into the retainer set (home, conversion, one volatile template).
3. Those URLs sit on a weekly lab schedule, with mobile and desktop as separate series where both matter.
4. One budget line per Core Web Vital the client already understands (or score bands if that is the retainer language).
5. A named reader for the first amber week: account manager, developer, or shared channel.
6. After any AI builder session that touches layout, media, or third-party scripts, the next scheduled run is mandatory reading, not optional polish.

You do not need a heavy stack on day one. You need a calendar and a short URL list. Tools that already define schedules, budgets, and multi-site views fit when the portfolio grows; the definition of automated monitoring is still those jobs, not a one-off paste.

## FAQ

**Can the launch checklist include Core Web Vitals?**\
Yes, as a lab sanity check on key URLs. Treat it as evidence for ship day, not as proof that field vitals will stay green.

**Is a monthly PageSpeed Insights paste a retainer checklist?**\
Only if you save dates, compare the same URLs, and act when numbers move. A lonely paste without history is still launch-style QA on a slower clock.

**Do AI-built sites need different monitoring than hand-built ones?**\
The metrics are the same. The change rate is often higher, so the retainer cadence matters more after prompts that rewrite layout or inject scripts.

**Where does a one-off “fix Core Web Vitals” agent prompt fit?**\
It can help diagnose a URL. It does not replace either checklist. Launch still needs human journeys; retainer still needs scheduled evidence.

## Keep both lists, stop merging them

Launch QA gets the site live. Retainer monitoring keeps the story honest after the next edit. AI-built websites make that split sharper, not softer. Ship with a launch checklist, then put the same critical URLs on a dated loop before the first unsupervised prompt goes live in production.

If you want that loop across many client hosts without another Monday paste, [try Apogee Watcher](https://apogeewatcher.com/sign-up?utm_source=hashnode&utm_medium=referral&utm_campaign=launch-vs-retainer-checklist-ai-sites) or run a [free domain check](https://apogeewatcher.com/check?utm_source=hashnode&utm_medium=referral&utm_campaign=launch-vs-retainer-checklist-ai-sites) on the URLs you just launched.

## References

- [What Is Automated Web Performance Monitoring?](https://apogeewatcher.com/blog/what-is-automated-web-performance-monitoring) (Apogee Watcher)
- [Why Agencies Need Automated Performance Monitoring in 2026](https://apogeewatcher.com/blog/why-agencies-need-automated-performance-monitoring-in-2026) (Apogee Watcher)
- [AI-built sites: the Core Web Vitals regressions that show up after the padlock](https://devlog.apogeewatcher.com/ai-built-sites-core-web-vitals-regressions-after-the-padlock) (Apogee Watcher DevLog)