I have sat on both sides of this table.

For most of my career I was the fire service leader evaluating vendors — asking questions, reading proposals, trying to figure out which products would actually produce outcomes and which ones would produce activity that looked like outcomes until the contract renewal conversation arrived. I understood the skepticism that most fire service leaders bring to vendor relationships because I shared it.

Then I became a vendor.

And I learned things from that side of the table that I could not have fully understood from the other.

This article is about CRR vendor partnerships specifically — what they can and cannot accomplish, what makes them work, what causes them to fail, and what a fire department needs to know before signing anything and after. It is written from both sides of the relationship because both sides matter, and because the fire departments that build the most effective CRR vendor partnerships are the ones that understand what their vendor partners actually need from them to succeed.

Why Fire Departments Cannot Do Everything Themselves

Start here because it is the foundation of the entire partnership argument.

The fire service cultural instinct — self-sufficient, problem-solving, unwilling to ask for help — is an asset in emergency response and a liability in sustained program development. We have addressed this in the context of community partnerships. The same dynamic applies to vendor relationships.

CRR at scale requires capabilities that most fire departments do not have internally and cannot build cost-effectively on their own. Technology platforms that deliver digital home safety assessments to thousands of households simultaneously. Data systems that aggregate address-level risk intelligence and surface patterns that manual analysis would never find. Public education content libraries developed by specialists in behavior change and risk communication. Reporting infrastructure that translates raw assessment data into the kind of visual, locally specific evidence that changes conversations with city managers and elected officials.

Building any one of these internally requires staff time, technical expertise, ongoing maintenance, and iterative development capacity that most fire departments — particularly small and mid-size ones — simply do not have. The alternative is not building them at all, which means the scale, data, and consistency problems we have discussed throughout this series remain unsolved.

Vendors exist because specialization produces better outcomes at lower cost than generalism. A technology company that has spent years building and refining a CRR assessment platform has invested thousands of hours of development, testing, and iteration into a product that a fire department could not replicate internally in any reasonable timeframe at any reasonable cost. The department that partners with that vendor is buying the outcome of that investment — not just the software.

This is the honest case for vendor partnerships in CRR. Not that vendors are always right or that every vendor relationship produces value. But that the capabilities required for genuinely effective CRR at community scale are in many cases more efficiently and effectively sourced from specialized partners than built from scratch internally.

What Vendors Can and Cannot Do

This distinction is where most vendor partnerships go wrong — and it goes wrong in both directions.

Fire departments sometimes expect vendors to do things vendors cannot do. A technology platform cannot create organizational commitment to using it. A data system cannot generate the cultural expectation that crews will enter observations consistently. A public education content library cannot substitute for the leadership decision about which populations to reach and how. A vendor can provide tools. The vendor cannot provide the organizational will, the leadership commitment, or the cultural foundation that makes those tools produce outcomes rather than activity.

Vendors sometimes imply they can do things they cannot. The sales conversation that promises transformation without naming the implementation requirements. The demo that shows the product at its best without surfacing the conditions under which it underperforms. The contract that includes metrics measuring platform activity — logins, completions, reports generated — rather than community risk outcomes. These are not always intentional misrepresentations. Sometimes they reflect genuine belief in the product. They are still misleading if they create expectations the partnership cannot meet.

The most productive vendor partnerships start with honest conversations about both sides of this equation. What does the vendor’s product actually do, under what conditions, with what level of organizational support required from the department? And what is the department actually prepared to provide — in leadership attention, staff time, cultural commitment, and sustained engagement — to make the partnership work?

Those conversations are uncomfortable. They are also the ones that produce successful partnerships rather than expensive disappointments.

What to Expect From a Good CRR Vendor Partner

A vendor partner worth signing a contract with should be able to do several things clearly and specifically.

Explain the problem their product solves in terms that match your department’s actual situation. Not a generic description of what the product does. A specific articulation of which gap in your CRR program this addresses, how it addresses it, and what evidence exists that it has addressed similar gaps in comparable departments.

Provide references from departments that look like yours. Not just from the largest and most well-resourced departments that have the most capacity to make any product work. From departments of similar size, similar staffing, similar prevention infrastructure, and similar community context. What those departments experienced — including what was harder than expected — is more useful than any sales presentation.

