How we know what we say

Verified

Checked against the cited primary source (usually the vendor's own page) on verifiedAt.

Editorial

OneLessTool's reasoned judgement (e.g. quality scores, fit). Not a vendor claim.

Estimate

A calculated or approximate figure; the methodology is stated alongside it.

Illustrative

An example scenario, not a measurement.

AI-suggested

Generated by an AI model and not yet reviewed by a human.

Unverified

Believed accurate but not checked against a primary source recently.

“Verified” means a person or a research agent read the price or feature on the vendor's own page on the date shown and recorded the URL. Vendors change prices often, so check the date. Some vendors block automated access or show prices by location; where we couldn't see a US price on the official page, we say unverified rather than guess.

Core feature

A core, first-class feature of the product.

Strong

Handles it well, though it isn't the product's focus.

Partial

Covers common cases with notable gaps.

Workaround

Possible with effort; expect friction.

Scores from 1 (poor) to 5 (best-in-class) rate quality, ease for a non-expert, precision, batch work, collaboration, brand consistency, reliability and privacy. They are editorial judgements based on documented features, not lab benchmarks. Each capability page shows which dimensions matter most for that job.

1. Start from what you actually pay. The audit uses the amounts you enter, not list prices.
2. Most expensive first. We evaluate subscriptions from most to least expensive. A tool counts as replaceable only if every capability you use it for is covered by tools that remain in your stack — so two overlapping tools can never both be marked redundant.
3. One action per subscription. Each subscription saves money through at most one action: cancel, downgrade, or replace.
4. Subtract incremental costs. If the covering tool needs extra seats, we subtract them at your current per-seat price.
5. Likely vs possible. “Likely” needs strong or native coverage by tools you keep. Partial coverage, plan downgrades (cheaper plans usually have lower limits) and assumed usage count as “possible” and are shown separately.
6. Critical stays. Business-critical tools are never marked for cancellation.
7. Effort is separate. One-time migration effort is estimated in hours and shown next to — not subtracted from — monthly savings. Annual figures are monthly × 12.

The engine is open in our codebase (src/lib/engine/audit.ts) and covered by unit tests, including tests that prove it never double counts.

We don't use affiliate links and vendors can't pay for placement. If we ever add partnerships, they'll be clearly disclosed and will never affect rankings or verdicts.