# Contact Amidship | Discuss a software problem

> Canonical URL: https://amidship.com/contact/
> Language: en-CA

- [Home](https://amidship.com/)
- Contact

Contact

# Bring us the problem.

A useful first note does not need a polished brief. Tell us what is happening, why it matters, what makes it difficult, and what decision or delivery point is coming next.

[Email admin@amidship.com](mailto:admin@amidship.com?subject=A%20software%20problem%20to%20discuss)
Business, partnering, and procurement inquiries go directly to Amidship.

## What to include

Share the workflow or product involved, the people who depend on it, the systems or data it must connect to, and any timing, procurement, privacy, security, or accessibility constraints already known.

If the problem is still ambiguous, say so. Amidship is often most useful before a larger team is assembled, when product behaviour, architecture, delivery risk, and the role of AI still need to be decided together.

## Who responds

Amidship is principal-led. Rida Al Barazi reviews fit and remains directly involved in the product, architecture, and engineering decisions that shape accepted work. Scope-specific specialists may participate when their expertise is useful; they are not presented as a salaried delivery bench.

The first exchange is used to understand the problem and determine whether a focused conversation, a bounded starting engagement, or another path makes sense. Sending a note does not create a support commitment or client relationship.

## Procurement and diligence

Canadian public-sector and enterprise buyers can review Amidship’s Government, privacy, Responsible AI, security, accessibility, and capability-statement pages before making contact. Include the mandate, expected role, procurement context, and any controlled-diligence requirements in your note.

See how engagements start

- [See how engagements start](https://amidship.com/work-with-us/)

- [Privacy](https://amidship.com/privacy/)