By Steadnet Cyber · 15 September 2026
Know what you are accepting
Use the agreed acceptance criteria and test the main journeys with realistic sample data. Record remaining limitations and who owns any follow-up work. A demonstration alone should not replace acceptance testing.
Put accounts under clear ownership
Identify the organisation responsible for hosting, domains, subscriptions and code. Give named people appropriate access and a recovery route. Share credentials through an agreed secure mechanism, not a general support email.
Ask for operational information
- How to start, use and administer the application.
- Where data is held and how to export it.
- What backup and restore arrangements are included.
- Who receives alerts and support requests.
- Which third-party services and ongoing costs are involved.
Define the support model
Agree the included period, scope, communication route and coverage. Distinguish faults against the accepted scope from new functionality. Ask how urgent problems are handled and what happens when the support arrangement ends.
Plan the first review
Collect feedback after people have used the application for real work. Review adoption, difficult steps and the quality of data. Prioritise changes based on evidence rather than adding every suggestion immediately.
Steadnet includes an agreed support model in small-app quotes; the details are defined before delivery. Larger or ongoing arrangements are scoped separately.