This guide takes you from a website URL to your first finished dossier in about fifteen minutes. By the end you will have an organisation model, one real piece of work, and a feel for the one control that changes everything: build scope.
Before you begin
Make sure you have:
- A Google account to sign in with — there is no separate password
- The real, public URL of the organisation you want to work on
- Ten minutes in which you do not need the answer yet — the first model is built while you read
This guide uses the web app. intelligent.page also works from the Chrome companion, from Slack, Discord, Telegram and WhatsApp, and over the API. See Platforms and integrations.
Step 1: Sign in and give it your website
Sign in with Google from the landing page. The first screen asks one question before anything else: what is your website URL?
Give it the real production site. It is fetched and read — what you sell, who you sell it to, how you describe yourself, your brand and imagery — and turned into the first version of your organisation model. A holding page produces a thin model, so start from the right domain.
Two short questions follow: who you are answering for, and what stage the business is at. Both change what the work treats as important. They take under a minute. See Start with your website for what each answer changes.
Your first directory is created for you, named after the site. A directory is one modelled organisation; you can add more later.
Step 2: Look at what it already knows
Open Memory in the sidebar. You should see docs that did not exist a moment ago — a first read of your market, your customers, your positioning.
That is the organisation model. It is ordinary, editable content. If something is wrong, fix it there and the correction holds for every later task.
Do not skip this step. Five minutes correcting the model now saves you from correcting the same misunderstanding in every dossier afterwards.
Step 3: Ask for something real
Go to New and describe an actual problem. Not "write a blog post" — the sort of thing you would give a capable new hire:
Map the competitive landscape for our top three challengers and tell me where we are losing.
Other good first requests:
Is our pricing leaving money on the table?
What has to be true for us to launch in the first quarter?
Who is our best customer, and where do we find more of them?
Ask for the outcome, not the artefact. You will usually get a sheet, a deck or a board anyway — chosen because it fits the answer, not because you guessed.
Step 4: Choose a build scope
Beneath the box is the build scope control. It decides how much of your organisation one request is allowed to reach.
Leave it on Only this for your first run. That answers the request and nothing else, which is the quickest way to see the system work. Your choice sticks for the next task until you change it.
Step 5: Send it, and walk away if you like
The task runs on its own. Follow it if you want to, or close the tab — it keeps going and tells you when it is done.
If it hits something it genuinely cannot decide — a conversion rate that is not in your model, a decision only you can make — it pauses and asks rather than guessing. Answering takes seconds, the run continues, and the answer is written into the work itself.
Step 6: Read the dossier
You get back a dossier. Start at the top: the entry doc is the answer in prose. Then look at:
- Issues — what the work needs from you: assumptions to confirm, evidence it could not find, decisions waiting on a human
- Index — every artefact the run produced
- Activity — what it actually did, stage by stage, if you want to audit it
Everything it built is a real working artefact, not a picture of one: formulas calculate, boards can be moved, charts can be inspected.
Step 7: Run the same request wider
Go back to the task and run it again with build scope on Connected. The same question now pulls in the work it touches — competitor positioning becomes pricing, channels and where you are exposed.
This is the single control that most changes what you get back. Most real work belongs on Connected; save Entire system for a genuine reset.
Step 8: Let it in
Two things make the third task better than the first:
- Answer its questions. Anything under Issues that asks for a number or a decision is written straight into the work when you answer it. You do not re-run anything.
- Connect a source of truth. Under Settings → Connectors, connect the calendar, analytics, repository or tracker that holds the facts. The model reads them instead of guessing.
Essential controls
Pro tips for your first week
Ask for the decision, not the document
Instead of "make a spreadsheet of pricing", ask "is our pricing leaving money on the table?". The sheet arrives either way; the question decides whether it answers anything.
Correct the model, not the prompt
When a result misunderstands the business, the fix belongs in Memory, not in a longer request. One edit there fixes every later task.
Read Issues before you trust anything
The Issues tab is where the work says what it could not verify. It is the part people skip and should not.
Model a competitor next
A directory is one organisation. Create a second one from a competitor's website and you get the same analysis pointed the other way.
What's next
- How intelligent.page works — the loop, what it can read, and the controls that keep you in charge
- Best practices — patterns that get better work back
- Prompt library — requests to copy and adapt
- Extend intelligent.page — connectors, skills, the Chrome companion, projects and the API
Getting help
- In the product: ask a task, in Ask mode, what it knows about the product
- Documentation: you are here — see Troubleshooting and the FAQ
- Vocabulary: the Glossary defines every word once