Who owns the day-to-day operations?
Clarify who manages the server, application, updates and support requests. A hosting account and an application support agreement can cover different responsibilities. Ask for a simple written list so the team knows where to report an issue.
What workload are we planning for?
Describe active users, busy periods, scheduled jobs, integrations and expected data growth. Ask how performance will be monitored and when capacity will be reviewed. A plan based only on total employee count may miss the periods when your system is busiest.
What is backed up, and can it be restored?
Agree the backup scope, frequency, retention and recovery responsibilities. Ask when a restore was last tested and what the recovery procedure requires. Discuss acceptable downtime and data loss in business terms rather than assuming every backup arrangement meets the same needs.
How are access and changes controlled?
Identify who needs administrative access and how it is removed when someone leaves. Agree how updates and custom changes are reviewed. Ask whether a separate test environment is available before changes reach everyday users.
What happens during an incident or a move?
Confirm how to raise an urgent issue, the coverage hours and the escalation contact. Finally, ask how your data and configuration can be exported if you change providers. Include handover responsibilities and any associated work in your agreement.