Our SaaS pricing research methodology
A comparison is useful when the evidence and assumptions can be checked. PackageLens separates published facts, modeled costs, unknowns and recommendations.
1. Define the decision and workload
We agree the product, up to three competitors, relevant features, billing period and two workload scenarios before researching. A workload can include seats, events, projects or another charging unit. We do not assume that similarly named plans provide equivalent capabilities.
2. Build a public-source evidence record
We prioritize official pricing pages, product documentation and vendor help articles. Each material observation records a source link and check date, currency, billing term, included allowance, add-ons and relevant qualification. Unavailable prices and ambiguous toggle states remain unknown rather than becoming estimates presented as facts.
3. Compare the same requirements
We select plans against the agreed features and workloads, then show the arithmetic. Annual commitments stay distinct from month-to-month rates. We do not silently convert currencies, assume taxes or negotiated discounts, or treat a missing feature as included. If a fair total cannot be calculated, we explain the gap.
4. Separate evidence from judgment
Observed fact: what a linked source states at the check date. Calculation: a result derived from named inputs. Unknown: information the available sources do not resolve. Recommendation: a proposed test based on the evidence, with no assumed commercial result.
5. Check and deliver
We check material claims against the linked sources, recompute the two scenarios and review the boundaries before delivery. AI tools support parts of the research process; all material claims require source checks. Source access and pricing can change. We include one factual correction round requested within seven days of delivery.
Limits and independence
We use public information. We do not claim customer interviews, proprietary market datasets, vendor affiliation or measured conversion improvements. The brief does not establish price elasticity, customer willingness to pay or a guaranteed winning price. Product names identify the vendors being researched.
See the approach in the privacy analytics pricing sample. For a correction, email packagelens@tyasi.io with the source and the disputed statement.