CONTACT INTELLIGENCE FOR WATER-UTILITY SELLING

    There is no decision-maker. There is a map.

    AquaIntel builds a stakeholder map for this kind of purchase: who uses, who signs, who wrote the spec. Verified labelled verified, candidates labelled candidates.

    There is a map. Who uses it, who signs it, who wrote the spec, rebuilt from names in the record. Verified marked verified, candidates marked candidates.

    Names in context, not a directoryIllustrative utility, meter replacement

    Salespeople in this market are not afraid of calling. They do not know whose phone.

    The title you are looking for does not exist. A utilities director in one town, a public works superintendent in the next, a board that meets monthly in the third. The org chart was never published. Contact databases are good at companies and thin on this long tail.

    The answer is in the minutes, names in context, not a directory entry.

    You have the accounts. Now you need the human beings.

    You already have accounts worth approaching, from monitoring, from your territory, from a short screen to ten or twenty. Now you need the people who sit on this kind of purchase.

    Not for

    • Spray-and-pray list building
    • A ZoomInfo replacement
    • “2,000 contacts narrowed”
    • Utilities buying software for themselves

    The job, as it exists today

    Every other industry solved the lookup a decade ago. This market breaks it in three places.

    The title does not exist.

    There is no one decision-maker. Titles vary by town.

    The org chart was never published.

    It lives in who reports, who signs, who is copied.

    The tools that work everywhere else stop at the city limits.

    Coverage is decent for the biggest systems and thin below that, inverted from where the market is.

    The obvious version is a lookup: find the org chart, find the title, find the address.

    Then decay: someone retires, a role merges, nobody sends a note. A contact list is a photograph of an organization that has already changed.

    WHAT THE WORKFLOW DOES

    Not a directory. A map rebuilt from the record.

    1. Finds people in the documents monitoring already reads

      Names in context: who presented, who signed, who was copied.

    2. Reconstructs structure from hundreds of mentions

      An inference, and labelled as one.

    3. Infers the email convention from addresses that have leaked in public packets

      First initial, dot, surname. Or not.

    4. Generates ranked candidates and verifies what it can

      A source or a bounce test. Nothing else counts.

    5. Hands over a stakeholder map per product category

      User, signer, and the consulting engineer who wrote the spec.

    What lands on the desk

    Predictions are candidates until confirmed.

    By a source or a bounce test. A predicted address is never written into the contact graph as a verified fact.

    NAMES IN CONTEXT, NOT A DIRECTORY

    Illustrative utility · meter replacement

    1. Board minutes · April

      Ms. Ortega, Utilities Superintendent, presented the AMI evaluation. Board directed staff to proceed with a pilot.

    2. Contract award · June

      Resolution 26-118. Authorizes the City Manager to execute a task order with the engineer of record for meter system design.

    3. Public packet, appendix · August

      Correspondence cc: d.ortega@[city].gov, j.reyes@[city].gov. Address convention: first initial, dot, surname.

    Stakeholder map for this purchase

    Uses it
    Utilities Superintendent (presented the evaluation)verified
    Signs for it
    City Manager, under Resolution 26-118verified
    Wrote the spec
    Engineer of record on the design task ordercandidate
    Meter shop lead
    Named in the pilot report; no address publishedcandidate
    Not found
    Purchasing contact. Never appears in the record. Says so.

    What this is not.

    The scope is narrow so the map is trustworthy. Six things we will not do, and why.

    • It does not send mail

      Drafts can live in a related workflow. The send stays in your stack.

    • Direct lines and personal addresses are out of scope

      They are not public.

    • We are not another ZoomInfo

      Databases sell coverage. This rebuilds who sits on this purchase.

    • We do not become your CRM

      The map lands in the system your team already uses.

    • A utility that never published a staff address still yields names

      The workflow says so rather than guessing.

    • Output is not five hundred people to email

      It is a small map for the ten or twenty accounts you are actually working.

    Where this sits in the loop

    All solutions

    1. Screen

    2. Monitor

    3. Map the room

    4. Clocks

    5. Draft

    6. Catch the bid

    7. Fit-check

    1. Screen

    2. Monitor

    3. Map the room

    4. Clocks

    5. Draft

    6. Catch the bid

    7. Fit-check

    Questions we get on every call

    WHAT YOU GET ON A CALL

    One purchase category, one utility, one map

    A walkthrough on an illustrative utility, not a named customer. No self-serve plan. No trial seat dump.

    1. Names in context

      Where people appear in the record and what they were doing there

    2. Verified vs candidate

      What a source confirmed and what is still an inference

    3. The stakeholder map

      User, signer, spec author, for this kind of purchase