What a client should own when a digital system goes live
Ansh PuniaIndependent AI & systems builder
A practical checklist for domains, accounts, data, repositories and documentation.
01Own the accounts that control the asset
Domains, hosting, analytics, email, cloud services and paid integrations should sit in client-controlled accounts wherever practical. Delivery access can be delegated without transferring long-term control.
02Know where the data and source live
The handover should identify production data, backups, source files, repositories and the method for restoring service. Access lists also need to show who can change, export or delete important information.
03Document the operating reality
Useful documentation covers routine administration, important decisions, known limits, renewal costs and the support path. A client should not need to reverse-engineer the project six months after launch.
Before moving forward, make these visible.
- Client-controlled production accounts
- Source, data and backup locations
- Current access register
- Operating and recovery notes
How I work
This thinking is part of how I approach delivery work—scoped around the business outcome, built in stages you can review, and handed over with the accounts and documentation in your name.
See how delivery projects run