Be honest about implementation requirements. What does the department need to do internally for the product to work? What staff time does it require? What training? What ongoing maintenance? What happens if adoption is lower than projected? A vendor who cannot answer these questions specifically is either not thinking clearly about implementation or is avoiding the conversation because the honest answers are not selling points.

Provide outcome metrics rather than activity metrics. The question is not how many assessments were completed or how many reports were generated. The question is what changed in the community’s risk profile as a result of using the product. A vendor who can only point to activity data when asked about outcomes has not yet built the evidence base that a mature product partnership requires.

Be a genuine partner in the CRR work rather than a transaction. The CRR vendor partnerships or relationships that produce the best outcomes are the ones where the vendor is invested in the department’s success beyond the contract period — where they bring ideas, surface problems early, and treat the relationship as ongoing rather than complete at the point of sale.

What Vendors Need From Fire Departments

This is the side of the conversation that almost never gets named directly — and its absence is one of the most consistent causes of vendor partnership failure.

Vendors need a clear problem definition before the contract is signed. The department that buys a CRR technology platform without a clear articulation of which specific gap and problem it is filling or solving, which population it is reaching, and what success looks like in measurable terms — that department is setting up a partnership that will struggle to demonstrate value when the renewal conversation arrives. The vendor can help refine the problem definition. They cannot create it.

Vendors need organizational commitment that extends beyond the purchasing decision. The contract signature is the easiest moment in any vendor partnership. What comes after — the internal communication, the training, the cultural expectation that the product gets used consistently, the leadership follow-through that makes adoption real rather than nominal — that is what the department has to provide. A product that sits underused because nobody created the expectation of use is not a vendor failure. It is a leadership failure that the vendor will be blamed for.

Vendors need honest feedback when things are not working. The fire service cultural instinct to manage problems internally and not show weakness to outside parties is understandable but counterproductive in a vendor relationship. When the product is not working as expected, when adoption is lower than projected, when the outcomes are not materializing — the vendor who hears about that early can do something about it. The vendor who discovers it at contract renewal cannot.

Vendors need a point of contact with actual authority. The prevention officer who champions the product but cannot make organizational decisions is not the right primary contact for a partnership that requires organizational commitment. The chief who signed the contract but has no daily engagement with the product is not the right contact either. The most successful partnerships have a primary contact who is close enough to daily operations to know what is working and senior enough to address what is not.

The Pitfalls Worth Naming

Some of these are more common than others. All of them are preventable.

Buying a solution before defining the problem. The technology looks impressive in a demo. The sales conversation is compelling. The contract gets signed before anyone has articulated specifically which gap this product addresses in this department’s CRR program. Six months later the product is underused and nobody can quite explain what it was supposed to accomplish.

Selecting vendors based on price alone. CRR technology is not a commodity. The cheapest platform that technically does what the specification requires is not always the right choice — particularly if the difference in price reflects a difference in implementation support, ongoing development, data quality, or the depth of evidence for the product’s effectiveness. Price matters. but it should not be the only thing that matters.

Ignoring implementation requirements in the budget. The contract price is not the total cost of the partnership. Staff time for training, for ongoing administration, for the cultural change work that makes adoption real — these are real costs that belong in the budget conversation. Departments that budget for the contract and not for the implementation are consistently disappointed by the results.

Measuring the wrong things. A vendor partnership that is evaluated on activity metrics — how many assessments were completed, how many reports were generated — is a partnership that optimizes for activity. A partnership evaluated on outcome metrics — what changed in the community’s risk profile, whether prevention resources are being directed more accurately toward high-risk populations — is a partnership that optimizes for outcomes. The metrics you choose to evaluate the partnership are the metrics the partnership will optimize for.

Treating the vendor relationship as adversarial. Some degree of healthy skepticism in vendor relationships is appropriate and protective. A posture of fundamental adversarial suspicion — where every vendor communication is interpreted as manipulation and every problem is assumed to be the vendor’s fault — produces partnerships where honest communication breaks down and problems go unaddressed until they become crises. The vendor is not the enemy. They are a partner with their own interests that need to be understood and aligned with the department’s interests rather than assumed to be in conflict with them.

