How the City of Mesa Went From 28 Vendors to a Confident Council Vote in Weeks

Ask most local governments how they pick a new software platform and the honest answer is uncomfortable: a couple of vendors already in the building, one the IT director saw at a conference, and a renewal quote. It’s fast, but it leaves a hard question unanswered when the decision reaches the council dais — how do you know this was the right choice, and not just the familiar one?

When the City of Mesa, Arizona set out to modernize its capital planning, it wanted a better answer than that.

The problem: plenty of data, no way to plan

Mesa’s Parks & Recreation and Facilities Management departments were running capital planning out of a spreadsheet — one with tens of thousands of rows of asset data. They had no shortage of raw information. What they didn’t have was a way to actually use it: to forecast department budgets, or to say with confidence which municipal assets needed replacing now versus which could wait.

They wanted off the spreadsheet and onto a real capital-planning platform. But choosing that platform for a city of 533,400 residents — a decision multiple departments would live with for years — meant answering to the departments who’d use it every day and to a city council that had to approve it.

That’s exactly where researching on the open web falls short. Search results are shaped by whichever vendors spend the most on marketing, “top 10” lists are pay-to-play, and none of it is built around how a government actually buys. You can end up confident about three options and blind to the twenty-five you never saw.

The approach: a structured filter, not a guess

Mesa’s project team defined its core problem and high-level requirements and handed them to Marketplace.city through Clearbox Source— the government-only vendor intelligence network — without having to write an exhausting, granular spec. From there, Marketplace.city ran a structured, data-driven filter:

• Market exploration: started from the full field — 28 capital-planning solutions across the landscape, not a shortlist.
• Requirement alignment: filtered those 28 against Mesa’s precise criteria down to 8, with the detail that decides a government purchase for each one — key features, use by comparable government entities, pricing and prior contracts, ability to meet required integrations, and fit against Mesa’s “must-have” requirements.
• Deep-dive collection: pulled hyper-specific information, localized pricing, and cooperative-contract data on those 8, narrowing to the 2 finalists that genuinely fit.
• The demo phase: coordinated demos for the final two. On paper they looked comparable; hands-on, one was a fantastic fit and the other didn’t match the city’s workflow. The right choice was obvious.

“We got to a point from 28 solutions — that we could never ever do a demo with — to two that very strongly met our needs. We went from 28 down to two, we held demos, one was fantastic, and from that there was a clear winner that we were able to walk through and get approval for. I don’t think we could have reached this point in either the pace or the quality of what we did without Marketplace.city.”

— Sam McKenna, Senior IT Project Manager, City of Mesa

The result: approved, adopted, and institutionalized

The proof of a good procurement isn’t the contract — it’s what happens after. Three things stand out for Mesa:

• A council vote that stuck. Because the market data was socialized with leadership well before the final presentation, the city council understood the rigor behind the decision and approved the purchase without re-litigating it.
• Real adoption. Today, 30 to 35 users across multiple departments actively work in the platform.
• A new default. Mesa has built Marketplace.city into its standard operating procedures — the first stop for any new procurement that needs real market research or vendor filtering.

The takeaway

Mesa didn’t get a better outcome by working harder on a spreadsheet. It got there by starting from the whole market instead of a handful of familiar names — then letting a structured filter carry it from 28 options down to the two worth a demo. That’s the difference between a defensible decision and a lucky one, and it’s what a government-only research network is for.

Want to see what filtering the full field looks like for a category you’re deciding on? Start a free 14-day trial of Clearbox Source — nearly 400 market landscapes built exclusively for the public sector. Start your free trial →