Written boundaries
We agree what’s included, what isn’t, and what “done” looks like before work starts.
How the work happens
Tell us what you need to achieve. We’ll compare sensible options, explain the work and agree a clear scope before you commit.
Build philosophy
Choose a proven existing product when it meets the need.
Make established tools work together before replacing them.
Remove stable repetitive work with controls and a fallback.
Build custom software only when the remaining gap justifies its ownership and operating cost.
Project sequence
Define the outcome, users, constraints, current state and who can approve decisions.
Compare sensible routes and make limits, dependencies and ownership visible.
Agree inclusions, exclusions, acceptance, access and change control before delivery.
Work in reviewable stages with the smallest practical privilege and data exposure.
Test the agreed result, failure handling and handover evidence.
Transfer knowledge, document assets and remove or retain access only as agreed.
We agree what’s included, what isn’t, and what “done” looks like before work starts.
Access and important decisions require a customer who is authorised to approve them.
The result includes the ownership, documentation and exit evidence appropriate to its level.
Understand what stays customer-owned, how delegation works and what an exit pack should contain.
Read the ownership model →See the concrete principles used to limit access, data and unsupported assurance.
Read the security approach →Next step
Tell us what you are trying to change and what is getting in the way. We will help identify the next useful step.
We agree scope, revisions, customer inputs, the total price and acceptance before work. AI assistance and protected-data restrictions belong visibly in the project agreement. Engineering checks, delivery permission and customer contractual acceptance remain separate.