Contacts
All correspondence is handled by email. Messages are read by engineers, and technical questions receive technical answers rather than a generic reply.
The categories below describe the kinds of correspondence we receive and the details that let us respond usefully the first time.
01
Questions about the company, our areas of work, how we structure engagements or how we handle information. A short description of your context is enough.
02
Requests relating to software development, cybersecurity, cloud, network, data or managed services. Technical detail shortens the path to a meaningful answer.
03
Working alongside an internal team or another supplier: shared delivery, specialist support within an existing programme, or review of work carried out elsewhere.
04
Proposals from agencies, consultancies, product vendors and infrastructure providers looking for a technical delivery or security partner.
Expected communication process
Step 1
Your message is confirmed by email and assigned to an engineer familiar with the subject.
Step 2
We ask focused follow-up questions where the technical context is incomplete.
Step 3
We evaluate feasibility, scope and the disciplines involved, and say plainly if we are not the right fit.
Step 4
You receive a structured reply describing our understanding, a suggested approach and next steps.
Correspondence is kept in writing so that scope, assumptions and commitments remain traceable for both sides. Sensitive technical details should not be shared until a confidentiality arrangement is in place; we will say when that point is reached.