Best-fit conditions
An initial assessment or implementation has exposed recurring architecture and reliability decisions that cannot be handled as occasional ad hoc advice.
Not a fit when
- No prior engagement or current system context exists and the buyer expects immediate recurring judgment.
- The requested role includes daily staff management, help-desk support, on-call operations, or hands-on implementation by default.
- No executive or technical decision owner is available to act on architecture and risk decisions.
- The buyer is purchasing unused hours rather than a maintained architecture and evidence function.
What the buyer receives
- Living architecture and AI-system inventory
- Technical decision records and unresolved-risk register
- Monthly architecture, vendor, and release review
- Evaluation and human-oversight standards maintenance
- Quarterly priority and sequencing refresh
- Executive risk and progress briefing
Delivery sequence
- Onboard from an existing assessment, blueprint, implementation, or equivalent client evidence.
- Establish the recurring decision calendar, owners, artifacts, and response boundaries.
- Review architecture, vendors, releases, risks, and evidence on the agreed cadence.
- Record decisions, exceptions, actions, and unresolved questions.
- Refresh quarterly priorities and recommend separate implementation scopes when needed.
Decision value
- Continuity of senior architecture judgment
- Less decision drift across vendors and internal teams
- Maintained evidence and release standards
- Visible risk ownership and unresolved questions
- A current quarterly sequence rather than a stale roadmap
- A clear boundary between oversight and implementation
Client responsibilities and scope assumptions
Client responsibilities
- Assign executive and technical counterparts
- Provide timely access to architecture, vendor, release, and risk information
- Retain operational authority and implementation ownership
- Route implementation work through internal teams or separate statements of work
- Respect response, meeting, and scope boundaries
Scope assumptions
- One named decision owner and one named technical owner
- A bounded system or workstream with timely access to representative evidence
- Public-safe qualification before confidential material is exchanged
- Client reviewers available for domain questions, disputes, and acceptance
Explicit exclusions
- Hands-on production coding or cloud administration
- Daily standups, people management, or help-desk support
- Always-on availability or incident command
- Authorized risk acceptance, legal advice, or compliance sign-off
- Unlimited vendor negotiation, diligence, or project management
Acceptance and commercial boundary
Acceptance: Monthly service is accepted through delivery of the agreed cadence, artifacts, and reserved access. Retainer capacity does not roll over unless the statement of work expressly says otherwise.
Commercial boundary: Available after sufficient system context exists. New implementations, major diligence events, incident response, or sustained work beyond the agreed cadence require a separate statement of work.
This commercial retainer is not a government labor-rate card. Public-sector or subcontract work is scoped to the opportunity and applicable terms.