Qualification
Qualifying the request: inventory, ranking, ownership
For CIO, brand, legal and IT roles, the request form works best from a concrete inventory rather than a generic brief. It should name which surfaces exist, whether anything is ranked by priority, and who owns each. With that, dotNice can separate a one-off exposure map from a standing programme, a defensive-registration build or a monitoring-to-enforcement integration — and recommend clearly what to inventory, rank and route first.
The review is most valuable when the buyer can describe the current gap: whether the portfolio has an auditable inventory, whether a core mark is exposed across ccTLDs without defensive coverage, whether a third-party registration is causing customer confusion in a priority market. A request is qualified when it states the surfaces, the priorities and the owners. The output is a scoped decision pack — a ranked exposure map with owners — not a service catalogue.
The cost of waiting belongs in the same record. An unmapped surface means the brand reacts to incidents it could have pre-empted, while renewal and defensive budget drifts to the wrong markets. Quantifying that — missed pre-emption, thinning coverage, slow response — is what moves brand exposure from a backlog item to a funded decision with an owner and a cadence.