The first deliverable is a scope description: who the version is for, what it will let them do and what it deliberately does not cover yet. For each feature, we add the conditions under which it works and how it will be accepted. That way, a “finished form” means agreed behaviour, including when an entry is invalid or data is missing.
Further work may include screen design, a prototype, building the app, data connections and preparing the release. We agree what is part of the engagement before it starts. You can read more about designing the flow on the app UX/UI design page.
We also describe dependencies on your side: the materials needed, access to systems, responsibility for content and the person who makes decisions. If the first version needs an external service, we first check that it can be used as planned. A screen that displays data does not by itself solve the question of where that data comes from.
We agree how feedback will be gathered after the release. This might be a conversation after a task is completed, observing a pilot or organising incoming reports. We do not add analytics or user accounts by default. If measurement is needed, we first define its purpose and the data involved.