For agencies and fractional operators

Can one Day.ai workspace handle several clients?

No, and you should not want it to. The workspace is the boundary for data, billing and access, so one client is one workspace and you join each as a member. That is more setup than one console showing everything, and it is the only arrangement that survives a client leaving.

How it divides when you run it for other people

ThingWhere it sits
Client dataOne workspace per client. No cross workspace view
Your accessYou join each workspace as a member. Admin or owner if you are configuring agents
BillingPer agent, per workspace. The client pays for their own
Your seatFree, if their workspace has at least one paid agent

The last row is the one that changes the economics. Day.ai charges per agent, not per seat, and a workspace with a paid agent can add colleagues at no cost. So being in ten client workspaces costs you nothing, which is not true of any per seat CRM and is the reason this shape works for an agency at all.

Client A workspacetheir data, their paid agentClient B workspacetheir data, their paid agentClient C workspacetheir data, their paid agentYoufree member of eacha seat costs nothingno view across workspaces
One workspace per client is the boundary for data, billing and access. You join each as a member and it costs you nothing, because Day.ai bills per agent rather than per seat. What you do not get is a view across them.

Four things to settle before client two

  1. Whose email connects

    The record builds from Gmail and Calendar per user. If only your address is connected, the workspace reflects your relationships and not the client's team, which quietly makes the CRM about you.

  2. Who owns the workspace

    Put it in the client's name from day one. An agency owned workspace holding a client's customer data is a conversation you do not want to have during an offboarding.

  3. What the agents are allowed to send

    Agents draft and send email. Under whose name, to whose contacts, with whose approval, is a policy decision and it should be written down before the first one is switched on.

  4. How you hand it back

    Agree at the start what the client keeps and how, while everybody is friendly. Good practice on any engagement, and worth writing down here because there is no published guide to it yet.

What nobody has published

There is no agency guide and no single console for running this across clients. With roughly 120 customers the honest reason is that it is early rather than that it is unsupported, and the shape below is derived from how workspaces and billing actually work.

Known

What we verified

Per agent billing, free teammates in a workspace with a paid agent, admin and member roles, and one workspace as the data boundary. All from their own pricing and setup pages.

Open

What we could not confirm

Whether a consolidated view across workspaces exists or is planned, whether agency billing can be centralised, and whether Outlook and Microsoft 365 are supported at all. Only Gmail and Google Calendar are listed.

That last one is a real qualifier. If your client runs Microsoft 365, confirm it before you scope anything, because the whole record builds off email and calendar and no published page says either way.

Running Day.ai for clients: questions

Does it cost me anything to be in a client's workspace?

No, as long as their workspace has at least one paid agent. Colleagues are free and free users can search, view and share.

Can I see all my clients in one place?

Not that anything published describes. Each workspace is separate and you switch between them.

Is there a partner programme?

Yes, aimed at firms that will own the outcome rather than configure software, with service bundles priced between $1,000 and $5,000 a month. Applications go by email; there is no form and no public partner list yet.

Where we come in

We set up the first client with you, then you run it

If you are standing this up for other people, the expensive part is the pattern rather than any one workspace. We build the first one with you and write down the shape so client two takes an afternoon.

  • The first client workspace built end to end, together
  • Access, billing and ownership settled in writing before it matters
  • A repeatable setup you own rather than a dependency on us
  • A second pair of eyes when a client asks something awkward

Free, no call required

The multi client setup guide

Not ready to talk to anyone? Take this instead. One email, nothing else unless you ask for it.