.jpg)
Article 1 of 3 in our Three R's series, exploring how firms that service buildings (engineering consultancies, RCx and MBCx firms, BMS contractors, and mechanical contractors) are using the PEAK Platform to change three things at once: their revenue model, their client retention, and the resources their firms need to grow.
Spend any time around Building Performance Leads at engineering consultancies, or principals at RCx and MBCx firms, and you'll notice the same conversation surfacing again and again. Pipelines are full. Teams are stretched. Senior experts are getting closer to retirement, and the juniors stepping in can't carry the institutional knowledge that took decades to accumulate. The commercial model these firms were built on, where you bill the hours, deliver the report, and move on to the next project, is starting to feel less like a runway and more like a ceiling.
The interesting thing is that the demand side isn't the problem. If anything, building owners are asking for more than they ever have. Continuous improvements rather than one-off audits. Auditable ESG performance instead of quarterly PDFs. Verified fault close-out instead of a recommendations report that nobody actions. The market has decided it wants outcomes, not hours, and the firms that figure out how to deliver those outcomes at scale are the ones quietly pulling ahead of the field.
This article is the first of three. We'll start with revenue, because it's the conversation we hear most often when partners first sit down with us, and because the maths is more interesting than most people expect once you dig into it.
What actually changes about how partners get paid
When firms first start exploring PEAK, the question we get asked most is some version of: how does this actually change my P&L? It's a fair question, and the honest answer is that it changes three different things at once. Each of them, on its own, would be a meaningful shift. Together, they reshape what's commercially possible for the firm.
The first change is the most fundamental, and it's about recurring revenue from the same client. Under the old model, supporting a $10M chiller replacement is a great year, but next year you start again from zero. PEAK changes the structure of the relationship entirely. The audit becomes the doorway, and continuous monitoring becomes the deliverable that follows it. The same building, the same client, every year. The client who used to leave when the project was delivered now renews, because the engagement is underpinned by a platform that supports ongoing improvements. Aero Performance Group, who we'll come to in a moment, built a whole new technology-based revenue stream on top of their existing consulting offering using exactly this mechanic.
The second change is new service lines on existing client relationships. This one matters particularly for partners who haven't yet built an FDD capability in-house. PEAK gives you the engine on day one, which means the first MBCx engagement on each of your existing clients can be delivered by your existing team, on PEAK, in weeks rather than the years it would take to build that capability internally. The platform is the new capability. The clients, importantly, are already there.
The third change is the one we think is the most strategic, and it's the end of the hourly billing ceiling. Person-hours contracts cap your upside the moment you get more efficient at delivering them. That's not a glitch in the model, it's a feature of how the contracts are written. Outcome-based contracts (a recurring fee for continuous assurance, with auditable proof attached) work the other way around: every hour PEAK frees up flows directly into your margin rather than getting trimmed out of the next quote. The partners who shift to outcome-based pricing first set the pricing for everyone else.
The thing worth noticing here is that these three mechanics aren't independent levers you have to pull one at a time. They compound. The same client engagement that converts to a recurring contract is also the engagement that sits inside a new service line, and gets priced as an outcome rather than a stack of timesheets. That's the part most firms underestimate when they first do the maths.
A note on the AI conversation
Every software company is talking about AI right now, and the partner conversations we have generally include a healthy degree of skepticism about what's marketing and what's real. So it's worth being specific about what PEAK's AI actually does, and more importantly, why it matters for the revenue conversation rather than for an abstract feature list.
Most fault detection platforms surface an anomaly and stop. They flag it, attach a note, call it an insight, and leave the engineer to figure out what to do with it. That's enough to charge for a report. It is not, in our experience, enough to charge for a retainer.
PEAK AI is built the other way around. It detects the anomaly, prioritizes it, assigns an owner, recommends the action, tracks the workflow through to completion, and confirms the fix is held. That difference, between an alert and a closed fault, is what makes outcome-based contracts deliverable in practice rather than viable in theory. And it shows up in partner P&Ls in three specific places.
The first is at deployment. ML-powered auto-tagging means that the six-month tagging project most data platforms require simply doesn't exist on PEAK. Auto-commissioning brings new sites live in under 30 days, which means engineers move from integration projects into billable deployments inside the same quarter the contract is signed. Time-to-first-revenue compresses by a factor most partners don't quite believe until they see it on their second or third deployment.
The second is in the rule library. By the time a partner joins us, our FDD library has been refined across more than 100 million square feet of deployed assets and over a decade of engineering investment. Every fault pattern in your next building is, statistically speaking, already known to the platform. You're not building the engine. You're not hosting the data. You're not paying a software team to maintain a rule set. You're inheriting the work that someone else has already done, which is a meaningfully different starting position from where most firms find themselves when they try to build something equivalent in-house.
The third is the most strategic, and it's the one worth thinking hardest about. Outcome-based pricing only works if you can prove the outcome. Continuous, time-stamped, auditable performance data, generated by the platform rather than assembled by hand in Excel after the fact, is what lets you walk into a client conversation with the verified-savings fee already evidenced. The AI, in that sense, isn't a feature. It's the thing that makes the new commercial model commercially viable.
What this looks like at a firm actually doing it
We've talked about the mechanics in the abstract. It's worth grounding all of it in a specific firm.
Aero Performance Group is the consulting division of the Hill Group in Chicago, and an Illinois engineering leader offering RCx and MBCx with a vast portoflio of US sites currently running on PEAK. After a comprehensive market evaluation a few years ago, Aero rolled the platform out across their portfolio, and the results have shown up across all three of the mechanics we just walked through. They've grown their active project portfolio by 50% without adding a single additional engineer, which is the engineer-capacity story. Underneath that, they've built a new ongoing technology-based revenue stream that complements their existing consulting offering, they've watched fixed-term project work transition into longer-term engagements as clients see the value of continuous visibility, and they've won the local utility's Top Performer award for most kWh saved three years running, which speaks to both the M&V capabilities and the AI-driven fault detection working as advertised.
Their VP, Nick Muscolino, summarised the experience this way:
"PEAK has helped us increase productivity and significantly expand the number of projects the team can actively work on. We have been very impressed with the platform's AI-powered monitoring, and the advanced visualization capabilities have enhanced our client engagement, helping to improve our retention rates. We are proud of our award-winning track record in delivering energy savings, and CIM has quickly become a key partner for our ambitious growth plans." - Nick Muscolino, Vice President, Aero Performance Group
Read the full Aero case study →
Hoffman Building Technologies in Charlotte have taken a different route to a similar destination. Rather than starting with a client portfolio, they deployed PEAK across their own 180,000 sqft headquarters first. The site now operates as a live, walkable demonstration of what FDD-driven optimization actually looks like in practice, and the Hoffman sales team opens prospect conversations with a working showcase rather than a slide. Within the first six months, they'd identified hundredsd of improvement opportunities across their HVAC systems, delivered a 58% reduction in fan power on a single air handling unit, and saved roughly 6,400 kWh annually on that AHU alone. PEAK is now part of how Hoffman sells, which is, in its own way, a revenue mechanic worth thinking about.
Read the full Hoffman case study →
What this means for your firm
The honest framing of all this is that the revenue conversation about PEAK is rarely about one thing. It's about doing more (more clients, more service lines, more verifiable outcomes, more rebate cycles, more recurring fees) with the team you already have, on the same client base you're already working with. The three mechanics aren't independent levers. They compound.
If there's one thing I'd leave you with, it's this: the partners we see succeeding fastest aren't the ones who treat PEAK as a product they're evaluating. They treat it as a new commercial model they're stepping into. The platform is one half of that. The client relationship is the other. CIM runs the hosting, the engineering support, the onboarding, the tagging, the AI investment, and the rule library, so that your team can focus on running the relationship, the retainer, the renewals, and everything above wholesale. It's a clean division of labour, and it's what makes the maths work for both sides.
We'll be back in the next article in this series with the second R, retention, and how continuous building performance data is changing the unit of the client relationship from project to platform. If you want to keep going before then, the links below are the fastest ways in.
.avif)
.avif)
