Published May 4, 2026. This page describes evidence categories and disclosure principles that may be used in Overloop buyer guides. The method varies by article, so rely on the methodology note, cited sources, and publication or update date shown on the specific page.
What we test
Depending on the category and the evidence available, a buyer guide may consider the following dimensions. The article-specific methodology note should identify what was actually reviewed and distinguish sourced facts from editorial judgment.
Deliverability
Inbox vs spam placement across Gmail, Outlook, GMX, Free.fr, Libero, and corporate Microsoft 365 tenants. Bounce rate, hard vs soft, catch-all behaviour.
Multichannel coverage
Email, LinkedIn, calls, WhatsApp, SMS - what is native, what runs through Zapier duct tape, what breaks at step 7 of a sequence.
Pricing transparency
Price at 1 seat, 3 seats, and 10 seats; credit caps; and annual versus monthly terms. Pricing should be tied to the article's review date and rechecked on the vendor's current pricing page before purchase.
EU compliance
RGPD posture, data hosting region, DPA quality, opt-out mechanics. Read against actual CNIL / AEPD / Garante / Wettbewerbszentrale enforcement.
AI quality
Personalisation quality, hallucination risk, signal quality, and model behavior. Any hands-on sample size should be stated on the article that reports it.
Integrations
Native vs Zapier vs API. CRM (HubSpot, Pipedrive, Salesforce), data providers, calling, calendar. What syncs both directions, what does not.
Support response time
When support is evaluated hands-on, the article should state the test date, channel, first-response time, and whether the answer resolved the issue.
Evidence depth
Review depth varies with the article, access level, and question being answered. A page should not imply a universal test period; it should state the evidence actually used for that edition.
- Documentation review: current product pages, help documentation, pricing, DPA, and subprocessor information where relevant.
- Hands-on access: trial or paid-seat behavior only when the article explicitly says what was exercised and when.
- Comparable criteria: the same decision questions for tools included in that edition, subject to disclosed access limits.
- Published sources: primary regulatory and vendor sources linked inline with dates where available.
For product or pricing decisions, treat the article date as the evidence boundary and confirm current behavior in your own trial and contract review.
Who tests
Articles may name contributors with different lenses. The byline and methodology note on the specific page indicate who contributed to that edition.
These lenses help separate deliverability, pricing, regulatory, and operator-fit questions. Their presence on this page does not imply that all three reviewed every article; use the contributors shown on the article itself.
Where data comes from
Buyer guides should name material sources inline and distinguish vendor-supplied facts, third-party evidence, and editorial judgment. Depending on the article, relevant source types include:
What we don't accept
The fastest way to wreck reader trust is to source-launder. The list below is what would never make it into a comparison piece on this blog.
- Paid placements or "sponsored ranking"
- Affiliate-only reviews (kickback bias)
- Vendor-supplied screenshots without us re-shooting
- Anonymous reviewer claims (no name = no claim)
- Marketing fluff masquerading as data
- Untested-on-our-side feature claims
- "X said on a podcast" without a transcript link
- G2 / Capterra rating imports without our own test
Tools sometimes ask to be added to a comparison in exchange for a backlink swap or a co-marketing push. The answer is no. Our position cannot be bought, and that is the only reason readers should keep paying attention.
Update cadence
Product details and pricing can become stale quickly. Use the publication or update date displayed on the specific article and confirm current facts before making a purchase.
How a verdict is built
A buyer guide can use the following framework when the article-specific methodology supports it. It is a decision aid, not a claim that every page follows an identical process.
Stage 1 - Independent scoring
Define the relevant criteria for the category and record the evidence source for each score or judgment. If multiple contributors are involved, the article should name them rather than implying a standing review panel.
Stage 2 - Cross-review
Compare evidence across criteria and flag conflicts or access limits. A tool may fit high-volume Anglo SaaS and not French mid-market; the recommendation should name the buyer context that explains the difference.
Stage 3 - Contradiction resolution
Where sources or observations conflict, state the uncertainty, run an additional check where practical, or narrow the verdict to the buyer and use case the evidence supports.
Stage 4 - The verdict ships
The published page should expose its author or contributors, date, material sources, disclosure, and fit rationale. If a verdict contradicts your real-world experience, send the article URL and supporting source to corrections@overloop.com.
Conflicts of interest disclosure
Two facts you should know about this blog before reading any comparison:
- Overloop is one of the tools we cover. When Overloop appears in a comparison piece, the same scoring rules apply. We have published comparisons where Overloop loses on a specific dimension to a specific competitor - and we have left those verdicts unchanged because changing them would defeat the whole point of running this blog. When Overloop wins, we still source the claim against the same evidence bar as any other tool.
- We do not run an affiliate program on this blog. No "buy via this link, we get a kickback" layer. The CTAs on the blog point to Overloop because we own Overloop, not because there is a hidden commission tier behind any vendor link.
Any article-specific sponsorship, affiliate relationship, or material conflict should be disclosed on the affected page and dated.
Author bylines
Use the byline shown on the article to identify the author or contributors. Current author pages include:
- Nicolas Finet - CEO Sortlist + Overloop (founder voice, market data, pricing math, regulatory posture)
- Vincenzo Ruggiero - Co-founder Overloop (deliverability, sequence design, hands-on testing protocol)
- Nathalie Saikali - Head of Sales Overloop (operator pass, French / Belgian / Swiss market relevance)
Where a page names multiple contributors or a guest author, its schema and disclosure should reflect the people actually involved in that edition.
Contact for corrections
Spotted an error or a stale claim?
Email corrections@overloop.com with the article URL, the issue, and a source. The team can review the evidence and date-stamp material updates where appropriate.
Send a correction