Managed AI employees · Pilot
We set up the role, the tools, and the checks. Send a brief, review the work, and keep control of what happens next.
Brief
Monthly report for October. Data file attached. Flag anything the data does not cover.
Checks
Figures traced · gaps flagged
Result
Report + sources
Monthly performance reporting that combines data, explains what changed, and cites its sources.
Briefs, drafts, letters, and summaries prepared for your review before anything leaves the company.
Scheduling, follow-ups, data entry, and recurring admin work that stalls when nobody has time.
Turns search and analytics data into a reviewed monthly report with sourced recommendations.
Handles scheduling, drafting, follow-ups, and document work with explicit approval before any external action.
You pick one jobdesk to start with. We confirm it is a fit for a scoped pilot.
You provide the company facts, tone, and constraints the employee must respect.
You approve which data the employee can read, and what it may never do on its own.
The employee delivers work for your review. Nothing external happens without your approval.
Every sample shows its inputs, its checks, and its sources. Nothing is presented as a live customer result.
Brief
Monthly report, October. Source file supplied with the brief. 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.
Pause at a checkpoint, revise the brief, approve an external action, inspect results. Each control is explained.
Stop the work between steps when the brief or the data changes.
Correct scope and inputs without starting over from a blank page.
Sending, publishing, or committing to a third party always waits for you.
Open the delivered artifact, its checks, and its source list.
A role is only offered after it clears a written evaluation. We publish the method, not a marketing percentage.
No public price list during the pilot.
One workflow, agreed capacity and service hours, confirmed in writing.
Quoted per scope
Ongoing role with connectors, checks, and escalation. Available after the pilot gates clear.
Not yet published
We describe the controls that exist today. Anything not yet in place is stated as a pilot principle instead of a promise.
The employee prepares work; a person authorises anything that leaves the company.
Access is granted per task and can be revoked. Connectors are read-only unless you approve otherwise.
Deliverables carry their inputs, checks, and sources so you can verify them.
We do not present the employee as a licensed legal, tax, or medical professional.
Revoke a connector, request a copy or deletion of your data, or report a security incident from this page. No login is required to start any of those requests.
A defined jobdesk that VIRTU sets up and operates for you: context, tools, checks, and an escalation path. You send briefs and review results. It is not a chatbot you configure yourself.
Two pilot roles: Marketing/SEO Reporting and Executive/Admin Operations. Additional roles are only offered after they pass evaluation.
Pricing is confirmed per scope during the pilot. We do not publish a number that later grows through hidden fees.
Service hours are agreed per package. Work outside those hours is quoted separately.
Channel delivery is planned and gated. During the pilot, tasks and results are exchanged through the agreed channel in your scope document.
Each role carries a written rubric and a held-out evaluation set. We share the evaluation method, not a marketing percentage.
The minimum needed for the scoped task. You approve access per connector and can revoke it.
You request rework. A failed check is recorded and does not count as a passed result.
Tell us the jobdesk and we will confirm whether it fits a scoped pilot.
Request a pilot