Managed AI employees · Pilot

A managed AI employee for your next workflow.

We set up the role, the tools, and the checks. You send a brief and review the work.

Every request is reviewed by the team before any offer is made.

Illustrative demo · sample data

  1. Brief

    Monthly report for October. Data file attached. Flag anything the data does not cover.

  2. Checks running

    Figures traced · gaps flagged

  3. Result

    Report + sources

Scope

What work can be delegated

Reports

Performance reporting with sources attached.

Documents

Briefs, drafts, and summaries for your review.

Operations

Scheduling, follow-ups, and recurring admin.

Roles

Two pilot roles

Both are under evaluation, offered as scoped pilots rather than verified experts.

Marketing / SEO Reporting

Pilot

Turns search and analytics data into a sourced monthly report.

Good fit for
Teams that publish content and need consistent, sourced reporting.
Minimum input
Read-only search console access, or an exported data file.
Sample result
Metrics table, change explanation, sources, prioritised recommendations.
Explore role

Executive / Admin Operations

Pilot

Handles scheduling, writing, follow-ups, and document work.

Good fit for
Small teams with recurring admin work and one person who can approve.
Minimum input
A written brief per task, plus business context.
Sample result
Letter prepared for signature, scheduling, follow-up list.
Explore role

Setup

How a managed employee is set up

No activation promise. Setup depends on scope, data access, and review.

  1. 01

    Choose the workflow

    You pick one jobdesk. We confirm it fits a scoped pilot.

  2. 02

    Share business context

    You provide the facts, tone, and constraints.

  3. 03

    Confirm tools and permissions

    You approve what it may read, and what it may never do alone.

  4. 04

    Review the first result

    Nothing external happens without your approval.

Evidence

Work you can inspect

Every sample shows its inputs, its checks, and its sources.

Brief

Monthly report, October. Source file supplied. Period and scope stated.

Sources

Supplied dataset only. No external lookup, no invented figures.

Output

Metrics table, explanation of change, open questions, prioritised recommendations.

Checks

Figures traced to source rows. Missing periods flagged rather than smoothed.

Sample · synthetic data · October 2026

Open the full output

Control

You keep control

Four controls, explained before you use them.

Pause at a checkpoint

Stop between steps when the brief changes.

Revise the brief

Correct scope without starting over.

Approve external actions

Sending and publishing wait for you.

Inspect results

Open the artifact, its checks, and its sources.

Approval demo. No external action is taken.

Evaluation

How we evaluate a role

A role is offered only after it clears a written evaluation. We publish the method, not a percentage.

  • A held-out set of tasks the role was never tuned on.
  • A written rubric per task: what a passing result must contain.
  • Deterministic checks for grounding and boundary behaviour.
  • Explicit tests for refusing to invent data and stopping at scope limits.
  • Practitioner-reviewed before the role is called ready.

Practitioner review is still pending for both roles. Until then, they are scoped pilots.

Pricing

Pricing and scope

No public price list during the pilot.

Pilot scope

One workflow, agreed capacity and service hours, confirmed in writing.

Quoted per scope

Managed employee

Ongoing role with connectors, checks, and escalation. Available after the pilot gates clear.

Not yet published

Sold as a managed employee, not a per-seat tool. Capacity, hours, and priority differ by package; the expertise standard does not.

Discuss your scope

Trust

Trust and data handling

We describe the controls that exist today. Anything not yet in place is stated as a pilot principle.

  • Human approval for external actions. The employee prepares work; a person authorises anything leaving the company.
  • Scoped data access. Granted per task, revocable. Read-only unless you approve otherwise.
  • Reviewable output. Deliverables carry their inputs, checks, and sources.
  • No professional substitution. Never presented as a licensed legal, tax, or medical professional.
  • Your controls, without an account. Revoke a connector, request your data, or report a security incident. No login required.

Certifications, uptime guarantees, and published response times are not claimed during the pilot.

Questions

What is a managed AI employee?

A defined jobdesk VIRTU sets up and operates for you: context, tools, checks, escalation. You send briefs and review results. Not a chatbot you configure yourself.

Which roles are available now?

Two pilot roles. Additional roles are offered only after they pass evaluation.

What does it cost?

Pricing is confirmed per scope during the pilot. No published number that later grows through hidden fees.

What are the working hours?

Agreed per package. Work outside those hours is quoted separately.

Can I use WhatsApp or Telegram?

Channel delivery is planned and gated. During the pilot, tasks move through the channel in your scope document.

How is quality checked?

Each role carries a written rubric and a held-out evaluation set. We share the method, not a marketing percentage.

What data do you need?

The minimum for the scoped task. Access is approved per connector and can be revoked.

What if a result is wrong?

You request rework. A failed check is recorded and does not count as a passed result.

Start with one workflow.

Tell us the jobdesk and we will confirm whether it fits a scoped pilot.

Request a pilot