Guides

How to get your software listed in comparisons

Send a comparison editor a public pricing page, a reachable trial, a human who answers mail, a true feature list and publishable screenshots, and you will usually get listed.

By Thinking Desk 6 min read

Key takeaways

  • Five things decide it: a public pricing page, a trial without a sales call, a reachable human, a feature list that is true, and screenshots you may publish.
  • Unverifiable pricing is the most common reason a product is left out of a comparison table.
  • The highest leverage sentence in a submission is the one naming the use case where your product is the wrong answer.
  • Plan in months: your submission waits for the category page it belongs to to be written or updated.
  • At a guide with a working firewall, paying cannot move a ranking position, and asking for one is remembered.
On this page
  1. Short answer
  2. What a comparison editor needs before they can list you
  3. What gets a product dropped from a comparison
  4. How to write a submission that gets read
  5. How long does it take to get listed in a comparison
  6. What we do at Thinking specifically

Short answer

Send a comparison editor five things and you will usually get listed: a public pricing page, a trial or demo a reader can reach without a sales call, a named human who answers mail, a feature list that is true, and screenshots you are allowed to publish. Everything else, the deck, the award badges, the follow-up calls, moves nothing. Editors do not reject products because the vendor is small. They drop products they cannot verify.

What a comparison editor needs before they can list you

A comparison page is a liability. Every number on it can be checked by a reader, a competitor or a regulator, so an editor only publishes what they can stand behind. That turns into five concrete requirements.

A public pricing page. Not a form, not "contact us for pricing", not a PDF behind a gate. If a price is not readable on your own website, a serious guide writes "price on request", and a row that says "price on request" next to three competitors with numbers loses the comparison before the reader finishes the table. If you genuinely sell only by quote, publish a starting price and what drives it, for example per terminal, per user, per location.

A trial or a demo that does not need a human. A self-serve trial, a sandbox account or a recorded product tour lets the editor see the thing. If the only way in is a 45 minute call with sales, the editor will either skip you or describe your product from your marketing copy, which never flatters anyone.

A reachable human. One address, answered within a couple of days, with authority to confirm a price. Not a shared inbox that routes to a chatbot. Most factual errors in comparison tables exist because nobody answered the mail.

A feature list that is true today. Mark what is on the roadmap as roadmap. An editor who finds one feature claimed and missing will stop trusting the rest of the list, and the way that shows up in the published piece is a short paragraph of hedging.

Screenshots you are allowed to publish. Clean UI shots, no customer data, no third party logos you do not have rights to, and a line that says explicitly that the publisher may use them. A vendor who sends usable assets gets described more accurately than one who sends none, because the editor can look at the product instead of imagining it.

Weekly, Thursday morning, Central European Time.

The Thinking briefing

One email a week: what changed in European business software, which prices moved, and which comparison we published. No sales mail.

What gets a product dropped from a comparison

  • Pricing that cannot be verified. The single most common reason. A guide that invents a price gets corrected in public, so it leaves you out instead.
  • A dead trial or a broken signup. If the editor cannot create an account, your product is untestable and therefore unlistable.
  • Claims that collapse on contact. "GDPR compliant", "AI powered" and "used by thousands" are not facts. "Hosted in Frankfurt, data processing agreement on this URL" is.
  • Review gaming. Incentivised or written-for-you reviews are now a legal risk, not just an ethical one. The US Federal Trade Commission adopted a rule in August 2024 that bans fake and paid-for reviews, insider reviews without disclosure, and review suppression. Editors read review sites for signal, and a cluster of five star reviews posted in one week is signal of the wrong kind.
  • Pressure. Asking for a better position, offering money for a ranking, or escalating to the publisher is the fastest way to be remembered as a vendor to avoid. At a guide with a working firewall it also cannot work, because the person who sells placements does not set the ranking.
  • Silence after the fact check. An editor sends a draft row, asks two questions, and hears nothing for two weeks. The row gets cut, not corrected.

How to write a submission that gets read

