Start with the work
Our profiles use official product and help pages to establish positioning and specific documented capabilities. They are desk research. We do not describe them as hands-on reviews and do not adopt vendor performance promises.
Build the working checklist
- Store an exact source URL, retrieval date and claim type.
- Record the territory and scope that remain unverified.
- Review changing product statements within the configured freshness period.
- Require a separate dated record before describing a hands-on observation.
Check it against a real task
The current freshness window is 45 days. When a claim expires, the public profile hides its positioning claim and outbound research link until it is reviewed again. The stored history remains available internally.
What to take away
Prices, plan entitlements, integrations and eligibility need their own direct verification. A link to a homepage cannot substantiate a precise claim about those details.
The claim record we require
Scroll horizontally to read all columns.
| Field | Why it exists | Example of scope |
|---|---|---|
| Claim and type | Make the statement precise enough to review | Broad positioning, documented capability or observed behavior |
| Exact source URL | Allow a reader to inspect the supporting material | The official feature or help page, not an unrelated homepage |
| Retrieval date | Show when the source was actually checked | A date is not changed merely because the website was rebuilt |
| Scope and territory | Separate the established fact from unknown conditions | General documentation; plan and account eligibility still unverified |
| Review status | Keep stale or unsupported statements out of active placements | Verified official source, needs review or withdrawn |
Evidence levels should not be blended
An official page can establish that a provider documents a capability. It does not prove we have used that capability, that it will work in every account or that the vendor’s performance claims generalize. Our proposed pilot procedures are original planning guidance, not accounts of completed product tests.
What happens when evidence ages
Dated product claims use a 45-day review window. Provider pages check that window in the browser, so a static build cannot keep an expired claim active indefinitely. Stale factual text and its official research links are paused until review. Editorial checklists remain available as planning guidance, with their own visible review date.
Working files
Blank templates for your own planning. These contain no customer records and are not submitted to Sales Fit Lab.
Source, date, territory, claim type, review status and a separate testing record.