## What the Vedy Score Measures
Every tool review here ends with one number between 0 and 10. That number is the Vedy Score.
It exists because "good" and "worth it" mean nothing on their own. A score forces us to say how good, and where the tool loses points. You may disagree with a number, but you should never have to guess what it means.
A Vedy Score is a snapshot of one tool at one version, tested by hand. It is not a summary of a feature page.
## The Four Sub-Scores
Four sub-scores sit under the main number. Each one answers a different question, so a tool can be strong in one and weak in another.
- **Ease of Use** — how long a normal task takes without opening the documentation.
- **Value** — what the tool gives back for the money and time it asks, judging the plan you would actually need.
- **Performance** — speed and reliability under a real workload. Failed runs and crashes count against it.
- **Design** — how the interface is organised, and whether it stays predictable as projects grow.
A sub-score is dropped only when a category does not apply. An empty sub-score means we could not measure it fairly.
## The Scale
The bands are the same for every tool, and the score card uses the same colours:
- **8.5 – 10 — Excellent.** Few tools land here. A score this high needs a reason we can point at.
- **7 – 8.5 — Good, with caveats.** Worth using, with at least one limitation worth knowing before you commit.
- **5 – 7 — Mixed.** It does the job, but something important gets in the way. Read the caveats before you pay.
- **Below 5 — Not recommended.** The tool fails at the job we tested it for.
## How We Test
A feature list cannot earn a score. Scoring starts with a working account or a licence, and with hands-on use.
- **Two weeks minimum.** Short tests flatter tools that demo well and punish tools that hold up over time.
- **One real deliverable.** A report, a landing page, an automation that runs on its own. Something the week needed anyway.
- **Counted steps.** Where the workflow is the point, we count manual steps before and after. "Faster" is not a finding; 12 steps down to 4 is.
## Where the Test Units Come From
Most tools here are paid for by us, with our own money. Some are tested on a free trial. Some vendors give us access to a paid plan for review.
A provided unit never buys a better score, and it never buys silence. If a tool we did not pay for has a problem, the problem goes in the article, worded exactly as it would be for a tool we bought.
## When a Score Changes
Tools change, so scores change. If pricing, limits, or a core feature moves after publication, we retest the affected part and update the article.
- The update date on the article changes.
- A note at the end records what changed and why the score moved.
- A score never changes quietly.
## Conflicts of Interest
VedyRating is funded by affiliate links. Some links pay us a commission when a reader subscribes.
That money does not enter the scoring sheet. We set scores while testing, before anyone checks whether a tool has an affiliate program. Tools with no affiliate program still get reviewed, and they can still win. The size of a commission buys nothing.
An offer to pay for a score ends the relationship. We refuse it and stop covering the vendor.
## Comparing Two Scores
Scores can be compared only inside one category. An 8.4 in AI Tools is not the same claim as an 8.4 in UI Design, because each category is held to different standards.
In a head-to-head article, both tools carry their own score card and their own sub-scores.
## Asking About a Score
If a number here looks wrong to you, say so. We keep the notes behind every review and can show which part of the test produced it.
Send corrections to
Vedy Crew. Fixing an error is cheaper than defending one.
