Why depth

A directory files. A map explains.

The last generation of revenue data got very good at one question: who has this title, in this country, at a company of this size. The work moved on. The filing system did not.

What changes when you move from a directory to Priorread
The job	A contact directory	Priorread
Find accounts	Headcount, industry, country, a title.	A sentence: motion, device, market, a recent change, a tie to your book.
Trust a row	A record, a freshness you cannot see, a guessed email.	A why, a source, a date, and a thin label when the signal is thin.
Work outside the US	Often a thin shadow of the US file.	Built to be asked about Lisbon, Lagos, Berlin, Zagreb, Bengaluru — and to show the record rather than a coverage number.
Prepare a call	Export, then tab-scramble when the meeting starts.	A brief before hello. A panel in Zoom, Meet, and Teams for the people who accepted.
Stay in the browser	A separate tab, if anyone remembers the login.	Sidecar on the page you opened. The page remains the page.
Hand work to an agent	A CSV in a prompt. The model improvises the rest.	MCP, skills, and an API. Permissions, a ceiling, a receipt.
Keep the CRM clean	A second database people stop updating.	Writeback of a few fields you chose. The CRM stays the record. The map stays the map.

A category contrast. Not a scoreboard against a named vendor.

What we will not pretend.

We will not quote a contact count we would be embarrassed to open. Sign in and look at a record in your market.

We will not claim a compliance badge we have not earned. The security page says what exists today and what is still a program.

We will not call a private-life surveillance feature “depth.” Device and audience signals describe products and accounts. Read the boundary in acceptable use before you write it into a prompt.

Know the room.

Know who is in the room before the email, the page, and the call, and which tie you can say out loud.