Tolerances
What we measure ourselves against on every job.
Scope before steel
Each phase begins with a short written scope listing what is included and, just as importantly, what is not. You approve it before work starts. Changes are written down with their effect on time and cost before anyone agrees to them.
Two-week cadence
Work is delivered in two-week stages. Each ends with a working build you can open yourself and a short written note of what changed. You can pause after any stage and keep everything built so far.
Testing
| Check | When |
|---|---|
| Automated tests for calculations, permissions and imports | Every change |
| Manual tests on real, older devices | Every stage |
| Accessibility pass to WCAG 2.2 AA | Before each release |
| Backup restore test | Before launch, then periodically |
Security basics, always
Encrypted connections, least-privilege accounts, secrets kept out of code, dependencies updated and two-factor sign-in on every administrative account we touch. For anything more specialised, we will recommend an independent review.
Documentation
A decision log during the project. At handover: an operating guide, an architecture outline, a data map showing what personal data is stored where, and instructions for routine tasks.
"Done" means
Working on agreed devices, used by at least one real person in your organisation, documented, and accepted by you.