Technical consultation

Request a technical consultation.

A short, non-confidential brief helps us assess engineering fit. Do not include trading credentials, client identities, positions or proprietary strategy parameters.

1. Scope  /  2. Context  /  3. Contact and review

Looking for MCP access? Go to developer signup.

  1. 1. Scope
  2. 2. Context
  3. 3. Contact and review

1. Scope

What do you need built or reviewed?

Describe the constraint, interfaces and acceptance criteria. Keep it non-confidential.
2. Context

Where you work and how the engagement would start.

No implied delivery promise.
Existing environment Cloud, language, broker or data interfaces, if known.
Routing context only — an indicative engineering budget, never investable capital, and not an automatic exclusion.
Country or time zone, if useful for scheduling.
Never fetched server-side.
3. Contact and review

Where we reply, and a final check before sending.

Use the address where you want us to reply.

We use these details to assess and respond to your enquiry. See our Privacy Notice for processing, retention and your rights.

What happens next

Scope Context Contact and review

Institutional requests receive human review. A principal confirms engineering fit and next steps before any confidential material is exchanged. Confidential evidence is shared only after qualification and verification that both parties have signed the mutual NDA.

NDA

We can agree a mutual NDA before discussing confidential detail. Initial requests should contain only non-confidential information. A form submission is not a bilateral NDA, and no NDA is auto-approved.

General enquiries

For anything that is not an engineering build request — including general questions — use the general contact form. Requests to invest or have capital managed are outside this practice's offered services.

Developer signup

MCP access tokens, credit packs and the tool catalogue live on the MCP tools page — a separate flow from this consultation.