Editorial Guidelines

This page documents the rules StackVersus Editorial follows when selecting, scoring, and publishing a software comparison. It exists so that anyone — a reader, a vendor, or a search engine trying to assess our trustworthiness — can see exactly how a verdict is reached.

What we score

Every comparison evaluates two products against the same fixed set of dimensions, so the comparison is apples-to-apples rather than a rewrite of either vendor's marketing page:

• Feature coverage. Whether each product has a given capability (e.g. marketing automation, built-in CRM, SMS sending, A/B testing, API access), drawn from a controlled list of feature fields so every comparison in a category is measured the same way.
• Pricing and plan structure. Published list prices, plan tiers, and any usage limits (contacts, sends, seats) that materially change what a plan actually gets you.
• Free plan availability. Whether a product can genuinely be used at no cost, versus a time-limited trial only.
• Fit for scenario. Where a comparison targets a specific use case (for example, a particular team size or workflow), we weigh which product's feature set and pricing better serve that scenario specifically, not which product is "better" in the abstract.

Where facts come from

Facts used in scoring are sourced exclusively from each vendor's own official pricing and features pages, captured with a source URL and a capture date, and checked by an editor before the product profile is approved for use in comparisons. We do not score based on secondhand reviews, forum posts, or a vendor's own claims about a competitor. When a page that drafts a comparison is generated, the drafting process is restricted to only the approved facts already on file for both products — it is not permitted to add pricing, features, or claims that aren't already in our fact base. A human editor reviews every draft against that fact base before it is published.

Sponsorship and affiliate independence

StackVersus participates in affiliate programs and may accept sponsorship arrangements with vendors, disclosed in full on our affiliate disclosure page. We commit to the following:

• Scoring happens against the fixed dimensions above, using facts captured before any commercial discussion with a vendor, if one exists at all.
• No vendor can pay to raise its score, change a verdict, alter a feature comparison, or have a negative point removed.
• A vendor's affiliate or sponsorship status may affect whether it's prioritized for coverage, and may affect which vendor's link is used as the default call-to-action when both products in a comparison are otherwise a similar fit — but it never changes the comparison's underlying facts or its written verdict.

Correction process

Software pricing and features change often, and we rely on readers and vendors to help us catch drift between what we publish and current reality. If you spot something inaccurate:

1. Email us at hello@stackversus.com with the page URL and, where possible, a link to the current vendor page showing the correct information.
2. An editor verifies the claim against the live vendor source before making any change — we don't take a correction request at face value without checking it.
3. Once verified, we update the underlying fact record and the affected page, and refresh the page's displayed "last updated" date so the change is visible.

See our About page for more on how comparisons are built end to end, and our contact page for how to reach us.