The Long Meadow Bulletin

The full picture before the deposit goes down.

10:32W16

Two Proposals, One Warehouse Portfolio. What Told the Good Consultant From the Plausible One

A composite case from three warehouses shows how buying outside expertise shifted from advisory reports to metered, invoice-linked work, and which proposal details predicted that.

Corporate6 min

A commercial refrigeration compressor room in a food distribution warehouse, with an electrical panel, conduit, and a portable data logger clipped to a pipe
A commercial refrigeration compressor room in a food distribution warehouse, with an electrical panel, conduit, and a portable data logger clipped to a pipe

The company in this account is a composite, assembled from the sort of engagement that has become routine: a regional food distributor with three leased warehouses, a customer base of grocery chains, and a procurement questionnaire arriving each spring asking for energy and emissions figures it did not have. Management wanted two things that are easy to confuse, a lower utility bill and a defensible number to report. It solicited proposals from four firms, shortlisted two, and the gap between those two proposals is the useful part. Both were competent on paper. Only one described work that could be checked.

What the first proposal promised, and what it actually contained

The first firm sent nineteen pages, well designed, with a maturity model, a roadmap organized into three horizons, and a section on stakeholder alignment. The scope described a benchmarking exercise, interviews with facility staff, a gap assessment against a recognized framework, and a prioritized set of recommendations delivered as a final presentation. The fee was a fixed sum, payable in thirds. Nothing in it was dishonest. The problem was that every deliverable was a document, the inputs were whatever the client could supply, and no sentence in the scope committed anyone to visit a building or read a meter.

That structure has a specific consequence: the firm cannot fail. A roadmap is delivered when it is handed over, and its quality is a matter of opinion for at least two years, by which time staff have turned over and the file is closed. Plausible work tends to have this shape. It is priced on effort, described in nouns rather than verbs, and its accuracy depends entirely on data the client assembled without guidance. The distributor's controller noticed the pattern when she asked a simple question and got a slow answer: where would the baseline numbers come from?

The second proposal was shorter and harder to read

The second firm sent eleven pages, most of it scope and assumptions. It proposed a two-day visit to each site with a named mechanical engineer, an interval-data pull from each utility account requiring a signed authorization, temporary logging on the refrigeration compressors and the dock door heaters, and a written baseline that reconciled to twelve months of invoices within a stated tolerance. Recommendations would carry installed costs from at least two contractors, a simple payback range, and an explicit note where the estimate rested on assumption rather than measurement. The final page listed what the firm would not do.

Exclusions are the most informative thing in a proposal, and the least flattering to read. This one said it would not certify the emissions figure for third-party assurance, would not design the controls upgrade it expected to recommend, and would not estimate savings for the leased site until the landlord released submeter access. A firm that names the boundary of its own competence has usually been asked to cross it and declined. The distributor's operations director read that page twice, then called the two references, both of whom described the same engineer by name.

Why the market moved from advice to measurement

A decade ago the first proposal was the norm and nobody thought less of it. The demand was for orientation: boards wanted to know what the landscape looked like, and a competent survey of frameworks was genuinely the product. What changed is who now reads the output. Purchasing departments at large grocery and food service customers began asking suppliers for figures in a fixed format, with methodology notes, and those figures started appearing in contracts as representations. State disclosure laws in California, phased in for large companies and reaching further up and down supply chains than their thresholds suggest, pushed the same way. A number that will be relied upon has to be traceable.

Two other pressures arrived at the same time. Utility and state incentive programs tightened their evidence requirements, so a rebate application now typically needs measured baselines, specified equipment, and post-installation verification rather than an engineer's letter. And the buildings themselves became legible: interval meter data, cheap loggers, and building management systems that export to a spreadsheet made it possible to check a claim in an afternoon. The Department of Energy oversees federal work on building efficiency measurement and equipment standards, and its benchmarking conventions have quietly become the vocabulary that serious proposals are written in.

The result is a market that has split. Firms that sell measurement have grown a delivery function, with engineers, loggers, and a lab-style habit of stating tolerances. Firms that sell orientation have moved toward implementation support, project management, and assurance readiness, because the pure advisory report no longer commands its old fee. Buyers benefit either way, provided they can tell which firm they are talking to, and the tell is almost always whether the scope commits to a physical act on a specific date.

What the engagement found, and where the label was doing the work

The distributor hired the second firm. The site visits produced a result that neither proposal had anticipated: the largest single cost item was not lighting or insulation but a refrigeration control setting at the oldest warehouse, where defrost cycles ran on a fixed clock rather than on demand, and two condenser fans had been wired to run continuously after a repair three years earlier. The fix cost less than the study. The second finding was less satisfying and more valuable, which is that the rooftop unit replacement everyone assumed was the priority had a payback long enough that the lease term made it the landlord's decision, not the tenant's.

The reporting question resolved separately, and this is where labels earn scrutiny. The company could have bought a certification badge for one facility, a recognizable mark that would have sat well in a customer questionnaire, and it would have changed nothing about the compressors. It instead spent the money on submetering at two sites, which produced a figure it could defend in a procurement conversation and could also use to detect the next wiring error within a billing cycle. The badge would have been faster. The meters kept paying attention after the consultant left.

Read the final report against the original proposal and the discipline shows. Every savings estimate carried its measurement basis, the leased site was flagged as unresolved rather than modeled optimistically, and one recommendation was withdrawn between draft and final because logging contradicted the assumption behind it. A firm that revises its own numbers downward in front of a client is displaying the habit you are actually buying. That habit is what distinguishes the good engagement from the plausible one, and it is visible in the scope of work before a dollar moves.

The questions that separated the two firms, and when to ask them

Three questions did most of the sorting, and all three were asked before the shortlist. Who specifically performs the work, by name and title, and what happens to the schedule if that person is unavailable. What physical measurement does the fee include, and what is the tolerance on the resulting baseline. What is excluded, and which exclusions would you expect us to want to buy separately later. The first question exposes firms that sell a partner and staff a junior. The second exposes work built on client-supplied data. The third exposes firms that have not thought past the invoice.

Ask them at the request-for-proposal stage rather than after, because a scope written in response to those questions is a different document from one edited afterward. The distributor's controller now keeps the three questions in the procurement template, alongside a requirement that references be reachable engineers rather than executives.

What survived the engagement was not the report. It was two submeters, a defensible number, and a purchasing habit that will make the next hire cheaper to evaluate.

Filed byPercival Ashcroft

Percival writes about green claims and which of them survive a closer look.