What the evidence can tell you.
A product can support a feature without including it in the plan you can afford. We keep those questions separate.
Capability, plan, price
Capability means the vendor documents the feature. Plan access means a named package includes it or sells it as an add-on. Price certainty means we can establish an amount, currency, billing period, and allowance for the configuration. Evidence for one does not establish the others.
Where the facts come from
Comparison facts link to public vendor pricing pages, product documentation, or developer references, with a date checked. A missing answer means our evidence has not established it. It does not mean the product lacks that feature. A listing in an integration directory does not establish every trigger, action, or sync direction.
How shortlists work
The shortlist tool counts documented matches to requirements you select. Paid add-ons can match, but remain labeled. Ties sort alphabetically. This is evidence coverage, not a quality rating. Company size and the apps you name help prepare demo questions; they are not used to invent a fit score.
What the calculator measures
It models usage from your inputs and applies recorded plan allowances. It does not measure a running workflow. Branches, retries, weighted operations, required features, and outside services can change the bill. We withhold price rankings when billing rules or currency are unresolved.
Read the formulas and limitations → · Pricing history →
Testing, updates and corrections
Public-documentation analysis is not hands-on testing. A measured result must identify the setup, date, and raw usage. No lab measurements are claimed by the calculator.
Check dates belong to particular facts, not an entire page forever. When we recheck a plan or billing rule, we retain its source, billing context and what changed. Older directory observations stay dated until that evidence is checked again. A new layout or typo fix does not make old research new.
Material page updates explain the change beside the affected comparison. The calculator also keeps a pricing history. If sources disagree, we show the disagreement rather than silently choosing a convenient answer. Corrections should identify the affected statement, the replacement and the supporting source; public examples must not expose private customer data.
Found a mismatch? Send the page and vendor source so we can check it.