Why Tested SaaS exists
Most software buying decisions start with a vendor’s own words. Feature pages promise speed, security pages promise safety, and pricing pages promise simplicity until the invoice arrives. Very little of it is checked by anyone without a stake in the sale.
Tested SaaS exists to do that checking. The name is a commitment: every claim we repeat, whether it comes from a vendor, a user forum or our own notes, gets put to the test of evidence before it shapes a verdict. When the evidence is thin, we say the evidence is thin. When we could not verify something, we say that too.
We write for people who have to live with the software after the demo ends: engineering and IT leads, analysts, operations teams, procurement, and anyone who has been burned before by a feature that turned out to be “on the roadmap.”
How we evaluate software
A Tested SaaS evaluation is a structured review of the available evidence about a product. Depending on the product and the question being answered, that evidence usually includes:
- Vendor documentation: product docs, API references and admin guides, which often reveal more than marketing pages do.
- Public pricing: published plans, seat and usage limits, add-on costs, and the conditions buried in footnotes.
- Security and compliance pages: what a vendor states about data handling, access controls, hosting and any attestations it says it holds. We report what is stated; we do not audit it.
- Changelogs and release notes: how often a product ships, what it fixes, and whether announced features actually appear.
- Published user feedback: patterns in publicly available reviews, community forums and issue trackers, read for recurring themes rather than isolated complaints.
Some reviews also involve hands-on use of a product, such as working through a free trial, a sandbox or a demo account. We do not assume this happened, and neither should you. When a review includes hands-on use, it says so explicitly and describes what was done: which plan or edition, roughly when, and which tasks were attempted. If a review does not contain that statement, it was based on the documentary evidence listed above.
The limits of our method
We would rather be clear about what we cannot do than imply more certainty than we have.
- We do not run a lab, and we do not benchmark performance at scale unless a review explicitly describes how it did so.
- Documentation can be outdated, incomplete or written to impress. We read it critically, but we cannot always confirm it against reality.
- Published user feedback can be skewed by incentives, small samples or a single bad week. We look for patterns, and we label anecdotes as anecdotes.
- Software changes constantly. Prices, plans and features may shift after we publish, which is why every review carries a date.
- Your environment is not ours. Treat our verdicts as informed starting points, not a substitute for your own trial.
How evidence is labeled in our reviews
Every review is written so you can trace a conclusion back to its source. In practice that means:
- A basis statement. Each review opens by stating what the verdict is based on: documentation reviewed, pricing pages checked, feedback sources consulted, and whether any hands-on use took place.
- Dates. We record when the evidence was gathered and when the review was last updated, so you can judge how fresh it is.
- Vendor claim versus observation. We distinguish between “the vendor states” and “we observed.” The two are not interchangeable, and we do not blur them.
- Confidence notes. Where a conclusion rests on limited or conflicting evidence, we flag it rather than smoothing it over.
Ratings and scores summarize our reading of that evidence. They are opinions, and the reasoning behind them sits next to them on the page.
Corrections
We get things wrong sometimes: a pricing tier changes overnight, or we misread a document. When that happens, we want to know.
If you spot an error, send the specifics to corrections@testedsaas.com: what is wrong, the source that shows the correct information, and the date you observed it. We review every report. If we confirm the error, we fix the review and add a dated note explaining what changed. We do not quietly rewrite verdicts.
Vendors are welcome to use the same process. A correction request from a vendor is weighed on the evidence it provides, the same as one from a reader. It does not buy a better rating, and declining to engage does not earn a worse one.
How the site is funded
Tested SaaS is free to read. To pay for research and running costs, the site may earn money in two ways:
- Affiliate and referral links. Some links to software vendors are partner links. If you click one and later buy, we may earn a commission at no extra cost to you.
- Sponsored placements. We may offer placements that are paid for by a vendor. These are always clearly labeled as sponsored and are kept separate from editorial reviews.
Keeping money away from verdicts
A commission is only worth anything if readers trust what we write, so we protect that separation deliberately:
- A partner program is invisible to scoring: it does not move a rating, reorder a comparison, or decide which products get reviewed.
- Vendors cannot pay to change a score, remove criticism or preview a verdict before publication.
- Sponsored placements never appear as editorial content and never carry our ratings as an endorsement.
- We will recommend a product with no partner link over one with a generous commission when the evidence points that way.
If you ever think we have fallen short of this, tell us at contact@testedsaas.com.
Who runs Tested SaaS
The legal name of the business behind this site is simply Tested SaaS. Our Terms and Conditions and Privacy Policy explain how the site works and how we handle your data. Every other route to us, from corrections to press, is listed on the Get in Touch page.