PRE-RFP ACCOUNT INTELLIGENCE FOR WATER VENDORS

    Know the account before the RFP exists

    Know which utilities are funding projects that fit what you sell — months before the RFP. One assignable piece of work: this account, this development, who to call, what to say.

    21 months between being in the room at month 9 and the RFP everyone sees at month 30. The spec is shaped in between.

    Thirty-six months before the purchase orderIllustrative utility

    A water utility tells you what it will buy. In public. In writing. Usually two or three years before the purchase order.

    Board minutes. Capital plans. Budgets. Almost none of it read.

    By the time the RFP publishes, everyone already knows, and the spec has usually been shaped by whoever was in the room a year earlier.

    You sell into US water. Your territory is too large to read by hand.

    You sell into US drinking water or wastewater utilities and you already know the RFP is late. You need the year before it.

    Built for

    • Pumps
    • Treatment
    • Meters
    • Controls
    • Engineering software
    • Chemicals

    Not for

    • Utilities buying software for themselves
    • A ZoomInfo replacement
    • Another screener dashboard

    The job, as it exists today

    It works. It is also just effort, and it does not scale.

    Several hundred
    documentsto do one utility properly
    Hundreds
    of utilitiesin a modest territory
    No two
    publish alikedifferent portals, formats, schedules

    A motivated person can sit with the packets, hold three unremarkable entries across eight months, and notice they are the same story.

    That is why it never becomes the job. Not laziness. A salesperson with a number this quarter is not paid to read three hundred PDFs.

    WHAT THE WORKFLOW DOES

    Every board meeting, every capital plan, watched for you.

    1. Finds where each utility’s material actually lives

      Agendas, packets, CIPs, budgets. Portal, PDF, or scan.

    2. Pulls on that board’s schedule, not yours

      Monthly, bi-weekly, whenever the packet posts.

    3. Makes scanned packets readable

      The 300-page scan becomes text you can search and cite.

    4. Extracts signals that a procurement is forming

      For your product. Not generic water news.

    5. Resolves them into an action in the system your team already uses

      Account, development, why it matters, who, what to say.

    What lands on the desk

    Finished means work left the desk.

    If someone still has to read the output, decide what it means, and act, you still have a tool with better manners.

    THE PUBLIC RECORD, EIGHT MONTHS

    Illustrative utility

    1. Board minutes · January

      Item 7b. Staff report on disinfection byproduct exceedances at Plant 2. Staff directed to return with treatment options.

    2. Draft capital plan · May

      Line 14. Plant 2 treatment process evaluation. $250K study. FY27 placeholder for construction.

    3. Adopted budget · September

      Plant 2 process upgrade: engineering study funded. Construction FY27-28, scope TBD.

    One work item, assigned to the territory rep

    Account
    Mid-size surface-water utility, 38K connections
    Development
    Treatment upgrade forming. Study funded; construction two fiscal years out.
    Why it matters to you
    Pre-design window. Spec not yet written.
    Who to contact
    Utility director; engineer of record on the study.
    What to say
    Offer reference data to the study team before the design RFQ.

    What this is not.

    The scope is narrow so the output is usable. Five things we will not do, and why.

    • An alert feed is not the deliverable

      A feed is more reading. The deliverable is an assigned action.

    • We do not become your CRM

      The action lands in the system your team already uses.

    • We do not send the outbound for you

      Your rep makes the call. We tell them who, why, and when.

    • Installed make, model, and serial are not in the minutes

      We stop one step short. The salesperson walks in and asks.

    • Screening ends at ten or twenty accounts to understand

      Not five hundred to email.

    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 real public-record example, end to end

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

    1. Monitoring

      Where the material lives and how it is pulled

    2. Account context

      What the entries add up to for this utility

    3. The next action

      Who to contact and what to say, in your system