Shifting from "feature shopping" to value-based procurement

The city was preparing to overhaul its digital presence. Stakeholders had developed a highly specific list of technical requirements, prescriptive (e.g., "Do you have a native form builder?") rather than outcome-oriented. That created a risk: hiring a vendor who could check the boxes while failing to solve the underlying operational friction.

I pivoted the procurement logic. Instead of asking vendors to confirm features, I reframed the RFP around Value-Based User Stories: from "omnichannel posting" to communication efficiency and time-to-public in a crisis; from "document replacement" to permanent link integrity and an ADA-compliant legal archive; from "form builders" to departmental autonomy and zero-code operations; from "job modules" to recruitment branding and hire-to-archive workflow. Vendors had to demonstrate how their solutions would improve staff efficiency and resident experience, not just list capabilities.

The city evaluated vendors on workflow speed, compliance, and measurable outcomes instead of feature checklists. Council got a clear scorecard based on staff time savings and resident satisfaction. The shift ensured the city got what it needed to function: targeted utility over "shiny" objects, and forced vendors to prove back-office utility, not just aesthetics.