Watch an agent team work.
No call and no account. Every scene runs on invented data and changes only this page, so nothing is ever sent.
One email, a team of agents, and you.
An ordinary customer email goes in. A worker agent drafts, a checker agent tests the draft, a supervisor agent watches every step, and a reply waits for you. Press play, or step through it with the controls.
Agents check each other. A supervisor watches every step. You approve the result.
Inbox
Today, 08:14Quote for 40 valve assemblies, delivery to Malmö
From Karin Lindqvist, Nordkap Fittings AB
Hi, we need a quote for 40 of the DN50 valve assemblies, delivered to our Malmö warehouse by the 14th. Can you confirm lead time and price?
- Quantity
- 40
- Part
- DN50 valve assembly
- Deliver to
- Malmö
- Needed by
- 14th
Worker's lookups
- Price list17,200 SEK for 40
- Stock62 in stock
- Freight to Malmö1,200 SEK, 2 days
Draft reply
Corrected versionHi Karin, Thanks for the inquiry. 40 DN50 valve assemblies, delivered to Malmö by the 14th, come to 18,400 SEK including freight of 1,200 SEK. Lead time is 6 business days from order confirmation. Let me know if you'd like to go ahead and I'll get the order raised. Best, Sales team
Changed: freight 1,450 SEK to 1,200 SEK, total 18,650 SEK to 18,400 SEK.
- Worker agentDone
- Checker agentPassed
- Supervisor agentRun closed and logged
- YouApproved
Checker's tests
All 5 passed- Price matches the price list
- Freight matches the price listFirst draft said 1,450 SEK. The list says 1,200 SEK.
- Stock covers 40 units
- Lead time is within 6 business days
- No discount or extra promise (policy)
Approval inbox
Approved by AnnaReply to Karin Lindqvist
Quote for 40 valve assemblies, 18,400 SEK. Checked and cleared.
Reply sent (simulated). Nothing left this page.
- An email arrives
A customer asks for a quote. The supervisor agent starts watching the run from the first step.
- The worker reads it and picks out the facts
The worker agent pulls out what matters: how many, which part, where to, and by when.
- The worker looks things up
It checks the price list, stock and freight. Each answer comes from your own systems.
- The worker writes a first draft
The draft is written in your tone, using what it just looked up.
- The checker tests the draft
A second agent tests the draft against the price list, stock, lead time and your policy. One test fails: the freight price does not match the list.
- The supervisor sends it back
The supervisor sees the failed test and sends the draft back for correction. The worker fixes the freight line and the total.
- The checker tests it again
The same five tests run on the corrected draft. All five pass.
- The supervisor clears it, then a person approves
Nothing goes out on the agents' word alone. The draft waits in your approval inbox until a person clicks Approve.
- Sent, after approval
Only now does the reply go out. In this demo the send is simulated, so nothing leaves this page.
Time and cost
IllustrativeIllustrative. Assumes 14 minutes by hand at $40 an hour, against 52 seconds and $0.14 of model use for the team, including the check, the correction and the supervisor. Your numbers will differ.
Not one agent
A team, with oversight.
Good agents need checks around them, and oversight on top. Here is how that works across the system, one scene at a time.
The harness
Checks, a supervisor, and your say.
Five situations, each with a different way things can go wrong, and what the team does about it.
The checker catches a wrong fact
A draft can look fine and still be wrong. A second agent compares every line with the record.
Reminder to Brightwater Bakery
Held for approval- Invoice 1042, 2,300 SEK, 14 days overdue
- Invoice 1051, 1,150 SEK, 3 days overdue
Nothing is sent until a person approves it.
- Worker agentDone
- Checker agentPassed
- Supervisor agentCleared
- YouHeld for approval
- The worker drafts a reminder
Three overdue invoices for one customer, written up as a polite reminder.
- The checker tests every line
A second agent compares each line with the ledger. One line does not match.
- The supervisor sends it back
The supervisor sees the failed check, stops the draft going further and sends it back for correction with the reason.
- The checker passes the corrected draft
Two lines left, both matching the ledger.
- It waits for you
The reminder is checked and cleared, and still not sent. A person decides.
Your inbox, one decision at a time
Approve, edit or reject. Each item arrives already checked and cleared.
Approval inbox
Inbox empty- Reply to the Nordkap Fittings quote request
Approved by you. Sent (simulated).
- Follow-up for Andersson Maskin AB, quiet for 14 days
Edited by you, then approved. Sent (simulated).
- Reminder for 4 overdue invoices
Rejected by you. Back to the worker. Not sent.
- Worker agentRewriting with your note
- Checker agentWaiting for the rewrite
- Supervisor agentLogged the rejection
- YouRejected 1
- Three drafts wait, each already checked
Every item shows who checked it and that the supervisor cleared it.
- You approve the first
One click. The send is simulated in this demo.
- You edit the second
You change a line and approve it. Your wording is what goes out.
- You reject the third
It goes back to the worker with your note. Nothing was sent.
The supervisor stops a loop
When a worker keeps failing, the supervisor stops it and tells you, instead of letting it guess.
Needs a decision
Escalated- Run 5120 stopped after 2 failed lookups.
- The registry did not answer. No number was guessed.
- Options: try again later, or enter the number yourself.
- Worker agentStopped
- Checker agentIdle
- Supervisor agentEscalated to you
- YouNeeds a decision
- A worker gets stuck
It needs a customer VAT number from a registry, and the registry does not answer.
- It looks it up again
Same question, same silence. The checker confirms there is still no answer.
- The supervisor stops the run
Two failures is the limit. The supervisor stops the worker instead of letting it loop or guess.
- It escalates to you with the facts
You get the plain story and your options. A number is never made up.
A failure is reported as a failure
When something breaks, the report says so, and a fallback is still tested.
Run 77213: reply-drafter
Held for approval- Local model unreachable
- Rule-based template wrote the draft
- 4 of 4 tests passed
- Flagged for you: this was a fallback run
- Worker agentDone
- Checker agentPassed
- Supervisor agentLogged as a fallback
- YouHeld for approval
- The model is unreachable
The first choice of model does not respond. The run says so plainly.
- A plain template writes the draft
An illustrative fallback fills in a template from the record. It is simpler, and the report says so.
- The checker tests it all the same
A fallback draft gets the same tests as any other draft.
- The report says fallback, not success
The run is never recorded as a normal success. You see it was a fallback before you approve.
A signed update, watched and rolled back
Updates are verified before they install, and you can go back with one click.
Release 2.4.0
Restored- Installed now: 2.4.0 (signed)
- reply-drafter: healthy
- Rollback logged
- Worker agentHealthy
- Checker agentTests passing
- Supervisor agentLogged the rollback
- YouRolled back
- A new release is available
Version 2.4.1, signed by Solutions Factory. Nothing installs by itself.
- The signature is checked before install
A release that fails the signature check is refused and never runs.
- Installed, and the supervisor watches health
After the update the supervisor keeps watching. In this example one agent starts to degrade.
- You roll back
One click restores the previous signed version. The change is logged.
CRM
The record that fills itself in, and a report that is checked.
Your team talks to customers. Agents do the typing and check each other, and you confirm each change.
Deal record
Updated- Stage: Proposal
- Close date: 28 Oct
- Task: send revised quote by Friday
Fields typed by hand: 0.
- Worker agentDone
- Checker agentDone
- Supervisor agentLogged 3 writes
- YouConfirmed 3
- A sales call ends
Today someone types the notes into the CRM, if they remember.
- The worker proposes three updates
Each change is a small, clear proposal. Nothing is written yet.
- The checker compares each one with the notes
A change that the notes do not support is rejected before it reaches you.
- They wait in your confirm inbox
A person confirms or rejects each one. Nothing is written without a yes.
- You confirm, and the record updates
Each yes writes one change. Three updates, one of them the follow-up task, and no typing.
Daily report
Ready- 3 quotes moved to "sent" after your approval yesterday
- Andersson Maskin AB has been quiet for 14 days
- Overdue invoices: 1, 6 days overdue
- Caution: the Andersson Maskin AB record was last updated 41 days ago
- Worker agentDone
- Checker agentDone
- Supervisor agentLogged
- YouReading it
- The worker assembles the morning report
It reads the records and writes up what changed overnight.
- The checker verifies every statement
Each line is compared with the record it came from. All three match.
- The supervisor adds a caution
A report can be correct and still rest on old data. The supervisor flags a record that has not been touched for weeks.
- You read a report that was checked
Every statement matches its record, and anything that looks old is marked.
Drengur
From a client email to a checked itinerary.
An itinerary agent for travel designers. A planner builds it, an overseer runs the audit gates, and nothing reaches a client without your approval.
Itinerary PDF
Held for approval- 6-day itinerary, Oslo, Flåm, Bergen
- Checked, cleared, not sent
Never sent automatically. The trip, the client and the places are invented.
- Worker agentDone
- Checker agentPassed
- Supervisor agentCleared
- YouHeld for approval
- A client email comes in
A travel designer receives a request for a 6-day trip. The supervisor starts watching.
- The planner builds the route and prices it
The worker agent plans the days and prices them from dated supplier rate sheets. It never invents a price.
- The checker tests the prices, legs and wording
A second agent checks each price against its rate sheet, each leg for feasibility, and the wording for your house voice.
- The overseer signs off the whole itinerary
The supervisor agent here is the overseer. It reads the test results and the open items, and clears the itinerary for you.
- The itinerary waits for you
A checked itinerary PDF is ready. It is never sent automatically.
Itinerary PDF
Held for approval- 6-day itinerary, Oslo, Flåm, Bergen
- All 15 gates passed, every day has its Plan B
Never sent automatically.
- Worker agentDone
- Checker agentPassed
- Supervisor agentCleared
- YouHeld for approval
- The planner builds a day block
Day 3 of an invented trip, with times and a place for each part of the day.
- The audit gates run
The overseer runs the 15 audit gates. They cover coverage, feasibility, season, shipping and weather, among others. One gate holds the day.
- The planner adds a Plan B
Each risky activity gets a named backup and the trigger that switches to it. The northern lights are never promised.
- The gates pass and the overseer signs off
All 15 gates pass on the corrected day. The overseer clears it for approval.
- The itinerary waits for you
Only a checked itinerary reaches your approval, and it is never sent automatically.
APG
Every agent on a budget, and in view.
A cap and a health light show what each agent spends, and a plain report appears when one stops.
Agents and budgets
- reply-drafterhealth: passed$7.92 of $12.00
- data-stewardhealth: passed$1.80 of $4.00
- follow-up-schedulerhealth: passed$0.90 of $3.00
- itinerary-builderhealth: degrading$11.40 of $25.00
- Worker agentreply-drafter resumed
- Checker agentTests run as normal
- Supervisor agentLogged the cap change
- YouRaised the cap to $12.00
Run request
Resumedreply-drafter, run 4418
Cap is now $12.00. The run goes ahead.
Log
- 08:02 data-steward: 12 contact records tidied
- 09:02 reply-drafter: stopped, monthly cap would be passed
- 09:02 You are notified
- reply-drafter.monthly_cap: 8.00 → 12.00
- Every agent has a budget and a health light
You can see all of them in one place, with what each has used this month. The supervisor agent watches every one.
- One run would pass its cap
The reply drafter is close to its monthly cap, and a new run would take it over.
- It stops before the model is called
The supervisor agent refuses the run up front, so nothing extra is spent.
- The failure is reported, not hidden
It shows up in the log in plain words, and you are told.
- You choose what happens next
Raise the cap or switch the model. Either one is a one-line config edit.
You stay in charge
The agents do the legwork. You decide.
Every figure on this page is demo or illustrative, and nothing here was sent. Your own numbers will differ.
Let an agent team take the first pass.
Tell us the task that eats your week. We will show you what a team of agents does with it.