The specification was written by somebody
A strategy consultancy came to us for a client entering the US market with the one question its target list could not answer: for each utility, which consulting engineer does it work with, and is that firm reachable? By the time a request for proposals is published, somebody else has already shaped it. This is the workflow that maps who is already inside an account, which firms write its specifications, and which door is open to you.
In March a team at a strategy consulting firm came to us on behalf of a client: a European company with leak-detection software, planning its entry into the American market. They had done the classical work already. The target was mid-sized utilities, twenty-five to a hundred thousand people, in three water-stressed states, and they wanted the list.
Then they asked the question the list does not answer. The market experts they had interviewed told them there were two ways into a utility of that size: through the consulting engineering firm that does its studies and writes its specifications, or through the service contractors who already do its leak surveys. So, for each utility on the list, could we say which engineering firm it works with? If it is one of the national giants, that door is closed to a newcomer. If it is a local firm, that is the whole go-to-market.
Their colleague, joining late, asked the other half of the same question. Who is the person responsible, and, in a utility that size, who else has to be spoken to before anything moves?
They were asking, from the client's side, the thing I have been repeating for a year without examining it: by the time a request for proposals is published, the specification has usually been shaped by whoever was in the room a year earlier, and you are bidding on a document someone else helped write. Everybody selling into this market knows that, but almost nobody can name the someone. This is the workflow that tries to. Its output is an understanding of the account more than a next step, and in a way it is the one everything else we build was pointing at.
The job, as it exists today
A utility sits inside an ecosystem it did not choose and mostly cannot avoid. There is an engineering firm that does its studies and usually writes its specifications. There are distributors and manufacturers' representatives through whom certain categories of equipment are bought, whatever the utility's procurement policy says. There is a list of pre-approved vendors, and firms holding standing contracts that let work be issued without a competition. There is an operations contractor, sometimes. And there is a set of incumbents whose equipment is already in the ground and whose service people are in the building every month.
Almost every real route into an account runs through one of those, and a salesperson's knowledge of them is anecdotal, personal, and lost when they leave.
Why it is harder than it looks
The relationships are visible only in aggregate. Any single award tells you almost nothing: a firm won a job, which happens. The pattern across ten years of awards is what tells you that this engineering firm does essentially all of this utility's treatment work, that a particular distributor is the route for pumps, and that a category you care about has been sole-sourced to the same supplier three times running.
The useful relationship is often not the obvious one. A firm that shows up constantly in awards may be a competitor, or may be your own channel. Getting this wrong is expensive in both directions: treating your distributor as a competitor, or trying to displace an incumbent whose contract has nine years to run and no re-compete in sight.
And the door that is open is rarely the front one. A pre-approved vendor list or an existing standing contract can be a faster route into a utility than a direct approach, because you are selling to somebody already permitted to invoice the utility. That is a different motion, and most vendors never look for it because nobody assembled the list.
What the workflow does
It builds the ecosystem from the award record. Ten or more years of awards, minutes and contract documents, aggregated by firm rather than by project: who wins what here, how often, in which categories, and under which procurement route. That last part matters, because how a utility buys determines which relationships are worth having.
It separates competitor from channel. For a given vendor, the same firm can be either, and the classification is specific to who is asking. This is the relevance-is-a-function-of-who-is-asking principle again, applied to organizations instead of signals.
It finds the specification writers. The consulting engineers who appear on the studies that precede procurements. If a firm wrote the condition assessment, it will very likely shape the specification that follows, which makes it the place to be known eighteen months before anything publishes.
And it surfaces the access routes. Approved-vendor status, standing contracts, cooperative vehicles and existing subcontract relationships: the mechanisms by which work can reach you without a competition, and which of them this utility uses.
Account Intelligence / Pine Fork Utility District / Ecosystem
A list of names is not a route in
The failure mode here is producing an org chart of companies and calling it intelligence.
Knowing that a particular engineering firm dominates a utility's capital work is a start, but it does not change what a salesperson does on Monday. What changes behavior is the next layer: that this firm has specified a competitor's equipment on the last three projects, that it has an office two hours away with a named water practice lead, and that the study it is currently running is the one that precedes the procurement you care about.
The same is true of an approved-vendor list. On its own the list does little. The useful form is: you are not on it, here is what being added requires, here is how long that takes at this utility, and meanwhile here are two firms already on it who subcontract work of your type.
So the work is finished when somebody can act on the information, and being correct is only the first step. The same rule runs through everything we build.
What it cannot do
It sees relationships, not standing. The record will show you that two organizations have worked together fifteen times. It will not tell you that the relationship soured last year, that the engineer who liked your equipment has retired, or that the utility is quietly unhappy with an incumbent everybody assumes is entrenched. Those facts change everything and none of them are published. They come from a person who has been in the room, which is why this workflow is a brief for a salesperson and needs one to use it.
And its resolution follows the record. Where awards are public, itemized and consistently published, the picture is good. Where a utility publishes awards as a single line in a consent agenda, or where a whole segment treats its supplier relationships as confidential, the map is directional at best, and I would rather promise a directional map at the start than deliver one at the end while calling it comprehensive.
One more limit, because it is the specific way this workflow could become dishonest. It would be easy to present inference as knowledge here, for example to say a firm is the incumbent when what the record supports is that it won four of the last six awards in a category. Those are different claims. The first is what a customer wants to hear and the second is what we can stand behind, so the second is the one we say.
AquaIntel builds that ecosystem for each account from years of award records, tags each firm as a competitor, a channel or a specifier for you, and shows the access routes that utility uses.
Related
- The bid you already knew about: the solicitation this workflow explains the origin of.
- Everything you sold has a clock: the award record, read for what is installed rather than for who specified it.