A proof on your own files. Not a demo.
Send twenty of your documents, fifty of your tickets or a week of a shared mailbox. You see what the agent did with your files: what it got right, what it flagged, what it would hand to a person. Under NDA, in a separate environment, deleted afterwards.
One slice of the real work. Not a description of it.
Twenty documents.
Invoices, orders, confirmations, forms, letters, in the formats they really arrive in, including the bad scans. For the Reader and the Checker.
Fifty tickets.
Or a week of the shared mailbox, with the replies your team actually sent. For the Sorter and the Drafter: we show how it would have labelled, routed and drafted, next to what you did.
A manual and twenty questions.
The documents people should find their answers in, and the questions they actually ask. For the Answerer: every answer comes back with the passage it came from, or with “not in the sources”.
Result, misses, verdict.
- STEP 1Agreement NDA and a processing agreement signed, the files received through a secure transfer, a separate environment set up for your proof alone.Signed
- STEP 2The run The agent is pointed at your files, with the rules you gave us and nothing more. It runs. We do not tune it to your sample, because that would show you a result you will not get later.Run
- STEP 3The review An engineer goes through every result by hand and marks what was right, what was marked for a person, and what was wrong, and writes down why.Reviewed
- STEP 4The call Your files on screen, the result next to them, the misses first. Then the verdict: which shape this is, what it should and should not decide, and whether it is worth building.Verdict
- STEP 5Deleted Your files and the environment are deleted, and you get the written confirmation. You keep the result. If you go on, a Factory Sprint turns it into a proposal with a fixed price.Yours
Under NDA, in a separate environment, deleted afterwards, by an ISO 27001 company.
Who this is for, and who it is not for.
Before you send anything.
Can we anonymise the files first?
Yes, as long as the chore survives it. A ticket without the customer’s name still sorts. An invoice without the supplier does not match. We tell you what the agent needs and what it does not.
What if the result is bad?
Then you have learned that early instead of after months of building, and you know why: usually the input is messier than anyone thought, or the rule is not written down anywhere. Both are worth knowing. We say it plainly, and we do not propose a sprint for a chore that will not pay.
Who sees our files?
The engineers who run the proof, under ISO 27001. Not sales, not a model provider’s staff.
Pick the chore. We send the transfer link.
Tell us which chore and roughly what the files are. You get the NDA and the processing agreement, then the transfer link and a date for the call.
Under NDA · separate environment · deleted afterwards