How We Evaluate Tools

Choosing a social media tool involves more than checking a feature list. The right choice depends on the platforms you use, the work you need to do, your budget, and the people involved in your workflow.

Locomu aims to help readers understand those differences. This page explains the criteria and evidence we use when preparing tool profiles, comparisons, and recommendations.

How We Select Tools

We consider tools that are relevant to social media work, including scheduling, publishing, content planning, creation, repurposing, analytics, collaboration, and related tasks.

A product may be included because it addresses a specific need, provides an alternative to another tool, or is useful to a particular type of reader. We do not aim to cover every product, and a listing does not imply that a tool is suitable for everyone.

Providers and readers may suggest tools through our Contact page. A suggestion does not guarantee inclusion, a review, or a favorable assessment.

Where Our Information Comes From

Depending on the product and the question, we may consult:

Official product websites and feature descriptions.
Pricing pages, plan details, and terms.
Product documentation, help centers, and release notes.
Official documentation from relevant social media platforms.
Direct experience with a product or feature.
Other sources that provide relevant context or help resolve discrepancies.

We aim to link to important sources where practical and identify when time-sensitive information was checked. Provider information helps us understand a product, but promotional claims should not be treated as independently verified results without supporting evidence.

Understanding Our Evidence

We distinguish between information obtained from documentation and information based on direct experience:

Documented: A claim is supported by a source, such as official product documentation, but has not necessarily been tested by Locomu.
Tested: A specific feature or workflow has been examined directly under identifiable conditions.
Unconfirmed: Available evidence is insufficient, unclear, or conflicting.

These descriptions apply to the relevant claim or feature. Testing one part of a product does not mean we have tested every plan, integration, or feature.

When information cannot be verified, we may omit the claim, explain the uncertainty, or identify it as unconfirmed. A missing detail should not automatically be interpreted as proof that a feature is unavailable.

What We Consider

The criteria vary with the product and the reader’s task. A scheduling tool, for example, may require different evaluation from a video editor or link-in-bio service. Where relevant, we consider the following.

Purpose and Fit

We examine what the tool is designed to do and which users or workflows it may suit. A product intended for one creator may have different strengths and limits from a suite designed for teams or agencies.

Platform and Account Support

We look beyond a list of platform names. Depending on the tool, useful details may include:

Supported networks and account types.
Supported content formats, such as posts, stories, videos, or carousels.
Whether a feature supports publishing, analytics, engagement, or another task.
Whether publishing is direct or requires a notification or manual step.
Plan, regional, or integration restrictions.

Support for a platform does not necessarily mean support for every account type, format, and feature. Readers should confirm capabilities that are essential to their workflow.

Features and Limitations

We consider the functions relevant to a product’s purpose and identify meaningful limitations where evidence is available. For a scheduler, those may include queues, calendars, content libraries, or approval workflows. For an analytics tool, they may include available metrics, reporting options, and data coverage.

We do not assume that a longer feature list makes a product better. A simpler tool can be a better fit when it handles the work a reader needs.

Pricing and Value

Where pricing is available, we aim to identify relevant conditions, such as:

Currency and billing period.
Whether a quoted monthly equivalent requires annual billing.
The number of channels, seats, workspaces, or other units included.
Feature restrictions, minimum commitments, and possible add-ons.
The date the pricing information was checked.

When comparing costs, we aim to use a clear scenario. A plan’s starting price may not represent the cost of the channels, users, or features a particular reader needs. Taxes, regional prices, discounts, and provider terms may also affect the final amount.

Usability and Workflow

When we have firsthand experience, we may consider how a feature works within a practical task: preparing content, reviewing a draft, scheduling a post, or producing a report. We aim to describe the context of that experience and any limitations encountered.

We do not describe a product as easy, difficult, reliable, or effective based on firsthand use unless the statement is supported by an appropriate basis.

Collaboration and Portability

For team-focused tools, relevant considerations may include roles, approval processes, client access, and how work is organized. Where evidence is available, we may also look at export options and information a user might need when changing tools.

How We Test

Not every listed product is tested firsthand. Where direct testing is practical, we may use a trial, free plan, paid account, or other access available to us. We aim to record the date, plan, account type, feature tested, and relevant conditions.

A test reflects the experience and access available at that time. It does not establish how a product will work for every account, region, team, or future version. If a product is described primarily from documentation, we aim to make that distinction clear.

If a provider gives us free or discounted access or another relevant benefit, we aim to disclose the relationship where readers can easily see it.

Comparisons and Recommendations

When comparing tools, we aim to use criteria that match the question being asked. For example, a comparison for a solo creator may focus on a different cost scenario and feature set from one for a team managing several client accounts.

We aim to explain the evidence, trade-offs, and assumptions behind a recommendation. If a product is presented as a strong choice for a particular purpose, the conclusion should be supported by relevant evidence. Affiliate compensation does not determine our editorial conclusions.

Locomu does not currently require a universal numerical score for every tool. If we use a rating or ranking, we aim to explain the criteria, the context, and any meaningful limits in the evidence.

Keeping Information Current

Products change. Features, platform integrations, plans, and prices may be updated or discontinued after we check them. We aim to revisit information when appropriate and correct material errors under our Corrections Policy.

A last checked date applies to the information identified on the page; it does not mean that every claim was verified or every feature tested on that date. Before subscribing or making a purchase, check the provider’s current documentation, pricing, and terms.

Commercial Relationships and Feedback

Some pages may contain affiliate links, advertising, sponsored content, or paid placements. Relevant relationships should be disclosed clearly. These arrangements do not guarantee inclusion, favorable coverage, or a particular evaluation.

If you notice an error, have updated documentation, or would like to suggest a tool, please contact us through the Contact page. Include the relevant page URL and source where possible.