Contact
Tell us what you are building.
Send the brief, or the beginnings of one. We will tell you what it takes.
Enquiries are read by an engineer, not a form inbox. If your question is technical, ask it technically — you will get a technical answer.
Enquiry
Before you write
Useful things to include.
What is actually fixed?
The regulation, the launch date, the hardware already ordered, the system that cannot be switched off. Constraints tell us more in one paragraph than a feature list does in ten pages.
Where are you now?
An idea, a specification, a prototype, a running system with problems, or a build by another vendor that you want assessed. Each starts differently.
Which markets?
Domestic, international, or both. This decides certification, support, and often the architecture, so it is worth saying early.
Who will own it afterwards?
Your team, ours, or nobody yet. It changes how we document and hand over, and we would rather design for the real answer.