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.

Start an engagement Prefer email? Open a draft

Product support

Ask about a Doric product.

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

Email Doric Stack

Security and privacy

Report sensitive issues.

Privacy, security, account, or sensitive routing questions.

Send a security or privacy note

Useful first note

Send enough context to make the reply useful.

1. Send the decision, deadline, and audience.
2. List the diagrams, vendor notes, docs, or product context available for follow-up.
3. Name the constraints, budget posture, and paths already rejected.
4. Email fallback remains available if the browser flow fails.

What happens next

You get a clear route, not a vague reply.

01 Route
The request is routed as consulting, product support, security, privacy, or no-fit.
02 Scope
If consulting fits, the reply narrows the decision, written artifact, and payment or booking path.
03 Protect
Sensitive material moves only after the right channel and handling rules are agreed.

Fallback

Email stays available.

If a browser, form, or scheduler fails, send the same details by email. The conversation can continue from there without losing the context.

Open email draft

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.