An agent can only act on what it can see
Why Unitive has more surfaces than a publishing tool needs, and why that is a precondition for the agent rather than the thing being sold.
There is an obvious way to add AI to a social media tool. Put a button in the composer that writes a caption. It demos well and it takes about a week.
It also runs into a wall almost immediately, and the wall is not the model.
The wall
Ask that caption button to do something slightly larger. Plan next week. It cannot, because it does not know which campaign is running. Tell it to use the approved photo. It cannot, because the asset library is a different product. Ask why last month's posts did better. It cannot, because the numbers live somewhere else again.
An agent can only act on what it can see. Everything outside its view is a thing you still do by hand, which means the agent is not doing the job. It is doing one step of the job and handing the rest back.
Which is why Unitive looks the way it does
Unitive has more surfaces than a publishing tool needs. Publishing, an asset library, projects, docs, review, messaging. From outside that reads like scope creep, and I understand why.
It is not the value proposition. Nobody is going to buy Unitive for the whiteboard.
The modules are there because they are the agent's field of view. When the brief lives in Docs, the task lives in Projects, the asset lives in the library and the sign-off lives in Review, the agent can follow a campaign from the idea to the published post and know what it is looking at the whole way. The same plan item id is threaded through all of it, so the connection is a real reference rather than the model guessing from context.
That is the bet. Owning the surfaces is the precondition for the agent being useful, not the thing being sold.
The honest version of the cost
It is a lot to build, and I am building it on my own.
Two of the surfaces are optional and I will not pretend otherwise. Whiteboards and RSS are genuinely useful to some teams and ignorable for everyone else. The other eight serve one workflow and those are the ones that matter.
It also means Unitive is not trying to replace Slack. The messaging here is for having a conversation with a thing attached to it: a post, an asset, a task. Keep Slack.
What it buys you
When this works, the agent stops asking you for context you already gave it somewhere else in the same product. That is the whole difference between a tool that writes captions and one you can hand a week to.