Which costs should you consider?
Running, backing up and monitoring the back-end system; third-party services; the required developer accounts; error handling; checks related to platform changes; and managing content and later features. Not every item applies to every project.
Bug fixing or further development?
A result that differs from the agreed behaviour is not the same as a new feature requested later. Acceptance criteria, a fault reporting process and change management help distinguish them.
Who is responsible for connected systems?
An app fault, a back-end outage or a change to an external API may require different interventions. It should be clear who checks each system, who has access and who decides on the necessary changes.
What should an operations agreement record?
The supported environment, contact channel, response and intervention rules, backups, responsibility for recovery and work charged separately. Response times and availability are specific commitments, not an automatic part of every development price.
How do we address this in the proposal?
We distinguish initial development from tasks after handover. The scope of support, platform updates and further development is defined for the particular app. The development fee does not automatically include unlimited support.