Write to us

What to include

A useful first message

• The system or process the request concerns, and who depends on it
• The problem you want solved, described in operational rather than technical terms
• Any constraint that is fixed: platform, data location, compliance requirement, deadline
• Whether an existing codebase or vendor is involved
• The kind of response you need — an assessment, a proposal, or a conversation

How we respond

Written, and specific

Enquiries are read by engineers rather than routed through a sales queue. A first reply sets out how we understand the request, what we would need to know before committing to scope, and how an engagement could reasonably begin.

If a request falls outside what we can do well, we say so and explain why rather than stretching to fit it. Confidentiality terms can be agreed before any technical detail is exchanged.