SaaSComparely publishes under a team editorial model, not a single named author. This page explains who we are, how our articles are produced, how we handle research and verification, and what we do when information changes or errors are reported.
We believe you should understand how the content you rely on for software decisions is produced. That transparency is not a formality — it is the foundation of the trust we are trying to earn.
Who We Are
SaaSComparely is an independent software research publication. Our editorial team is a small group of researchers, writers, and editors focused exclusively on business software comparisons, pricing analysis, and buying guidance.
We are not a SaaS company. We are not affiliated with any software vendor. We do not sell implementation services or consulting. Our only product is well-researched, clearly reasoned editorial content about software — produced without commercial influence from the tools we cover.
We publish under a team byline because that is the honest description of how this content is produced. Software comparisons that are genuinely useful require research across pricing pages, product documentation, user communities, changelog histories, and — where we have direct access — hands-on tool evaluation. That work is distributed across a team, reviewed collectively, and published under shared editorial accountability.
How Articles Are Produced
Every SaaSComparely article follows a structured four-stage process:
Stage 1 — Research & Source Gathering
Before a single word is written, our team identifies and gathers the primary sources that will anchor the article. For a comparison article, this means:
- The official pricing page for every tool covered, captured and dated at time of research
- Official feature documentation, help centres, and product changelogs
- Integration directories and third-party compatibility documentation
- Community signal research — Reddit communities, LinkedIn discussions, product-specific Slack groups, and G2/Capterra review aggregates (used as directional signal for real-world complaints and praise, not as our primary editorial verdict)
- Where direct tool access is available: hands-on evaluation using the free tier, trial access, or publicly available demo environments
When direct access to a tool is not available — typically for high-ticket enterprise platforms with sales-gated access — we disclose this in the article and explain how we compensated (e.g., documentation review, community research, and analysis of third-party evaluations).
Stage 2 — Drafting
Our editorial team uses AI language tools to assist with initial research organisation, comparison framework structuring, and first-draft production. This is a standard part of our workflow that we disclose transparently.
AI assistance in our process means: AI helps structure information, organise criteria into comparison frameworks, and produce initial drafts that the human editorial team then works from. It does not mean: AI-generated text is published without review, or that AI determines our editorial conclusions.
Every draft produced with AI assistance is reviewed and substantially rewritten by a human editor before proceeding to the next stage. No article is published as raw AI output.
Stage 3 — Editorial Review & Fact Verification
Before publication, every article goes through an editorial review that covers:
Factual accuracy — Every feature claim, pricing figure, and integration statement is verified against its primary source. If pricing has changed since initial research, it is updated before publication. If a feature claim cannot be confirmed from an official source, it is removed or flagged as unverified.
Framing and balance — We review every comparison conclusion to ensure it is supported by the evidence presented and genuinely serves the reader’s decision-making need — not the interests of any tool covered. If our conclusion would disproportionately favour a tool with which we have an affiliate relationship, we examine the reasoning more closely.
Completeness — We check whether significant use cases, buyer types, or limitations have been omitted. A comparison that does not acknowledge what a tool is genuinely bad at is not a useful comparison.
Currency — We check whether any major updates to the tools covered have occurred since research began. If material changes are found, the research is updated before publication.
Stage 4 — Publication, Dating & Scheduling
Every article is published with:
- A Published date — when the article first appeared
- A Last Reviewed date — when the article was most recently reviewed for accuracy and currency
- A Pricing verified as of [month, year] notice on any article containing pricing information
How We Handle Updates
The SaaS market changes constantly. Tools add features, change pricing, lose integrations, get acquired, or shut down. Content that was accurate six months ago can become meaningfully wrong without any error on our part — simply because the product changed.
Our update process works as follows:
Scheduled reviews — Every published article is assigned a review date based on the volatility of the category. Pricing-focused articles are reviewed every three to four months. Feature comparisons are reviewed every six months. Foundational explainer content is reviewed annually.
Trigger-based updates — When a major change occurs (significant pricing revision, a substantial product update, an acquisition, or a product discontinuation), we update immediately and do not wait for the scheduled review. These updates are noted in the article with a “Updated [date] to reflect [change]” notice.
Reader-reported updates — If a reader reports that information in an article is outdated or incorrect, we investigate and, where the report is accurate, update the article and publish a correction notice.
How We Handle Corrections
We make mistakes. Pricing changes before we catch it. A feature we described as available is later removed. A tool we described as a niche product raises a significant funding round and expands its scope. When errors are reported or discovered, we correct them transparently.
Our correction process:
- The reported error is investigated against current primary sources
- If confirmed, the article is corrected
- A correction notice is added to the article: “Correction [date]: [brief description of what changed and why]”
- The Last Reviewed date is updated
If you believe something in a SaaSComparely article is factually incorrect, please email us at info@saascomparely.org with the article URL and the specific claim you are questioning. We respond to every credible correction request.
How We Use AI
We use AI tools as a standard part of our editorial workflow. We are transparent about this because we believe readers have a right to understand how the content they rely on is produced.
What AI does in our workflow:
- Assists with organising research from multiple sources into comparison frameworks
- Produces initial structural drafts that human editors then review and substantially rewrite
- Helps identify gaps in coverage during the review stage
- Assists with formatting and consistency checking
What AI does not do:
- Determine editorial conclusions — which tool is better suited for a given use case is a human editorial judgment based on the evidence gathered
- Replace source verification — all factual claims are verified by a human editor against primary sources
- Publish content without human review — every article goes through human editorial review before publication
Articles produced with significant AI assistance carry a disclosure note at the bottom of the article. All articles on SaaSComparely meet this threshold; the disclosure is present across the site.
Our Editorial Independence
SaaSComparely earns revenue through affiliate referral arrangements. When readers click certain links and subsequently purchase a software subscription, we may receive a commission from the software vendor.
This arrangement does not influence:
- Which tools we choose to cover
- How we structure our comparisons
- What conclusions we reach
- How we handle updates when a tool’s performance changes
We cover tools with no affiliate relationship. We recommend cheaper alternatives over more expensive ones when they genuinely serve the use case better. We change our editorial conclusions when tools change — regardless of whether that change benefits or disadvantages an affiliate partner.
We do not accept payments from software vendors for placement, inclusion in comparisons, or favourable editorial treatment.
Contributor Transparency
SaaSComparely accepts editorial contributions from verified external contributors who have genuine, direct experience with the software they write about. All contributors are required to disclose any financial or professional relationship with tools covered in their submission.
Contact the Editorial Team
For corrections and factual disputes: info@saascomparely.org Subject line: Editorial Correction — [Article Title]
For contribution pitches: info@saascomparely.org Subject line: Contributor Pitch — [Proposed Title]
For general enquiries: info@saascomparely.org


