Product Roadmap: What We Are Building Next
Updated · Multi Post Social guide
This roadmap shows what has shipped, what is being built now and what is planned across every module of Multi Post Social. It is a statement of intent, not a promise: items move when networks change their rules, when something turns out harder than expected, or when many customers ask for something else first. Shipped items also appear on the changelog.
Roadmap by module
| Module | Shipped | In progress | Planned |
|---|---|---|---|
| Publish | Composer, queue, calendar, reminders, threads, first comment, hashtag groups | Keyboard-accessible reschedule; evergreen repeat rules | Bulk CSV upload on Team plans; post templates inside the composer |
| Create | Ideas board, tags, idea to post | Media library with reuse across posts | Shared idea boards across workspaces |
| AI Assistant | Captions, rewrites, hashtags, repurposing | Brand voice profiles learned from past posts | Image alt-text drafts; caption translation |
| Engage | Unified inbox, labels, saved replies, AI suggestions | Assignment rules and routing | Review responses for Google Business Profile; inbox analytics |
| Analyze | Overview, per-channel, best time, reports | Chart data as tables; scheduled report emails | Competitor benchmarks; link-click attribution by campaign |
| Listen | Streams, sentiment, alerts | Longer history on higher plans | Trend detection; share of voice per competitor |
| Collaborate | Roles, approvals, notes, client links, workspaces | Pause all queues for an organization | Audit log export; two-step approvals |
| Start Page | Builder, themes, buttons, latest posts, clicks | Custom domain for start pages | Email capture block; scheduling link block |
| Platform | Web app, settings, 2FA, API, webhooks, MCP | Server-side accounts replacing the browser demo; native iOS and Android apps | SSO (SAML), audit logs, custom retention for Enterprise; browser extension |
| Channels | 12 networks | Instagram collaborative posts | New networks when their public APIs allow scheduling |
How to request a feature
Email [email protected] with what you are trying to do, how you do it today and how often it comes up. Describe the problem rather than the button you imagine; the best solution is often different from the first idea. Requests are grouped by problem and counted, and the count is one of three inputs to this roadmap, with network changes and security work as the other two. We reply to every request and tell you when something you asked for ships.
A note on dates
We do not publish dates for planned items because they move, and a missed date costs more trust than a vague one. In progress means engineers are working on it now and it usually ships within a few weeks. Planned means it is agreed and sequenced. If an item disappears from this page, the changelog either shows it shipped or a note explains why it was dropped.