The
Audit Standard
How we build CRM buyer pages, what we verify, and where the limits of the content are.
StackCompare is being rebuilt around a smaller CRM editorial system. The goal is not maximum page count. The goal is a smaller set of pages that help a buyer make a cleaner software decision.
1. What we verify
For indexed CRM pages we try to anchor the page in three things:
- Vendor sources: pricing pages, product documentation, and primary product messaging.
- Editorial fit analysis: who the tool fits, who should avoid it, and which tool to compare next.
- Page-level evidence: reviewer notes and update logs visible on the page.
2. What we do not claim
We do not want the methodology page to overstate the system. Unless a page explicitly says otherwise, a StackCompare review is not a commissioned lab benchmark, a customer survey, or a formal hands-on implementation audit.
Current quality rule
If a page sounds confident but cannot show source logic, decision logic, or a meaningful reason to exist, it should not stay in the indexed editorial set.
3. AI assistance
AI can help produce structure, outlines, or first drafts, but publication requires a manual editorial pass. We are actively replacing templated review pages with curated CRM review briefs and visible methodology blocks.
4. Commercial links
Some pages include tracked vendor links or affiliate links. Those links are allowed, but they should never decide the verdict. The page should still stand on its own as buying guidance even if the link is removed.