SUPERWISE services · Step 7 of 7

Managed AI operations

Keep live AI monitored, maintained, and improving, with a report every month.
$3,500 to $15,000 per month12-month term

What you walk away with

  • Service agreement and responsibility map
  • Operating baseline
  • Runbook and escalation path
  • Incident and change record

Where this fits

Step 7 on the services path

Each step answers the question the last one raised. Start wherever the assessment points you.

  1. Managed AI operations

Why it matters

What changes for your team

After launch, your live AI keeps a named operating team, an agreed service level and a monthly record of what happened and what to improve next.

Someone owns the system after launch

Monitoring, maintenance, issue handling and routine tuning run on one cadence, so the agent, Sentinel fleet or Chat workspace does not become an unowned side project.

Problems follow an agreed path

The service agreement sets coverage and response terms; the runbook says who investigates, who approves a change and when an issue comes back to your team.

Leadership can see what changed

Monthly reports and quarterly reviews keep a lasting record of performance, incidents, configuration changes, risks and the next improvement decisions.

How it works

Three stages, with your team in the room

12-month term

Month 1

Hand over the system and get agreed service levels and a baseline to measure against.

Every month

Your AI is monitored, maintained and tuned, and you get a report on what happened.

Every quarter

Choose the next improvements from a review of performance, risk and changes.

The details

Everything you need to decide

Price, fit, your team’s time, how data is handled, and what you keep.

Price and scope

Draft pricing for review: we confirm a fixed scope and price after a scoping call.

TierPrice rangeDurationIncluded
Service$3,500 to $15,000 per month12-month termOne agent or Sentinel fleet

Not included

  • A new application, agent or workflow build, or a major new integration.
  • Software, model, data, device-management or other third-party subscriptions.
  • 24/7 coverage or a one-hour response, unless priced and written into the service agreement.
  • Additional agents, systems, sites or business units beyond the covered agent, Sentinel fleet or Chat workspace.
  • Major data remediation, product development or compliance certification.
Is this the right starting point?

Good fit if

  • For teams that want a dependable partner to monitor, maintain, report on, and improve live AI.
  • Teams with a live agent, Sentinel fleet, or Chat workspace
  • You want a defined handover your team keeps.
What you keep

Service agreement and responsibility map

The written coverage, business-hours service level, response and escalation terms, client contacts, approval limits and exclusions for the covered agent, Sentinel fleet or Chat workspace. Use it to know who acts when something changes or fails, and what is maintenance versus a separately scoped build.

Operating baseline

A month-one record of the system, configuration, dependencies, expected signals, known issues and the measures the monthly report tracks. Use it to tell a real change from the condition accepted at handover, and to onboard a future operator.

Runbook and escalation path

The checks, routine maintenance steps, issue types, contacts, approval points and handoff steps for running the covered system. Use it in an incident, a staff change or a provider handoff, so the response does not rely on one person’s memory.

Incident and change record

A running log of issues, investigation, resolution, configuration and tuning changes, approvals and open follow-up. Use it to answer what happened, what changed and why, and to spot repeat problems that need a bigger fix.

Monthly operating report

A monthly summary of the agreed performance and availability signals, incidents, service-level handling, maintenance, changes, risks and decisions needed from your team. Use it for operating reviews, internal reporting and evidence that the live system is watched, not just left on.

Quarterly service review and improvement plan

A quarterly look at performance, risk, recurring issues and product or dependency changes, with ranked maintenance and improvement actions. Use it to approve next quarter’s changes, budget separate build work and check that the service still fits.

Configuration history and handover package

The current runbook, operating records, reports and history of configuration and approved changes, kept through the term. Use it to renew with full context, bring operations in-house or hand the service to another provider.
What your team gives

About 4 to 8 hours across your team in month 1, then about 2 to 4 hours a month plus the quarterly review and any material incident. These are planning figures; the covered systems and response model determine the actual need.

