Concepts
Core concepts
Projects, Pages, Campaigns, Variants, Concepts, Ambitions. The words the app uses, and what each one precisely means.
The app uses these words precisely. Skimming this page once will save you a lot of guessing later.
Where things live
Org → Project → Page → Campaign → Variant| Term | Means |
|---|---|
| Org | Your company. Holds billing, members and org-wide settings. Optimeleon staff create Orgs, so you never mint one yourself. |
| Project | One site or brand, identified by its domain (www.example.com). This is the isolation boundary: data, settings, media and events all belong to a project. An agency runs one project per client. |
| Page | One optimizable URL on that site (example.com/pricing). A project's set of pages is its portfolio. The Page is where you spend most of your time in the app. |
| Campaign | The continuously running optimization of one page. One page has exactly one active campaign at a time, and that campaign lives for as long as you keep optimizing the page. |
| Variant | One alternative version of the page, an arm of the campaign. The base version (your original) is an arm too. |
Note
The domain belongs to the Project, not to a Page. If you catch yourself calling
www.example.com a page, you are one level too high.Words from the optimize loop
| Term | Means |
|---|---|
| Scan | The read of your live page that produces the understanding behind everything else. Runs through the browser extension, on the real page, with your real styles. |
| Discovery | The first half of a run. Optimeleon reads the page and comes back with three competing concepts to choose from. |
| Concept | One choosable thesis about how the page could be better: a hook, and the part of the page it would go after. It is choice material, not a build plan. The plan is made later, in the browser. |
| Picker | The dialog where you choose one of the three concepts and dial its ambition. The two you do not pick are discarded rather than saved as clutter. |
| Ambition | How far the build may go: Surgical, Structural or Whole page. The dial asks “how big may this build think?”, and the answer is always yours, never the model's. |
| Build | The second half. Leo opens your page in a real browser, surveys it on desktop and mobile, plans, builds versions, then screenshots and checks them. |
| Idea card | What a finished build leaves on the page's board. One card can hold several versions: building again on the same card appends a version rather than starting a new card. |
| Seed | Optional input to a discovery: an instruction, reference images, reference URLs, or an ad group. It steers the three concepts. It never skips them. |
The three ambitions
| Ambition | What the build may do | Reach for it when |
|---|---|---|
| Surgical | One precise intervention at the entry point. Breadth is not the goal here. | The page basically works and you want a cheap, low-risk win. |
| Structural | Rebuild, insert and move sections wherever the thesis demands it. | The message is right but the page buries it, or the order fights the reader. |
| Whole page | The whole page carries the argument. Every relevant zone gets a verdict. | The page is telling the wrong story and small edits keep failing to move anything. |
Who does what
Leo is the name of the AI that does the work. In Leo's Kitchen you see the crew he runs (Scout, Strategist, Builder, Publisher, Analyst, Researcher) and which of them is busy with your project right now.
Nothing Leo builds reaches a visitor without a human pressing publish. That is a product rule, not a setting.