- Checks & evidence
Two Wurqurs, Rights Handler and Evidence Clerk, turn a deletion request from a memory test into a process.
~$52,000 saved a year for an HR software company
See howMost of what crossed their desk didn't need a person. It just hadn't been sorted yet.
Document Reader and Exception Handler clear 80 to 100 tenders a month for a commercial electrical subcontractor, rejecting what fails the playbook and flagging what still needs a decision.
Commercial electrical subcontractor · 65 employees · four systems
The pile
Tender packages arrived through SharePoint: drawings, bid instructions, subcontractor agreements, insurance requirements, change orders, sometimes running hundreds of pages. The estimators understood every one of them. What ate their time was reading the same handful of commercial terms out of each: payment terms, retainage, bonding, insurance limits, dates, anything unusual in the contract.
80 to 100 tenders came in a month, and most followed a pattern the business had already worked out. A playbook covered most of the bid or no bid call: fails on compliance, out of their domain, reject. What it couldn't resolve on its own still needed a person, and there was no way to find that slice without reading everything first.
They'd already written the rules. Nobody had built anything to run them.
What we found, and left alone
Most of what crossed their desk was already covered by rules they'd written themselves. A real slice still needed a person's judgment, and that's exactly the part that stayed one. The bid or no bid decision on anything the playbook doesn't cleanly resolve is theirs, same as before.
What we built
Document Reader checks every tender against the playbook as it reads it, extracting the commercial terms along the way. A clear fail moves to the rejected pile with the reason attached; a pass gets its terms pulled into a summary. Exception Handler owns whatever the playbook can't resolve on its own, ambiguous, unreadable, or genuinely outside the rules, and gets it to a person with the context already assembled.
Document Reader
Reads every tender against the playbook, extracts what matters, flags what it can't resolve.
- exception
Exception Handler
Owns whatever the playbook can't clear on its own, with the context attached.
And a dashboard, which is ours
A simple screen, built by us rather than assembled from what they already had. The rejected pile sits on one side with its reasons; everything still under consideration sits on the other. What the sales team used to read and check by hand, most of it is already done by the time they open it.
What changed
the review on one tender
An afternoon
5–10 min
960–1,200
tenders a year, cleared fast
600–840 hrs
a year, back to the estimators
~$37,000
a year
What used to cost them roughly $3,120 a month by hand now runs on two Wurqurs for $219/month.
Where the humans stayed
The bid or no bid decision on anything the playbook doesn't cleanly resolve. The workflow turns the first stage of review from a document search into an exception review.
What it connects
Where a tender arrives, the two Wurqurs and the screen between them, and where the result lands.
where it arrives
- SharePointthe incoming tender folders
- OCRmakes a scanned PDF readable
what runs
- Document Readerchecks against the playbook, extracts the terms
- Exception Handlerowns what the playbook can't resolve
- The dashboardbuilt by us, the rejected pile and what's still under consideration
where it lands
- Their estimating workflowstructured results feed straight in
- Microsoft 365where the source documents already live
What it took
Six weeks. Five to deploy ingestion, extraction and the dashboard, one to shadow-run it against past tenders where the client already had a ground-truth decision to check against.
The same idea, somewhere else
A stream of routine work, with the exceptions pulled out for a person to see.
Every company has a pile like this one.
Tell us the job. We will tell you whether a Wurqur can hold it.