- Checklist
- Seven items
- The test
- Change one rule without the supplier
- Nexvix
- Recorded walkthrough included
The seven items
- Admin credentials transferred to your accounts, not shared from theirs
- Source code in your repository, with commit history
- An architecture note: what runs where, and what calls what
- Rules, prompts and thresholds in editable, version-controlled form
- The evaluation set and the verification results against your target
- The operating guide: how to pause, change and monitor the system
- A recorded walkthrough of all of the above
None of these are unusual requests. A supplier declining any of them is telling you something useful about the next two years.
The test that proves it
Two weeks after handover, change one rule yourself (a threshold, a business-hours window, an escalation owner) without contacting the supplier. If you can, ownership is real.
If you cannot change one rule alone, you did not take ownership.
What support should be after that
Optional, priced separately, and never a requirement for the system to keep running. A retainer that is load-bearing is a dependency dressed as a service.
The first eight weeks
Real traffic finds cases the audit did not, so budget for change in the first two months and watch the escalation rate weekly. This is normal and worth planning; it is not a sign the build was wrong.