Editorial policy

The rules we hold ourselves to, written down so you can hold us to them too.

On this page
  1. What we are, and what we are not
  2. Claims we will not make
  3. How we research
  4. How products are selected
  5. How we rank and reach verdicts
  6. Updating and maintaining content
  7. Conflicts of interest
  8. AI and how this content is produced
  9. Corrections
  10. Reader feedback

This policy governs everything published on SoftwaresPick. It is deliberately specific. A policy that only says "we value accuracy and independence" tells a reader nothing they can check.

What we are, and what we are not

We are an independent research and publishing team. We read documentation, pricing pages, security disclosures, changelogs, developer forums and support threads, and we turn that into pages that help people decide.

We are not a testing lab. We do not run standardised benchmarks across products, we do not maintain deployments of every tool we write about, and we do not employ a panel of certified experts in each category. Plenty of sites imply that they do while doing exactly what we do. We would rather say it.

That shapes what we will and will not claim.

Claims we will not make

  • No invented testing. We never write "we tested", "we used this for six months" or "in our testing" unless that is literally true and the page says what was done.
  • No scores we did not measure. No ratings out of ten, no five-star verdicts, no "8.4/10 for ease of use" — those numbers imply a measurement, and an invented measurement is a lie with a decimal point.
  • No fabricated user voices. No invented testimonials, no made-up quotes, no "users say" without a source, no fake reviews.
  • No invented expertise. No fictional authors, no borrowed credentials, no "reviewed by our panel of IT directors" where no such panel exists.
  • No fabricated statistics. Where we cite a number, it comes from a named source we link to. If we cannot source it, it does not appear.
  • No invented pricing. If we cannot confirm a current price, we describe the pricing model rather than guessing a figure.

How we research

Primary sources first. Vendor documentation, pricing pages, security and compliance pages, status pages, release notes and official support articles. When something matters and can change, we link the exact page we checked.

Corroboration for anything contested. Where the vendor's description and users' experience diverge — support quality, migration difficulty, hidden limits — we look for substantiated accounts in developer communities and support forums, and we describe them as what they are: reported experience, not measurement.

Dating everything perishable. Every page shows when its information was last reviewed. Pricing, plan structures and feature availability all decay; the date tells you how much to trust them.

Verification before publication. Product facts are checked against the source at the time of writing, not carried over from an earlier draft or another article.

How products are selected

For a shortlist or category page, a product qualifies for consideration if it is actively developed, available to the audience the page is written for, and genuinely capable of the core job. From there we select for coverage of different needs rather than a ranked ladder: the tool that suits a two-person business is rarely the one that suits a 200-person one, and a list that pretends otherwise is not useful.

We include free and open-source options wherever they are genuinely competitive, and we say when the honest answer is "you do not need this category of software yet".

Commercial relationships play no part in selection. See our advertiser disclosure.

How we rank and reach verdicts

Where a page ranks products, the basis for the ranking is stated on the page. Usually it is fit for a defined use case — "best for a small team without a dedicated admin" — not an abstract notion of quality.

We are willing to reach no single verdict. When two products serve different buyers, the page says which buyer each one suits. Manufacturing a winner for the sake of a conclusion is a disservice to the reader who fits the other profile.

Criticism is specific. "The reporting is limited" says nothing; "reports cannot be scheduled or exported on the entry plan" is a fact a reader can act on.

Updating and maintaining content

Software content rots faster than almost any other kind. We handle that by:

  • Reviewing pages on a recurring cycle, with priority given to pages where pricing or plan structure is central.
  • Updating immediately when a significant change is reported to us or spotted — a discontinued product, a repackaged pricing tier, an acquisition, a security incident.
  • Showing an "Updated" date only when the content genuinely changed. We do not refresh dates to look current. A stale date on an unchanged page is information, and removing it would be a small lie told for ranking purposes.
  • Retiring or redirecting pages that no longer serve anyone, rather than leaving them to mislead.

Conflicts of interest

Anyone writing for this site must disclose any financial interest, employment history or personal relationship connected to a product they are covering. Where a conflict exists, the person does not write or edit that page.

We do not accept payment, equity or gifts from vendors in exchange for coverage. Free trials, extended evaluation access and technical briefings may be accepted where they help us describe a product accurately; they carry no editorial conditions, and any that materially informed a page is disclosed on it.

AI and how this content is produced

Research and drafting tools, including AI tools, are used in producing this site. Two rules apply without exception:

  1. No claim is published because a tool produced it. Every fact is verified against a primary source by a person before it appears. A generated sentence that cannot be sourced is deleted, not softened.
  2. Nothing is published unreviewed. Every page is read and edited by a human who is accountable for it.

We think transparency here matters more than the label. The failure mode of AI-assisted publishing is confident, unsourced, unverifiable claims produced at volume — which is precisely what the rules above exist to prevent.

Corrections

Mistakes get fixed, visibly. See our correction policy for what we correct, how quickly, and how changes are marked. Report anything wrong to partners@softwarespick.com.

Reader feedback

Disagreement is welcome and occasionally changes our mind — write to partners@softwarespick.com. What we cannot do is accept content, links or edits from anyone with a commercial interest in the products discussed.

Questions about this page? Email partners@softwarespick.com and a person will read it.