Start with one client and one useful improvement.

1. Set up the workspace

Create an account, name your workspace, then add a client with its website and name. The Overview then shows the next step for that client. Getting started, in the app, keeps a six-step checklist for each client (client, approved facts, a starter prompt set, first answers, a first task and a first report), read from what is saved, and links to an example client that shows every screen with clearly labelled sample data. Each client has a separate project. A new workspace can hold one client during its 7-day trial; a subscription adds more. Owners manage membership and billing; editors work on permitted projects; viewers can inspect permitted evidence. An invitation does not grant access to unrelated client projects.

Follow the verification instructions before starting verification-gated jobs. During this staging preview, email delivery and several external integrations are awaiting setup, so those actions remain unavailable.

2. Gather an observation

Open Site audit, or save a prompt set in Visibility. For now site audits fetch only a public test site, while secure fetching for other websites is set up; you can still add tasks from sources you have read. Website permission, verified in Settings, is needed before publishing or connecting Search Console. Connected API runs use the displayed allowance and budget limits; disconnected providers do not produce sample results. Search Console connects only an authorized property.

The measurement guide explains what each observation can support.

3. Turn evidence into a brief

Open a task in Tasks, check what was observed and the assumptions behind it, then assign it or start a brief from it. Add facts and sources you have reviewed. A source being present does not automatically approve the facts: approve the brief separately.

4. Review an exact revision

Write or edit a draft, check its facts and attribution, then approve that revision. You can export reviewed work without connecting a CMS. A subsequent edit clears the active approval while retaining the earlier revision in history.

Connected WordPress operations require the current approval and a verified permitted target. Draft is the default. Publishing requires a separate authorized action.

5. Show the work

Open Reports and choose a date range to see the client’s real observations and recorded work, ready to print or share. Export a CSV for further analysis. A report link still requires workspace and project permission; sending someone a link does not give them access.

Allowances and account controls

Check the workspace usage before starting a run. A credit is reserved before dispatch, and a successful bounded generation consumes a draft credit. A provider can charge for a failed attempt even when a successful-sample credit is not consumed. Staging paid API gates remain closed.

Settings includes account data export and separate personal or workspace erasure requests. Review the scope and outstanding-operation checks before confirming a request. Billing is unavailable until a verified isolated sandbox and release configuration are ready.