Skip to content

Contact

Tell us the decision - the scope can come later.

Three or four sentences on what changed, the choice in front of leadership, and what's making it hard are enough for a useful first message.

Writing a good first message

Give us enough to understand the situation - nothing sensitive.

Do not send passwords, recovery codes, private keys, tenant exports, personal data, or confidential system detail.

  1. What changed?

    A renewal, budget pressure, a project collision, a recurring risk, an ownership gap, or a new business requirement.

  2. What's the decision?

    Name it in plain business language, even if you don't have the full list of options yet.

  3. Who needs to be involved?

    The accountable leader, plus whoever on the operations or technical side is closest to the evidence.

  4. What's making it hard?

    Timing, capacity, contract terms, missing evidence, competing priorities, or unclear authority.

What happens next

A conversation about fit, not a fixed process.

There's no ticket queue and no automatic booking. Sending a message just starts a conversation about whether we're a fit.

What it isn't

No booking, no SLA, no emergency desk.

Sending a message doesn't create a signed engagement, a response-time guarantee, or an emergency-response commitment. Say so directly in your message if timing is critical.

What it starts

A conversation about fit and scope.

We'll reply on whether the decision matches what we do, and name a concrete next step if it does.

Choose how to reach us

Use the form below, or pick another way in.

Contact form

Fill in the form below

Name, organization, and the decision context in one set of labelled fields.

Jump to the form

Prepare first

Build a first-meeting agenda

The decision brief tool runs in your browser. Copy the result into your own notes, or carry it straight into the form.

Open the decision brief tool

For background beyond this page, see Mirage Informatique (Quebec).

The decision note

Name, organization, and the decision context below-the same information either path needs.

Required fields are marked with an asterisk (*).

Do not send passwords, recovery codes, private keys, tenant exports, personal data, or confidential system detail.

Read the privacy policy to understand how this request will be handled.