Features
Everything a publishing week needs. Nothing it doesn’t.
This is deliberately one product rather than a suite. Each capability below exists because a real step in the week was happening somewhere else — in a spreadsheet, a chat thread, or six browser tabs.
01 — AI assistant
Something to react to, faster than a blank page
The hardest part of a content week is rarely the editing — it is the starting. The assistant produces a first version from a short brief, so the work begins with a paragraph to argue with rather than an empty field.
It also works on copy you already have: alternate phrasings of a line, a shorter version that fits a tighter limit, or the same idea rewritten for a different network’s conventions.
- Draft from a brief
- Describe the post; edit what comes back like any other draft.
- Alternates
- Several phrasings of the same line, to choose between rather than accept.
- Repurpose
- Turn one post into a version that suits another network.
- Always reviewed
- Suggestions never publish themselves — a person approves every post.
02 — Content creation
One composer, one media library
Write the post once and shape it per network in the same place. Images and video are uploaded to a shared library rather than re-attached each time, so the same asset can appear in several posts without being uploaded again.
Drafts stay in the workspace where the rest of the team can see them, which is what makes a review step possible at all.
- Per-network variants of a single post
- Media uploaded once and reused anywhere
- Drafts and reusable templates kept in the workspace
- Everything visible to the team, not to one person
03 — Content optimisation
Catch the network’s rules before the network does
Every network has its own limits — length, how many images, which media types, what a link preview will do. Pheonix Solutions checks a post against the rules of each network you have selected while you are still writing it.
The point is not to score your writing. It is to stop a post failing at publish time for a reason that was knowable an hour earlier.
- Per-network checks
- Limits and format rules applied as you compose.
- Media validation
- Flags a file a network will not accept before it is queued.
- Preview
- See roughly how the post will sit on each network.
The point
A tool should fit the loop a team already runs.
A social team’s week is not really a list of posts. It is a loop: decide what the period needs, make it, get it agreed, send it out, deal with the response, then look at what happened and decide again.
Every feature on this page sits somewhere on that loop. None of them are there to be counted on a comparison table.
04 — Scheduling
A calendar you plan in, not a list you tick off
Content is planned against dates rather than against a backlog. The calendar shows what is scheduled, what is still a draft and what is waiting on someone — for every connected account at once.
Queues handle the repetitive half: set the times each network should post at, and new content takes the next free slot instead of needing a time chosen by hand.
- Calendar
- Every account and every state in a single grid.
- Queues
- Posting times defined once per network.
- Move freely
- Reschedule a post, a day or a week without rebuilding anything.
- Time zones
- Schedule against the audience’s clock, not the office’s.
05 — Publishing
It goes out whether or not anyone is awake
Approved content publishes to each connected account at its scheduled time through the networks’ official APIs. There is no browser extension to keep open and no phone reminder at an awkward hour.
When a network rejects something — an expired connection, a media type it has stopped accepting — the post is reported as failed with the reason, rather than disappearing quietly.
- Official APIs
- Publishing through each network’s supported integration.
- Status you can see
- Published, scheduled, failed — with the reason attached.
- Reconnect prompts
- Expiring account connections are surfaced before they break.
06 — Analytics
Comparison, rather than a scoreboard
A number on its own means very little. Pheonix Solutions reports content performance and account performance together, over a period you choose, so a format can be compared against another format and a month against the month before it.
Reports can be pulled for a period and handed to someone who was not part of the work — which is usually the actual reason anyone opens analytics.
- Content performance
- How individual posts and formats did across accounts.
- Account performance
- Audience and activity trends per network.
- Cross-network view
- All six networks on one timeline, where the data allows it.
- Honest gaps
- Metrics a network does not expose are marked unavailable, not estimated.
07 — Engagement
The conversation, next to what started it
Comments and messages from connected accounts arrive in one queue rather than in whichever app someone happens to open. Replies go back out from the same place.
Because the conversation sits beside the post that prompted it, whoever answers can see what was published, when, and what else is going out that day — which is most of the context a good reply needs.
- One queue across connected accounts
- The originating post shown alongside the reply
- Shared visibility, so nothing is answered twice
08 — Team collaboration
More than one person, without more than one copy
Work happens in shared workspaces — one per brand or client — each with its own calendar, accounts and team. Roles decide who writes, who approves and who can publish, so the final say does not have to come with the credentials.
Review happens on the post itself rather than in a separate thread, and approved content keeps the slot it was already given. There is no copy-paste step between the approval and the schedule.
- Workspaces
- Separate brands or clients, cleanly divided.
- Roles
- Publishing rights granted deliberately, not by sharing a login.
- Review step
- Require an approval before anything reaches a network.
- Feedback in place
- Comments attached to the draft they are about.
09 — Automation
The parts that repeat should only be decided once
A lot of a social week is not creative work — it is placing things in slots, re-running something that worked, and moving an item from one list to another because it was approved.
Pheonix Solutions takes those decisions once. Queues place content automatically, evergreen posts can be scheduled again without being rebuilt, and approved work moves to scheduled on its own.
- Posting times set once per network, then applied
- Evergreen content rescheduled with its media and variants intact
- Approved posts move to the schedule without a manual handoff
- One record of what is going out, rather than a second list to maintain
10 — Integrations
Connected to the networks, open to your stack
The integrations that matter most are the six network connections themselves — each one authorised properly, through the network’s own process, and re-authorised before it lapses.
Beyond that, the workspace is hosted and operated by us rather than by a third party, which means the way it fits alongside the rest of your systems is a conversation rather than a fixed list.
- Network connections
- Authorised per account through each network’s official flow.
- Managed hosting
- Run and maintained by Pheonix Solutions.
- Fits your setup
- Tell us what it needs to talk to and we will scope it with you.
Platforms
What this looks like per network
The capabilities above are the same everywhere. What changes is the formats each network supports and how much it lets any tool do — which is what the platform pages go into.
FAQ
Questions, answered
Is every feature available on every plan?
Yes. This is one product, not three tiers of one. All three plans carry the same capabilities. What differs between them is the scale of use each covers — accounts, workspaces and seats — which is sized with your team before you start.
Does the same post have to look identical on every network?
No. You can write once and then adjust the version for each network in the same composer — different lengths, different media, different framing — without maintaining separate drafts.
Where do the analytics numbers come from?
From the networks themselves, through their official APIs. Each network exposes a different set of metrics, so a figure that a network does not publish is shown as unavailable rather than estimated.
Can we restrict who is able to publish?
Yes. Roles separate writing from approving and publishing, so contributors can prepare content without having the rights — or the credentials — to send it live.
Is there programmatic access?
The workspace is built to be integrated with rather than worked around. If you need content created or reported on from another system, talk to us about what that would involve for your setup.
See it against your own calendar.
The quickest way to judge any of this is with your accounts and your content in front of you. Talk to Pheonix Solutions and we will set that up.