Dispatch schedules and publishes LinkedIn posts for agencies and in-house teams. What makes it different is what travels with the post: the figure, the publisher, the date, the sentence it was taken from — and a check that keeps running after the post is live.
We took apart 35 tools before writing a line: 16 social suites and 19 LinkedIn-specific products. Not one attaches a source to a claim. Their approval workflows approve copy. Nobody approves the evidence.
The demonstration account, rendered exactly as Dispatch renders it. The figures and the flag are seeded demo data, not a claim about any quarter.
Three things happen to a post here that happen nowhere else. The rest — calendar, queue, approvals, client links, analytics — works the way you already expect it to.
Sources are gathered and read first: publisher, title, date of publication and the exact sentence a figure came from. The post is written against them, not decorated with them afterwards.
A figure in the body with nothing behind it is flagged before anyone is asked to sign off. Approval needs a named person and is bound to a fingerprint of the exact text — edit an approved post and the approval falls away, including when the edit puts the words back.
Cited pages are re-fetched on a schedule and compared with the sentence recorded at the time. When a page changes, the live post resting on it is named, with the old figure, the new one and the date of the check.
Every feature we expected to find, we found: white-label domains, multi-stage approvals, no-login client review, scheduled first comments, bulk import, best time to post. Most of what a scheduler does is table stakes and we say so. Then there is this.
| Capability | 16 social suites | 19 LinkedIn tools | Dispatch |
|---|---|---|---|
| A research step before writing | none | none | yes |
| A citation attached to a claim | none | none | yes |
| Verification of a statistic | none | none | yes |
| A currency check — this figure was superseded | none | none | yes |
| A check the cited page still says it | none | none | yes |
| A claim-level risk flag: opinion or evidence | none | none | yes |
| Slop detection — while all 35 ship AI generators | none | none | yes |
XONIK teardown, September 2026: 35 products checked feature by feature — 16 social management suites and 19 LinkedIn-specific tools. Every row above was absent from all of them.
In July 2026 LinkedIn discontinued its own “enhance your post” AI writer and shipped a proofreader in its place, beside a reader-facing “seems like AI slop” control — over a million uses in three weeks, and roughly 40% fewer views on the posts it flags. The platform moved from generation to assistance. Thirty-five third-party products did not.
In agency retainers scheduling takes one to two hours of a seventeen to twenty-eight hour month; research and content take ten to fifteen. And clients who leave name delivery and value, not price — while three quarters of agencies believe they left over budget. A tool should defend the ten hours, not automate the one.
Photographed against the demonstration account while it was running.





Ten client brands in one account, each isolated: its own destinations, voice, sources and media, with nothing shared by accident. A monthly report that shows the work rather than describing it.
One brand, its page and its founder's profile. Sign-off sits with a named person. When a board, a customer or a regulator asks where a figure came from, the answer is one click and it is dated.
Opens a link, sees the post as it will appear with its sources underneath, approves it or sends it back with a reason. No account, no password, no seat to pay for.
Limits are counted per account rather than per brand, enforced by the software, and refunded when a scheduled post fails.
The application and the evidence layer, proved by automated checks that include the panels driven in a real browser.
The LinkedIn application: one developer application, verified against the company page.
Development tier while under review — 500 calls a day for the application, 100 per member. The software budgets for that tier rather than the one after it.
No scraping, no automated connection requests, no automated messages, no scraped lead database.
No customer results, case studies or ROI figures. There are none yet, and a product about evidence cannot open with an unsourced number.
No. Composing, sources, evidence, approvals, client review links and reports all work today. Publishing is the one part that waits for LinkedIn to approve the application.
Dispatch re-fetches the page on a schedule and compares it with the sentence recorded at the time. When it differs, the live post resting on it is named, with the old figure, the new one and the date of the check. It flags; it never edits or deletes a published post.
No. They open a signed, expiring link scoped to one brand, see the post as it will appear with its sources underneath, and approve it or send it back with a reason.
No. Every row carries the brand it belongs to and every query is filtered by it. Cross-account reads are the failure most likely to end a company, so isolation is proved by a dedicated suite of automated checks rather than by convention.
Never without an approval carrying a name. Approval is bound to a fingerprint of the exact text, so editing an approved post drops the approval — including when the edit puts the words back.
No. Official API only. No scraping, no automated connection requests, no automated messages, and no scraped database of people.
Plans run from a free trial to an agency plan. Limits are counted per account rather than per brand, enforced by the software, and refunded when a scheduled post fails.
You do. Research briefs and drafts are assembled with the help of a language model, and everything generated is labelled as such and waits for a person to approve it.
The trial takes an email address and posts five times. If the evidence layer is not worth it by the fifth post, nothing has been spent.