Skip to content

Agencies

One licence, twenty client sites

If you build WordPress sites for a living, this is a component you install once and reuse. The multi-site plans exist for exactly that.

While checkout is being finished, multi-site plans are arranged directly: tell us how many sites you need and we invoice you, then you get the plugin and every update from the built-in channel. Licence keys and a self-service portal are next on the list.
  • Five or twenty sites on one plan, with one-click updates delivered to every one of them from the Plugins screen.
  • White-label — remove our credit line so the widget is simply part of the site you delivered.
  • Client-safe settings — the admin is plain language, so a handover does not create a support queue for you.
  • Export and import settings — configure once, reuse the configuration on the next build.
  • A deployment playbook — the checklist we use ourselves for going live on a client site, from content sync to the questions to ask the client.

How it runs on an agency build

1Install once, configure onceSet up the provider, persona and design on the first site, then export the settings file. API keys are deliberately left out of it.
2Import on the next buildThe configuration lands in minutes. Sync the new site’s content, add its business facts, and the assistant knows that client instead of the last one.
3Hand it over white-labelledDrop the credit line and the widget is simply part of what you delivered. The admin is plain language, so the handover does not become your support queue.

Questions agencies ask

Can I move a licence from one client site to another?

Yes. A site can be deactivated and the licence used somewhere else — a staging site that becomes production, or a client you no longer look after. Until the self-service portal is live, tell us and we move it for you.

Does a staging or development copy use up a site?

No. Staging, local and development copies of a site you already licence do not count against the total. That is the point of building on staging.

What does the client see?

On a white-label plan, nothing of ours: no credit line in the widget and no branding in the admin. The plugin still appears on their Plugins screen, because it is a normal WordPress plugin on their hosting.

Who pays the AI provider?

Whoever owns the key. Most agencies put the client’s own key in, so the AI is billed to the client directly and you are not reselling tokens. You can also run your key and bill it on.

How do updates reach twenty sites?

The same way any plugin update does: each site checks the update channel and offers the new version on its Plugins screen. There is nothing to deploy by hand after the first install.

Put it on your site this week

One plugin, your own content, and seven days on our AI before you add a key. No subscription to a chat platform, no data leaving your hosting.

  1. Download and install. Upload it under Plugins → Add New, like any other plugin.
  2. Start the trial. The setup wizard asks for an email; the answers run on our AI while you decide.
  3. Sync your content. One click reads your pages, posts and products. From then on it answers your visitors.

Currently at version 1.59.0 · what changed

Talk to the person who built it

Pre-sales questions, licences, agency work, or a site that needs a look. One inbox, read by the developer.

  • A reply within a working day — usually much sooner.
  • Support by the person who wrote the code, not a queue.
  • A 14-day refund on every plan, no questions that matter.