AGENCYFor agencies

Many clients.
One place to learn.

Instead of one account per client you get a structure: your agency on top, clients underneath, their websites alongside. Roles stay separate, results stay findable.

  • Unlimited clients
  • Reports with your name
  • One invoice

The problem

Testing for clients rarely
fails because of the idea.

01

Logins everywhere

One tool account per client, passwords in chats, and at offboarding nobody knows what stays.

02

Reporting costs hours

Screenshots in slide decks, every month again, different for every client.

03

Knowledge gets lost

What worked for client A a year ago is known only to the person who left.

04

Debate instead of decisions

Without explainable numbers, the loudest opinion in the room wins.

The structure

Three levels that
fit together.

Agency, client, website: every level has its own roles. Whoever should only see results sees only results. Whoever looks after a client sees their websites, and nobody else’s.

RoleCan
Agency adminCreate clients, manage teams, see everything
Client adminManage the websites and experiments of this client
EditorBuild and start experiments, not manage access
ViewerRead results, change nothing

Reporting

Results you can
simply pass on.

A report link shows the result read-only and without a login, with your agency’s name at the top. The link expires if you want it to, and can be withdrawn at any time.

  • Read-only, aggregated numbers only, no visitor data
  • With an expiry date or permanent, revocable at any time
  • Built to print as a PDF, for the monthly review
  • CSV export for your own analysis

Day to day

From pitch to monthly report.

01

Create the client

Their own space, their own roles, connect websites, run the setup check.

02

Run the tests

Plan ideas as experiments, set the sample size, build variations, let them run.

03

Hand over the result

Send the report link, record the learning, derive the next question from the result.

FAQ

Questions from agencies.

Can clients see their own results?

Yes. Either as a viewer in the workspace, where they see only their own websites, or through a report link with no account at all.

What happens when a client leaves?

You withdraw access to the client space. Experiments, results and learnings stay where they belong, and report links can be revoked individually.

Is traffic counted per client or in total?

In the agency plan the total across all clients counts. That way small clients can run alongside without booking a plan each.

Can it plug into our processes?

Through API tokens, webhooks and Slack notifications. And through the MCP server, if your AI agents should create experiments or summarise results.

Make your next change an informed one

Less guesswork.
More now we know.

One question is a good place to start.