Methodology

Every claim about what a platform allows comes from that platform own documentation or policy page. We record the URL, the date it was read, the API version where one applies, and the person who owns rechecking it. A claim without those four things does not go on the site.

Platform capabilities

• Before a connector starts, and again before it carries customer traffic.
• Every month for platform changelogs and vendor pricing.
• Every quarter for competitor plans, community rules and legal documents.
• Immediately after any platform rejection, enforcement notice, deprecation, or an unexplained change in publishing or analytics behaviour.

• Every comparison states who each product is best for, including when that is not us.
• Every comparison carries the research date and links the primary pricing and capability sources.
• A missing capability is labelled either as something we have not built or as something the platform does not allow. These are different sentences and we never merge them.
• We do not use another company customer logos, quotes or interface screenshots, and we do not claim an endorsement we do not have.

Comparisons

Any number drawn from customer activity states its sample, its exclusions, its metric definition and its privacy threshold, and is aggregated so no workspace can be identified. If a sample is too small to publish safely, we say that instead of publishing it anyway.

A model may research, outline, translate, check and format. A named person owns every claim, edits the piece and keeps it current. We do not publish unreviewed generated articles, and we do not generate the screenshots.

AI Use and Generated Content Policy

When a page is wrong we correct it in place, add a dated correction note, and list the correction on the changelog. When a page is too stale to fix we retire it rather than leaving it up.