Roadmap

What is coming, and what is not

Munshi Social, the AI content marketing engine for small teams, is built by a small team in public. This page is the plan as it stands; the changelog is the record of what actually shipped, and the two are kept in step.

Updated with the changelog, weekly

Building now

In progress this month. Each moves to the changelog the day it ships.

  • Generation that learns from your results

    Content pipelines that read what actually performed and let it shape what they propose next, instead of treating every piece as the first one.

  • Publishing directly to YouTube

    The connection is built and waiting on YouTube's API review before it can be switched on.

Thinking about

Real requests, no date. Ask on the contact page or in Discord and it moves up.

  • A third seat, and roles

    A workspace has two seats and no role hierarchy today. Teams of three have asked, and a reviewer role that can approve but not publish is the shape we are considering.

  • More blog platforms

    HubSpot, Wix and Shopify blogs come up most often. Each one is added when a customer needs it, so tell us on the contact page if that is you.

  • An API and an MCP server

    So your own scripts, or your own AI assistant, can read your calendar and queue drafts for approval. Designed and prototyped; it ships when enough customers ask.

  • A full year of results history

    Results today cover the recent past in detail. Keeping a full year per channel, so this September can be read against last September, is the plan.

Not doing

Decided against, on purpose, so you can plan around it.

  • Publishing without a human approval

    Nothing goes out that you have not seen. Autopilot content is how brands end up apologising, and no amount of demand will change this one.

  • Lifetime deals

    Founding members keep their price for life, which is a different promise from a one-off payment for a product that has to keep running servers.

  • Billing that hides the cancel button

    Cancelling is one click in the billing portal, and a first payment carries a seven day money back guarantee. No retention flow, no emails to write.

The receipt

Shipped most recently

The newest features from the changelog, so the lanes above can be read against the pace things actually move at.

  • Take your strategy out, and bring an answer back

    Blog strategy now exports three ways: copy it for whichever AI you already work with and paste the reply straight back in, save a branded PDF to share with a client, or keep the file itself. Importing also works as a way to start a strategy from scratch.

  • The whole app works on a phone

    Every screen now has a phone layout: a top bar and a bottom bar in the order you work, Home leading with the verdict, Calendar opening on the week, Results tables reading as cards, and the composer and Settings as full screen sheets. Tablets have a layout of their own between the two. The desktop layout is unchanged.

  • The workspace keeps its own clock

    Settings now carries a timezone for the workspace, and it governs when a scheduled post goes out. Two teammates in different countries therefore mean the same moment by nine in the morning. Left unset, Munshi continues to follow the browser as before.

  • Report on any period up to a year back

    Results is no longer fixed to the last 7, 30 or 90 days. Pick the day a window starts on and every card, chart and export on the page reads the same stretch of time.

  • A branded cover for every blog post

    Munshi now draws a cover image for each article from your workspace colors, logo and font, so nothing publishes without one. Settings holds the brand kit behind it, read from your website when you connect it, with a sample cover showing where each color lands.

  • Enterprise on the pricing page

    Past Studio the plan is shaped in a conversation, and the pricing row now says so. A third card sits beside the two you can buy with a card and leads to a call rather than a checkout.

The full list, with fixes and improvements: changelog · RSS

Shape it

The order is set by who asks

Everything in the Thinking about lane is there because a customer asked. If one of them matters to your business, say so on the contact page or in the Discord. A builder reads every message.