How we review software

What a profile has to answer

Each profile is written against the same set of buyer questions: what workflow the tool improves, how it is priced, who it fits by team size and sales motion, what it has to connect to, how much RevOps and admin effort it creates after launch, and which direct competitors belong next to it. The buying question that drives each category page decides which of those questions gets the most room.

A section that cannot answer its question with something specific gets cut rather than padded. A security heading saying a vendor takes security seriously tells you nothing. A line naming the certification the vendor publishes and pointing at its trust page tells you where to check.

What we check before publishing

• Identity and ownership. Whether the product still exists under the name we are using, and whether it has been acquired, renamed, merged into a suite, or split out of one. Two listings that turn out to be the same product get merged.
• Category placement. Whether the tool would realistically appear on a shortlist for the category it sits in, rather than touching that category from the edge.
• Pricing figures. Every published price, plan name, seat minimum, and billing term read off the vendor's own pricing page, with the date recorded.
• Integration claims. Named integrations checked against vendor documentation or a marketplace listing, not against a logo wall.
• Competitor set. Whether the tools we tell you to compare it against are priced and positioned closely enough for the comparison to be worth your time.
• Links and dates. Internal links resolve against the live data files, retired slugs are replaced, and the review date on the page reflects the last time someone looked at it.

Where the facts come from

Primary sources come first: vendor pricing pages, product documentation, help centers, API references, release notes, security and trust pages, and the vendor's own announcements for acquisitions and packaging changes. When a fact exists in a primary source, that is the version we publish, and a vendor-supplied correction is checked against one before it changes a page.

Secondary sources are labeled as such. Where a figure comes from a third party rather than the vendor, the page says it is a third-party estimate and names where it came from, so you can weigh it accordingly. We read public RevOps and sales operations discussion for recurring patterns in how tools behave after rollout, and we describe that as reported experience rather than measurement.

We do not link out to competitor review directories such as G2, Capterra, or TrustRadius, and we do not use their star averages as an input to anything we publish. An aggregate rating assembled from an unknown mix of reviewers is not evidence we can trace, so it has no place in a profile.

How pricing is handled

Where a vendor publishes prices, the profile reports the figure with the plan name it belongs to and the date it was read. Profiles with a figure verified that way carry a visible "Pricing checked" date; every other profile says plainly that its pricing is not independently verified. Vendors change prices without telling anyone, so treat any figure as a starting point and confirm it before you negotiate.

Quote-only vendors are stated as quote-only. We do not reverse-engineer a number from a press mention or an old contract, and we do not publish a range we cannot source. Instead the page names what drives the quote, usually seat count, a platform fee, a usage tier, contract length, or which modules are in scope, so you know what the vendor will be pricing against.

What we do not do

Being clear about the gaps matters more than sounding authoritative, so here is what you will not find on this site:

• No scores or star ratings. There is no numeric score, no five-star rating, and no weighted model producing one. The rubric drives the written verdict, the fit guide, and the cautions, because a tool that is wrong for a ten-person team can be the right pick at two hundred seats and a single number hides that.
• No user reviews. SalesOpsClub does not run a user review program, does not collect ratings from readers, and does not republish vendor-supplied testimonials as review content.
• No hands-on testing claims. We do not run a testing lab, and unless a page says otherwise, an assessment is desk research rather than a product trial we ran. We do not claim vendor briefings we did not take.
• No invented people or numbers. Pages are credited to Rajat Gupta, a real person with a public profile, and to nobody else. There is no invented reviewer persona, no panel, and no reader survey, so you will not see a sample size, an hours-tested count, or a satisfaction statistic anywhere on the site.

Corrections

Pricing, packaging, and integration detail go stale faster than anything else on a software page. If something here is wrong or out of date, tell us through the contact page with the page URL and a source for the correct information. Vendors use the same route as readers.

We check every report, fix confirmed factual errors, and update the review date on the page. A correction fixes facts. It does not change a verdict unless the facts behind that verdict were wrong, and it is not a route to having cautions removed.

Commercial relationships and independence

SalesOpsClub does not currently use affiliate links or sell sponsored placements, and there is no separate disclosure document because there is nothing yet to disclose. We are open to clearly labeled sponsorship on the terms set out on Advertise. If that changes, any sponsored or affiliate link will be labeled where it appears.

What stays fixed either way: a vendor cannot pay to be listed, removed, moved up a category list, or given a softer verdict. Sponsorship can buy visibility, never a conclusion. The full position is on the editorial disclaimer.