The social scheduling market, and the gap we're building into.
From a 29-agent research sweep: 36 competitor teardowns, revenue figures re-verified against primary sources, and a read on the agent-native landscape. The short version is below; the full report lives in docs/MARKET-RESEARCH-2026-06.md.
The market is big and barbell-shaped
$25–29B in 2024/25, growing 17–23% a year. Two enterprise giants, a healthy bootstrapped middle, and a fast indie tail — and the low end is not saturated: solo founders still reach $70K+ MRR.
“Agent-first” is no longer an open lane
It's the fastest-growing contested one. Postiz markets “autopilot with AI agents” and 5×'d its MRR after the pivot. Buffer, Vista Social, Typefully and Simplified all ship MCP servers.
The open wedge is trustworthy agent automation
Nobody combines agents-propose/humans-approve + anti-fabrication brand context + analytics-grounded briefs. Postiz has no approval workflow; the API players have none by design.
The agentic pivot is the best-documented growth lever
Postiz $21K→$113K MRR in months. Post Bridge $0→$41K MRR on an /agents wedge. The direction is validated — the differentiation just has to be sharper than “works with Claude.”
Everyone is racing right or sitting top-left. The top-right is open.
Two axes that actually separate the field: who drives the tool, and how much human control survives. Agent-driven with real governance is empty — that's the Skedlark quadrant.
Skedlark's wedge: agent-driven like Postiz, but with the approval queue, scoped permissions, and anti-fabrication brand context none of them ship. The #1 buyer objection — “can I trust an AI to post as me?” — is our positioning.
Three rings compete for “the scheduler AI uses.”
Incumbents bolting on MCP
A send button for agents on a human dashboard.
The gap: MCP is a feature, not a workflow. No capture→brief→approve loop.
Agent-native apps
Racing to “autopilot.” Our direct competitors.
The gap: Autopilot with no brakes: Postiz ships no approvals — a top user complaint.
Agent infrastructure
Raw APIs that commoditize publishing.
The gap: No product: no calendar, approvals, briefs, or brand context.
The money, re-checked against primary sources.
Barbell market: two giants, a healthy bootstrapped middle, a fast indie tail. The only Stripe-verified scheduler numbers anywhere are the two agent-positioned indies — Postiz and Post Bridge — and they're the fastest growers.
| Company | Figure | Tier | Confidence | Note |
|---|---|---|---|---|
| Sprout Social | $457.5M FY25 revenue | enterprise | High | public 10-K; net loss $43M |
| Hootsuite | ~$350–400M ARR | enterprise | Medium | CEO-stated; private |
| Later | $250M Mavely buy · $2.4B GMV | enterprise | High | GMV ≠ revenue |
| Buffer | $25.2M ARR · $2.10M MRR | middle | High | live open dashboard |
| Agorapulse | ~$24M ARR | middle | Medium | acquired Mention |
| Metricool | €15.3M revenue FY24 | middle | High | team.blue majority |
| Publer | $3.3M ARR | middle | Medium | bootstrapped, +70% YoY |
| ContentStudio | $2.9M ARR | middle | Medium | ships MCP + API |
| Typefully | $1.6M ARR | middle | Medium | team of <10 |
| Postiz | $1.3M ARR · $141K MRR | indie | High | Stripe-verified · 5×'d after agent pivot |
| Pallyy | $74K MRR | indie | Medium | solo, ~95% SEO |
| Post Bridge | $41K MRR | indie | High | Stripe-verified · /agents wedge |
What their users complain about — our copy ammunition.
Buffer
Trustpilot 2.1Shallow analytics — “can't prove ROI”; per-channel cost creep.
Hootsuite
Trustpilot ~1.5Killed the free plan; $99+/user; reviewers name cheaper escapes.
Later
Trustpilot 1.3Surprise charges, cancellation friction; removed X scheduling mid-sub.
Loomly
Bending SpoonsStarter repriced to $65/mo; post-acquisition layoffs & churn.
Postiz
G2 / TrustpilotNo approvals, basic analytics, IG connection reliability.
AI writers
—“Generic, template-y output” — the #1 complaint against Taplio-class tools.
Full teardowns, sources, and the site plan
All 36 competitor profiles (with exact hero copy and landing structures), the adversarial revenue verification, EU/GDPR page requirements, and the complete build plan are in the repo: