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.
0 — No publishing or scheduling; the product is a listening, analytics or inbox tool only.
3 — Posts scheduled to several networks from one composer, with a list or calendar of what is planned.
5 — A content calendar with scheduling across the main networks, per-network text and media variants, drafts, and post previews.
8 — Bulk upload or CSV import, queue or evergreen scheduling, best-time suggestions, link shortening with UTM tags, stories, reels or shorts where the API allows, and failure notifications with a retry.
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 Skeptic
Seven networks including Pinterest, direct publishing named for six of them, a content calendar with previews and drafts, best times drawn from the account's own previous performance, UTM-tagged bit.ly links and Instagram stories, reels and carousels — that is a real publishing surface. What I hunted for and did not find is the failure story: we found no public information on failure notifications, retry, bulk import or queue scheduling, and I have seen what a silent queue costs the morning a platform changes something. 3 4