Contact

Routes for decisions, products, and sensitive issues.

Choose advisory intake, product support, or security and privacy. Email stays available if the browser flow fails.

Consulting intake

Scope a decision.

Architecture, vendor, AI, SaaS, and product decisions that need a senior read.

Open intake email

Product support

Ask about a Doric product.

Product access, purchase questions, license help, or an active support thread.

Email Doric Stack

Useful first note

Send enough context to make the reply useful.

  1. 1. Send the decision, deadline, and audience.
  2. 2. Attach diagrams, vendor notes, docs, or product context that can be shared.
  3. 3. Name the constraints, budget posture, and paths already rejected.
  4. 4. Email fallback remains available if the browser flow fails.

What happens next

You get a clear route, not a vague reply.

  1. 01 Route

    The request is routed as consulting, product support, security, privacy, or no-fit.

  2. 02 Scope

    If consulting fits, the reply narrows the decision, written artifact, and payment or booking path.

  3. 03 Protect

    Sensitive material moves only after the right channel and handling rules are agreed.

Privacy-safe submissions

Do not send card numbers, passwords, private keys, production credentials, or regulated customer data. Share sanitized context first. If a deeper review needs sensitive material, the channel and handling rules will be agreed first.