Frequently Asked Questions

Do you replace existing vendors or internal teams?

Usually no. Opertus often works alongside internal engineering, security, operations, legal, and vendor teams to clarify architecture, governance, and operational ownership.

Are you compliance authorities?

No. We design and align systems for compliance readiness and coordinate with legal, security, and audit partners where formal assurance is required.

Who owns the technology and deliverables?

Clients retain ownership of their systems, data, documentation, and project deliverables unless a contract says otherwise.

What kinds of organizations are a fit?

Teams with a real system to change: AI in a sensitive workflow, infrastructure that is hard to reason about, internal tools that need ownership, or a modernization effort where mistakes would be expensive.

What is not a fit?

Pure model shopping, generic IT support, speculative strategy decks, and projects where no internal owner can make decisions are usually not a fit.

What happens on the first call?

The first call is a fit and risk conversation. Opertus tries to understand the system, decision, timeline, stakeholders, and what would make the work unsafe or expensive if handled poorly.

Do you only advise, or can you help implement?

Both are possible. Some engagements end with a review and recommended sequence. Others include implementation support, release planning, documentation, validation checks, or handoff work.

How are engagements priced?

Pricing follows the shape of the work: assessment, advisory, implementation support, or retained guidance. Scope depends on the systems involved and the level of responsibility expected.

How quickly can we start?

For most engagements, discovery can begin within one to two weeks after scoping.