Keep it to one screen. Editors read dozens of these.

  1. One sentence on what it is and who it is for. "POS and invoicing for Luxembourg hospitality, built for the local VAT rules." Not "the operating system for modern commerce".
  2. The three links. Product page, pricing page, trial or demo. In that order.
  3. The two numbers. Cheapest paid plan with the unit, and how many paying customers you have. If you are at nine customers, say nine. Editors use it for context, not as a filter, and a vendor who says nine is a vendor whose other numbers you believe.
  4. One honest weakness. Name the use case where you are the wrong answer. This is the single highest leverage sentence in the whole submission. It tells the editor you will not fight the published weaknesses, which is what they are quietly worried about.
  5. The one thing competitors get wrong. A concrete, checkable claim, not an adjective. "Competitor X cannot apply a different VAT rate per article, which matters in Luxembourg because food and alcohol are taxed differently on the same ticket."
  6. Assets and permission. Screenshot links plus one line granting publication rights.

What to leave out: the funding announcement, the award badges, the deck, the pitch video, and any sentence containing the word "revolutionary".

How long does it take to get listed in a comparison

Plan in months, not days. A serious guide publishes against its own editorial calendar, which means your submission sits until the category page it belongs to is written or updated. Realistic sequence: a reply within a week at a small desk, a fact check round when the relevant page is next touched, and publication whenever that page ships. The large directories work differently: a profile there is self-service and can be live in days, but the ranked comparison content on the same site is still editorial or paid, and the categories a reader actually reads are updated on a schedule.

Two things speed this up and they are both on your side. Keep your pricing page current, because the next update of a comparison starts by re-checking prices. And answer fact-check mail the same day, because an unanswered question becomes a cut row.

If you are deciding where else to spend the effort, start with the directories a European software vendor should be in and with what actually makes an AI assistant name a product. Those two and your own pricing page cover most of the ground.

What we do at Thinking specifically

We profile European business software whether the vendor pays or not, and submissions are read by a person. The rules are short:

  • A paid plan buys verification of facts or a clearly labelled sponsored placement. It never buys a ranking position and it never buys an editorial score.
  • Every paid link is rendered with rel="sponsored nofollow", which is what Google's own spam policy requires for links that change hands for money.
  • Scores are set against criteria we publish before the ranking, and where a competitor is the better answer for a use case, we write that.
  • Thinking is published by TTA Technologies, which also builds LUXPOS, Salonify, BoxBee and DepotGest. Those products appear in our comparisons, every page that names one carries a disclosure, and their position is justified against the same published criteria.

The full rulebook, including how to report a factual error, is on how listings work on thinking.lu. When your pricing page and trial are ready, submit at /en/get-listed. One screen is enough.

Questions and answers

Do I have to pay to be listed in a comparison?
Not at a guide that keeps an editorial firewall. A free editorial listing exists because the comparison has to be complete to be useful. Paid plans buy fact verification or a labelled placement, never a position in the ranking.
What if we have no public pricing page?
Publish a starting price and the unit that drives it, even if the full quote is bespoke. Without it a comparison writes price on request, which reads as the most expensive option in the table.
Can I ask for a correction after publication?
Yes, and you should. Send the factual error with a link to the source that proves it. A desk worth your time corrects a verified factual error within days and dates the correction.
Do award badges and funding news help?
No. Editors verify prices, features and reachability. A funding round changes none of those and takes space in a submission that is read in under a minute.

Sources

Every price and fact above was checked against these pages on the date shown.

  1. [1] Google Search Central, Spam policies for Google web search (link spam, paid links must carry rel=nofollow or rel=sponsored) accessed 2026-11-11
  2. [2] FTC announces final rule banning fake reviews and testimonials (16 CFR Part 465, announced 14 August 2024) accessed 2026-11-11
  3. [3] European Commission, Unfair Commercial Practices Directive (2021 guidance covers transparency of search results and consumer reviews, amendments applicable since 28 May 2022) accessed 2026-11-11
Topics vendorslistingscomparisonseditorial

Thinking is published by TTA Technologies in Luxembourg, which also builds LUXPOS, Salonify, BoxBee and DepotGest. Read the full disclosure policy