Method & standards
Slow where it matters, quick where it does not.
Our approach is four seasons long: listen, shape, build, release. Each ends with something written down that you can keep.
Listen
Conversations with you and, ideally, with a few future users. Output: a one-page problem statement and list of assumptions.
Shape
Journeys, priorities and prototypes. Output: a scoped version one and a phased estimate.
Build
Short cycles with installable builds or preview links. Output: working software and a running changelog.
Release
Checklists, store preparation, staged rollout. Output: a launched product and a maintenance note.
Our checks before anything is called finished
Every release we are responsible for is checked against these before we call it done.
- Understandable. A new user can complete the main task without help.
- Accessible. Keyboard and screen-reader paths work; colour contrast meets WCAG 2.2 AA.
- Respectful of data. Only data with a stated purpose is collected; privacy notices match reality.
- Readable copy. Plain British English, helpful error messages, no dead ends.
- Tested on real devices. At least one older phone, not just the latest.
- Recoverable. Backups, rollback steps and who-to-call written down.
- Documented. Someone else could pick it up from the handover notes.
- Honest limitations. Known issues listed, not hidden.
What we can honestly point to
ELAIOS LTD is a young practice. We do not publish client names, testimonials or results without written permission, and we have no awards to display. Rather than fill this space with borrowed credibility, here is what we can state plainly:
- We have a registered UK company and a published Edinburgh address.
- We have written our quality criteria and apply them to our own work, including this website: no trackers, no external fonts, a working contact form with honest error messages.
- We will share examples of relevant work privately on request, where the people involved agree.