04 · Run · Agent Teams First pilots

Managed AI agent teams, run and verified by human experts

AI agents do the work. A named human lead owns the result. You buy an agreed outcome instead of headcount.

Spec sheet
Engagement
Monthly
Model
Agents execute · humans stay accountable
Teams
Product BA Team · Product Development Team
Oversight
In the loop · on the loop · at the helm, chosen per process
Pricing
Base retainer plus a fee tied to the agreed result
Status
First pilots: two client teams onboarding by year end
Position in the loop
  1. 01
  2. 02
  3. 03
  4. 04
What it is
  • A team of agents with a named human lead accountable for outcomes
  • Contracted around service-level objectives and a metric leadership agreed
  • Weekly human review of real work; monthly report to leadership
What it isn't
  • A chatbot subscription
  • Offshore staff augmentation with an AI logo
  • Agents with nobody accountable when they're wrong
  • A black box you can't audit
Teams

Two teams launching now. A third on request.

Every team ships with a named human lead, an AgentOps layer and a metric agreed before day one.

Team 01

Product BA Team

From 1 month

Product and operations leaders drowning in stakeholder requests

Agents do

Interview synthesis · requirements drafting · story and acceptance-criteria generation · backlog grooming

Humans own

Stakeholder validation · prioritization and risk calls · sign-off

Build-ready specs: synthesized interviews, requirements, user stories, acceptance criteria and a groomed backlog.

Team 02

Product Development Team

From 1 month

Teams with a shipped product and a long roadmap

Agents do

Code generation · test writing · documentation · first-pass review · release notes

Humans own

Architecture · security · merge authority · production accountability

Working software released weekly, with tests, documentation and a full audit trail.

Team 03

Custom Agent Team

Scoped

Operations with a repeatable, measurable process

Agents do

Process execution inside explicit guardrails

Humans own

Exception handling · escalation decisions · quality verification

A team designed around one metric: vendor resolution, order exceptions, customer response time.

The operating loop

Run → Review → Tune → Prove

Agents execute. Humans review the real work weekly, tune what they find, and report the metric to leadership monthly.

  1. 01

    Run

    Agents execute inside explicit guardrails, goals and escalation triggers set by your human lead.

  2. 02

    Review

    Weekly human review of real conversations, specs and pull requests: the actual work, not samples.

  3. 03

    Tune

    Knowledge, guardrails and escalation rules updated from what the review found.

  4. 04

    Prove

    Monthly report on the agreed metric to leadership. The variable fee tracks it.

Review weekly · Report monthly

The human layer

How much a human touches each decision

Every process the team runs gets an explicit oversight level. The riskier the call, the closer the human. The level is written into the contract and visible in the audit trail. It isn't a setting an agent can change.

  • A named human lead signs off the level per process
  • Escalation triggers route risky decisions to a person automatically
  • Levels tighten or loosen only after a review, never silently
Oversight level Chosen per process
Agent autonomy Human control

Human in the loop

The agent runs the process. A person owns every call that carries risk.

Use when
Customer commitments, money movement, regulated decisions.
Human role
Approves each consequential action before it lands.
AgentOps

The performance and risk function behind every agent team

Observability, evaluation and drift detection are what make “human on the loop” honest. Without them, management by exception is management by hope.

01

Observability

Every agent action logged with inputs, outputs, cost and latency.

02

Evaluation sets

Golden test cases run on every change to knowledge or guardrails.

03

Drift detection

Quality and behavior tracked over time, with alerts when the agent starts to wander.

04

Escalation rules

Explicit triggers that route a decision to the human lead.

05

Audit trail

A reviewable record of decisions for leadership and compliance.

06

Cost governance

Token and tool spend tracked against the outcome it produced.

Commercial model

Priced on the result, not the hours

01

Base retainer

Covers the agent team, the accountable human lead and the AgentOps that keeps it honest.

02

Result-linked fee

Tracks the metric agreed up front, reported monthly with the evidence attached.

Contracts are structured around business outcomes, service-level objectives and performance metrics: shared accountability, not billed hours.

Outcome

You get this

Every team is contracted backwards from these. If one isn't on the list, it isn't in the price, and we'll say so.

  • 01 Results reported against the agreed metric
  • 02 A named human lead accountable for them
  • 03 A full audit trail of agent decisions
  • 04 A monthly leadership report

“Two client teams are onboarding our first agent teams before the end of the year.”

— Agent Teams, first pilots
Accountability Named human lead
Fee Linked to the agreed result
Ask about a pilot
Agent teams: questions

What people ask about agent teams

Short answers to the questions that come up in the first conversation about this offering.

01 Who is accountable when an agent gets it wrong?

A named human lead on our side, written into the contract. That's the difference between a managed agent team and an AI tool subscription.

02 How is the fee tied to results?

A base retainer covers the team and AgentOps. A variable component tracks a metric we agree in advance and report monthly: cycle time, resolution rate, release cadence.

03 In the loop, on the loop, at the helm: what's the difference?

How much a human touches each decision. In the loop: a person owns every risky call. On the loop: humans supervise and manage by exception. At the helm: humans set goals, limits and triggers, then watch the audit trail. You choose per process.

Get started

Ask about a pilot

Thirty minutes to pick the process, the metric and the oversight level, and to tell you whether an agent team is the right move yet.