Tool selection usually starts in the wrong place: a list of vendors. Then every demo quietly rewrites your requirements around whatever that vendor is good at, and the team ends up choosing between feature lists instead of against its own needs.
Flip the order. Spend one hour writing requirements first – what your team actually publishes, who reviews it, what gets reported – and the vendor conversations become short and comparable. This guide walks an in-house marketing lead through that hour, requirement by requirement, with the evidence to request for each. Where Kontentino is the example, the plan each feature requires is stated, and the marketing teams page has the full product detail.
Start with four questions, not forty features
Everything in the checklist derives from four facts about your team. Write them down literally:
- Where do you publish? List the networks and the account count per network – including the ones marketing inherited but rarely posts to.
- Who touches a post? Count every role between idea and publish: creator, designer, copy reviewer, approver. Two people is a different tool problem than six.
- Who has to say yes? Name the sign-off. A marketing manager? Legal on some posts? A brand director in another office? The approval path is the single biggest differentiator between tools.
- What do you report, to whom, how often? The monthly slide for your CMO defines your analytics requirement better than any feature tour.
With those four answers, the checklist below sorts itself into essential and optional for your team specifically.
What are the essential requirements for social media management tools?
Not every requirement deserves the essential label, so here is the test: an essential is something that will bite you every single week if the tool gets it wrong, not something you’d merely shrug about. Six things pass that test for most in-house teams, and each of them comes with a simple way to check the tool before you commit to it.
1. Direct publishing to your actual networks
A publishing tool has one unbreakable promise to keep: when you schedule a post, it goes out on its own, in the format you made it, on the network you made it for. That sounds obvious until you discover that “supports Instagram” in a comparison grid can mean anything from full carousel publishing to a reminder notification on your phone. So read the vendor’s supported-networks documentation against your own list of networks and formats – carousels, Stories, Reels, LinkedIn documents, vertical video – and then publish one of each during the trial to watch it happen for real. Kontentino, for example, publishes across nine networks, including every Instagram format. Carousels publish automatically up to 10 items, and up to 20 with manual publishing through the mobile app. Both limits sit in its help center where anyone can check them, which is the level of transparency you can reasonably expect from any vendor.
2. A true-to-platform preview
Before anything gets approved, the person reviewing it should see the post exactly as it will appear once it is live: the crop, the point where the caption cuts off, the first slide, the link preview, on desktop and mobile for every network the post is going to. The simplest way to test this is to publish a post during the trial and hold it next to its preview. If the two don’t match, every approval your team gives from then on is a guess dressed up as a decision.
3. An approval step that matches how you sign off
Think back to who has to say yes before a post goes live in your company, because that exact path needs to exist inside the tool – our approval workflow guide maps the common ones. For most in-house teams that means an internal approval, where a manager reviews and approves before anything gets scheduled, and for some teams there is also an outside yes from legal, a brand director, or an executive. Approvals are the most commonly gated feature in this category, so read the pricing page carefully and ask the vendor directly which plan includes internal approval, which one covers external reviewers, and whether a reviewer needs a paid seat. Kontentino’s answer is public: internal approvals come with Starter at €49/month billed annually, client and external approvals come with Standard at €109/month, reviewers join by invitation and count toward the plan’s bundled users, and on Standard, anyone can get a preview link to see a post without a seat – though viewing is all a link does, approving happens from an invited account. Whatever tool you’re considering, get its version of that paragraph in writing.
4. Statuses the whole team can read
At any moment of the week, the calendar should be able to tell you what is still a draft, what is waiting for review, what is approved, and what is scheduled, without anyone having to ask in a meeting or a Slack thread. A good way to test this during the trial is to have the least technical person on your team open the calendar and talk through the status of the week. If they can’t, your Monday standup will keep doing the job the tool was supposed to take over.
5. Reporting that survives contact with your CMO or CTO
Whatever you report monthly today is the report the tool needs to produce – in minutes rather than an afternoon, exportable, and presentable without being rebuilt in a spreadsheet first. Build last month’s real report on trial data and time yourself doing it. While you’re at it, check what is included in the plan and what costs extra, because analytics is a separate module in several tools. In Kontentino, analytics is an add-on from €54/month billed annually below the Pro plan, and it has its own trial, so you can switch it on during the evaluation and judge it like everything else.
6. Roles and permissions
Everyone on the team should be able to do their own job in the tool and nothing beyond it, so the designer edits visuals, the junior writes drafts without being able to publish them, and the manager approves and schedules. Map the vendor’s roles onto your real team – our roles and permissions guide shows what a sensible setup looks like – and then run one small test during the trial: have someone who is not an approver try to schedule an unapproved post. The right answer is a polite refusal.
The optional requirements (nice until they’re not)
These matter for some teams and are noise for others. Decide which, before a demo decides for you:
- AI assistance for captions, translations, and variants. Essential if you localize or publish at volume, optional otherwise.
- Bulk operations – duplicating a post across networks, sending a batch for approval at once. Essential above roughly ten posts a week.
- A mobile app that covers review and approval, not just notifications. Essential if your approver travels.
- Multi-market structure – central content distributed to local teams for adaptation. Essential for multi-country brands, irrelevant for single-market ones.
- Asset library with team access, so visuals stop living in someone’s downloads folder.
- Pre-publish checklist recording your standards (alt text, UTM tags, link tested) per post.
Mark each as essential or optional for your team in the checklist. A tool that nails your essentials and skips your irrelevants is a better buy than one that half-does everything.
Pricing: read the model before the number
Publishing tools price four ways, and the model decides your invoice’s future better than the entry price: per seat (each user costs), per channel (each connected account costs), per brand workspace (each brand costs), or flat plans with bundled users and profiles. For a single-brand in-house team, flat bundles are usually the honest fit – your profile count is stable and your team grows slowly. Whatever the model, price it at your team size from question two plus two hires, and require the number without a sales call – for Kontentino, the pricing calculator gives it to you directly.
One more line for the checklist: trial terms. A real evaluation needs around two weeks on your real content – Kontentino’s 14-day trial requires no credit card, and that should be your baseline expectation of any vendor.
And one question for your own side of the table: who maintains the tool? Someone owns connecting profiles, managing users, and handling the renewal. Naming that person during selection, not after, is the difference between a tool that gets adopted and a login nobody remembers owning.
Final Decision Checklist
Copy this into the document you’ll bring to the decision meeting. Score each requirement: met with evidence, met on vendor’s word, or not met. Decision rule: every essential met with evidence, or no annual contract. “Met on vendor’s word” is a reason to extend the trial, not to sign.
| Requirement | Essential? | How to check it | Result |
|---|---|---|---|
| Publishes to all our networks, in our formats | Essential | Supported-networks docs + one trial post per format | |
| True-to-platform preview | Essential | Trial: compare a published post against its preview | |
| Approval path matches our sign-off | Essential | Plan documentation in writing + a trial run of the path | |
| Reviewer seat policy understood | Essential | Pricing page + direct vendor answer in writing | |
| Readable statuses on one calendar | Essential | Trial: non-technical teammate narrates the week | |
| Monthly report in minutes, exportable | Essential | Trial: rebuild last month’s report, timed | |
| Roles match our team | Essential | Roles docs + trial permission test | |
| AI, bulk, mobile, multi-market, assets, checklist | Per team | Mark each one essential or optional before any demo | |
| Price at team size + 2, without a sales call | Essential | Written quote or public pricing | |
| Trial: 14 days, real content, no credit card | Essential | The vendor’s trial terms |
Requirements first, vendors second. If you want to run this checklist against a real tool this week, start a Kontentino trial – 14 days, no credit card – or book a demo and bring the checklist. We’ll answer every evidence row, including the ones where the honest answer is that another tool fits you better.
FAQ: choosing a publishing tool for an in-house team
How do I choose a social media publishing tool for my team?
Write requirements before looking at vendors: your networks and formats, how many people touch a post, who signs off, and what you report monthly. Separate essentials from optionals, demand evidence per requirement – documentation, plan names in writing, trial behavior – and refuse annual contracts until every essential is met with evidence.
What features does an in-house marketing team need in a publishing tool?
The essential six: direct publishing to your actual networks and formats, true-to-platform previews, an approval step matching your sign-off path, readable post statuses on one calendar, reporting your leadership will accept, and roles that fit your team. AI, bulk operations, mobile approval, and multi-market structure are essential for some teams and noise for others.
What’s the difference between a publishing tool and a social media management tool?
Publishing tools center on scheduling and getting posts live. Management tools add the surrounding workflow: planning, collaboration, approvals, and reporting. Most in-house teams discover their real requirement is the workflow – the publishing itself is table stakes across the category, as our comparison of social media management tools shows side by side.
Do publishing tools include approval workflows?
Unevenly – approvals are the most commonly gated feature in the category, often sitting on upper tiers. Always check which plan includes internal approval, which includes external reviewers, and whether reviewers need paid seats. In Kontentino, internal approvals come with Starter and client approvals with Standard, with reviewers drawing on the plan’s bundled users.
How much should an in-house team budget for a publishing tool?
Flat-plan tools for teams start around €49 to €109/month with users and profiles bundled, with analytics sometimes an add-on. Per-seat tools multiply by your headcount. Budget at your team size plus two hires, and check what’s gated: a cheap plan without your approval path is just an incomplete plan with a nice price. (Verified October 2026.)
How long should we trial a publishing tool before deciding?
Two weeks on real content: two full planning-review-publish cycles plus one reporting moment. Build last month’s actual report, publish every format you use, and run your real approval path. A decision made on demo data is a decision made on the vendor’s best day.
Bring your checklist to a real tool
Write the requirements in an hour, gather the evidence in two weeks, and the decision defends itself in the meeting. More than 4,000 brands run their publishing through Kontentino, which is rated 4.7 on Capterra and 4.6 on G2. Start the trial with no credit card, or book a demo and we’ll go through your checklist row by row.
