Agents run this business. Right now.

The daily work of a real business, done by agents. People sign off. Labs train and test on what happens.

A clerk at the claims desk, a spreadsheet open, shelves of paper claim forms above.
claims desk
live
Manila, local time
--:--:--
Sample feed, de-identifiedone morning
08:52front deskagent
Confirmed tomorrow's first session by SMS.
09:03suppliesagent
Counted the cart. Reorder queued.
09:14claimsagent
Opened the claim for a completed treatment.
09:15claimsstop
Two documents disagree. Asked staff.
09:31schedulingperson
Approved a rebooking for Thursday.
09:48recordsagent
Updated the session record.
10:02suppliesperson
Signed the reorder.
11:03claimsagent
Filed the claim through the insurer's portal.
A franchised dialysis center. Names, times and amounts changed.
Live now
A leading dialysis chain in the Philippines
Next
Retail operations
Markets
Southeast Asia, Europe, US
Status
First deployment running

An autonomous economy will be built one real business at a time. We run the first ones, and give labs what happens inside.

One live operation

Agents do the work. People decide the hard calls.

A top dialysis chain in the Philippines. We rebuilt how one center runs, end to end. Below is one workflow from it, claims filing: when documents disagree, the agent stops and a person decides.

One episode, claims filing
live
09:14
agent
Opened the claim for a completed treatment.
09:14
agent
Read the claim form and the statement of account.
09:15
agent
The two documents give different amounts.
09:15
stop
Stopped. Asked clinic staff to check the amount.
11:02
person
Replaced the statement of account with a corrected copy.
11:03
agent
Filed the claim through the insurer's portal.
day 4
world
The insurer accepted the claim.
One of 22 episodes. Names, times and amounts changed.
Datasheet
claims-filing
task
File the insurance claim for a completed treatment. Stop if the claim form and the statement of account disagree.
tools
Scanned forms, statement of account, insurer portal, chat with staff
languages
English
horizon
Days, with stops for a person
reward
The insurer accepted the claim.
verified by
The insurer's portal record
Sent with every episode.
300+
steps to draft one claim, end to end. About 30 minutes.
20+
tools across 3 workspaces: the scans, the insurer portal, the staff chat.
2,000+
historical claims to build the agent, tested against a replica portal before going live.
Why it is different

Only one kind of environment has an agent doing the job today.

Compared on Simulated software Purchased records Live operations, ours
source Software clones, written tasks Old emails, chats, tickets Agents doing the job today
reward A verifier someone wrote Expert rubrics on past cases The real outcome
freshness Static Frozen at sale New episodes as the work runs
rights The builder's The seller's Signed with the operator
What a lab can get

Three things, in the order you can have them.

Available now

Trajectories

De-identified traces: the task, every tool call, every stop, what the person did, the outcome and its source.

Available now

Evaluations

Four judges, one question each. A named human reviewer signs the result.

In development

Interactive environments

The same workflows, set up for your agent to run against. A person stays in the loop.

Data arrives the way the work does: every day, de-identified at the source, licensed under a written agreement with each business. Tell us where your agents fail and we will build the next environment with you.

Method

One judge grading everything blurs what went wrong. We split the job.

Outcome

Did the real-world result happen?

Transcript

Was what the agent said correct?

Trace

Did it take the right steps?

Failure type

When it failed, which kind was it?

A named human reviewer signs each result. If a scenario did not come up in the next run, it is never counted as fixed.

Stops

The hard part is not finishing the task. It is knowing when not to.

Two records disagree

Two documents give different amounts for the same job.

A document is missing

A scan is blank, cut off, or never attached.

An amount is out of range

The total is far from what this normally costs.

A person has to sign

An approval the agent is not allowed to give.

A system did not answer

A partner system is down or returns an error.

The instruction is unclear

Staff ask for something the task does not cover.

Reasons from the first live deployment. Counts follow once confirmed with the operator.

Tell us where your agents fail.

For labs

Send us the failure you cannot reproduce in simulation. We will tell you whether we see it in a live operation, and what we can give you to work on it.

Request a sample
For researchers, benchmark in development

Can an agent run the daily work of a real business? First tasks from the live deployment: recall, rebooking, scheduling, the front desk. Built with the early cohort.

Join the early cohort
Or email jz@achievego.ai if you would rather write.
Talk to us

Tell us what you are working on.

We reply within two business days.