How we deliver
The standards behind every release
These are the commitments we work to on every project, whatever its size. They are written to be checked: ask us at any time to show how a standard is being met.
Stage by stage
Discovery delivers
- A written problem statement and list of intended users.
- Priority journeys and a "not yet" list.
- A clickable prototype of the core journey.
- A build plan with costs per cycle.
Each build cycle delivers
- A working preview you can try on your own device.
- A short written summary of what changed and what is next.
- Code reviewed by a second developer before merging.
- Automated checks running on every change.
Release delivers
- A completed release checklist covering accessibility, security and content.
- Store submissions or web deployment during working hours.
- A rollback plan agreed before switching over.
Handover delivers
- Source code in a repository you own.
- Account access transferred to your organisation.
- Run-book notes: how to deploy, back up and update.
Accessibility
We design and test against the Web Content Accessibility Guidelines at level AA as our working target. That covers colour contrast, keyboard access, screen reader labelling, text resizing and motion preferences. Where a third-party component falls short, we tell you and propose alternatives.
Security and personal data
- Collect only the personal data a feature genuinely needs.
- Encrypt data in transit and use reputable hosting with encryption at rest where available.
- Keep secrets out of source code and rotate credentials at handover.
- Apply dependency and platform updates as part of support plans.
Communication
You will have one named point of contact, a shared place where work in progress can be seen, and a written summary after each review. Estimates are given as ranges with assumptions spelt out; if something changes, we tell you before the cost does.