How we score
marketing tools.
Every score on Toolpulse is an editorial decision — documented, sourced and versioned. No anonymous reviews. No pay-to-rank. No black-box algorithm. This page explains exactly how we work.
Editorially independent — always
Toolpulse scores are created by our editorial team — not by users, not by AI alone, not by vendors. Every score is based on a documented 6-step review process that takes 3–4 hours per tool.
Verified Pro Listings give vendors visibility — signal inbox, analytics, profile editor. They do not influence scores. A paying vendor with a poor score stays poorly scored. That is the deal and it is non-negotiable.
Scores cannot be bought
No vendor has ever paid for a better score. No vendor ever will. If a paying subscriber receives a poor score and cancels — the score stays.
Every decision is documented
Each criterion score has a written rationale citing specific, verifiable sources. "This tool feels good" is not acceptable — concrete facts are.
Affiliate relationships are declared
If we earn a commission from a tool link, it is labelled on the page. Affiliate partner scores follow the identical review methodology.
What every score is made of
Every tool is evaluated against five equally weighted criteria. Each criterion score runs from 1 to 10. The five scores are averaged, then adjusted by the sentiment factor.
Usability
How quickly does a new user reach their first result?
20%
What we evaluate
Time-to-value from signup · navigation intuitiveness · learning curve after 30 days · mobile experience · onboarding quality · documentation completeness
Primary sources
Hands-on product trial · G2 ease-of-use rating · G2 review excerpts · Capterra usability score · YouTube demo analysis
Features
Does the tool solve the problem fully — or only on the surface?
20%
What we evaluate
Completeness of core feature set · integration ecosystem · API availability · automation depth · reporting quality · feature velocity (changelog)
Primary sources
Official feature page · changelog (last 6 months) · developer documentation · G2 feature ratings · category benchmark comparison
Value for money
Do you get what you pay for — in context of the target audience?
20%
What we evaluate
Entry price for typical usage · scaling costs at 10× volume · freemium quality · hidden costs (onboarding, premium support) · pricing change history (last 12 months)
Primary sources
Official pricing page (dated screenshot) · Wayback Machine for history · G2 value-for-money rating · community reactions to price changes
Support & documentation
Do you get help when you need it?
20%
What we evaluate
Documentation completeness · support channels available · response time (from user reports) · community quality · onboarding support · status page availability
Primary sources
Own support test · G2 customer support rating · Glassdoor support team trend · Reddit and community sentiment
Data privacy & GDPR compliance
Unique to ToolpulseThe only criterion no competitor scores. Mandatory for European businesses — so it is mandatory here.
20%
What we evaluate
EU server location documented · DPA (data processing agreement) available · Standard contractual clauses (SCC) · ISO 27001 or SOC 2 certification · No GDPR enforcement actions (last 24 months)
Primary sources
Official privacy policy · DPA request verification · GDPR Enforcement Tracker · BfDI and EDPB databases · ISO/SOC certification registry · Sub-processor list
Scoring matrix (0–2 pts each)
Score conversion
The formula
Total score = (usability × 0.20)
+ (features × 0.20)
+ (value_for_money × 0.20)
+ (support × 0.20)
+ (gdpr × 0.20)
± sentiment_factor (max ±0.5)
≥ 8.5
Top Pick
Best in category. Strong across all criteria.
7.0–8.4
Recommended
Solid choice. Minor weaknesses in 1–2 areas.
5.5–6.9
Conditionally
Works for specific use cases. Read the caveats.
< 5.5
Not recommended
Significant issues. Explore alternatives.
Sentiment factor (±0.5 maximum)
A 30-day rolling signal feed adjusts the base score by up to ±0.5 points. Positive signals — major feature launch, funding round, price reduction — push the score up. Negative signals — unjustified price increase, data breach, GDPR enforcement — push it down. Minimum change threshold before publication: 0.2 points. Signals are sourced from 30 automated data sources updated daily.
When and why scores change
Scores do not change on a fixed schedule. Every change has a documented trigger. All changes are visible in the public score history on each tool profile.
Score history — public and permanent
Every score change is logged with: date, trigger type, scores before and after, criteria affected, and a public two-sentence explanation. Nothing is silently adjusted. The history is permanent.
2026-04-14 · pricing_change · 7.8 → 7.5
"Price increased from €49 to €79/mo in March 2026 without new features. Community reaction on Reddit and G2 predominantly negative."
What happens when a vendor disagrees
Vendors may dispute scores they believe are factually incorrect. We take factual disputes seriously and investigate every one. We do not adjust scores based on opinion or commercial pressure alone.
Dispute received — confirmed within 24 hours
Score freeze activated. Written confirmation to vendor. Internal dispute document created with date, vendor, and contested points.
Fact vs. opinion assessment
Factual disputes — wrong server location, outdated pricing — are investigated and corrected if valid. Opinion disputes — "our UX is better than your score suggests" — require new factual evidence to proceed.
Accepted dispute example
"Our EU server location is Frankfurt, not London as stated." → Factual, verifiable — will be investigated.
Declined dispute example
"Our interface is more intuitive than your score suggests." → Opinion without new evidence — declined.
Decision communicated — within 14 business days
Written response: accepted or declined with full rationale citing sources. Score freeze lifted. Outcome archived. If accepted, score updated with public explanation in the score history.
Where our data comes from
Automated · checked daily
Editorial · per review
We only use aggregated review data
We never reproduce individual review text from G2, Capterra or other platforms. We use overall ratings and total review counts as data points — always cited and linked to the source. This respects copyright and avoids the dependency that makes other directories' data unreliable over time.
How to verify our work
Score history
Every tool profile shows a full public score history — date, trigger, what changed and why. Nothing is silently adjusted. Ever.
Criterion rationale
Each criterion score has a published written rationale citing specific sources. Visible on every tool profile under "Score breakdown".
Contact editorial
Spotted an error? Think a score is wrong? Write to editorial@toolpulse.io with evidence and we will review it within 14 business days.
This methodology is version-controlled
Any change to how we score tools is documented here with a version number and date. You can always see exactly what methodology was in place when a score was set.
Current version: v1.0 · May 2026 · editorial@toolpulse.io