P

PostHub

Waking up your workspace

All use cases
Use case

In-house marketing teams

A shared pipeline where drafts, sign-off, the calendar and the numbers live in the same workspace instead of four tools.

Who this is for

Marketing teams of two to twenty-five who plan campaigns together and need someone accountable for sign-off.

Team publishing breaks in two places: nobody knows what is scheduled, and nobody knows who approved what. Both are structural — a shared calendar answers the first, a named approver with a decision history answers the second.

Honest caveats

  • Seats are 5 (Starter), 10 (Professional) or 25 (Agency) — the plan decides how many people can be invited.
  • AI assistance is a paid-plan feature with a daily allowance per seat; it is off during the trial.
  • No SSO. Two-factor authentication via TOTP is available on the account.
  • Analytics have no CSV/PDF export; pull numbers through the API if you need them elsewhere.

The workflow, step by step

  1. 01Write

    One composer, shared conventions

    Everyone drafts in the same composer with the same per-network previews, so a post looks the same in review as it will on the network. Labels keep campaigns findable and groups keep brands and timezones separated inside one workspace.

  2. 02Schedule

    The calendar is the plan of record

    Month, week and list views over the same scheduled posts, colour-coded per brand. If it is not on the calendar, it is not agreed — which removes the weekly “what is going out?” thread.

  3. 03Approve

    Strict workflow, real roles, an audit trail

    Set the workspace to strict and only an approver or admin can release a post. Five roles — owner, admin, editor, approver, viewer — plus optional lock-on-approval and per-group overrides. The approvals desk keeps pending and history feeds so a decision can be traced back to a person.

  4. 04Publish

    Same clock, fifteen networks

    The scheduler ticks every 60 seconds and publishes through each network’s official API, respecting per-network rate limits. Failed posts surface in the inbox with the platform’s own error, so remediation is a queue rather than a scramble.

  5. 05Measure

    Numbers with a known provenance

    Metrics are read back from each network’s API into per-post snapshots and kept for 90 days. Because unreported metrics stay null instead of zero, an executive summary built on this data cannot silently overstate a channel.

Every claim on this page is checked against the product

The fact sheet has the verified numbers, and the comparison pages put them next to the alternatives — without invented checkmarks.