Working standards and boundaries
What we hold ourselves to on every engagement, and the things we will tell you we cannot do.
Talk to usScope is written before work starts. Every engagement opens with a document that states the deliverables, the dates and the fee. If something falls outside that scope, it is quoted separately rather than absorbed quietly into the timeline.
Evidence is separated from opinion. Where we are expressing a judgement rather than reporting a finding, the document says which is which, so a reader can disagree with the judgement without having to re-derive the facts.
Assumptions are written down next to the figures they affect. A plan that depends on a migration finishing in a particular quarter says so, in the same place as the conclusion that depends on it rather than in a footnote.
Findings are handed over in a form your team can use: documents, diagrams, and where relevant the prototype and its evaluation criteria. Nothing is withheld to create dependency, and no engagement is extended automatically.
What we do not do: we do not certify compliance, we do not act as a regulated adviser, we do not resell licences or hardware, and we do not promise a specific financial return from any technology decision.