Skip to content

Software research · Evaluation records

Every verdict shows its evidence.

We evaluate business software from vendor documentation, public pricing, security pages, changelogs and published user feedback. Each report states exactly what its verdict rests on, including whether anyone used the product.

Hands-on use
Only when a report says so
Vendor claims
Always labeled as such
Every report
Dated, with its basis
eval_record.txt Illustrative
SUBJECT
CRM option (example)
QUESTION
Seat pricing past 10 users
EVIDENCE
  • vendor docs
  • public pricing
  • changelog, 6 months
  • published user feedback
  • hands-on: not performed
CLAIM
"Unlimited pipelines" Vendor states
CONFIDENCE
medium
STATUS
draft verdict
Sample record showing the format. Not a real product or review.

01 Method

The method, written as a spec sheet.

Five inputs, read critically. Nothing on this list involves taking a vendor's word for it.

  1. M-01

    Basis statement

    Every report opens with what the verdict rests on: sources read, pages checked, and whether hands-on use took place.

  2. M-02

    Vendor documentation

    Docs, API references and admin guides. They often commit to less than the landing page implies.

  3. M-03

    Public pricing

    Published plans, seat and usage limits, add-on costs, and the conditions sitting in the footnotes.

  4. M-04

    Changelogs and security pages

    How often a product ships, whether announced features arrive, and what the vendor states about data handling. Stated, not audited.

  5. M-05

    Published user feedback

    Reviews, forums and issue trackers, read for recurring patterns. One loud complaint is labeled as one loud complaint.

  6. X-00

    Out of scope

    We do not run a lab. Performance benchmarks appear only when a report describes how they were done.

02 Labels

How we label evidence.

"The vendor states" and "we observed" are not the same sentence. Our reports never blur them.

Vendor states
Taken from the vendor's own docs, pricing or security pages. Repeated with attribution, not confirmed.
We observed
Seen directly during hands-on use. Only appears when the report says what was done, on which plan, and when.
Unverified
Reported somewhere, confirmed by neither of the above. Kept because it may matter, flagged because it is thin.
Example annotationTool B · generic

The Starter plan includes five seats Vendor states A 2,000-row CSV import finished without errors on the trial We observed Several users report delayed calendar sync Unverified

03 Index

Categories under evaluation.

28 folders on 5 shelves. 8 are described in full; the register lists all of them. Report counts are real and start at zero.

Selected folders 08 of 28

Jump to full register

04 Reports

Latest reports.

Newest first. Each row lists the date and what the verdict is based on.

05 Corrections

Found an error?

Pricing changes overnight and documents get misread. Send what is wrong, the source that shows it, and the date you saw it. Confirmed fixes get a dated note. Verdicts are never quietly rewritten.

Report a correction

Vendors use the same process. It does not buy a better rating.