Every engagement is bound by seven rules. A delivery that breaks one is defective regardless of its results.
- Read before write. No change is made to a surface we have not first inspected and described.
- Scope in writing, before work. You approve what will change, where, and what explicitly will not. Work outside it is a new order, never a quiet addition.
- Smallest correct change. We change the mechanism, not the symptom — no bulk rewrites, no theme forks we then have to maintain.
- Platform-native surfaces only. Changes go through the platform's own hooks, templates and settings, never a hack the next update silently removes.
- Prove it after. Every change is fetched live and compared with the before state. Deployed is not done; verified is done.
- State the rollback. If we cannot describe how to undo it, we do not make the change.
- Report what we did not change. Out-of-scope findings and untouched systems are listed. Silence about a known defect is dishonest.
Every delivery contains five artefacts
- Scope record — the written scope you approved, dated.
- Findings — what we observed and the mechanism behind each, ranked by impact.
- Change record — surface, before value, after value, and why that change.
- Verification — the live fetch with URL and timestamp, plus the before state.
- Open items — what we found but did not touch, and why.
If any of the five is missing, the delivery is incomplete. Tell us and we finish it at no cost.
What we do not claim
We hold no SOC 2 or ISO 27001 certification and do not imply one. We do not guarantee rankings, traffic or revenue. This standard covers work we perform, not third-party apps you install.