What this site compares
PR platforms compared side by side, on cost per user per year in the Netherlands
One platform against another, on the points that decide it: price, data location, integrations, and what each vendor documents in public.
The short answer
- You pay EUR 1,325 per user per year for De Perslijst, 2 logins from PR-Dashboard. The page prints EUR 2,650 per year for two logins.
- You pay EUR 2,640 per user per year for Essential from Mynewsdesk. The page prints EUR 220 per month.
- Both figures were read on the vendor’s own price page on 31 August 2026. Every comparison here uses the same five points, and says so when a vendor publishes nothing on one of them.
On every axis a dash sits next to the platform that puts more of it in writing.
PR-Dashboard
De Perslijst, 2 logins, published as EUR 2,650 per year for two logins
EUR 1,325 per user per year
pr-dashboard.nl/meer/veelgestelde-vragen, read 1 September 2026
Mynewsdesk
Essential, published as EUR 220 per month
EUR 2,640 per user per year
mynewsdesk.com/en/plans/, read 31 August 2026
Topics on this site
Pick the comparison you need, from the eight on this site
Every topic puts two platforms next to each other on the same five points, and the price per user per year comes first.
PR-Dashboard compared with the alternativesPR-Dashboard against one named platform at a time, on the same five points.25 comparisons
Journalist databases compared head to headJournalist databases: how many contacts each vendor claims, and how the list is broken down.25 comparisons
Press release distribution services comparedPress release distribution: what a single send costs and which media are included.25 comparisons
Online newsroom providers comparedOnline newsrooms: what the hosted page does, and what the vendor documents about it.25 comparisons
Dutch PR tools versus international platformsDutch tools against international platforms, including where each one hosts your data.25 comparisons
PR software versus a PR agencyDoing it with software against handing it to an agency, with both bills written out.25 comparisons
Monthly versus yearly PR subscriptionsPaying by the month against paying by the year, converted to one figure per user per year.25 comparisons
Switching from one Dutch PR tool to anotherMoving from one Dutch PR tool to another: exports, contacts and what carries over.25 comparisons
The points we compare on
The five points every comparison on this site is judged on
- 1
Point 1: Cost per user per year
The published amount, divided by the logins the vendor includes. A monthly price is multiplied by twelve first, so nothing is compared across periods.
A vendor that prints no amount at all is not placed on this axis and is named as a vendor without a public price, so a missing figure never turns into a guess.
Read from the price page of each vendor, on 27 and 1 September 2026.
- 2
Point 2: Where the data is hosted
Whether the vendor names a country or a region for the data itself.
A country, a region or a city is something a vendor can be held to later. Wording such as secure European hosting names no place, so it does not count as an answer.
Read from the page where the vendor names a location: a pricing page, an FAQ or a security page.
- 3
Point 3: Integrations named on the vendor's own pages
Counted by name, not as a promise that everything connects to everything.
An integration counts once the vendor names the product on the other side of it. Everything connects to everything is a claim, not a connection.
Counted on the integrations page or the product page of each vendor.
- 4
Point 4: Pages in Dutch on the vendor's own site
Whether the vendor publishes anything in Dutch at all, and how many pages.
A page in Dutch is a page the colleague who has to approve the purchase can read without help, which is why the count is worth having.
Counted from the vendor's own sitemap, one entry at a time.
- 5
Point 5: Customer stories published
Counted as separate pages a buyer can open and read.
A story counts when it is a page of its own with a named organisation on it, so you can see which kind of team the platform is used by.
Counted as pages under the vendor's own customer or case section.
One comparison in full
PR-Dashboard compared with Mynewsdesk, point by point
Both columns hold what each vendor publishes on its own pages. The amount per user per year is worked out from the published price and the logins each vendor includes, so a monthly price and a yearly price end up on the same axis. Where a vendor publishes nothing on a point, the column says so.
PR-Dashboard
De Perslijst, 2 logins, EUR 2,650 per year for two logins
Mynewsdesk
Essential, EUR 220 per month
Cost per user per year
The published amount, divided by the logins the vendor includes. A monthly price is multiplied by twelve first, so nothing is compared across periods.
EUR 1,325 per user per year
pr-dashboard.nl/meer/veelgestelde-vragen, read 1 September 2026
EUR 2,640 per user per year
mynewsdesk.com/en/plans/, read 31 August 2026
Where the data is hosted
Whether the vendor names a country or a region for the data itself.
The FAQ names the Netherlands.
not documented on the pages we measured
Integrations named on the vendor's own pages
Counted by name, not as a promise that everything connects to everything.
Three, all Dutch monitoring services.
not documented on the pages we measured
Pages in Dutch on the vendor's own site
Whether the vendor publishes anything in Dutch at all, and how many pages.
31 pages in Dutch.
not documented on the pages we measured
Customer stories published
Counted as separate pages a buyer can open and read.
One published quote on the product page.
66 customer cases, counted from their own customer_case sitemap.
The same four questions put to eight platforms at once, with the source page under every cell, are on The same questions put to every platform.
What is left out of every comparison
What we do not compare, and why an opinion never gets a column here
A comparison is only useful if you can check it yourself. So three kinds of statement stay out, however often they decide a purchase elsewhere.
A vendor whose price only appears after JavaScript renders is named as such rather than converted to an amount per user per year, because we cannot read it in the page itself.
- How a platform feels to use
- Ease of use, a modern interface, a friendly onboarding: none of it can be read off a page and checked a month later. Where a vendor documents a concrete feature we put the feature in the table instead.
- What is said in a demo or a sales call
- A figure that only exists in a conversation cannot be verified by the next reader. Only what a vendor puts on its own pages goes into a column, with the page and the date next to it.
- Star ratings and review counts
- A score on a review site measures who was asked, not what a licence costs or where the data sits. We count pages, contacts, integrations and amounts, because those can be counted again.
About this site
How we read the vendor pages, and when we read them
- Step 1
Open the vendor page itself
Plain HTML, fetched without JavaScript, so what we record is what a reader and a search engine both get.
- Step 2
Copy the amount and its period
The published amount stays in view with its own period. A yearly amount is never printed next to a monthly one without saying so.
- Step 3
Convert to one figure per user
Monthly amounts are multiplied by twelve and divided by the logins the vendor includes, so both sides land on the same axis.
- Step 4
Write down the reading date
Every figure carries the page it came from and the day it was read, so you can check whether it still says that.
The comparisons on this site are written by Eva Lindeman, Koos Reinders and Anouk Terlouw. Prices were read on 31 August 2026 and 1 September 2026. Where a vendor publishes nothing on a point, the column says “not documented on the pages we measured” rather than an estimate.