The answer is in one of these two hundred files
You wrote most of these files. You still can't answer a question without twenty minutes of scrolling. Here's how the answer comes back with its page number.
The folder is called Marsden — 2024. Inside it are two hundred and six files: a contract, four addenda, twenty-two site photographs, three copies of the same specification named v2, v2-final and v2-final-b, and a scan of something that was signed on the bonnet of a van.
The question you were asked ninety seconds ago is does the price include the second staircase?
The answer is in there. You wrote most of it.
What ninety seconds turns into
You could answer from memory. You’re fairly sure it’s in the spec. But “fairly sure” is how people end up paying for staircases, so instead you open the contract, then the spec, then the addenda — because an addendum in March may well have changed what the spec said in January, and the version that matters is the last one anybody signed.
Twenty minutes, realistically. Longer if the answer is in the scan.
Say six of those questions a week, which is a quiet week for most people. That’s two hours, about $120 of your own time at $60 an hour, and roughly $500 a month spent finding things you already own. Nothing about the business improved during those two hours. You just got back to where you already were.
The interruption is worse than the twenty minutes. It lands mid-quote, mid-drive, mid-conversation with somebody else, and it takes the rest of the afternoon a while to recover.
Then there’s the version of this that costs real money: you answer from memory, you’re wrong, and the argument that follows is about a staircase you’ve now agreed to build. Or the slower one, where you don’t answer at all for two days, and the client learns that asking you a straight question is a slow business.
How it gets handled
No new filing system. No renaming eleven hundred documents on a Sunday. The files stay where they are, named as badly as they are.
Here’s the order it actually happens in.
1. Everything gets read once. Contracts, specs, scans, the photographed page, the email with the change buried in the third paragraph. Read once, up front, including the ones that aren’t typed text — the scan of the thing signed on the van becomes searchable like everything else.
2. You ask a plain question. Does the Marsden price include the second staircase? Not a search term, not a file name, not a set of folder trees to click down. The question you’d ask a colleague who’d read everything.
3. The answer comes back with the page. Two lines, then where it came from: the document, the section, the date. If two documents disagree, it says so and shows you both — the January spec and the March addendum that changed it.
4. You check the source. One click to the actual paragraph. Ten seconds to satisfy yourself, which is the whole point: you’re confirming, not hunting.
5. You answer the client. Ninety seconds after they asked, with the clause number in the reply, in the voice of someone who has their paperwork in order.
The catalog calls this one the Document Analyst. It has read every page of every job you’ve ever done, which no human being on your payroll has, including you.
A few versions of it:
The builder. The specification says one thing and the addendum from March says another, and the argument on site is about which one governs. The answer names both, in order, with dates. Three minutes at the tailgate instead of an evening with the laptop, and the conversation stops being a memory contest between two tired people.
The insurance broker. A client asks whether they’re covered for hired-in plant. That answer never lives in one place — it’s the schedule, plus an endorsement, plus the exclusion on page forty-one that quietly takes back half of it. All three come back together, which is exactly the assembly job that used to eat a morning.
The engineering consultancy. Half the archive isn’t text at all: drawings, site notebooks, a decade of PDFs scanned crooked from a machine that’s since been thrown out. Those get read too. The question “what depth did we specify on the Halesworth footings?” stops being a two-hour excavation of your own basement.
When the answer has to be right and immediate, this matters more, not less. A gluten question in the middle of service is the same lookup with four minutes and somebody’s health on it.
What it won’t do
It doesn’t decide what the answer means. It will tell you the clause says the price excludes stair balustrades. Whether you charge for it, absorb it, or ring the client and sort it out like adults is a judgement about a relationship, and it isn’t a filing question.
It won’t invent an answer to be helpful. When the files don’t say, it says they don’t say. That’s the behaviour to insist on and the one to test hardest in the first fortnight — ask it three things you know aren’t written down anywhere and watch what it does.
It can’t read what was never written. The concession you made on the phone in April, the handshake about the extra parking bay: if it isn’t in a document, an email or a note, it doesn’t exist here. It only knows the paper trail you actually kept.
And it won’t tidy up after you. Your folders stay a mess and your file names stay meaningless. They just stop mattering as much, which is a different thing from being fixed, and if the real problem is that half your documents never got saved anywhere, that’s a process to sort out before it’s a search problem.
Stop hunting through your own paperwork.
Operio builds and runs the AI workers that take a job like this off your desk — set up around how you actually work, watched over, and improved as it goes. You approve everything before it reaches a customer.
Or browse the full catalog of specialists to see what else can come off your plate.