The bakery is launching on Thursday, the fitness studio wants Reels by Wednesday, the skincare brand keeps emailing about Threads, and somewhere in all of that you nearly posted one client's content to another client's account. In Maeve every client is its own workspace with its own calendar, drafts, connected accounts, labels, and analytics, and you move between them from one sidebar. Click into the wrong client and the calendar is empty, because none of it is shared. The rest of the management platform is in there too, scoped to whichever client you are standing in.
3 days free. Cancel anytime.
Every workspace looks the same from the sidebar, so switching clients takes a second and you stop thinking about it. Underneath, each one is separate: the bakery's Instagram, the skincare brand's Reels, and the studio's TikToks never share a calendar, a draft, a media library, a label, or a row of analytics.
Roles are set inside each workspace rather than across your whole account, so the same freelancer can be a manager on one client, an editor on another, and view-only on a third. The four roles are manager, editor, creator, and viewer, and the labels, pillars, formats, and hashtag groups belong to one client as well, so renaming the bakery's launch label leaves everyone else's alone.
When you request review on a post you choose the path it takes: internal only, straight to the client, or internal first and then the client. You also choose how the sign-off works, whether any one approver is enough, everyone has to approve, or people approve in a set order, which is the difference between a strategist glancing at a caption and a regulated client that needs three names on it.
A post waiting on review is locked, and if someone edits an approved post the approval resets, so the version the client signed off on is the version that publishes.
The Request Review dialog is where the routing is decided: which path the post takes, who the approvers are, what the policy is, and which client batch it joins. Set it once for a client and the rest of the month follows the same route.
Getting a client to approve a week of posts usually means a PDF, a spreadsheet, or a thread of screenshots, and the feedback comes back as "the second one, the blue image, can we change the wording". Instead you send the batch as one link. They open it on their phone, scroll the posts as they will actually look, and approve, ask for changes, or comment on the post itself.
There is no login, no seat to buy, and nothing else in your workspace is reachable from that link. You set how long it lives, you can resend it, and you can cancel the batch.
The batches list is the honest answer to "has the client come back to us yet". Each batch shows what is approved, what needs changes, what is still pending, when the client last touched it, and when the link expires, and you can resend the link or cancel the batch from the same row rather than chasing it over email.
Onboarding a client normally involves a password over email, a screen share, or a two-factor code read out over the phone. Instead you generate a connection link inside their workspace, choose which platforms it should offer, and send it. They tap through the platform login screens themselves, and the accounts appear in your sidebar ready to publish against.
The link expires on its own, you can revoke it early, and the panel logs each attempt, so if a client says they connected Instagram and it is not there, you can see whether the authorization failed or was never finished.
Every connected account is tracked from the day it is connected, so the month is already sitting there when the client asks for it. Pick a date range, export, and the PDF comes out with your agency name on the cover, followed by engagement, reach, follower growth, and the posts that actually worked, and you can total several accounts of the same platform into one number.
Analytics covers the six platforms that report data back, which are Instagram, YouTube, Facebook, TikTok, Pinterest, and Threads. Audience demographics come through on Instagram, Facebook, and YouTube, because those are the ones that hand the data over.
Comments and direct messages from Instagram, Facebook, and Threads land in one queue with the post beside the conversation, so whoever is on inbox duty can see what the customer is reacting to without going back through the calendar. Assign a conversation to a teammate, leave an internal note the customer cannot see, and resolve it when the client's question is actually answered.
A post fails at 7am on the client's Instagram and you would rather hear it from Maeve than from the client. Temporary failures retry on their own, and anything that still will not publish is flagged in the sidebar straight away, with the platform's reason in plain words and the post ready to fix and requeue. If the account needs reconnecting, Maeve says so instead of retrying into the same wall.
If your team runs Claude, Codex, or Cursor, Maeve's MCP server lets an agent read the calendar, draft posts, schedule them, and pick up failures. The connection is granted the workspaces you choose, so an agent helping the bakery cannot read the skincare brand, writing needs an editor or admin role, and anything that publishes or deletes has to send an explicit confirmation before it runs. Every tool call is logged with who ran it and what it touched.
The whole product, with the multi-client layer over the top of it.
All eight sit on the same calendar, and each one keeps its own caption, media, and posting options inside the post.
The agency workspace is the same product the rest of Maeve runs on. A post moves from a brief to a draft to client review to the calendar to a report without ever leaving the workspace it belongs to.
Yes. Each client gets its own workspace, and the calendar, drafts, connected accounts, labels, and analytics all live inside it, and you switch between them from the sidebar on a single login. If you click into the wrong client the calendar is empty, because there is nothing of anyone else's in there.
No. You send a batch of drafts as one link. The client opens it on their phone, scrolls through the posts the way they will look once published, and approves, requests changes, comments, or reacts. There is no login screen for them or for their team.
Yes. Set the post to internal and then client, and your team approves it first before the same draft moves into the client review batch, so the client only sees the version your account manager has already checked.
You generate a connection link inside their workspace and send it over, choosing which platforms the link offers. They tap through the platform login screens on their own phone, and the connection lands in your sidebar ready to publish against. The link expires, you can revoke it, and no password ever changes hands.
Yes. Roles are set per workspace, so the same person can be a manager on one client, an editor on the next, and a viewer on a third. The four roles are manager, editor, creator, and viewer.
No, and that is on purpose. Each workspace has its own labels, pillars, formats, and hashtag groups, so renaming one client's launch label leaves the others alone, and adding a pillar for one client does not show up in the rest.
Yes. Pick the date range and export a PDF with your agency name on the cover, engagement, reach, follower growth, and top posts, and audience demographics on Instagram, Facebook, and YouTube, which are the platforms that hand that data over. You can also total across several accounts of the same platform.
Eight: Instagram, Facebook, LinkedIn, TikTok, YouTube, X, Pinterest, and Threads, with carousels, Reels, Stories, video Pins, Shorts, and threads where the platform supports them.
Yes. An MCP connection is granted access to the workspaces you choose, so an agent working in one client's workspace cannot read another. Reading is open once you grant it, writing needs an editor or admin role, and anything that publishes or deletes has to send an explicit confirmation before it runs.
It lands in the failed posts queue and is flagged in the sidebar as soon as it happens. You see what the platform said, fix the post or reconnect the account, pick a new time, and put it back in the queue, without raising a support ticket or losing the slot.
A freelancer with a couple of clients can run on Basic. The agency-shaped features, which are team roles, internal approvals, and client review workflows, sit on Standard, and Premium removes the workspace and connection caps. The pricing page has the current numbers.
Not yet. Comments and direct messages come in from Instagram, Facebook, and Threads today, with the post they are reacting to beside the conversation. The other five platforms publish through Maeve, and their replies still live in their own apps.
These are free and you do not need an account to use them.