How we build to a standard
Jesse Cliff Orita, Co-Founder & COO · 10 August 2026 · 1 min read
The warranty, the ownership terms and the build quality that come with every project we deliver, explained plainly.
Every project we deliver comes with four commitments. They are not marketing lines. They are the terms of the engagement, and they are the same whatever the size of the work.
A 60-day warranty
Any defect in delivered work reported within 60 days of launch is fixed at no charge. A defect is work that does not do what the agreed scope said it would do. New requirements are new work, and we say so plainly rather than quietly absorbing or quietly billing them.
Full ownership
You own the code, the content, the domain, the data and the accounts. There is no charge for leaving. If you decide to host and maintain the system yourself, or move it to another company, everything transfers. Management is optional, and it stays optional.
A published build standard
Accessibility to WCAG 2.2 AA, and Core Web Vitals within recommended limits, on every site. Publishing the standard is the point: it turns quality from an opinion into something you can test. We check against it during review, before launch, not after a complaint.
A named contact
One person is responsible for your engagement from start to finish. You are not routed through a queue, and you do not have to re-explain the project to a new person halfway through.
Why this matters
Most disputes about digital work come from things that were never written down. A written scope, milestone-based payment, a published standard, clear ownership and a warranty remove most of that ambiguity before it can become an argument.