Separate ownership from access
A vendor may need administrative access without owning the account. The business should understand whose name controls the domain registration, analytics property, payment processor, email service, and customer database.
Where practical, client-owned accounts with documented vendor access create a cleaner handoff and reduce uncertainty.
- Domain and DNS account
- Website source and content
- Analytics and advertising accounts
- Payment processor
- Customer and CRM records
Define the monthly service
Hosting is only one part of ongoing service. A monthly plan may include monitoring, backups, routine updates, small content changes, analytics review, or support—but those boundaries should be written down.
Ask what happens if the monthly service ends. The agreement should explain service continuity through the paid term, data export, migration assistance, and which components can operate independently.
List external costs before activation
Payment processing, email delivery, calendars, mapping, fraud protection, user seats, domains, and specialized analytics may come from third parties. Their prices and terms can change outside the developer’s control.
A responsible proposal identifies known external costs, explains who pays each provider, and requires approval before a paid integration is activated.
Create a change and offboarding path
Routine maintenance and new development are different kinds of work. Define examples of each, the approval process, and how estimates will be presented.
Offboarding should include exportable customer records, account and integration documentation, current source or transfer-eligible materials, and a clear timeline. A future transition should be planned even when everyone expects the relationship to continue.