Service owner

Owns the business priority, takes escalations, approves material changes and joins the monthly and quarterly reviews.about 1 hour, with more time during a material incident

System or workspace administrator

Coordinates access, users, dependencies and client-side changes, and helps during onboarding and issue investigation.about 2 to 3 hours in month 1, then about 1 hour

Domain owner

Judges whether outputs and workflow behavior still fit the work, and helps assess exceptions or tuning requests.about 1 hour when review or tuning is needed

Security or governance owner

Reviews material incidents, control changes and the quarterly risk record where the covered system needs it.about 1 to 2 hours each quarter, plus incident time when needed
Data, security, and ownership
  • Access is limited to the covered system and operating tasks named in the service agreement. Your organization retains control of its accounts and credentials, and approval boundaries are recorded in the runbook.
  • The operating record captures incidents, maintenance, approved configuration changes and the agreed performance signals; it does not replace the product’s own audit record.
  • For Sentinel, supported requests are checked on the PC and go straight to the AI provider; SUPERWISE receives only check metadata. The service’s coverage matches the documented Sentinel facts.
  • For SUPERWISE Chat, the covered workspaces and their administration are agreed in scope. Chat uploads are stored in SUPERWISE’s Google Cloud environment and are handled separately from Sentinel’s on-device processing.
  • We never widen production access or make a material change outside the approvals in the service agreement.

SUPERWISE signs a Business Associate Agreement with healthcare customers, and the scope is confirmed during scoping. See the trust center.

You keep the operating records, monthly reports, configuration history, runbooks, decisions and handover material. Product subscriptions and any underlying source or configuration follow the product and build agreements already in place. If you stop working with us, the current package and open-issue list come back to you, so your team or another provider can take over.

Managed AI operations runs on a 12-month term. Each quarterly review decides what stays routine operation and what needs a separately scoped integration, new build or governance change, and coverage, service level and the improvement plan are reviewed before renewal. If the service ends, the handover package closes the operating record, and support does not continue beyond the agreed term unless renewed.

Examples and how we measure success

These are examples of suitable work, not claims about past client engagements.

A live agent needs a steady owner

The agent depends on data, integrations and business rules that change. The service watches the agreed signals, handles routine maintenance, records incidents and brings material changes to your owner.

A Sentinel fleet needs policy upkeep

A team with Sentinel on its covered PCs needs one place for fleet status, policy changes, issues and the documented coverage limits. The service maintains the agreed fleet and includes it in the operating report.

Chat workspaces need administration

Departments use approved Chat workspaces that need routine configuration, user and issue handling. The agreed workspaces join the service cadence under a named owner.

An update changes behavior

A model, dependency, data source or business rule changes, and the workflow behaves differently. The team investigates against the baseline, records the decision and applies an approved fix or tuning change.

A quarterly review exposes the next risk

Repeated exceptions, new data conditions or a control that no longer fits show up in the operating record. The review turns that pattern into an owned improvement instead of more support tickets.

Measures we agree at kickoff

  • Service-level performance: covered issues are acknowledged and handled within the response terms in the service agreement.
  • Operating visibility: every monthly report has the agreed performance signals, incidents, maintenance, changes, risks and open decisions.
  • Change control: every material configuration or tuning change has a recorded reason, approval and outcome.
  • Issue learning: recurring incidents and exceptions become owned actions at the quarterly review.
  • Handover readiness: the runbook, configuration history and open issues are enough for you or another provider to take over.
Who delivers the work

The SUPERWISE services team runs managed AI operations for Renova Health and Boca Raton Regional Hospital today. Renova Health has a published case study showing governed AI in chronic-care work. There is no published Boca Raton Regional Hospital case study on this site, so no link or result is shown for it.

Managed AI operations questions

What to expect before you start

Talk to us

Talk to our team

Tell us about your team and we will scope managed ai operations with you.

Tools in scope (required)