You cannot pay to be in a Buyer's Guide. You can show your evidence.
The Buyer's Guides are read by people choosing engineering and manufacturing software. Vendors and their agencies ask to be included often, and that is welcome. This page sets out how a request is handled, so every vendor faces the same rules and so readers can see what a listing does and does not mean.
1. The scope test
Each guide covers one category, and a product is considered for it when it clearly belongs there. A request needs:
- the guide you are asking about (the 13 categories are listed on the Buyer's Guides hub);
- one sentence on why the product belongs in that category;
- one URL to the product page.
Add-on modules for a product already covered, directories, marketplaces and services businesses are usually outside scope. If a product does not fit any current guide, that is a useful signal and worth telling us.
2. The evidence checklist
Ratings are built on evidence. Some of it is checked by us, and some is supplied by the vendor.
Checked by us
- Public product documentation and pricing model.
- Public statements about ownership, funding and company status.
- Independent sources, such as filings, press coverage, user documentation and third-party reviews.
Supplied by the vendor
- Deployment and data model: cloud, on-premises, open source, AI-native.
- Verifiable customer references, named, or anonymised with proof that we can check.
- Security and compliance statements, such as SOC 2 or ISO 27001, with certificate identifiers.
- For any AI claim: what it does, in which release, and a demo or documentation.
- Optionally, a briefing or demo with us. A briefing helps us understand a product. It is never decisive on its own.
3. Rating states
Every entry is in one of three states, and each shows the date its evidence was last reviewed.
| State | What it means |
|---|---|
| Not yet rated | The product is described, but evidence is too thin to score. |
| Provisional | The score rests on limited evidence, mostly public documentation. It can move up or down when better evidence arrives. |
| Rated | The score rests on verified evidence, with the evidence dates shown. |
A provisional or not-yet-rated state is not a judgement that a product is poor. It is a statement about how much we have been able to verify.
4. Vendor claims are labelled as claims
What a vendor says about its own product is reported as a vendor claim until it is verified. If a claim cannot be verified, the entry says so.
5. Right of reply
If a vendor believes an entry contains a factual error, it can send a correction with evidence. Corrections are considered within 10 working days. Where a correction changes an entry, the change is dated, and a vendor's response may be published as a dated vendor response.
Scores are not negotiable. Evidence can change them.
6. Ordering
Products are ordered by score. Ties are ordered alphabetically. There is no "first position", and no vendor can request one.
7. Independence
- There are no inclusion fees, no sponsored placements, no paid tiers and no featured slots.
- Link exchanges, content swaps and reciprocal mentions are not part of any inclusion decision, and are not requested before or alongside one.
- Entries written by third parties are not accepted. Agencies can raise a request, but must name the vendor and confirm they are authorised to act for it.
- The author works as an independent analyst and advisor, and has commercial relationships with some software companies. These relationships play no part in any rating, and no company receives different treatment because of one. Specific disclosures are made where the author is free to make them.
8. Review cycle
The guides are updated in quarterly editions. A request received after an edition's cutoff is held for the next edition. Cutoff dates are announced with each edition. Vendors are also added without being asked, when the evidence says they belong.
How to submit
Email michael@demystifyingplm.com with the subject line Submission: [vendor], [guide], and include:
- Vendor name and product name.
- The guide you are asking about.
- Your role, and a line stating: "I am authorised to submit for this company." Agencies must name the vendor and state their authority.
- The product URL and the one-sentence reason it belongs in that category.
- Links to the evidence listed in section 2.
You will receive a reply with the checklist and the edition date. Submitting does not guarantee inclusion, and inclusion is not for sale.
This page was last updated on 17 November 2026.
Want to listen instead of read? 56 DemystifyingPLM articles are available as audio.
Browse audio →Looking up PLM terminology? Browse the canonical reference.
PLM Glossary →Cite this article
Finocchiaro, Michael. “How a vendor gets into a Buyer's Guide.” DemystifyingPLM, November 17, 2026, https://www.demystifyingplm.com/how-vendors-get-into-a-buyers-guide
Michael Finocchiaro (opens in a new tab)
PLM industry analyst · 35+ years at IBM, HP, PTC, Dassault Systèmes
Firsthand knowledge of the evolution from early 3D modeling kernels to today's cloud-native platforms and agentic AI — the history, strategy, and future of PLM.


