FlowsBook a callSign inCreate free accountSign up
AI employees and automation

AI employees for agencies: running them for many clients at once

How to set up AI employees for agencies: one organization per client, one design copied for many, a branded page each client can open, and limits that keep accounts apart.

Part of the guide AI employees

By the xMap team · · 4 min read

Setting up ai employees for agencies comes down to four decisions: keep each client apart in its own organization, build an AI employee once and reuse it for every client who needs it, give each client a read-only page with their results, and put limits on each account so one client's work never eats into another's. Do that from the start and twenty clients feel like one tidy workspace instead of twenty tangles.

This article is for marketing, research and consulting agencies that want to offer AI employees as part of a retainer or a managed service. It covers how to structure clients, how to reuse work, how clients see results, a made-up agency's setup, and the mistakes that make multi-client work messy. The AI employees for agencies page has the full picture of the partner offer.

Structure: one organization per client

In xMap Flows an organization is a separate workspace with its own flows, results, connections, people and limits. Agencies usually keep one organization of their own for internal work and make one for each client. Your staff are members of each client organization they work on; switching between them is one click, from one sign-in.

Keeping clients apart matters for three reasons. Their data never mixes. Their app connections (a client's Slack, a client's sheets) stay with them. And when a client leaves, you hand over or close one organization without touching the others.

  • Roles: admins, members and viewers, plus custom roles that switch off deploying, sending, public links, new connections or deleting for some people.
  • Teams inside an organization can have a monthly credit quota, useful when several of your staff work one large account.
  • A monthly spending limit per organization stops anything past it.
  • The activity log shows who changed what, for each client.

Reuse: build once, run for many

Most agencies find that a handful of AI employees cover most clients: a rating watch for a client's locations, a monthly market note, a list of new businesses for a client's sales team, a rival watch. Build each one well once, then reuse it.

  • Flow files. Export a finished AI employee as a file and import it into another client's organization. Sign-in details never travel in the file; each client connects their own accounts.
  • Linked copies. Inside one organization, make one main AI employee and a copy for each city or brand, each with its own few settings. Change the main and every copy follows.
  • Template pages. Share an AI employee as a page with a few questions, so a client or a colleague can set up their own copy without seeing the editor.

Reporting: a page for each client

Clients rarely want a login. A client view is a branded, read-only page you make for one client: a note at the top, the results of the AI employees you choose, one map of everything they found, and each one's weekly report. It opens from a private link and can be stopped at any time, after which the link no longer works. Pair it with a monthly PDF report sent by email for clients who prefer a document.

A worked example

This example is made up. A local marketing agency in Toronto looks after fourteen multi-location clients: dental groups, gyms and two restaurant chains.

  1. The agency builds three AI employees in its own organization: a rating watcher that compares each client location with rivals nearby every month, a new-competitor alert, and a quarterly market note written as a PDF.
  2. It exports each as a file and imports the ones each client has bought into that client's organization, setting the client's locations and where results go.
  3. For the restaurant chain with eleven sites across Ontario, it uses linked copies: one main rating watcher and a copy per site.
  4. Each client gets a client view. The account manager links it in the monthly email instead of building slides.
  5. Every client organization has a monthly spending limit matching what that client pays for.

When the agency improves the rating watcher's instructions, it updates the main in its own organization, exports it again, and replaces it in each client's organization over a week, checking a test run each time.

Mistakes to avoid

  • All clients in one organization. It looks simpler for a month, then results, connections and permissions blur together.
  • Connecting your own accounts to client work. Results should go to the client's Slack or sheets, connected in their organization, not to your agency inbox.
  • A different design for every client. Small differences become a maintenance burden. Keep a standard set and change only settings.
  • No limit. Without a spending limit per client, one busy account can surprise you at the end of the month.
  • Promising data that does not exist. Population figures exist only in some countries, and footfall arrives about ten days late. Check before you put it in a proposal.

The AI employees agencies start with

A rating watch for clients built on Nearby places, xMap LLM and Make a report is the usual first one; start from Rating watch for my clients. For finding new clients for the agency itself, Businesses with low ratings and no website builds a weekly list, and When something changes powers competitor alerts. The marketing and agencies page lists more templates by use.

Questions

Can one person work across many client organizations?

Yes. A person can be a member of several organizations and switch between them from the same sign-in.

Do clients need an account to see results?

No. A client view is a read-only page opened from a private link, and you can stop it at any time.

Can I move an AI employee from one client to another?

Yes, as a flow file. It carries the blocks and settings but never sign-in details; the new client connects their own apps.

Can the client's page show our agency's brand?

Each organization can have its own logo and colour, which appear on its client views, emails and PDF reports. A small Made with xMap Flows line stays.

Templates that do this

Read next

More on ai employees and automation · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.