Start a practical scoping conversation for AI, infrastructure, or internal systems work.

# Contact

Use this channel when AI, infrastructure, or internal systems work needs careful scoping before it moves. A polished brief is not required.

The first conversation is about fit: what is changing, who owns it, what could go wrong, and whether Opertus is the right partner.

Not every engagement is appropriate for Opertus involvement.

<div className="cols-2">
  <section className="info-panel">
    <h2>Contact Channel</h2>
    <ul className="stack-list">
      <li>Email: hello@opertus.systems</li>
    </ul>
  </section>

  <section className="info-panel">
    <h2>Operating Geography</h2>
    <p>Opertus works primarily with clients in San Francisco, New York City, Northern Utah, and Toronto, with remote advisory available for aligned organizations elsewhere.</p>
  </section>
</div>

<div className="cols-2">
  <section className="info-panel">
    <h2>Helpful Context</h2>
    <ul className="stack-list">
      <li>which systems, vendors, or teams are involved</li>
      <li>what AI, automation, or workflow change is being considered</li>
      <li>what could fail, leak, drift, or become hard to review</li>
      <li>who needs to be involved and when</li>
    </ul>
  </section>
</div>

---

## Engagement Expectations

Expect a practical scoping conversation, not a sales sequence. If the work is not a fit, Opertus will say so directly.

<div className="briefing-list">
  <section className="briefing-item">
    <h3>What happens first</h3>
    <p>Opertus reads for fit, asks for any missing context, and recommends either a bounded review, a narrower next step, or no engagement.</p>
  </section>

  <section className="briefing-item">
    <h3>What to send</h3>
    <p>A short note is enough: the system or decision in question, why timing matters, who owns the work today, and what would make a bad outcome expensive.</p>
  </section>
</div>
