Outcome-Based Procurement: A Different Way to Write Public Sector RFPs

For decades, government RFPs have been built around a checklist: capabilities, integrations, uptime guarantees, feature parity with the incumbent system. Responses followed suit, answering every requirement line by line.

Lately, a different model has been surfacing in solicitations and in conversations with finance directors, county administrators, and procurement leads. It’s called outcome-based procurement, and it changes the question the RFP asks.

What Outcome-Based Procurement Means

Under a conventional solicitation, the solution is specified by the agency, and vendors are asked to prove they can deliver it. Under an outcome-based solicitation, the result is specified instead (e.g., modernized records access, shorter constituent wait times, stronger short-term rental compliance), and the route is left open.

The distinction matters. A capability-based RFP asks a vendor to build a vehicle the agency has already designed. An outcome-based RFP asks a vendor to help reach a destination that may not be fully mapped. This is an acknowledgment that agencies know best what their communities need, while vendors bring experience from solving similar challenges across many jurisdictions. An outcome-based RFP puts both to work.

Why It’s Emerging Now

Among the forces pushing agencies toward this model, two stand out.

1. Tools are outpacing procurement cycles. In fast-moving categories like short-term rental compliance and cloud-based records management, capabilities evolve faster than solicitation timelines can absorb. With a rigid capabilities list, an agency can be locked into yesterday’s solution before the contract is even signed.
2. Naming a problem without prescribing its fix has become more acceptable. Agencies are increasingly comfortable describing the gap and inviting vendors to help shape the answer. Precedent exists at the federal level, where fixed-price, outcome-based contracting ties vendor performance to defined results rather than to hours billed or boxes checked. At the state and local level, the Harvard Kennedy School Government Performance Lab has documented the same shift for years, and its guidance on results-driven solicitations has been applied across dozens of jurisdictions.

What Changes in Evaluation

Once the outcome leads, compliance stops being the grading threshold. Most qualified vendors can check most boxes, so a fully compliant response is where scoring starts, not where it’s won. Evaluation shifts toward three signals that are much harder to fake:

1. A point of view on the problem, not a list of features that touch it. What distinguishes a strong response is an explanation of how the work gets done and why it’s done that way. The difference between a vendor who has solved this before and one who has only read about it shows up on the first page.
2. Evidence of comparable outcomes elsewhere. Past results carry more weight than theoretical capability. A compliance rate, a processing time, a revenue figure from a jurisdiction of comparable size—these answer the question a feature matrix cannot: Will this actually work here?
3. A collaborative posture and a clear path. A strong response accounts for where the agency is today, what the first year looks like, and what the result should be two years out. It reads as an opening position on a shared problem, not a fixed deliverable handed over at signing.

Scoring for these qualities takes more preparation than scoring a feature matrix. Weighting has to be settled before responses arrive, evaluators need a shared definition of strong evidence, and the panel needs at least one member who understands the operational problem, not just the procurement process.

Where It’s Gaining Ground in Technology Procurement

Much of the documented history of results-driven contracting sits in human services, where outcomes like sustained employment or stable housing are relatively straightforward to name and measure. Technology procurement is a newer frontier, and adoption is taking hold in categories where the underlying problem is well understood but the ideal solution is not yet standardized.

Short-term rental compliance is one clear example. Registration and tax revenue lost to unregistered listings is a known gap, but the right mix of detection, enforcement, and taxpayer experience varies widely by jurisdiction. Bay County, FL doubled tourist tax collections after shifting from scattered outreach to focused enforcement built on accurate property data, a result that would have been hard to write into a feature specification in advance but easy to name as a goal.

Cloud-based records modernization is another. Agencies replacing legacy systems are weighing today’s needs against flexibility they cannot fully define yet. In Berks County, PA , 270+ years of records dating back to 1752 were unified in a single system, eRecording adoption reached 95%, and document processing now runs 10x faster than paper. The destination was clear from the start, even if the route was not.

Questions Worth Asking Before the Next Solicitation

For agencies weighing whether an outcome-based approach fits, a few questions settle it quickly:

• Is the problem well defined, or is the solution well defined? Only the first case calls for an outcome-based RFP.
• Would a vendor with a better idea have any way to propose it under the current scoring matrix?
• What measurable result would make this procurement a success two years from now, and is that result written anywhere in the document?
• Which internal stakeholders need to agree on the outcome before the solicitation is published?

Moving the Bar, Not Lowering It

For government leaders planning a modernization initiative in these categories, or others where the solution space is still forming, a capabilities-first RFP undersells what’s possible. Writing the outcome first asks more of a vendor. It moves the bar toward results constituents can feel and elected officials can defend, and it rewards the vendors willing to show their work.

In agencies across North America, that shift is already underway. Neumo works with government teams to deliver against the outcomes they define.

Book a Demo to talk through what an outcome-based approach could look like for your next initiative.