Features
One page per piece of the product: what it solves, who uses it and where it stops.
Features
The networks we connect, and what each one can do
Roles and permissions: who can see and do what
How a role is built out of per module permissions, and why the plan and the role answer two different questions.
Workspaces, brands and clients: how it is all organised
The hierarchy of the product on one page: what a workspace is, what a brand is, and when a client appears at all.
Branding: your name in front of ours
What exactly can carry your branding, where a client sees it, and which part of it is bought separately as a domain.
Claude and ChatGPT inside your workspace: what MCP is
What the MCP protocol is, what your assistant can do inside the workspace, and exactly where its permission stops.
Tasks, chat and Drive: the work next to the content
How the board, the chat, the procedures and the files sit beside the content calendar of every brand you run.
Client portal: what a client sees when they sign in
The whole path a client walks inside their portal, and the four things they can do there without calling you.
Scheduling: Google Calendar both ways, and a booking link
How the calendar syncs in both directions, what somebody booking time with you sees, and which calendars are left out.
Approvals: your team or the client, and one yes is enough
Who can say yes, who sees what, and what happens when somebody asks for changes.
Inbox: messages, comments and reviews in a single thread
What lands in the inbox, what you can answer from it, and why a Google review is a case of its own.
CRM: deals and contacts next to the brands you already run
A CRM that lives in the same place as the work, and the three things it deliberately does not do.
Reports: what a report measures and what its reader decides
The numbers each network sends, the ones that do not exist, and how to read a monthly report honestly.
Ads: Meta, Google, LinkedIn, TikTok and Pinterest in one dashboard
What each platform sends into a single dashboard, and why Google behaves differently from the other four.
Quotes, contracts and invoices with your series and your VAT
The road that runs from a brief to an invoice, with the numbering series, the eight VAT regimes and the withholding.
Bio: one link page per brand, with your own numbers
How a brand link page is put together, what gets measured on it, and exactly what the Pro version adds.
Cross posting from one network to another without uploading twice
A standing rule that carries what you already posted on one account to another, in the format the destination accepts.
Auto DM: from a comment to a conversation, step by step
The three triggers behind an automation, how the follow gets asked for, and what is measured after the send.
Calendar and publishing: one piece, fourteen networks
How a month of content gets planned brand by brand, and what changes network by network when it goes out.
One page per piece
Every module has its own: the problem it solves, who can switch it on given their plan and their profile, and the steps it really takes when you use it. They are written from the code that runs them, not from a competitor's feature list.
They serve two different moments: deciding before you buy, and checking afterwards, when you are already inside and want to know whether something is possible without opening a support chat.
The limits are written down too
Each page says where the piece stops: which formats a network accepts, what cannot be edited once it is published, what needs a permission you may not have. A limit you discover on a Tuesday afternoon costs far more than a limit you read before you paid.
Fourteen days to decide
Connect one account and schedule a week. If it does not fit, cancel before day 15 and pay nothing.