Failing to plan for succession. The prevention officer who championed the vendor relationship retires. The chief who understood the strategic rationale for the CRR vendor partnerships moves to another department. The institutional knowledge of why the product was selected, what it was supposed to accomplish, and how to evaluate whether it is working — that knowledge leaves with them if nobody planned for succession. Vendor partnerships need to be documented and institutionalized, not held in the heads of the individuals who built them.

Technology Specifically

CRR technology deserves specific treatment because it is where the most significant investments are being made and where the gap between expectation and reality is most commonly wide.

The technology that matters most for CRR — digital assessment platforms, data aggregation systems, reporting and visualization tools — is genuinely valuable when it is implemented well and genuinely disappointing when it is not. The difference between those two outcomes is almost never the technology itself. It is the conditions under which the technology is deployed.

A digital home safety assessment platform reaches thousands of households at a cost that in-person programs cannot approach. That is real and important. It reaches those households if the department deploys it — if the QR codes get distributed, if the social media posts go out, if the link appears in the utility bill insert, if the faith community partner shares it with their congregation. The platform does not distribute itself. The department does. The platform’s value is entirely dependent on the department’s willingness to do the distribution work that makes reach possible.

A data aggregation system surfaces patterns in community risk intelligence that manual analysis would never find. That is real and important. It surfaces those patterns if the data going into it is consistent and complete — if crews are entering observations, if assessment responses are being captured, if the system is being fed the information it needs to do the analytical work it was designed to do. Garbage in, garbage out is a technology cliché because it is consistently true.

A reporting system translates raw data into the locally specific evidence that changes conversations with city managers and elected officials. That is real and important. It changes those conversations if someone is using the reports — if the chief is bringing them into budget meetings, if the prevention bureau is using them to adjust program priorities, if the evidence is being connected to decisions rather than sitting in a dashboard that nobody opens.

Technology amplifies organizational capacity. It does not substitute for it. The fire department that deploys CRR technology without the organizational commitment to use it is not going to get the outcomes the technology is capable of producing. The fire department that deploys the same technology with genuine organizational commitment — with leadership attention, cultural expectation, and sustained engagement — is going to get outcomes that justify the investment many times over.

The Standard Worth Holding

A successful CRR vendor partnership looks like this at the end of a contract period.

The department can point to specific, measurable changes in its community’s risk profile that the partnership contributed to. Not just activity — outcomes. Reduction in incident rates in targeted areas. Improvement in risk conditions in specific populations. Prevention resources directed more accurately toward high-risk households than they were before the partnership existed.

The vendor can point to a department that used the product as designed, provided honest feedback when things were not working, and engaged with the partnership as a genuine collaboration rather than a transaction.

Both parties can articulate what the next phase of the partnership should accomplish and why — because the evidence base built during the first contract period provides a clear picture of where the partnership produced value and where it has more to offer.

That is a successful CRR vendor partnership. It is achievable. It requires honesty, clear expectations, and genuine commitment from both sides of the table.

The departments that build CRR vendor partnerships like this are having different conversations about CRR outcomes than the ones that do not.

And they are producing genuinely safer communities as a result.

Brent Faulkner, MAM, FO, is the CEO and Founder of Virtual CRR Inc.
A retired Battalion Chief from Anaheim Fire & Rescue, Brent brings 28 years of fire service experience, including leadership in structure fires, wildland operations, hazardous materials response, EMS incidents, and specialized rescue operations. He also served 17 years on a Type 1 Hazardous Materials Response Team.

A defining moment in Brent’s career came while leading Critical Infrastructure Protection (CIP) efforts at a DHS-recognized Terrorism Fusion Center. There, he oversaw initiatives to safeguard critical infrastructure from terrorism, natural disasters, and emerging threats — an experience that shaped his passion for Community Risk Reduction and ultimately led to the creation of Virtual CRR.

Brent holds a Master’s Degree in Management, a Bachelor’s in Occupational Studies, and Associate Degrees in Hazardous Materials Response and Fire Science.