Publishing & calendar
How this is scored
Scheduling across networks: per-network formatting, the calendar as a working surface, bulk operations, and what happens when a post fails at 3am.
0 — One post to several networks at once with no per-network variation and no calendar.
3 — A calendar with scheduling and basic per-network text variants; failures are discovered by noticing the post never appeared.
5 — Per-network content, media and first-comment variants, drafts, a usable calendar with drag-and-drop, and failure notifications with a retry.
8 — Bulk upload and CSV import, evergreen or queue-based scheduling, link shortening with UTM rules, preview matching each network's actual rendering, and stories, reels or shorts supported where the API allows.
10 — Publishing is dependable at volume: hundreds of scheduled items across many accounts without collision, best-time recommendations from the account's own history, and every failure surfaced with the platform error and a one-click recovery.
The Community Manager
Scheduling across eleven channels with real per-network touches is well evidenced — threads on X, Bluesky, Threads and Mastodon, a scheduled first comment on Instagram, Facebook or LinkedIn, queue refills, tags and ideas, plus phone reminders for Instagram, TikTok and YouTube where direct publishing is limited. What decided the score against it: we found no public information on the calendar as a working surface, previews, bulk upload or CSV import, and nothing on failure notifications or a retry — the 3am silence is exactly the gap. 2 1 4