Jason and I spent years inside a vendor that tried to sole source everything. From that side of the table, we heard every framing a sales team can construct to persuade a customer that competition is not in their interest.
“We will save you the procurement effort.” “We will offer pricing you cannot get through an RFP.” “We will throw in additional licensing at no charge.” Every framing made the deal sound favorable for the agency. None of them mentioned the cost the agency would pay later for the absence of competition.
Sole source is not automatically wrong. There are situations where it is the right answer. In public safety technology, it is almost always more dangerous than agencies realize, and we cannot think of a single time we would endorse skipping competition without first proving it was the right call.
A sole source decision may be legal. That does not automatically make it wise, defensible, transparent, or in the agency's long-term interest.
This Insight is about the difference between sole source as a documented operational necessity and sole source as a comfort decision dressed up as one. CAD, RMS, LMR, body-worn cameras, digital evidence, jail management, NG911, station alerting, CAD-to-CAD, mobile data, and records systems become part of the agency's operational nervous system. Once installed, these systems shape workflow, staffing, policy, responder safety, evidence handling, community trust, and future procurement leverage for years. The procurement decision is not a purchase. It is a ten-year operating commitment.
A good RFP is not red tape. A good RFP is discovery, governance, leverage, transparency, and risk management in one process. A defensible sole source is a fact-based exception to that process. The agencies that get this right understand both.
What Changes Inside The Vendor When Competition Goes Away
Inside a vendor, the tone around a competitive procurement is different. When an agency issues a strong RFP, the vendor knows it has to earn the award. Pricing gets sharper. Executive attention increases. Product managers get pulled in. Legal becomes more flexible. Concessions that were previously “not available” suddenly become possible. The sales team starts talking about win themes, competitive differentiators, service commitments, implementation risk, executive relationships, and how to prove value.
When an agency sole sources, the vendor already has the most important thing it wants: control of the lane.
That does not mean every vendor behaves badly. It means the incentives change.
In a competitive RFP, the vendor has to answer the agency's question: “Why are you the best option?” In a sole source, the vendor often only has to answer: “How do we get this approved?” That distinction is everything.
Pricing posture changes. In a competitive procurement, the vendor knows price will be compared. It knows the agency may have other viable offers. That forces discipline. In a sole source, the vendor can frame the price around continuity, risk avoidance, bundled value, ecosystem alignment, and timing. The number may still be discounted, but the discount is measured against the vendor's own price book, not against the market.
Negotiation behavior changes. In competition, agencies negotiate from strength: “Your competitor is offering this. Can you match it?” In sole source, the vendor knows the agency has already accepted the premise that there is no practical alternative. That weakens the agency before legal review even starts.
Concessions are offered differently. In a competitive environment, vendors offer additional training, stronger SLAs, extended warranty, more favorable payment terms, enhanced implementation support, data migration assistance, interface credits, or governance commitments. In sole source, concessions are often packaged as “special pricing” or “included modules,” but those extras can deepen vendor lock-in. Free software is not always free. Sometimes it is a hook.
Internal language changes. A competitive agency is treated like a deal that must be won. A sole source agency is often treated like an account that must be managed through approval. That difference affects urgency, creativity, escalation, and sometimes humility.
Axon publishes its own argument for sole source procurement of body cameras and digital evidence. The argument is sophisticated. Body cameras are not commodities. The technology is integrated with cloud evidence management, CJIS-compliant storage, and prosecutor sharing workflows. A six-to-twelve month RFP is inefficient when the product is already validated through field testing. Axon makes the case directly to agencies on its own website.
Some of what Axon says is true. The technology is complex. The stakes are high. The integration matters. The counterpoint Sentinel makes is straightforward: the vendor may be right that the technology is sophisticated. That is exactly why the agency should be cautious about giving up competition.
Competition changes vendor behavior. Sole source changes agency leverage.
The Four Justifications Agencies Use, And What Each One Misses
When an agency justifies a sole source, the language is consistent across the country. Four reasons get used most often. Each has a grain of truth. None survives serious scrutiny on its own.
“We already have the platform”
This is the most common justification and, in many cases, the weakest.
An existing platform is a factor. It is not a conclusion. The public safety industry lives in ecosystems now: CAD to RMS, CAD to mobile, RMS to courts, evidence to prosecutors, radio to CAD, NG911 to CAD, mapping to AVL, body-worn camera to digital evidence, jail to RMS. Integration matters. “We already have the platform” should not be treated as proof that the next purchase must go to the incumbent.
We live in the age of interfaces and APIs. There is almost nothing in modern public safety technology that cannot be interfaced. The real question is whether the existing platform creates a technical necessity, or whether it simply creates a vendor preference. Those are not the same. Federal grant procurement standards under 2 CFR 200.319 specifically warn against restrictive competition, including brand-name-only specifications without allowing an equivalent, and against organizational conflicts of interest in evaluation.
“We already have Vendor X” may explain the environment. It does not automatically justify Vendor X for the next five or ten years.
“Switching costs are too high”
Sometimes this is true. More often, it is incomplete.
Switching costs are real. Data migration, interfaces, training, overtime, cutover support, policy rewrites, workflow redesign, testing, acceptance, and change management all cost money. Agencies often compare the cost of switching against the price of staying. They rarely compare it against the cost of staying with a product that does not actually meet their needs.
The cost of a bad system shows up in places the capital budget does not capture. Dispatcher frustration. Officer report-writing time. Records rework. Duplicate data entry. Workarounds. Delayed incident closure. Morale degradation. Staff turnover. Public records request delays. The inability to meet future operational needs that the agency cannot even articulate yet because the current system has trained the workforce to stop asking for them.
The question is not whether switching is expensive. Of course it is. The question is whether staying is more expensive over the next decade.
“The vendor knows our environment”
This sounds persuasive. It is usually overstated.
Unless the agency operates a genuinely unique environment, this argument confuses institutional familiarity with exclusive capability. Any vendor worth considering can conduct an environmental analysis as part of pre-deployment work. They will know the agency's environment within weeks of engagement. The “they already know us” framing is a comfort blanket that papers over a much harder question: why is the agency unwilling to expose itself to a new vendor's discovery process? The answer is usually that the existing vendor has made the agency feel that competition is risky. That is exactly the position the existing vendor wants the agency in.
Familiarity may reduce transition risk. It does not prove that no other vendor can perform.
“We do not have time to run a competitive process”
This is the most common justification and the most circular.
Yes, an RFP takes time. If the agency skips the RFP, the time saved during procurement gets spent later dealing with the system that does not perform. In the long run, the agency pays in dollars and in staff hours.
Agencies frequently treat time as a binary: a full twelve-month RFP, or sole source. That is false. There are several competitive and semi-competitive procurement models that compress timeline while preserving integrity. We will get to those.
The federal rules also do not treat urgency as a blank check. 2 CFR 200.320(c) permits noncompetitive procurement only in specific circumstances: micro-purchase threshold, single source, public exigency or emergency that will not permit delay, written approval by the federal agency or pass-through entity, or inadequate competition after soliciting an adequate number of sources. “We did not start early enough” is not on the list.
“We do not have time” is often not a procurement justification. It is evidence that the agency waited too long to govern the decision.
The deeper problem with all four justifications is that they assume the vendor's interests and the agency's interests are aligned. They are not. The vendor's interest is to expand its footprint with the lowest possible competitive pressure. The agency's interest is to deploy the right technology at the right price under terms that protect the agency for the life of the contract. Those two interests touch occasionally. They do not run parallel.
The agency that does the work on the front end produces a different result. An honest internal discovery identifies the actual pain points in current technology and process. It determines what the best possible solution looks like for the agency specifically. It surfaces stakeholder alignment across patrol, dispatch, records, jail, fire, EMS, IT, command, and the city or county attorney. Then a bulletproof RFP becomes possible. Vendors that would never have worked out get dismissed automatically by the requirements themselves. The vendors that remain are forced to compete on price and product. If the evaluation committee does its job, the clear winner rises. Done correctly, there is no sole source out there that could beat a competitive analysis. There is also no vendor that will ever tell the agency that.
What Sole Sourcing Actually Costs Over A Decade
Sole source looks fast on the front end because it removes friction. Friction is not always bad. In procurement, friction is often where the agency discovers risk.
The long-term cost shows up in several places.
Pricing escalation. Once the vendor knows the agency is locked into the ecosystem, pricing leverage shifts permanently. Annual subscription increases, storage growth, license true-ups, support uplifts, module add-ons, interface costs, professional services rates, device refreshes, and required upgrades become the new operating reality. The Woodburn, Oregon body camera staff report is a public example of how this plays out. The report noted that Evidence.com storage costs had risen annually because the agency had not adequately projected data volume growth, while devices were aging and being repaired or replaced on a per-incident basis. The vendor did not do anything wrong. The agency's original assumptions did not capture the long-term cost model. That is the pattern, repeated across hundreds of agencies. Many vendors hide upfront costs or spread them across a decade so the front-end number is easier to digest. The cost is not avoided. It is delayed.
Roadmap lock-in. Once the agency is embedded, the vendor's roadmap becomes the agency's roadmap. If the vendor prioritizes a module, the agency may get it. If the vendor delays a feature, the agency waits. If a needed workflow is not core to the vendor's product direction, the agency may pay for customization, accept a workaround, or change its operations around the product. The agency stops driving the technology. The technology starts driving the agency.
Feature withholding and ecosystem bundling. Public safety vendors increasingly sell ecosystems, not products. Body cameras are bundled with digital evidence. CAD is tied to mobile. RMS is tied to reporting and analytics. Digital evidence is tied to redaction, prosecutor sharing, storage, transcription, and disclosure tools. Radio systems are tied to infrastructure, subscriber units, maintenance, encryption, and lifecycle services. The bundle may be valuable. It may also make it harder for the agency to separate what it needs from what the vendor wants it to buy.
Structural contract risk. Many sole sourced procurements use an existing contract vehicle to add new technology. The vendor proposes adding the new product under the terms of a master services agreement, often signed years earlier when the agency was negotiating a different solution against different competitors. The terms in that older contract may not protect the agency for the new procurement. The pricing schedule may not include the new product. The service-level commitments may not extend to the new functionality. The agency inherits the new technology under a contract structure that was never designed to govern it.
Lessons not incorporated. No procurement is perfect. Every deployment surfaces issues the original contract did not anticipate. A new RFP gives the agency the opportunity to fix those issues in the next contract. A sole source under an existing vehicle does not. The agency repeats its previous mistakes and accepts the previous shortcomings because there is no point in the process where those shortcomings get formally raised and resolved.
Loss of leverage. Sole sourcing eliminates the only moment in the relationship when the agency holds real negotiating power: the moment before the vendor is selected. After selection, every subsequent conversation happens with the vendor already inside. Pricing escalation cannot be effectively challenged. Feature requests get treated as optional. The agency cannot credibly threaten to leave because there is no competitor on deck and the vendor knows it. Every future renewal, change order, interface, support negotiation, and contract amendment starts from the same place: the vendor knows the cost and pain of leaving.
Audit and public confidence risk. The public may not understand the technical architecture, but it understands fairness. Sole source procurement can create the appearance that the outcome was predetermined, even when the agency had legitimate reasons. Public safety leaders have to think beyond legality. They have to think about public trust, council questions, county board questions, media questions, public records requests, and grant audit questions. The procurement file gets pulled when the agency least wants it to. The file either holds together or it does not.
From a political standpoint, this is one of the most embarrassing and challenging positions an organization can be in. We have witnessed sole source procurements go genuinely south when people started digging, looking for a traceability matrix, looking for vetting documentation, looking for the analysis that explained why this vendor and this solution were chosen, only to discover that the deal was sole sourced and the features and functionality had not actually been explored or documented properly. Procurement should be looked at as an opportunity to improve a system or introduce technology that genuinely makes a process better. Handled properly, it can be one of the most favorable things an organization does in service of its workforce and its mission. Handled poorly, it becomes a finding.
Sole source saves time when the contract is signed. Competition saves time when the system is questioned.
What The File Actually Looks Like When The Auditor Arrives
When an inspector general, a grant auditor, a city attorney, a state auditor, or a council member pulls the file, they are not just asking whether the agency had the authority to sole source. They are asking whether the agency can prove the decision was fair, necessary, documented, and free from improper influence.
The questions sound like this. Why was competition not used? What legal authority allowed noncompetitive procurement? Who made the determination? Was the determination approved before award? Was market research performed? Were other vendors evaluated? Were alternatives documented? Was there a true single source, or simply a preferred source? Did the vendor help write the requirements? Did any employee have a conflict of interest? Were gifts, travel, employment discussions, speaking fees, consulting relationships, or vendor-sponsored events involved? Was price determined fair and reasonable? Was the contract within the original scope of an existing agreement? Was a cooperative or neighboring-agency contract used properly? Were federal grant approvals required? Were required clauses included? Was the sole source posted publicly or subject to protest?
Federal procurement standards require procurement records sufficient to detail the history of each transaction, including the rationale for procurement method, contract type, contractor selection or rejection, and the basis for contract price. 2 CFR 200.324 requires cost or price analysis for procurements and modifications above the simplified acquisition threshold, with independent estimates before bids or proposals are received. The COPS Office sole source fact sheet is explicit: sole source procurement must follow 2 CFR 200.320, recipients must use documented procurement procedures consistent with federal standards, sole source justification is needed when competitive procurement is infeasible, and conflicts of interest are prohibited under 2 CFR 200.318(c).
What is usually missing is almost always the same set of documents. Real market research. Evidence that alternatives were considered. An independent cost estimate. A price reasonableness memo. Conflict-of-interest disclosures. Documentation that the vendor did not write the requirement around itself. Lifecycle cost analysis. Explanation of why interfaces or equivalent products would not work. The approval chain. Grantor approval, if required. Scope analysis when using an existing or cooperative contract. Documentation separating operational preference from technical necessity.
A defensible sole source file is not a one-page memo saying “we already use this vendor.” It includes the procurement authority, the exact sole source basis, technical analysis, market research, alternatives considered, operational risk analysis, interface analysis, lifecycle cost comparison, price reasonableness determination, conflict-of-interest certifications, legal and procurement review, grantor approval if required, governing body approval where applicable, public notice or intent-to-award where required, contract clause review, contract scope analysis, and documentation that explains why the decision protects the agency, not the vendor.
A defensible sole source file does not say, “We picked this vendor because we know them.” It says, “We tested the market, documented the risk, proved the necessity, protected the price, and preserved the public trust.”
The Public Record: What Sole Source Failure Looks Like At Scale
Five public-record cases are worth studying. They are not random examples. They are the patterns this entire Insight is written about.
Albuquerque and TASER: the worst-case sole source
This is the case every public safety leader should know.
In 2013, the Albuquerque Police Department processed a $1.95 million noncompetitive purchase of TASER Axon Flex body cameras and Evidence.com under an “Other Exempt Purchase” designation. The procurement file relied on a 2011 sole-source contract for TASER weapons that the department then extended and used as the basis for the body camera purchase, despite the original contract not covering body cameras or Evidence.com.
The New Mexico State Auditor and Albuquerque's own Office of Inspector General each documented the result. The state auditor found probable violations of city and state ethics rules, weak documentation, vulnerability to noncompetitive procurement based on connected exemptions, and concerns about an apparent unfair advantage. Public reporting documented that the former chief of police had spoken at TASER-sponsored events from Amsterdam to Australia, and accepted a consulting arrangement with TASER at $1,000 per day plus airfare, meals, and hotels, with the consulting offer coming within weeks of the city approving the body camera contract. Auditors found that department personnel claimed they had tested cameras from other brands, including VieVu, Scorpion, GoPro, and Wolfcom, but had not provided procurement with any documentation of that testing.
This is what agencies should fear most. Not that the sole source was unpopular. That the file could not separate legitimate operational need from vendor influence, weak documentation, and public trust concerns. The career consequences played out in public. The reputational damage was permanent. The corrective action was extensive.
Every Sentinel client should know this case exists. It is what an undisciplined sole source looks like when it survives long enough to be audited.
LAPD and Axon Fleet: the structured ecosystem argument
The Los Angeles Police Department's sole source justification for Axon Fleet in-car video is a different example.
LAPD already used Axon body-worn cameras and Evidence.com. The existing in-car video system was reaching end of life. The systems could not synchronize. The new in-car solution would integrate immediately into the existing cloud-based, CJIS-compliant evidence repository. The City of Los Angeles treated the agreement as sole source and documented the operational dependency, the integration issue, the end-of-life context, and the reason competitive bidding was not considered practicable or advantageous.
This is the kind of file that can stand up to review. Ecosystem integration can genuinely justify sole source. Whether it should in any specific case depends on whether the agency has tested the assumption that no competing solution could deliver equivalent integration. The argument is real. It can also become the language of permanent lock-in. The difference is in the analysis, not the conclusion.
Santa Monica and Motorola: the interoperability case
The City of Santa Monica documented its limited-source procurement of Motorola radios based on a specific operational set of facts. The existing radios were no longer supported by the manufacturer. Replacement parts were unavailable. Many of the radios were incompatible with the future regional system. The project required interoperability with the regional ICIS Master Site and the LA-RICS system that connects Los Angeles County public safety agencies.
This is the kind of factual record that supports a defensible limited-source decision. The file does not say “we like Motorola.” It says compatibility with the regional interoperability system constrains the procurement. That is a different argument, and it is the kind of evidence-based justification federal procurement standards contemplate.
Cheyenne and Axon: the routine sole source pattern
The City of Cheyenne's public memo for Axon Body 4 cameras at $800,797.50 is a useful example of what many modern sole source procurements look like in practice. A local memo, a vendor-supplied sole source letter, and a public approval path through the governing body. The question for any agency facing a similar procurement is whether that file is enough, or whether the file also needs to prove market analysis, price reasonableness, lifecycle cost comparison, conflict-of-interest disclosures, and long-term agency protection.
Most sole source files in this country look more like Cheyenne's than like the Albuquerque outlier. That is not a criticism of Cheyenne. It is a recognition that the bar most agencies are clearing is the legal bar, not the audit-defense bar. The difference matters when the file gets pulled.
Orange County and Motorola: the long-cycle accountability gap
The Orange County, California Motorola radio relationship is a fifteen-year case study in what happens when sole source becomes routine.
Public reporting by Voice of OC documented that Orange County's 800 MHz Countywide Coordinated Communications System, used by all law enforcement agencies across the county, had not received an independent review for fifteen years despite costs exceeding $100 million during that period. The original system was installed in 1999 under an $84 million contract with Motorola. In 2017, the Board of Supervisors was poised to approve an additional $29 million in no-bid contracts with Motorola to finish a $140 million upgrade project, with no competitive bidding on the overall project, no presentation to supervisors, and a single-page “white paper” that did not include the full $140 million price tag in the staff reports.
Whether the underlying procurements were technically justified is a separate question from whether the public-accountability record was adequate. The reporting illustrates a structural problem that affects many long-running mission-critical vendor relationships in this country. Once a system reaches a certain level of operational integration, the procurement conversation stops happening at the same level of rigor as the original contract. Long-running vendor relationships require periodic independent review precisely because of how easy it is for the relationship to drift past the point where competition is even considered as an option.
Public safety systems are too expensive, too important, and too politically sensitive to run indefinitely on trust alone.
When Sole Sourcing Is The Right Call
Not every sole source decision is wrong. Sometimes it is the right answer, and Sentinel will say so when the case for it is real.
The first legitimate case is true proprietary continuation. If the agency is buying maintenance, replacement parts, firmware, licenses, or manufacturer-controlled services for an existing proprietary system, sole source may be appropriate. The Santa Monica radio facts are a good example of the operational evidence that supports this category. End-of-life equipment, unavailable replacement parts, incompatibility with the future regional system, and regional interoperability requirements together build a defensible record.
The second legitimate case is integration complexity inside an existing ecosystem where the integration value is genuinely higher than the value of competition. The LAPD Axon Fleet example fits this category when the documentation supports it. The agency's file has to explain the operational dependency, the integration constraint, the legal authority, and the reason the agency believes competition would not improve the outcome.
The third legitimate case is genuine emergency. A cyber incident, system failure, end-of-life collapse, dispatch continuity issue, radio failure, or public safety emergency can justify urgent procurement. Emergency procurement should be limited to what is necessary to stabilize the operation. It should not become a backdoor ten-year platform decision.
The fourth legitimate case is failed competition. If the agency solicits several qualified sources and competition is inadequate, noncompetitive procurement may be allowed under federal standards. The file has to prove the agency actually tried.
The fifth legitimate case is adjacent-product purchase from an existing vendor at a meaningfully discounted price because the vendor does not have to invest in a new RFP cycle. The discount has to be real. The terms have to be appropriate. The integration value has to be substantive.
The sixth legitimate case is solid proof of performance at a peer agency operating in a comparable environment, where the agency adopting the product is leveraging completed peer-agency evaluation rather than skipping evaluation entirely.
In all of these cases, the sole source has to be surfaced appropriately. Leadership has to approve it. The justification has to be documented to audit standard. Those in control have to have visibility and buy-in. The procurement file has to be defensible if it gets pulled.
The difference between defensible and lazy sole source is straightforward. A defensible sole source is based on evidence. A lazy sole source is based on comfort.
Sole source is appropriate when the facts make competition impracticable. It is inappropriate when convenience is dressed up as necessity.
The Competitive Process The Agency Thinks It Cannot Run
The most common argument against running a competitive procurement is time. Most of the time, that argument is wrong.
A procurement process can be as long or short as the agency genuinely needs. Frequently the agency's own internal regulations slow it down. Most of those internal steps are timed to protect the agency and ensure due diligence is conducted. The steps required by law cannot be skipped. The steps required by internal policy can sometimes be compressed.
The agency does not have to run the process alone. There are firms that manage RFPs on the agency's behalf, or support the components of the process the agency does not have the bandwidth to handle internally. Procurement consultants, technology advisors, and independent evaluators exist for this reason. The agency that says “we do not have the time” usually means “we do not have the internal capacity,” and those are different problems with different solutions.
Several compressed procurement models preserve fairness, transparency, and leverage even when timeline is tight.
A streamlined RFP. A focused solicitation with fewer pages, clearer requirements, a limited response format, and a condensed timeline. Instead of asking vendors for three hundred pages of boilerplate, the agency asks for direct responses to critical requirements, implementation approach, pricing, support model, risks, exceptions, and references.
A Request for Information followed by short-list procurement. If the agency does not fully understand the market, a rapid RFI identifies viable vendors, validates assumptions, and shapes a better RFP. This is especially useful when the agency is leaning sole source based on incomplete market knowledge.
A pre-qualified bidder list. Where allowed, the agency can use an existing qualified vendor pool, state contract, cooperative purchasing vehicle, or pre-qualified list. Federal standards require prequalified lists to be current and include enough qualified sources to ensure maximum open competition.
A single-stage evaluation. For time-sensitive procurements, the agency can avoid multi-phase evaluation and use one structured scoring event: written proposal, scripted demonstration, pricing review, references, and best-and-final offer.
Best and final offer. BAFO gives the agency leverage even on a compressed schedule. Vendors know they have one final chance to sharpen price, clarify exceptions, improve implementation commitments, or strengthen SLAs.
Scripted demonstrations. For public safety software, demos should not be sales theater. They should be scripted around agency workflows: call entry, dispatch, unit status, mobile report, evidence upload, case review, fire recommendation, EMS response, jail booking, or RMS approval.
Limited-scope pilot. For some products, especially field technology, a short controlled pilot with defined success criteria can substitute for one phase of evaluation. The key is to document the test plan and the results. The Albuquerque case is a warning here. Auditors noted the absence of testing documentation as a factor that weakened the legitimacy of the no-bid procurement. A pilot is only useful as competitive evidence if the agency can produce the file that shows what was tested, against what criteria, with what results.
For smaller, well-scoped procurements, a compressed competitive process can sometimes be completed in four to eight weeks. For complex CAD, RMS, LMR, or NG911 procurements, that is usually too aggressive, but the agency can still compress the process by running discovery, requirements validation, scoring design, vendor Q&A, demos, and BAFO in a disciplined sequence.
The agencies that run sole sources because they could not be bothered to run a competitive process pay the full cost. The agencies that run abbreviated competitive processes pay a fraction of that cost. The difference is meaningful, and the audit file looks meaningfully different too. The traceability matrix can be partial. The board question can be answered. The agency is exposed, but exposed less.
An abbreviated competition is almost always more defensible than no competition.
The Long Game Of Public Safety Procurement
The vendor that wins without competing wins on terms the agency can never recover. Every renewal, every change order, every interface, every roadmap conversation that follows starts from the same place: the vendor knows the cost and pain of leaving, and the agency knows it too.
Public safety procurement is not a finite game. The agency's mission does not end with the contract. The mission continues through deployment, through operation, through eventual replacement, through whatever comes next. The decision the agency makes in procurement is not a decision about a single contract. It is a decision about how the agency wants to be positioned in the next contract, and the contract after that, and the contract after that.
The agencies that win this game over a decade are the agencies that maintain optionality. They run competitive procurements even when they expect the incumbent to win. They preserve the agency's right to walk away. They build files that survive scrutiny. They train procurement teams to ask hard questions. They invest in the discipline that produces good decisions decade over decade.
Those agencies do not always pay less in any given year. They almost always pay less over ten years.
Why Sentinel Does Not Represent Vendors
Sentinel does not represent vendors. We are not a reseller. We do not take commissions. We do not have favored relationships with manufacturers that pay us referral fees. We do not push product.
This is one of the largest differentiators between Sentinel and other firms working in this space, and it is one of the things we are most proud of. When an advisory firm forms alliances with vendors and begins pushing products on its clients, the value of having the firm on the agency's side diminishes to the point of disappearing. We do not endorse that approach, regardless of how successful we have been working with a particular vendor's product on a previous engagement. Every procurement is unique. Every agency's needs are unique. Every solution has to be tailored to the specific need and the specific organization.
When a vendor advises an agency on procurement strategy, the advice is naturally influenced by the vendor's desired outcome. That does not mean the vendor is dishonest. It means the vendor is not neutral. The vendor's job is to win. Sentinel's job is different. Sentinel represents the agency's mission, governance, operational continuity, public trust, and long-term technology posture.
What Sentinel actually does in this work is straightforward. First, we challenge the premise. When an agency says, “We need to sole source,” we ask whether that is true, or whether it is what the incumbent vendor has made easiest. Second, we document the decision path. If competition is feasible, we help the agency run a fair, efficient, well-scoped procurement. If sole source is genuinely justified, we help build the file to audit standard before approval, not after someone starts asking questions. Third, we protect the agency's leverage. Even in a sole source, the agency can negotiate hard: price caps, renewal controls, SLA commitments, implementation staffing, acceptance criteria, data ownership, termination rights, support obligations, cybersecurity requirements, and roadmap transparency.
Sentinel does not begin with a vendor preference. We begin with the agency's operational requirement, risk posture, procurement obligations, and long-term leverage. If competition is viable, we will almost always recommend competition. If sole source is the right answer, we will help make sure the file proves it.
Sentinel governs the procurement. We never sell the platforms. Independent. Practitioner-led. Vendor-neutral. Built for the audit file and the council briefing. Not the salesperson's pitch deck.
We do not represent vendors. We represent the agency's decision integrity.
The Decision In Front Of You
The RFP process is not perfect. It can be slow. It can be overbuilt. It can be political. It can produce bad outcomes when the requirements are weak or the evaluation committee is not disciplined. Done correctly, an RFP is one of the most valuable exercises an agency can undertake.
It forces the agency to define its pain. It forces leadership to articulate the future state. It forces vendors to compete. It forces pricing into the open. It creates a record. It gives the governing body confidence. It gives the public a defensible answer. It gives the agency leverage that lasts ten years.
Sole source may sometimes be the right answer. It should be the exception that survives scrutiny, not the shortcut that avoids it.
In public safety, procurement is not just how an agency buys technology. It is how the agency proves fairness, protects trust, and decides who will shape its operations for the next decade. A sole source may get the deal done faster. A disciplined RFP, or even a disciplined abbreviated competition, helps make sure the agency can live with the decision after the vendor leaves the room.
If you are an agency facing a major technology procurement in the next twelve months, the most important decision you will make is not which vendor to choose. It is how you will choose. The how determines the who. And the how, run correctly, is the difference between a five-year contract that strengthens the agency and a ten-year contract that costs more every year and cannot be unwound.