A calendar by day and week
Posts show by day, coloured by state and platform. States run from idea and draft through approved and scheduled to published, with error and manual states for posts a person finishes.

A calendar of posts by day, a composer per channel and an approval step for the people who must say yes. Publishing to the platforms is still being built, so drafts stay drafts for now.

Floating cards and figures are examples on sample data, not a customer account.
Sample data, fictional brand. This is how Social shows a figure: the value, where it came from, the formula behind it and when it was last updated.
Rule: every number shows its source, formula and update time. A missing source reads "not measured", never 0.
One of four areas of the product, sharing the same client record, roles and log.
Posts show by day, coloured by state and platform. States run from idea and draft through approved and scheduled to published, with error and manual states for posts a person finishes.

X takes a post or a thread. Reddit takes a title and text or link for manual posting. Facebook pages, LinkedIn, Google Business Profile and Telegram take a text post, saved as a draft.
A channel can require approval before scheduling, and only owner, admin or client approver roles can approve. Posts should claim only facts recorded for the brand.
Follow public competitor profiles on Instagram, Facebook, X and Reddit. This is reading only, and it depends on the data providers being configured.
Connections start read-only. Writing is switched on per account, only after you grant the rights.
Lines draw as you scroll. Platforms on the left are read-only first, Social sits on the one client record, and each output keeps its receipt.
Sources are read first, the numbers are stored once per client, and every output shows its source, formula and update time.
The same four moves apply to every module in this area.
From first connection to the number a client sees.




Choose the platform and enter its account identifier. Account connection by sign-in (OAuth) is planned, not built.

Write it in the composer and see a preview with character counts.

The approver sees the exact text and time, and approves or rejects it.

Automatic scheduling and publishing are planned. Today a post is saved as a draft, and Reddit posts are marked as posted by hand.

Photos are stock images that show the kind of business this is built for. They are examples, not customers.




Stock photos and example labels, not customers.
Connections are read-only first and go live only after the platform access is approved.
Built: the connector exists in the product and goes live per account once access is granted. Planned: not built yet.
No single tool replaces this module; it connects work that is usually split across several.
Modules that share this client record, these roles and this log.
The composer covers X, Reddit, Facebook pages, LinkedIn, Google Business Profile and Telegram. Today posts are saved as drafts, and automatic publishing is planned.
No. Nothing publishes at all yet. When publishing arrives, a channel set to require approval will hold each post until an approver says yes.
Yes, with a client approver role. They see only their own brand, and another client's data returns not found.
Not yet. An AI content studio for post text and images is planned and is not built. The sample copy in the composer comes from templates, not a model.
We open one agency at a time, with your own accounts connected read-only first.