Delivery standards
The terms we set ourselves before anyone asks.
These are working commitments, not achievements. They describe how we intend to behave on every engagement and what you are entitled to hold us to.
Written scope
Every engagement begins with a statement of what is included, what is not, and what we need from you.
A range before a figure
We give a cost range early and refine it as uncertainty shrinks, never the reverse.
Named assumptions
Estimates list the assumptions they depend on, so changes are traceable rather than arguable.
Visible progress
You can see working software or design at least every two weeks during active delivery.
Early warnings
If a date or budget is at risk, you hear it from us as soon as we know, with options.
Change control
New requests are welcome; each is estimated and agreed in writing before it is started.
Accessibility
WCAG 2.2 AA is our working target; known exceptions are recorded and explained.
Security
Dependencies are kept current, secrets are never stored in code, and access follows least privilege.
Testing
Automated tests cover critical logic; manual checks cover real devices, browsers and assistive technology.
Privacy
We collect only the personal data a feature needs and document where it goes.
Source and accounts
You receive the source code and hold the accounts for stores, hosting and domains.
Documentation
Architecture notes, run-books and a list of every external service the product depends on.
A quiet exit
If you move to another supplier, we will help hand over in an orderly way.
What we do not claim
No borrowed credibility.
This website does not list awards, client logos, star ratings, statistics or testimonials. That is deliberate. We would prefer that you judge us on the clarity of the first conversation and the quality of the written diagnosis that follows it.