Every public manager eventually faces the same deceptively simple question: should we do this ourselves, or hire someone else to do it? The make-versus-buy decision sits at the heart of modern governance, yet it is routinely treated as a financial calculation rather than a strategic one. The result is a landscape littered with contracts that save money on paper but destroy public value in practice—and in-house operations that persist not because they perform well, but because no one has built the case for change.

The real challenge isn't choosing between direct provision and contracting. It's understanding that each option creates a fundamentally different governance architecture—a different set of risks, accountability relationships, and management demands. Contracting doesn't eliminate the need for government capacity; it transforms it. You trade the challenge of managing employees for the often harder challenge of managing markets, contracts, and third-party relationships across political cycles.

What follows is a strategic framework for navigating these decisions with the sophistication they demand. We'll examine the criteria that should drive make-or-buy choices beyond simple cost comparison, the art of writing contracts that are simultaneously precise and adaptive, and the disciplines required to maintain accountability without strangling contractor performance. If you manage public services or design the policies that shape them, these frameworks will sharpen how you think about one of governance's most consequential decisions.

Cost comparison is where most make-or-buy analyses begin and, too often, where they end. But Eugene Bardach's insight about implementation complexity applies directly here: the decision to contract is itself a policy choice with its own implementation chain, and every link in that chain can fail. A strategic framework must evaluate not just production efficiency but the total governance cost—including the cost of specifying, monitoring, enforcing, and adapting the arrangement over time.

The first criterion is asset specificity. When a service requires deep institutional knowledge, specialized relationships with citizens, or capabilities that can't easily be rebuilt if lost, the risks of contracting rise sharply. Consider child protective services: the judgment calls involved, the integration with courts and social services, and the reputational stakes make outsourcing extraordinarily risky. Contrast this with fleet maintenance, where the work is well-defined and the market of capable providers is robust. The more specific and irreplaceable the institutional asset, the stronger the case for internal provision.

The second criterion is measurability. Contracting works well when you can clearly define and verify what success looks like. It struggles when outcomes are ambiguous, when quality is subjective, or when the most important dimensions of performance resist quantification. If you can't measure it well enough to write it into a contract, you probably can't manage it well through a contractor. This isn't a permanent condition—measurement capabilities evolve—but it's a constraint that must be honestly assessed rather than wished away.

The third criterion is market competitiveness. Contracting delivers value when genuine competition exists among qualified providers. When the market thins to one or two realistic bidders, the theoretical advantages of contracting evaporate. You end up with a bilateral monopoly—government can't easily switch providers, and the provider can't easily find another client of that scale. These relationships require a fundamentally different management approach than competitive procurement, and pretending otherwise is a recipe for contractor capture.

Finally, consider political and democratic accountability. Some services carry such direct implications for citizen rights, equity, or public trust that the attenuation of accountability inherent in contracting becomes unacceptable regardless of efficiency gains. The question isn't merely can we contract this, but should the public's relationship with this service pass through a private intermediary? Strategic managers weigh all four criteria together, recognizing that the right answer often isn't a binary make-or-buy but a carefully designed hybrid.

Takeaway

Cost is the easiest criterion to measure and the least sufficient to decide on. The strategic make-or-buy decision hinges on asset specificity, measurability, market competitiveness, and democratic accountability—and the strongest analysis weighs all four simultaneously.

The contract document is where strategic intent meets operational reality, and the gap between the two is where public value goes to die. The central tension in contract specification is between precision and adaptability. Specify too little and you get creative compliance—contractors meeting the letter of vague terms while missing the spirit entirely. Specify too much and you get rigidity—an agreement that cannot adapt to changing conditions, emerging needs, or better methods the contractor might discover.

The most effective approach is to anchor contracts in outcome specifications rather than process prescriptions wherever possible. Instead of dictating how many staff must be deployed or what hours they must work, define the results you're purchasing: response times, quality thresholds, citizen satisfaction levels, equity metrics. This gives contractors the freedom to innovate on methods while holding them accountable for what actually matters. But outcome specification only works when paired with robust measurement systems—which loops back to the measurability criterion from the make-or-buy decision.

