Contact

Start with the problem.

Describe what is not working in plain language. You get a straight answer about whether we are the right firm for it, within one business day.

Enquiries

New engagements

Five fields. An engineer reads it.

There is no qualification call standing between your message and someone technical. The person who replies is the person who would scope the work.

The address we reply to. One business day.

Two or three sentences is plenty. The rough version is more useful than the polished one.

Optional. It routes the message a little faster; it does not narrow what we look at.

Scope

What to send

The three we hear most.

You do not need a specification, a budget or an internal consensus before you write. These are the shapes a first message usually takes.

  • A migration that has stalled

    Half the estate moved, the rest will not, and the business case is quietly expiring while both run in parallel. Tell us what landed, what did not, and what the remainder is actually blocked on — licensing, a database version, or one application nobody will sign off.

  • An audit finding you cannot close

    ISO 27001, SOC 2, a customer security review or an insurer's questionnaire. Send the finding as it was written. We will tell you what closing it properly costs, and where the cheap version will simply reappear at the next audit.

  • A platform nobody wants to touch

    It runs, nobody is certain why, and the person who built it left two years ago. Send whatever documentation exists, including none. Working out what a system does is the first hour of an assay, not an obstacle to starting one.

If none of those fit, describe it in your own words anyway. We would rather read a rough paragraph than a tidy requirements document — the rough one usually contains the real problem.

Response

Three steps

What happens after you send it.

A response expectation is only worth setting if it is kept. This is the one we keep.

  1. Read

    Your message lands in [email protected], which engineers read. It is not triaged by a queue and it is not sold to before it is understood.

  2. Reply

    Within one business day, including the answer “this is not for us” with the reason and, where we can, the name of a firm that does it properly.

  3. Assay

    If it fits, we propose the fixed-fee assay: two to four weeks, a fixed date, and a written finding with costs attached. It is yours whether or not you continue with us.