Built by an agency, for agencies

Why this exists

Running social media for other businesses is mostly not the posting. It is the back-and-forth: a caption in an email, a revision over WhatsApp, an image in a shared drive, a client who approved "the one with the blue background" and a designer who has three of those.

Then something goes out that the client says they never signed off on, and nobody can prove otherwise. That conversation is expensive, and it is entirely avoidable.

So approval is the centre of this product rather than a feature bolted onto a scheduler. Nothing publishes without an approval, the approval is a record rather than a message, and resubmitting after changes starts a new round so an old approval can never be mistaken for a new one.

How we build

Three commitments, which we would rather be judged against than described by:

• Official APIs only. No scraping, no browser automation, no unofficial endpoints. If a platform does not allow something, we say so on the platform page instead of routing around it and putting your clients' accounts at risk.
• Say what is true. A TikTok post that landed privately is not labelled published. A platform still in review is not shown as available. An integration we have not finished is visibly not finished.
• Treat access as the crown jewels. The tokens your clients grant you are the highest-value thing in the system, and they are handled accordingly - the detail is here.

Where we are

Socio Pulse is in early access. The workflow - client workspaces, approvals, media, the composer and the calendar - is built and working. Automatic publishing is built and tested, and is waiting on each platform to approve our application, which is their timeline rather than ours.

We would rather tell you that than imply otherwise and disappoint you in week two.