Every contract must address what Bardach would call the implementation scenario—the realistic sequence of events through which performance will unfold. This means specifying not just standards but the information architecture that will make compliance visible: reporting requirements, data access rights, audit provisions, and inspection protocols. A contract that defines excellent performance but provides no reliable way to observe whether it's occurring is functionally unenforceable. The specification of monitoring mechanisms deserves as much attention as the specification of deliverables.

Equally critical is the change management framework built into the agreement. Long-term service contracts that lack structured mechanisms for renegotiation become prisons for both parties. Effective contracts include provisions for periodic review, defined triggers for renegotiation, and clear processes for scope changes. They also specify what happens when things go wrong—graduated remedies that range from corrective action plans through financial penalties to termination. The remedy structure must be credible; penalties so severe they'll never realistically be imposed are no penalties at all.

Perhaps most overlooked is specifying the transition architecture—what happens at the end of the contract. Who owns the data? How is institutional knowledge transferred? What happens to service continuity during rebidding? Failing to address transition creates massive switching costs that lock government into incumbent contractors regardless of performance. The best time to negotiate your exit is before you enter, when competitive leverage is highest.

Takeaway

A well-specified contract is not a longer contract—it's one that defines outcomes clearly, makes performance observable, accommodates change gracefully, and protects the government's ability to walk away.

Once the contract is signed, a different kind of governance challenge begins. The central paradox of contractor management is that the relationship must be simultaneously arm's-length and collaborative. Too much distance and you lose situational awareness—problems fester until they become crises. Too much closeness and you risk regulatory capture, where the oversight function is compromised by personal relationships and shared interests that diverge from the public interest.

Effective contract management operates on three tiers. The first is compliance monitoring—systematic verification that contractual requirements are being met. This is the baseline, and it must be rigorous without being adversarial. Regular reporting, data analysis, site visits, and citizen feedback loops all contribute. The key discipline is maintaining consistent attention; many contract failures trace not to inadequate specifications but to monitoring regimes that were vigorous at launch and atrophied over time as attention shifted to newer priorities.

The second tier is performance management—an ongoing dialogue about how outcomes can improve, not just whether minimums are being met. This is where the relationship becomes genuinely collaborative. High-performing contract managers hold regular performance reviews that look forward, not just backward. They share information about changing needs, emerging challenges, and evolving expectations. They treat contractors as partners in problem-solving while never forgetting that the partnership exists within an accountability framework defined by the public interest.

The third tier is strategic management—maintaining the government's capacity to make informed decisions about the future of the arrangement. This means preserving enough internal expertise to evaluate contractor performance intelligently, maintaining awareness of market alternatives, and investing in the data systems that make informed rebidding possible. The greatest risk in long-term contracting isn't poor performance during the contract—it's the gradual erosion of the government's ability to know whether performance is poor, or to do anything about it if it is.

The organizational design question matters enormously. Contract management is a professional discipline, not an administrative afterthought. Yet many governments assign contract oversight to program staff who lack procurement expertise, or to procurement staff who lack program knowledge. The most effective models create dedicated contract management functions staffed by people who understand both the service domain and the disciplines of oversight—and who have enough organizational authority to act on what they find.

Takeaway

The hardest part of contracting isn't choosing a provider or writing the agreement—it's sustaining the institutional attention, expertise, and independence needed to manage the relationship over years without either neglecting it or being captured by it.

The make-versus-buy decision is not a procurement question. It is a governance design choice that shapes accountability, capability, and public value for years or decades. Treating it as anything less—reducing it to cost comparisons or ideological preferences for public or private delivery—is a strategic failure with compounding consequences.

The framework that emerges is demanding but clear. Decide strategically by weighing asset specificity, measurability, market conditions, and democratic accountability together. Specify contracts around outcomes, build in observable performance measures, and protect your ability to exit. Then invest seriously in the ongoing management capacity that makes the entire architecture function.

None of this is simple. But the alternative—contracting by default, managing by hope, and discovering failures only when citizens bear the cost—is a pattern that public managers have the tools to break. The question is whether they have the institutional will to invest in the unglamorous disciplines that make contracting actually work.