INSTALLED BASE AND CONTRACT CYCLES AS DATED ACTIONS

    Everything you sold has a clock on it

    AquaIntel turns both clocks into a dated action: this account, why it is live now, the window.

    Year 14 of 16. Contract ends September. Either clock alone sends a rep too early or with no reason. Both together date the action: open the conversation this quarter.

    Two clocks on one lift stationIllustrative utility

    A vendor selling equipment into water utilities is sitting on a forecast of its own future revenue and mostly cannot read it.

    Every pump, blower, meter, valve, and membrane you installed is still out there, ageing on a roughly knowable schedule. You invoiced for all of it. The data is yours, and unusable.

    There is a second clock that governs: who holds the service or supply contract, and when it expires. Until those two dates line up, an end-of-life nudge alone sends a salesperson to a utility that cannot buy yet.

    You sell or service equipment into US water. You have an installed base you cannot read.

    You have an installed base in your own systems, ERP, CRM, warranty, invoices, and you care about competitor installs and contract renewals you cannot see from inside.

    Built for

    • Pumps
    • Blowers
    • Meters
    • Valves
    • Membranes
    • Service contracts

    Not for

    • A “Replacement Opportunity Radar” score
    • Deal-size inventing
    • Utilities buying software for themselves

    The job, as it exists today

    The job has two halves. Most vendors have a rough sense of one and almost none of the other.

    Your installed base

    What you sold, where, how old, when the replacement conversation should start, well before the utility writes a specification. It sits unread inside the company.

    Everybody else’s

    Which competitor’s kit sits in the stations you did not win, who maintains it, when that arrangement expires. It is scattered through awards, board approvals, and maintenance discussion in the public record.

    The first half is a data problem you own. The second is a reading problem nobody has staffed. Until both clocks are on one calendar, the salesperson is guessing at the window.

    WHAT THE WORKFLOW DOES

    Not a list of ageing assets. A calendar with reasons.

    1. Takes in what you already know

      File dump or integration. Most start with a file.

    2. Puts a service life against each line

      Your engineering judgment, mapped. Not invented by us.

    3. Reads the utility’s replacement behavior from the public record

      Programme versus run-to-failure, so the calendar is not naive.

    4. Maps the competitor’s base and its contracts

      Who supplied what you did not, who maintains it, when that expires.

    5. Emits a dated action

      Not a ranked list of ageing assets.

    What lands on the desk

    Sometimes the action is: start the replacement conversation.

    Sometimes: the incumbent’s contract expires this quarter, and until then the way in may be as a subcontractor.

    TWO CLOCKS, ONE ACCOUNT

    Illustrative utility

    1. Your invoice · 2012, from your ERP

      Lift station 4. Two submersible pumps, 60 HP. Commissioned June 2012. Your service life: 15-18 yrs.

    2. Board minutes · Last November

      Operations: LS4 pump no. 2 rebuilt under the maintenance agreement. Third rebuild in four years.

    3. Contract award · Three years ago

      Three-year pump maintenance agreement awarded to the incumbent service firm. Term ends September next year.

    One dated action

    Account
    Suburban sewer district, 14 lift stations
    Clock one
    LS4 pumps at year 14 of a 15-18 year life. Repair history says sooner.
    Clock two
    Incumbent maintenance agreement ends September next year.
    Why it is live now
    Replacement conversation should start before the FY budget locks in spring.
    The action
    Open with the district engineer this quarter. Until September, the way in may be as a subcontractor.

    What this is not.

    Both clocks, or the page is only half true. Six things we will not do, and why.

    • End-of-life alone is not enough

      Without the contract clock, the nudge sends a rep to a utility that cannot buy yet.

    • Competitor make, model, and serial are not published

      Where a model is named in the public record we take it. We will not go looking by other means.

    • No asset-register scraping. No competitor serial hunting

      Public record only. Coarser on the competitor half, on purpose.

    • We do not become your CRM

      The dated action lands in the system your team already uses.

    • We do not send the outbound for you

      Your rep opens the conversation. We tell them when and why.

    • An alert feed of ageing assets is not the deliverable

      A feed is more reading. The deliverable is a date and a reason.

    Where this sits in the loop

    All solutions

    1. Screen

    2. Monitor

    3. Map the room

    4. Clocks

      • This page

    5. Draft

    6. Catch the bid

    7. Fit-check

    1. Screen

    2. Monitor

    3. Map the room

    4. Clocks

      • This page

    5. Draft

    6. Catch the bid

    7. Fit-check

    Questions we get on every call

    WHAT YOU GET ON A CALL

    Ingest, service life, contract clock, one dated action

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

    1. Installed-base ingest

      A slice of what you sold, from a file

    2. Service life and record

      Your numbers, plus how this utility actually replaces

    3. The dated action

      Which clock governs, and the window