The first week after launch is when the real process shows up. The exception nobody mapped. The integration that only fails on Fridays. The dashboard that was right in staging and stale in production. If you walk away at go-live, you shipped a demo.
Living intelligence is the boring work after: alerts that stay current, numbers the team will quiz, a loop you can still reverse. We stay on for that — not as a retainer slogan, as the part of the build that makes the system honest.
Go-live is not the end of the product
Launch day is a screenshot. Month two is the product. If the quote ends at deploy, you will pay for the missing week in Slack. Scope the after: who watches the loop, what we measure, when we come back.
What “stay current” means
- The dashboard reads the same records the team writes.
- An alert fires on the exception, not on every row.
- Someone can explain a number without opening three tools.
How to budget for it
Put a named window after launch in the statement of work. Not “support.” A week of watching the real process, fixing the exception path, and confirming the number the operator will quiz. That is cheaper than a silent wrong write that lives for a month.
This is why we talk about human review and order intelligence in the same breath as launch. The write and the number have to stay honest after the party.
What we watch in the first weeks
On catering and tutoring systems, the first weeks expose the Saturday path, the cover shift, the city that is out. On shipping, they expose the document that is always late. Those are not edge cases. They are the product. Map them, then decide what to automate.
Frequently asked questions
Is this a retainer?
It can become one. It starts as scoped aftercare on the build, so the system is honest in month two.
Can we skip this if the UAT went well?
UAT is not Saturday in production. Budget the week anyway.
Does this include training?
The people who run the loop should be in the room before go-live and after. See Training & Workshops if the team needs a facilitated pass, not a handoff PDF.
What to do next
If your last vendor left at deploy, we can still take the after. Contact us and bring the loop that is already lying to you.
