---
"@type": WebPage
"@id": "https://helloloam.dev/solutions/you-dont-have-to-understand-it"
"@source": "https://helloloam.dev/data/webpage/you-dont-have-to-understand-it.json"
"@stamp": "2026-10-22T21:53:55+00:00"
about:  # 3
  - "@type": DefinedTerm
    "@id": "https://helloloam.dev/data/definedterm/no-dashboards.json"
    name: No dashboards to learn
    identifier: no-dashboards
    inDefinedTermSet:
      "@type": DefinedTermSet
      "@id": "https://helloloam.dev/data/definedtermset/gives-you.json"
      name: Gives you
      identifier: gives-you
  - "@type": DefinedTerm
    "@id": "https://helloloam.dev/data/definedterm/ai-compatibility.json"
    name: AI compatibility at its core
    identifier: ai-compatibility
    inDefinedTermSet:
      "@type": DefinedTermSet
      "@id": "https://helloloam.dev/data/definedtermset/gives-any-site.json"
      name: Gives any site
      identifier: gives-any-site
  - "@type": DefinedTerm
    "@id": "https://helloloam.dev/data/definedterm/draft-and-live-lifecycle.json"
    name: Draft and live lifecycle
    identifier: draft-and-live-lifecycle
    inDefinedTermSet:
      "@type": DefinedTermSet
      "@id": "https://helloloam.dev/data/definedtermset/mechanics.json"
      name: Mechanics
      identifier: mechanics
description: Say what you want, the way you would to a colleague. Your agent knows how your site works — so you don't have to.
headline: You don't have to understand it
identifier: you-dont-have-to-understand-it
image:
  "@type": ImageObject
  contentUrl: /assets/images/hero-home.jpg
  caption: A shop owner packs an order and checks her laptop.
inLanguage: en
name: You don't have to understand it
url: "https://helloloam.dev/solutions/you-dont-have-to-understand-it"
---

# You don't have to understand it

## The worry

Most website systems ask you to learn them first: [a dashboard](/principles/no-dashboards), its menus, where a title lives and which button publishes it. Many people never get past that. They ask someone else, and wait — for a comma, a date, an opening hour.

## What happens instead

A loam site has no dashboard to learn. You tell your agent what you want, in your own words. It finds the right place, makes the change and [keeps it as a draft](/principles/draft-and-live-lifecycle). You look at the whole site as it would be, and say publish — or not.

## How your agent knows

Every loam site explains itself to agents. Where other sites have a login form, a loam site has an explanation written for them: what the site is, how to connect, what the rules are. You connect your site once, from [the assistant you already use](/byoa). Your agent reads the same files the site is made of, so it never has to guess where a title or a price lives.

## In practice

- “Move the summer closure notice above the opening hours.”
- “Add an English version of the about page.”
- “Take the old vacancies page offline.”
- “What changed last week?”

None of these is a feature you have to find. It is a sentence.

## What it costs

You need an assistant that can work with your site — the one you already use, or one you choose; its cost is yours, not part of loam. For someone who cannot or will not use one, there is an edit client on the site itself: a plain editor that follows the same rules.