Let’s talk about your next step.

You do not need a finished specification to begin a conversation. Describe the business process, the difficulty you are seeing and the decision you are trying to make. An early enquiry might concern whether AI is appropriate, how two systems could connect or what would be involved in replacing an ageing application.

Include the context that changes the answer, such as the number of users, an important deadline or a provider that must remain in place. Keep the first message focused on the problem. Detailed technical evidence can be gathered once the right people and the next useful step have been identified.

Use an enquiry for an early discussion, a general question or an introduction. Use the project brief when you already have goals and constraints that need a structured review. For an existing system with a problem, the support form helps capture impact and investigation details.

These routes serve different stages of work. Selecting one does not purchase a service or create a delivery commitment. If an existing agreement already defines how to contact the team, use that route. For an urgent incident, follow the agreed escalation process rather than relying on a general enquiry to reach the appropriate responder.

State who should be involved and include availability with a time zone. If several teams own parts of the workflow, identify the person who can coordinate their input. A short description of the decision required helps keep a first meeting focused and makes it easier to prepare relevant questions.

Review the details before choosing Send. Sending emails the request to Cobnex but does not book a meeting. You can download a PDF copy separately. Remove confidential material that is unnecessary for the discussion. A subsequent conversation can establish what further information is needed and how that information should be handled.