Two prices are fixed. One has a published floor. One is quoted after scoping, because its cost depends on your platform, your license and your drivers. Everything free stays free.
A working session with the stakeholders, then the scoped measurement specification that comes out of it.
Ten business days. Your current measurement framework, scored against the standard, with the changes that would move it most.
Quoted per period once scope is set. It moves with the platform you license, how far back that license reaches, the human-verification ceiling and the number of drivers.
Assess, scope, build, hand off. At the end your team runs it without me.
Most teams do not need a vendor forever. They need a method, a specification and someone alongside them the first two times they run it. This is that engagement, and it is built to end.
What you have now, scored against the four-part standard. What your license can do, including how far back it reaches.
PBI with your stakeholders. Persona statements, priority markets, the competitive set, source authority, and the drivers with their weights.
MRS configured on your coverage. First period scored by me with your team watching, then calibration: your analysts score the same articles and we reconcile the differences.
Second period built by your team, reviewed by me. Scoring guide, verification protocol, templates and the written specification, all yours.
None of these are gated, none require an account, and none of them expire. A method nobody can inspect is an opinion with a number attached.
100 Fortune 1000 companies scored monthly on open data, with the query and the article behind every figure.
Every tool from the appendix, interactive, in your browser. No software, no account, nothing transmitted.
Fifteen questions, your score against the field, and the three answers costing you most. Built with the DDC practice at Meltwater.
Because the scope is fixed. Ten business days, a defined set of outputs, and a specification you keep. A day rate would make it my interest to take longer.
It is the work that determines what gets measured, so it is the most valuable thing in the engagement, not the sales call before it. It is credited against what follows, so nobody pays for it twice.
Because scoping is short and it is the decision everything downstream inherits. The audit is the opposite: priced to be easy to say yes to, not to reflect the days in it. Paying by elapsed time would be paying for the wrong thing in both cases.
Its shape is fixed and its size is not. One business unit with six people trained is a different engagement from four regions with twenty, and pretending otherwise would mean either overcharging the first or underdelivering the second.
Four things move it and none are known before scoping: which platform you license, how far back that license reaches, how many articles a person verifies each period, and how many drivers are scored. A list price would be a guess I would then have to correct.
Media licensing. The Brief runs on the platform you already license, whichever one that is. If you do not have one, it can run on open data instead, the way the public index does, and the report says which it used.
The questions procurement, security and legal ask first, answered before they have to ask.
Client work runs on an export from the media platform you already license. No credentials to your platform are needed and nothing is scraped. Your coverage is used for your engagement and nothing else.
Many platform contracts allow exports to be shared with a consultant working on your behalf; some restrict it. Your contract is checked in scoping, before any data changes hands. Where it does not allow it, the work is done alongside your team on your own systems.
Each Brief is a single self-contained file with no external calls and no tracking, delivered by whichever channel your security team prefers. Nothing you receive depends on an account that can lapse.
A mutual NDA is signed before any data is shared. Engagements are contracted and invoiced by measuredPR, LLC, doing business as measuredI/O. Security questionnaires are answered in writing.
measuredI/O is one person, and that is why the method is published, the specification is yours, and the 90-Day Build ends with your team running the loop. If I were unavailable, you would keep the specification, the scoring guide, the verification protocol and every report.
The book's foreword is by Meltwater's CEO and the maturity assessment is built with Meltwater's DDC practice. Neither makes Meltwater a requirement. The method reads coverage, not a vendor.