GUBERNATORgoo-ber-NAH-tor
Managed Agent Operations
Gubernator is Latin for the helmsman, the root of “govern.” Our operators steer your agents every working day, and your people set the course.
AI agents do the work of the role every day. Our operators run them, and your team approves what matters.
A monthly fee, agreed in writing for the tasks and volume in scope. Systems scoped through a Workforce Blueprint start here directly.
Prices, coverage hours, and response targets are set in each agreement, not published.
Is this for you?
- Businesses that want the work of a role done, without hiring, training, and managing for it
- Owners without an engineering team who want one accountable operator for their agents
- Work that runs every day and needs a person watching the exceptions
- Teams that want to add roles over time, one at a time
The problem
Agents need someone running them, every working day.
An agent that works in a pilot still meets new formats, odd requests, and rules that change. Someone has to watch the queue, fix what goes wrong, and know when to ask a person.
Most businesses under 500 employees do not have that team, and do not want to build one. They want the work of the role done, with a clear line to whoever is responsible.
They also want their own people to keep the decisions that matter. Payments, commitments, and judgment calls stay with the business.
How we solve it
One team builds, runs, and reports on your agents.
Agents carry the agreed tasks of the role across the systems you already use. Each one works inside a written permission level, and every run is recorded.
Ergon operators run the agents every working day. They watch the queues, resolve exceptions within policy, correct outputs, and pass anything consequential to your named approver.
You pay a monthly fee for the work in scope, agreed in writing. At the agreed interval you receive a report in business terms: volume, exceptions, corrections, and cost.
Roles we run
Where managed operations fit.
Typical managed roles across industries. Illustrative examples, not client results.
- Accounting firm
Managed client intake
Agents request, receive, and sort client documents through the season. Operators chase gaps and handle unclear files. Staff accountants confirm what is filed and own every client conversation about tax.
- Distributor
Managed order entry
Agents turn emailed and portal orders into draft order lines. Operators resolve catalog mismatches within policy. The sales team approves pricing exceptions and credit holds.
- Medical practice
Managed referral coordination
Agents prepare referral summaries and track missing paperwork. Operators follow up with referring offices. Front-desk staff approve scheduling, and clinicians make every clinical decision.
- Property management
Managed maintenance coordination
Agents triage tenant requests and propose vendors. Operators schedule routine work within an approved spend policy. The property manager approves anything above it.
- E-commerce
Managed first-line support
Agents draft replies on order status, returns, and product questions. Operators send replies the policy allows and correct the rest. Your team owns refunds outside policy and every escalation.
- Professional services
Managed billing preparation
Agents assemble draft invoices from time entries and billing rules. Operators check them against the rules. A partner approves every invoice before it goes to a client.
- Home services
Managed booking and follow-up
Agents answer booking requests, propose slots, and send reminders. Operators handle reschedules and unusual requests. The dispatcher owns the schedule and every customer complaint.
- Staffing agency
Managed recruiting coordination
Agents screen applications against stated requirements and schedule interviews. Operators check summaries for errors. Recruiters make every shortlist and hiring recommendation.
What you receive
Agents doing the work
Agents carry the agreed tasks of the role, within written permissions, across the systems you already use.
Named human operators
Ergon operators watch the queues, resolve exceptions, correct outputs, and escalate anything consequential to your team.
Approval where it matters
Payments, customer commitments, and changes outside an agreed policy wait for your named approver, every time.
A regular report
Volume handled, exceptions, corrections, and cost, at the agreed interval, in business terms.
Improvement under control
Corrections become test cases. Changes to agents, prompts, or models pass the agreed tests, then your approver releases them.
Room to grow
Add a task or a role when the evidence supports it. Each addition is scoped and priced before it starts.
How it works
Onboard
The agents move into daily use in the agreed mode. Operators learn your rules, systems, and escalation contacts.
Run
Agents do the work. Operators watch the queues, resolve exceptions, and pass consequential actions to your approver.
Report
At the agreed interval, you see volume, exceptions, corrections, cost, and what the operators recommend.
Improve
Corrections feed the test set. Each change passes the agreed tests, and your approver decides what is released.
Expand
When a task runs well, the next one is scoped and priced. You approve each addition.
A working day
Who does what, hour by hour.
A sample day for a managed intake role. Times and tasks are set for your operation in the agreement.
| When | Agents | Ergon operators | Your team |
|---|---|---|---|
| Overnight | Read new requests and prepare drafts | None | None |
| Start of day | Queue drafts by priority | Review the exception queue | Approve items waiting for a decision |
| Through the day | Enter records, draft replies, follow up | Resolve exceptions within policy, correct outputs | Handle escalations and judgment calls |
| End of day | Summarize volume and open items | Log corrections as test cases | Review the day’s summary, if wanted |
| Each reporting period | None | Report volume, exceptions, cost, and recommendations | Approve changes and releases |
Consequential actions wait for your named approver at every hour of the day.
What you see in each report
The measures your approver reviews.
Each measure is agreed before operations begin, with how it is counted and how often it is reported.
- Volume handled
- How much work the agents completed in the period, by task.
- Exceptions and how they ended
- What reached an operator or your approver, and how each was resolved.
- Corrections
- Outputs an operator or your team corrected, with each one logged as a test case.
- Cost
- The monthly fee and model costs in scope, set against the work completed.
- Recommendations
- Changes the operators propose, each waiting for your approver before release.
Common concerns
What owners ask before they sign.
- Consequential actions
- Payments, commitments to customers, and changes outside an agreed policy wait for your named approver, every time.
- Coverage
- Operator hours and response targets are written into the agreement for your operation. Outside those hours, agents hold anything that needs a person.
- Your data
- Agents and operators work inside the systems and permissions you granted. Access is reviewed when scope changes.
- Changes and releases
- A new model, prompt, or rule version passes the agreed tests before your approver releases it.
- Continuity
- Runbooks, run records, and the test set are kept current, so another team could take over under the agreement’s handover terms.
Who does what
Who builds, who runs, and who approves.
Your team
- Name the approver for consequential actions
- Own the rules: pricing, credit, refunds, and policy
- Handle escalations and judgment calls
- Review each report and approve each release
- Decide when to add or remove work from scope
Ergon
- Run the agents every working day
- Resolve exceptions within the agreed policy
- Correct outputs and log each correction as a test case
- Report volume, exceptions, and cost at the agreed interval
- Prepare improvements for your approval
Afterward
Where clients go next.
Most take one of these routes. You choose, and nothing starts without your approval.
Add a task
When a task runs well, the next one in the role is scoped and priced for your approval.
Add a role
A second role starts with its own Workforce Blueprint, so its duties and approvals are written down first.
Raise a permission level
When run records support it, your approver can let a task move from draft to a pre-authorized routine write.
Bring it in-house
Take operations over with your own team under the agreement’s handover terms, using the runbooks and test set.
Before you start
What to have ready.
- A completed Workforce Blueprint, or the agents and system you run today
- The named approver for consequential actions
- Your escalation contacts and their hours
- Your rules for pricing, refunds, credit, or other exceptions
- The measures you want in each report
Related services
The crew on your work
Who runs your agents, and who approves their work.
Every agent has an operator watching it and an approver above it. Each consequential action waits for a named person on your team.
- Your named approverSets the rules, approves consequential actions and releases, and owns every decision that commits the business.
- Ergon operatorsRun the agents every working day: watch queues, resolve exceptions, correct outputs, and escalate to your approver.
- Ergon engineerMaintains the system, writes tests from corrections, and prepares each change for your approval.
- Intake agentReads what arrives, classifies it, and routes it to the right queue.
- Work agentsDo the role’s tasks: entering records, drafting replies, reconciling, scheduling, and following up.
- Check agentCompares each output with the role’s rules before an operator or approver sees it.
Who approves what
Operators run the agents. Your approver decides.
Ergon engineers build and test each change, and Ergon operators run the agents inside these levels. Your named approver authorizes consequential actions and releases.
| Level | What the agent may do | Who approves | Example |
|---|---|---|---|
| Read | The agent reads the sources it was granted, and nothing else. | The access is approved once, when the system is scoped. | Reading open invoices in the accounting system. |
| Draft | The agent prepares work, and a person decides whether it is used or sent. | An Ergon operator or someone on your team reviews each draft before it leaves the system. | A reply to a customer, waiting in the review queue. |
| Pre-authorized routine write | The agent makes a bounded, reversible change that a written policy already allows. Every change is logged. | A named owner on your team approves the policy in advance. Operators watch the changes, and anything outside the policy waits for a person. | Correcting a duplicate customer address under the approved conflict rule. |
| Consequential action | Payments, commitments to customers, changes to a record of truth outside an approved policy, and anything that cannot be undone. | A named person approves each one, every time. If nobody approves, nothing happens. | Paying a supplier, or changing a price a customer was quoted. |
| Release | A new model, agent, prompt, or rule version goes live. | The client’s named approver approves each release after the agreed tests pass. Contractual acceptance of the work is a separate step. | Moving an improved extraction model from testing into daily use. |
What the agreement sets out
Scope, approvers, and reporting, agreed in writing.
- The agreement names the tasks in scope, the systems touched, and the permission level for each.
- Each consequential action has a named approver on your team.
- Reporting measures, their interval, and coverage hours are agreed in writing before operations begin.
- Changes to scope, and each release, follow the agreed change and approval process.
Talk about managed operations
Tell us about the work to run.
If a Workforce Blueprint should come first, we say so. Otherwise we reply with a short assessment conversation.
- An engineer reads every request
- A reply by email within two business days of receipt
- No obligation until scope and price are agreed
Not ready to scope this? Ask an engineer first: a free 15-minute call about which parts of the role agents could take on.
Where this fits
- Learn How it works
- Ask free Ask an engineer
- Trial one role Agent Role Diagnostic
- Scope the system Workforce Blueprint
- Run every day Managed Agent Operations
Not ready yet? Workforce Blueprint & Starter Agent.
Questions
Does this replace employees?
It can take on the work of a role you would otherwise hire for, or free the people you have for work that needs them. Which it is, and how quickly, is your decision. The plan names what stays with people.
Who are the operators?
Members of the Ergon team who run your agents day to day. They work from your written rules and pass anything outside them to your named approver. Coverage hours are set in the agreement.
What happens when an agent gets something wrong?
Operators review exceptions and correct the output before it moves on, wherever the permission level calls for review. Each correction is logged and becomes a test case for the next change.
Can we start here without a Workforce Blueprint?
If you already run agents or have a scoped system, yes, after a short assessment. Otherwise the Blueprint comes first, so duties and approvals are written down before operations begin.
How is it priced?
A monthly fee set by the tasks, volume, and systems in scope, agreed in writing. The proposal sets it beside what the same work costs you today.
Which AI models do you use?
Whichever clears the agreed quality bar at the lowest cost, task by task. A model change passes the same tests and your approver’s release before it reaches daily use.
Can we end the service?
Notice and handover terms are set out in the Master Services Agreement. Documentation and run records are kept so another team can take over.
Can we reduce scope later?
Yes. Scope changes, up or down, follow the change process in the agreement, and the monthly fee is adjusted in writing.