# If your website offered tools instead of pages Topic: [Machine-readable website](https://btlabs.dev/en/ai-website) > From looking to getting done: a thought on what happens when assistants act rather than answer — including the reasons it might not work out. I have been building pages for twenty years. Home, services, about us, contact. The order has changed, the design certainly, the underlying principle never: a website is a collection of pages a person looks at. Lately I think that principle is not becoming wrong, but incomplete. And I am writing this expressly as a thought, not an announcement — nothing described here as a possibility is a promise. ## The difference between looking and getting done. A page is something to look at. You read it, you understand it, and then you do something — call, fill in a form, drive over. The last step happens outside the website. A tool is something to use. “Check whether the 14th is still free.” “Work out what that costs for 120 square metres.” “Send me the spare-parts list for this model.” Those are not pages. They are actions with an outcome. Today such actions mostly sit on websites as text, and a person translates them into clicks. The thought here is: what if a business did not only describe them but **offered** them — in a form a machine working on a customer's behalf could use? ## Why this becomes thinkable now. Two developments are converging. The first: assistants have moved from answering to acting. They no longer only answer questions, they carry out tasks — booking, comparing, ordering, filling in. How well that works is another matter; that it is the direction is visible in every new version. The second: methods are emerging by which a website can offer not only content but **capabilities** — described, with clear boundaries, so a program can call them without needing a human click. These are not widely established today, and I do not claim to know which of them will prevail. But they exist, they are openly documented, and they answer a question nobody used to ask: what if the visitor cannot click at all? ## A thought experiment, not a product. Take a business that installs and services refrigeration systems. Today its website says: what it does, for whom, a contact form, perhaps an emergency number. It would instead be conceivable — and I stress: **conceivable**, not available — that the same business offered three things that do not look like pages: - **Check availability.** Not as the sentence “give us a call”, but as a queryable fact: the next free slot for this kind of job in this area. - **Give an estimate.** From a few details, an order of magnitude — not a commitment, but more than silence. - **Start a case.** Take an enquiry with what the business actually needs, instead of a standard form that then produces five follow-up questions. The point is not the technology. The point is: **those are the same three things that happen on the phone today.** They are already part of the business. They simply are not written down anywhere in a form something other than a person could reach. ## What makes me sceptical about it. I have been through enough waves to run the counter-check on a thought like this. **It may be that nobody uses it.** Plenty that was technically possible never made it into daily life, because the detour through people stayed more convenient. **It may fail on trust.** Letting a machine make a binding booking assumes both sides trust the outcome. That question is not technical, and it is not solved. **And the large platforms may take it over** before it becomes relevant for an individual business — as happened with reviews and map services. Then your own website would again not be the place where it happens. One thing I still consider certain, and only this one: anyone whose capabilities are already **describable** today — what they do, for whom, in which area, with which limits — will have an easier time if one of these developments does become everyday. Not because they would be faster, but because the groundwork is the same one that makes them findable today. ## Why I see this as the same line continued. In [Why “web agency” is too narrow](https://btlabs.dev/en/posts/why-web-agency-is-too-narrow) I described how the job has shifted: from designing a view to maintaining a source. The thought here is the next step along the same line — from a source you can **read** to one you can **do something with**. And both start in the same place: with cleanly filed facts. A website whose services, responsibilities and limits exist only as running text can do neither. One where they exist as data can be read today — and perhaps more tomorrow. ## To close, with all due caution. I do not know whether websites will offer tools in five years. I know the question has become sensible, and that three years ago it would not have made sense. What I therefore advise businesses is unspectacular and carries no risk: build nothing on suspicion. But whatever has to be maintained anyway — services, hours, areas, responsibilities — file it so that not only a person can read it. That pays off today, with no future required. --- Source: https://btlabs.dev/en/posts/if-your-website-offered-tools Last-Modified: 2026-09-25T08:28:55.311Z Languages: [de](https://btlabs.dev/llms/de/posts/wenn-deine-website-werkzeuge-anbietet) · [it](https://btlabs.dev/llms/it/posts/se-il-tuo-sito-offrisse-strumenti) See also: [llms.txt](https://btlabs.dev/llms.txt) · [ai.txt (Policy)](https://btlabs.dev/ai.txt) · [identity.json](https://btlabs.dev/identity.json)