Distribution workload · October 2026 findings
Cross-platform publishing: budget beyond the source post
Nearly a quarter of eligible source posts reached multiple platforms, and delivery work exceeds the source-post count.
Source: Postly Research. Anonymized retained publishing data: 72,883 documents inspected; 47,388 posts with verified publications; 165,158 deduplicated destination deliveries; 3,645 destination accounts. Observation cutoff: 2026-10-04 22:35:49 UTC.
Download this complete report ↓Distribution workload
Cross-platform publishing: budget beyond the source post
Nearly a quarter of eligible source posts reached multiple platforms, and delivery work exceeds the source-post count.
Retained eligible publications up to October 4, 2026; October is partial.
The finding
11,186 of 47,388 eligible source posts reached multiple platforms (23.6%). The remaining 36,202 reached one platform. Across the complete sample there were 3.5 deliveries per eligible source post on average. Recurrence and multiple destination accounts also contribute to that ratio, so it is not the average number of platforms.
Each eligible source document counted once, classified by distinct platforms with accepted receipts. Multiple accounts on one platform remain one platform.
| Observed group | source posts | Accounts |
|---|---|---|
| One platform | 36,202 | 2,309 |
| Multiple platforms | 11,186 | 1,922 |
At least 30 accounts and 100 observations per displayed group. Account counts overlap. Small groups are withheld; absence from this table does not mean zero usage.
What this means for teams
A calendar measured only in source posts understates the delivery workload. Every additional destination creates adaptation, verification and response tasks even when the creative is reused. The observed multi-platform group is large enough to make a destination checklist useful, while the larger single-platform group shows that cross-posting should not be assumed to be universal.
Recommended actions
Give each campaign a source brief and a destination matrix. For each destination, record the audience question, placement, adapted opening, link, owner and success measure. Reuse the core idea but check the audience action separately. Before adding another platform, estimate the time to prepare, verify and respond there, then compare incremental qualified outcomes with that time cost.
What this cannot establish
More destinations do not demonstrate more growth, incremental reach or better return on effort. The same people may see several versions, and recurring publications can increase delivery counts without increasing creative variety. Product-specific channel rankings require validated product categories and linked outcomes, neither of which is established by the source-post distribution.
Source and counting rules
The census reads retained Postly production records in bounded batches from a database secondary. Receipts require platform, destination account, publication identifier and timestamp. TikTok also requires confirmed success. Repeated provider identifiers are counted once per destination. This is a live retained-data census, not a random sample or an atomic snapshot. Deleted records and publishing outside Postly are absent. Small groups are withheld: every displayed row requires at least 30 destination accounts and 100 observations. Accounts are not necessarily independent businesses; their counts overlap between rows.
Citation: Postly Research, Cross-platform publishing: budget beyond the source post, October 2026.