Delivery standards
What you can hold us to, on every project, written down before work starts.
Eight commitments
| No. | Standard | What it means in practice | How you can check |
|---|---|---|---|
| 1 | Written scope | Every phase begins with a short written scope, including what is excluded. | You approve it before work starts. |
| 2 | Fortnightly builds | A working build or prototype every two weeks. | A link you can open yourself. |
| 3 | Your ownership | Code repositories, domains and store accounts in your name. | You hold the admin credentials. |
| 4 | Accessibility | WCAG 2.2 AA as the working target. | Checklist delivered with each release. |
| 5 | Security basics | Encrypted connections, least-privilege roles, dependency updates, secrets kept out of code. | Summary in the handover notes. |
| 6 | Data minimisation | We collect only what a feature needs and document where it is stored. | Data map in the handover. |
| 7 | Plain records | Decisions logged in a shared document, not lost in email. | Read access from day one. |
| 8 | Handover | A guide written for whoever looks after the system next. | Delivered before final sign-off. |
How a project is phased
Discovery is short and paid, ending in a written scope, a prototype and a broad range for the build. Build runs in fortnightly increments. Each increment is demonstrated, and you can stop after any of them with working software and its code. Launch is followed by a settling period where we watch for problems closely.
Testing we do as standard
Automated tests cover the logic that records depend on: calculations, imports, permissions. Manual testing covers real devices, including older phones, in the conditions the software will meet. Before any release we run an accessibility pass and a check that exports and backups actually restore.
When things change
They will. A change request is written down with its effect on time and cost before anyone agrees to it. Small adjustments within a fortnight's work are absorbed; larger ones are scheduled openly.
What "done" means
Done means the feature works on the agreed devices, has been used by at least one real person in your organisation, is covered by the handover notes, and you have said yes. Not merely that the code was written.