A clear way of working, agreed before work begins.
Every engagement follows the same disciplined sequence: understand the situation, agree the scope in writing, deliver in visible stages and hand over properly.
01 / Engagement formats
Three ways to work together.
The format follows the need. An engagement can also move from one format to another as the situation changes.
Defined project
A fixed scope with a clear outcome — a new application, a migration, a security review. It starts with a written proposal and ends with a full handover.
Ongoing support
Continuous care for your IT, infrastructure or software, with routine work scheduled in advance and a clear route for requests.
Advisory & review
An independent look at your current systems, risks or plans, delivered as a written assessment with prioritised recommendations.
02 / Process
Five stages, each with a clear output.
You always know which stage the work is in and what you will have in hand when it ends.
-
Discovery
A conversation about what you need and how things work today. We ask questions before suggesting answers.
Output: shared understanding -
Assessment
Where relevant, we review existing systems, access and documentation to see what is really in place.
Output: summary of findings -
Proposal
A written scope covering the work, its sequence, responsibilities on both sides and everything that is excluded.
Output: written proposal -
Delivery
Work proceeds in stages you can review. Any change to scope is discussed and agreed before it happens.
Output: working result, stage by stage -
Handover & care
Documentation, credentials and knowledge are handed over in full. Ongoing support continues if agreed.
Output: documentation and handover
03 / Communication
You always know where things stand.
Good IT work is invisible when it goes well. Communication is how you stay in control of it.
Regular updates
Progress updates at an agreed rhythm, in writing, describing what was done and what comes next.
One channel
Requests and decisions are kept in one agreed place, so nothing depends on a forgotten phone call.
Early warnings
If something is going to take longer or cost more, you hear about it before it happens, not after.
Plain language
Updates are written for the people making decisions, with technical detail available whenever it is needed.
04 / Security
Security is part of how we work, not a separate line item.
The same rules apply whether we are building an application, administering a server or supporting a laptop.
Least access
We request only the access a task needs and remove it when the work is done.
Secure credentials
Passwords and keys are shared through secure tools, never by plain email or chat.
Changes recorded
Significant changes are recorded, so there is always a clear history of what changed and when.
Your data stays yours
Data, accounts and documentation belong to you and can be handed back in full at any time.
05 / From you
What helps us start well.
None of this needs to be perfect. Incomplete information is normal — it is part of what the first stage sorts out.
- A contact person who can make decisions
- A short description of the problem or goal
- Access to existing systems, when the work requires it
- Any documentation that exists, however incomplete
- Known deadlines or constraints
- Candid feedback while the work is in progress
Next step
Start with a conversation.
Discovery is the first stage, and it begins with a message. Tell us what you are working with.