More clients, same team, nothing forgotten.

An AI agent for your agency, each client and each project. You brief it in plain words, approve the plan, and it ships the work with the proof attached.

Join the waiting list Talk to us

Set up and trained by our developers. Priced on a call.

Where an agency's week goes.

Six things that cap an agency, and the fix for each.

  • Capacity has a ceiling.

    You can only take on as many clients as you have developers. Every new retainer means another hire, and the margin goes with it.

    The fix: agents take the repetitive work. Your team reviews and approves it.

  • Every switch costs an hour.

    WordPress at nine, Magento at eleven, Drupal after lunch. Re-learning each client's setup eats the day.

    The fix: each client agent already knows the stack and the house rules.

  • Knowledge walks out of the door.

    When a developer leaves, the client's quirks and hard-won fixes leave with them.

    The fix: every fix is written down and stays in your Orchestrator.

  • The same mistake, twice.

    A fix learned on one client never reaches the next one, so the team solves it again, and bills nobody for it.

    The fix: overnight, a fix on one client reaches every agent.

  • Small changes eat the retainer.

    Ten-minute edits arrive as tickets, quotes and chasers. The hours vanish and the client still waits.

    The fix: clients ask in their own workspace, and you approve the plan.

  • SEO, ads and reporting need specialists.

    Clients ask for them. Hiring for them is a gamble, so the work goes to someone else.

    The fix: the same agents do the SEO, the ads and the reports.

Hiring helps with one of these. The Orchestrator is built for all six.

A week with the Orchestrator.

The same four moves on every client job, whatever the platform.

  1. Brief it

    Paste the client's email, drop in a screenshot or dictate it. The client's agent reads the history, the playbook and your house rules first.

  2. Approve the plan

    You get a short numbered plan with the risk and the way back. Approve it, change it or reject it. Nothing changes before you say so.

  3. Check the proof

    Every job ends with a written validation, plus screenshots and checks listed with pass or fail. You see what the job cost too.

  4. It learns overnight

    Each night it turns the day's mistakes into written rules, so a fix on one client reaches every agent.

Let clients see the work, not chase it.

Give a client their own workspace for their project, signed in with Google, inside your website. They can ask for changes, approve plans and see the proof. They see their project and nothing else.

Join the waiting list

Can we add size guides to the product pages?

Plan ready. Nothing changes until you approve.

PLAN: size guidesApprove

Proof attached

Signed in with Google. This project only.

Sell more than development.

The same agents that build and fix also write SEO changes, Google Ads fixes, reports and client emails. You can say yes to more of what clients ask for.

Start with work you already sell: website maintenance and security patching.

  • SEO

    SEO changes, planned first and proved after, like any other job.

  • Google Ads

    Fixes for the ads and landing pages a client already runs, with the same plan and proof.

  • Reports

    Monthly reports written for you. A schedule runs them at the time you set.

  • Client emails

    Real email, with attachments and threads. It drafts by default and sends only where you allow it.

One product runs your team. One sits on a client's site.

Use the Orchestrator to run the work. Add Webgentic for sites for a client who wants to ask for small changes on their own website.

A real job: a PHP upgrade across 27 hosts.

Northgate client needed 27 hosts moved from PHP 8.0 to PHP 8.2. Before the change, the agent recorded the status and the page size of every host.

After the switch, 25 of 27 hosts came out byte-identical, which is close to proof that nothing changed. The same baseline showed one site returning 200 with a 310-byte page while its siblings returned about 150,000. It had been broken for about six months, and no status check could see it.

One homepage moved by 5 bytes and nobody could say why, because only the size had been saved. The rule we wrote down: save the page, not just its size.

  • Status and page size recorded for every host first
  • Every host compared after, not just checked for a 200
  • Each lesson written down for the next job

Example based on a real job, details changed.

Set up and trained by our developers.

The Orchestrator is installed by us, not downloaded. Real developers from our team in Bromley set it up and stay on hand.

Setup

We map your clients, platforms and access, then install your Orchestrator and load your house rules. Your team runs real client jobs with one of our developers alongside.

See how setup works

Training

We train your team on real jobs. They learn to brief the agents, review the plans and check the proof on work you already have.

See how training works

Run on our own client work first.

We have run our own client work through the Orchestrator since April 2026. These are our delivery records, not a prototype.

  • 6,600+agent runs

    Jobs planned and finished by an agent since April 2026.

  • 190+client projects

    Across 26 clients, all on one Orchestrator.

  • 861mistakes turned into rules

    Each written up with what to avoid next time.

Measured on our own Orchestrator, 29 October 2026.

Questions agencies ask first

  • Does it replace my developers?

    No. It takes the repetitive work off them, and they review and approve more work than they could do by hand.

  • Can one client's agent see another client's files?

    No. Each agent can only read and change its own client and project folder, and that limit is enforced in code, not left to good behaviour.

  • Can my clients use it directly?

    Yes, for Orchestrator work, in a workspace limited to their own project. They sign in with their Google account, ask for changes, approve plans and see the proof. You choose whether a client can interact or only watch.

  • What does setup involve?

    A scoping call, then we install it, load your clients, access, platforms and house rules, and train your team on real jobs.

  • Does it work on the platforms we run?

    Yes, if you run WordPress, Magento or Drupal. We count 41, 24 and 11 client projects on them so far, as of 29 October 2026. Shopify and Craft CMS work is light so far.

  • How much does it cost?

    It is priced on a call, because setup depends on how many clients and platforms you bring. Join the waiting list and we will be in touch.

  • Something else on your mind?

    Ask us directly and a developer will reply.

    Ask a question

Bring us your client list.

Join the waiting list. When your place comes up, we will show you the Orchestrator running on one of your real jobs in the first call.

Join the waiting list Talk to us