Chapter 10 of 11
How we play fair
These are the rules we hold ourselves to. They're not achievements or awards — just commitments you can hold us to and check.
Before we start
- Written scope. A plain-English summary of what we'll build, what we won't, and what we're assuming.
- Estimates with ranges. Every estimate shows its assumptions and what would move it up or down.
- No surprise extras. Anything outside the agreed scope is quoted and approved before we do it.
- Your accounts. Repositories, hosting, store and domain accounts set up in your organisation's name.
While we build
- Fortnightly demos. Working software you can try, with short release notes.
- A shared list. One place where every task, question and decision is visible to you.
- Early bad news. If something is going to slip, you hear about it as soon as we know, with options.
- Office hours. Replies Monday to Friday, 09:00–18:00 UK time.
Quality
- Accessibility. We design and test toward WCAG 2.2 AA, including keyboard and screen-reader checks.
- Security basics. Least-privilege access, secrets kept out of code, dependencies kept current, data minimised.
- Testing. Automated tests for important logic; manual testing on real phones and browsers before each release.
- Privacy. We collect only what the product needs and help you describe it honestly to users and app stores.
Handover
- Documentation. How to run, deploy and change the software, written for a developer who has never met us.
- Credentials list. Every account, owner and renewal date in one document.
- Walkthrough. A recorded session explaining the code and infrastructure.
- No lock-in. You can take everything to another supplier at any time.
What you won't find here
No invented client lists, no percentage-improvement claims, no star ratings we can't evidence. If we cite something about our work in future, it'll be something you can verify. Until then, we'd rather let the way we work speak for us — and you're welcome to ask hard questions on a first call.