/process
Release
gates.
Delivery standards expressed as gates a release must pass. They describe how we work, not outcomes we claim — we publish no invented results, ratings or testimonials.
Estimating
Estimates are ranges with assumptions attached. When an assumption proves wrong we raise it immediately with the impact on cost and time, and nothing proceeds until you have chosen how to respond.
Cycles and logs
Work runs in ten-day cycles. Each closes with a runnable build and a written log: completed, carried over, risks discovered. Logs are kept in a shared space you control.
Quality evidence
When we say something is accessible, fast or secure, we attach the evidence: which tests were run, on what, with which results and known exceptions. Absence of a test is reported as absence, never as a pass.
Data discipline
We collect the minimum data a feature needs, keep analytics off by default, and align privacy notices with actual behaviour before launch.
Exit by design
Any engagement can end cleanly. Handover includes source, infrastructure notes, credentials inventory and a recorded walkthrough.
Release readiness check
Mark each gate as passed. The readout updates live. Results stay in this browser and are only remembered between visits if you accepted optional storage.