How to Justify Strategic Planning Software to a City Council on a $200K Budget

It's 4:47 PM the day before the council meeting. Forty-seven emails. Three from the Chief of Staff. Public Works hasn't updated its KPIs in fourteen weeks. The pivot table just broke. And the Council Member who calls every quarter wants the equity overlay on pothole response times by district — for tomorrow's packet.

You know the fix. You've sat through three demos this quarter. You also know the line that kills it dead at the dais: "Why do we need software for this? Don't we already have Excel?"

We've spent twenty years watching that line decide council votes. Some cities answer it well. Most don't. Across the council proposals our customer success team has helped build, what separates a yes from a no isn't the software. It's the case the city manager builds in the seventy-two hours before the gavel — and the data that case rests on.

This is what we've watched work, and what we've watched fail. With the numbers — and a clear line between the figures we measure across our platform and the illustrative math you should run for your city.

‍

‍

What our platform data actually shows (the benchmark most decks lack)

Before the framework, the numbers we wish every city manager had on slide 2 of their deck. These are live figures across the local-government strategic plans we host on ClearPoint — the kind of peer benchmark a Council Member will ask you to stand behind.

Two patterns surprise nobody who runs this work, and both are measured, not estimated:

1. About half of local-government metrics have no active owner. Across our local-government plans, 51.98% of measures have no active owner — a "phantom owner" who logs zero updates during the reporting cycle. Roughly three in ten measures (29.71%) have never been populated even once. That is the source of the slide that says everything is green when half the metrics haven't been touched since Q1.
2. A large share of goals never leaves the starting line. Just over one in five goals — 21.06% — sits in "Not Started." Only 16% of all measures read green; among measures that have actually been rated, 64.2% are green. The honest distribution is the one that wins skeptical Council Members, because it looks like the plan they already suspect they have.

If you take nothing else from this article, take that benchmark. Print it. Bring it to the dais — and then put your own city's number next to it.

How we measure this. A "phantom owner" is any metric owner who submits zero updates during an active reporting cycle. The 51.98% figure is the share of measures with no active owner across the U.S. local-government strategic plans on ClearPoint, after excluding demonstration and training data — a base of 124 local-government organizations, 1,167 active plans, and 41,687 tracked measures (verified June 2026). This is the same methodology we use internally to flag at-risk plans for our customer success team.

How to build the case before the meeting

We've sat in on dozens of council votes on planning software, working alongside our customer success team. The vote rarely turns on what the software does. It turns on four questions, asked in this order:

1. What is the status quo costing us? (cost of doing nothing)
2. What will this realistically deliver? (benefit projection)
3. What's the risk if it fails? (risk control)
4. How do we de-risk the decision? (pilot rollout)

Skip any of the four and the proposal stalls. We've watched that happen more times than we can count. Cover all four with concrete numbers and named peer references, and the Council Member who walked in skeptical walks out asking when you can start.

The pattern in the proposals we help build is striking. Most that lead with features need a second attempt; most that lead with a dollar figure for the cost of doing nothing pass on the first. The single strongest predictor of first-attempt passage isn't deck length or vendor reputation — it's whether the proposal opened with the cost of the status quo. For a fuller treatment of the buying decision itself, see our guide to writing an RFP for strategic planning software in local government.

‍

‍

Step 1: Quantify what doing nothing already costs

Most council justifications skip this entirely. They open with what the new tool does, instead of what doing nothing costs. Until you put a dollar figure on the current cost, the new tool reads as an expense, not a substitution.

We've watched cities sitting on a six-figure hidden tax walk away from a mid-five-figure platform proposal because slide 1 led with the demo. Same data on the deck. Same vendor. Different order. Different vote.

There are four cost lines that show up in every winning council deck we've seen. The figures below are an illustrative worked example for a mid-sized city — run the same lines with your own city's hours and rates; the structure is what travels, not our placeholder numbers.

1. The reporting cycle tax

Suppose your strategy office spends roughly twelve working days per council reporting cycle — counting analyst hours, department-head chasing, formatting, QC, and rework. For a quarterly cycle, that's about fifty working days a year on a single deliverable nobody has time to read. Put your own cycle length in; most cities we work with land somewhere between two and three weeks per quarter.

That's not a software problem. It's a hidden tax on your strategy office.

2. The phantom-owner tax

The phantom-owner rate isn't a vanity stat — across our local-government plans, 51.98% of measures have no active owner. It's the source of the slide that says everything is green when half the metrics haven't been touched since Q1. Every unowned metric is chase time for your analysts, on data whose quality is questionable the moment it finally arrives. For a city tracking dozens of KPIs, that chase can run on the order of one to two analyst-weeks a year — time you can put a loaded-labor dollar figure against on slide 1.

3. The audit findings tail

Cities that miss a single audit finding pay meaningful extra audit fees per finding the following year, on top of staff remediation time. Practitioner discussions at GFOA conferences commonly put that in the low tens of thousands of dollars per finding — use a conservative figure your own finance officer will defend, not a vendor estimate. Customers tell us it runs higher when corrective action plans drag across two cycles.

The Pittsfield, MA ARPA case is the canonical recent example. Auditors Scanlon & Associates wrote: "The reporting error stemmed from a bookkeeping problem, not a spending problem — expenses were incorrectly included in both the first- and second-quarter reports." A copy-paste error became a public audit finding.

4. The shelfware cost

Denver City Auditor Tim O'Brien wrote in 2025: "Denver's Mayor's Office of Social Equity and Innovation created a strategic plan, but it lacks measurable objectives, updated metrics, cost and responsibility designations." That plan exists. It just doesn't run anything. The cost isn't the consultant fee that produced it. It's the credibility tax every time leadership references it and someone notices nothing has moved.

How this lands on slide 1: in dollars. Reporting hours × loaded labor rate. Audit findings × your finance officer's per-finding figure. Plus the line "as of today, X% of our strategic plan objectives have a measurable owner and current data." Our local-government benchmark says about half of measures have no owner at all and one in five goals is "Not Started" — if your own number is in that range, you have your case.

What we've actually watched fail (the post-mortem)

Two stories from our own files. Both with permission. Neither named. The dollar figures are the cities' own ROI-calculator inputs, not platform measurements.

Failed first attempt — a Pacific Northwest city, 180,000 residents, 2023.
The strategy office walked into council with a deck we helped build. The vote tied. The Mayor pro tem said: "Bring me a number for what we're spending on this today." They hadn't run that number. The proposal was tabled for nine months. When they came back, the deck wasn't better. The order was different. Here is the side-by-side:

Cost first. Tool second. That's the entire lesson.

Failed second attempt — a Mountain West city, 95,000 residents, 2024.
This one was on us. The proposal led with cost. The numbers were defensible. The pilot was scoped. But the team didn't pre-brief Council Members one-on-one. The skeptical Member walked in cold and raised three objections in twelve minutes, in this order:

1. "How do we know this won't take three years like Tyler Munis?" — implementation timeline. The answer was on slide 22, the 90-day Gantt with public dashboard milestone at day 90. He never got there.
2. "What happens to our data if we want to leave?" — vendor lock-in. The answer was on slide 18, the data export clause language. Same outcome.
3. "Who runs this alongside our Tyler implementation?" — staff capacity. The answer was on slide 14, the configurability comparison showing analyst-led setup. Same outcome.

The vote split 3-3 with the Mayor abstaining. The Member resigned six months later for unrelated reasons. The proposal hasn't come back. By the city's own ROI-calculator inputs, the delay has cost it well into six figures in continued reporting tax plus two more audit cycles with no remediation tracking — against a platform proposal that would have cost a fraction of that in year one.

The lesson there: the deck doesn't pass votes. The conversation in Council Members' offices the week before passes votes. The deck just confirms what's already been agreed. If a Council Member's objection lands on slide 14 of an appendix nobody opens, that objection wasn't answered.

We share these because most vendor blogs only show you the wins.

When you should walk away from any planning platform — a self-screening framework

We should have written this checklist before a conversation we had with a small town in late 2022. We didn't. They signed. By month fourteen they cancelled. Here is the discovery list we now run with every prospect — and the one any city manager should self-run before agreeing to a platform proposal. Ours included.

If you can't tick at least four of the five, the platform won't deliver enough value to defend the procurement. The honest move is to walk away, hire a part-time analyst, run two reporting cycles on a structured spreadsheet, and revisit in eighteen months.

We should have walked the small town in 2022 through this checklist. They would have ticked two of five. We took the contract anyway. The town got eight months of value, then twelve months of unused license. That's on us. The framework above is what we should have used — and what we now run with every prospect, including the ones who later hear "come back in eighteen months."

Step 2: Project benefits a Council Member can defend in cross-examination

We've watched Council Members nod through "this cuts our reporting cycle from weeks to days" and lean back in their chairs at "a fundamental shift in how the city operates." The first lands because a Member can defend it under cross-examination from a colleague. The second sounds like every Tyler Munis pitch they remember failing.

Three benefit categories pass the cross-examination test. Anything beyond these three is harder to defend on the dais.

Benefit A — Time returned to your team

The strongest, most defensible claim. Across our government clients, council reporting cycles drop from weeks to a couple of working days within the first two cycles, because the platform holds the structure between reports instead of rebuilding it each quarter. Measure your own before-and-after and quote that.

Frame it on the slide as: "We will return X analyst-hours per quarter to actual analysis." Not: "We will become more efficient."

Benefit B — Public dashboards Council Members can actually point to

This one is underrated. Most cities already maintain public-facing dashboards in some form. Bloomberg What Works Cities Platinum cities like Cambridge, MA and Kansas City, MO are evaluated explicitly on the depth and discoverability of their public dashboards. We host hundreds of public customer dashboards on ClearPoint. Tacoma, WA's Open Performance is a frequently-cited example.

The slide that lands in council is this one: open Tacoma's Open Performance on a tablet. Pass it across the dais. Then say "this is what residents see in our city today" — usually a static PDF, sometimes nothing. "This is what they could see by Q3." We've watched that single tablet pass change the temperature of a vote more than once.

Benefit C — Audit-readiness as a side effect

When the strategic plan, the KPIs, the source data, and the narrative all live in one place, single audits get measurably faster. The story we share with skeptical Council Members is from a Midwest county we work with — population around 320,000. Coming into FY2024, they had three open audit findings carried over from the prior cycle, with an average corrective action plan close time of about eleven months. After moving their corrective action plan tracking onto the platform — same underlying data, just structured and time-stamped — all three findings closed inside fourteen weeks of the next cycle. The findings haven't recurred.

We share that one because it's the cleanest before-and-after we have. Your starting baseline determines what's possible. If you have ten open findings and no tracking, it's a bigger lift. If you have one and a working spreadsheet, the gain is smaller. But the pattern — structure plus timestamps plus owner accountability cuts close time — holds.

‍

‍

What NOT to put on the council slide: anything that promises to fundamentally change how the city operates. After the Cascade PBS Bellingham AI scandal in early 2025, two of our city manager clients independently told us their councils now flag any vendor pitch with "AI-powered" or "next-generation" for extra scrutiny. One of those councils now requires a written AI-disclosure from any vendor before procurement signs.

Step 3: Pre-answer the risk question that always lands

Every council has that Member. The one who watched the Tyler Munis implementation drag three years. The one who saw the Workday rollout go millions over. They will ask, in some form: "What happens when this doesn't work?"

We've watched that exact question land in council rooms repeatedly. Each time, the city manager who had a slide ready — exit clause, data export terms, decision-point language — passed the vote. Each time the city manager who didn't, walked out without one.

You answer that question before they ask it. Three risk categories, three controls.

Risk 1 — Implementation drag

Control: scope a 90-day pilot, not a 12-month enterprise rollout. Two departments, one outcome metric per department. Define what "success" looks like in writing before kickoff. If the pilot misses, the contract has an exit. If it lands, you expand by department, not all at once.

Risk 2 — Vendor lock-in

Control: the data is yours. Confirm in writing that you can export every plan, every measure, every milestone, every comment as structured data, on demand, without a per-record fee. Confirm public dashboards remain accessible to residents during any transition. This single clause kills the majority of council pushback we've watched.

Risk 3 — Staff turnover during rollout

City manager and finance director turnover hit sharply in 2024-2025. Calistoga saw double-digit senior-staff turnover. Tigard lost its Mayor and CM inside 70 days. Similar patterns hit Oakland and Ashland. Council Members read the news.

Control: the platform must be configurable by an analyst, not a consultant. The plan structure must survive the departure of the person who built it. Phrase it on the slide as: "The plan has its own operating system, independent of any one staff member." When leadership churns, the plan doesn't die with it.

In practice: A mid-Atlantic county we work with had its Performance Manager leave six months into implementation. Because the plan structure, the KPI definitions, the owner assignments, and the historical data were all in the platform — not in someone's spreadsheet — the new hire was running the next council report inside three weeks. That's the operating system, not the software.

Step 4: Scope a pilot the council can approve without committing the city

We've watched pilot scope flip tied council votes on its own. When the ask is scoped as a 90-day pilot rather than a city-wide rollout, first-attempt pass rates climb sharply. Same buyers. Same skeptical Members. Different ask.

A defensible pilot has six elements. Each one fits on a single line.

The decision-point line is the one that closes skeptical Members. It says: "We are not asking you to approve the city-wide rollout today. We are asking you to approve the test."

That's a different vote. That's the higher pass rate above.

‍

‍

How to choose the right tool for your council vote

Here's what cities are actually choosing between — scored honestly across the four options that show up on every shortlist we've seen in the last three years. For the full landscape and a structured scoring sheet, see our companion guide on writing a strategic planning software RFP for local government, and the broader guide to strategic planning.

When ClearPoint is not the right answer. Three scenarios we tell prospects to walk away from us:

1. Cities under 10,000 residents with no dedicated strategy office. A structured spreadsheet plus a quarterly review cadence does the job. The platform's value lift is below the cost. Re-procure us when you grow past 25,000 or hire your first Performance Manager.
2. A single one-off strategic plan with no annual renewal and no public dashboard requirement. A consulting engagement to write the plan plus a basic project tracker covers the need. Don't pay for an operating system you'll touch twice.
3. Cities already deep in the Tyler ERP ecosystem who want a lightweight scorecard tied to existing financials, not a strategic plan operating system. Tyler Performance's Munis integration can outweigh its design limits for a first cycle. We've seen cities run it that way for a year and re-procure to us when their needs grew past the scorecard.

The matrix above is otherwise hard on rivals because, for the buyer this article is written for — a city manager going to council with a multi-department strategic plan — those rivals are genuinely behind on government-specific dimensions. But Envisio's ease of use and resident-dashboard design support are real advantages, and saying so honestly is the only way the rest of the matrix earns its credibility.

‍

‍

The 30-day council prep plan

If you have a council session within the next 90 days where this conversation lands, here's what works.

Days 1–7 — Quantify the status quo.
Pull reporting hours from your strategy office. Pull audit findings cost from the last two cycles. Audit your published strategic plan: how many objectives have a measurable owner and current data today? Compare your number to our local-government benchmark — about half of measures have no owner and one in five goals is "Not Started." If your own plan is in that range, you have your case.
We've seen this go wrong when: a strategy office pulled a multi-week reporting-cycle figure and buried it on slide 22 because it felt "too embarrassing." That number was the case. If you find the number embarrassing, you've found your headline.

Days 8–14 — Find your peer.
Identify three peer cities — same size, same region, same fiscal pressures — running on a strategic planning platform. Look at their public dashboards. Email their Performance Manager. Many of them respond. Bloomberg What Works Cities and ICMA networks are the fastest path to a peer reference.
We've seen this go wrong when: a city brought peer references the Council Members had never heard of. A peer reference Council Members can't place is dead weight. Tacoma, Charlotte, Cambridge MA, Kansas City — those names land. A city in another state with a similar population that nobody recognizes does not.

Days 15–21 — Score the four shortlist options on the matrix above.
On one page. Side by side. No marketing language allowed in the cells. Bring the matrix to procurement.
We've seen this go wrong when: the procurement officer vetoed a winning proposal because the scorecard cells were copied from vendor marketing decks. If you didn't write the dimensions and the rationale yourself, you don't own the conclusion — and procurement will say so.

Days 22–28 — Build the deck.
Six slides, in this order: cost of status quo · benefit projection · risk control · pilot plan · vendor matrix · decision ask.
We've seen this go wrong when: a six-slide deck became a thirty-slide deck the morning of the meeting because someone wanted to be "thorough." The appendix is where details go. The deck is where the decision goes.

Day 29 — Pre-brief Council Members one-on-one.
Block thirty-minute calendar holds with each Member individually. Walk through slides 1, 4, and 5 — cost, pilot, decision ask. Ask which question they expect to raise on the dais. Write it down.
We've seen this go wrong when: see the Mountain West story above. Three objections, three appendix slides nobody opened, a six-figure delay. Skip the pre-brief and the deck has to do work it isn't built to do.

Day 30 — Present.
Lead with the Tuesday at 4:47 PM. End with the pilot.

‍

‍

Frequently asked questions

How do you justify strategic planning software to a skeptical city council?

Lead with the cost of the status quo, not the features of the new tool. Quantify reporting hours, audit findings, and stale plan objectives in dollars. Then present a 90-day pilot scoped to two departments with a public dashboard milestone, an exit clause, and a council review point before any city-wide expansion. The strongest predictor of first-attempt passage we see is whether slide 1 opens with a dollar figure for the cost of doing nothing — and a defensible peer benchmark, such as the fact that 51.98% of local-government measures on our platform have no active owner.

How do you answer the Council Member who says "we already paid for Tyler — why aren't we using that?"

The honest answer has two parts. First: Tyler's performance module is a financial-system reporting tool. It tracks budget execution and grant compliance. It is not a strategic plan operating system — it doesn't model goals, owners, public dashboards, or council narrative the way a city actually structures its plan. Second: a city deeply embedded in the Tyler stack can absolutely run a basic scorecard inside Tyler Performance for a first cycle, and that may be the right move for year one. But the moment the council asks for a cross-departmental view, a public dashboard residents can read without a login, or a comparison to peer cities, the Tyler module hits its design ceiling. Frame it on the slide as: "Tyler does the financials. We need a tool that does the strategy."

What happens to historical strategic plan data during a mid-cycle City Manager transition?

It depends on where the data lives, not on which platform you bought. If your strategic plan, KPI definitions, owner assignments, source data, and council narrative all live in one platform with role-based access — not in the departing CM's spreadsheets and email threads — the new hire can run the next council report inside three to four weeks of arrival. When that knowledge lives in the departing CM's filesystem instead, the gap is more like two to three reporting cycles and a budget season — a six- to nine-month visibility gap your council will notice. The fix is structural: keep the plan, the history, and the public dashboard platform-resident, not person-resident.

What do you do when a Council Member raises an objection in real time you don't have a slide for?

Three rules. First, never answer immediately. The pre-brief was supposed to surface this; if it didn't, the dais is not where you find the data. Say: "That's a fair question. I want to give you a defensible answer, not a guess. Can I bring you a written response before next session?" Second, write down the exact phrasing of the objection and which Member raised it, in the moment — the specific words determine which appendix slide or external study answers it. Third, schedule a follow-up briefing with that Member specifically before the next reading, never the full council. In our experience, the objecting Member who gets a written, one-on-one answer becomes a yes far more often than the one a city manager tried to answer cold in the room. Don't ask for a vote you don't have the answer for.

The bottom line

The most instructive council vote we ever watched was a narrow pass for a platform proposal in a city that had rejected a cheaper consulting engagement earlier the same evening. The difference wasn't the price. The consultant had walked the council through deliverables. The city manager had walked the council through what doing nothing already cost them — loaded analyst hours, audit findings the prior cycle, and a strategic plan that was mostly stale. The council voted on the comparison, not the invoice. The cheaper line item lost. The more expensive one passed — because one of them came with a number for the status quo.

The Pacific Northwest story and the Mountain West story together teach the harder lesson. Cost on slide 1 won't save you if you skip the pre-brief. The best pre-brief in the world won't save you if your deck still leads with a demo. Both. Always.

Number on slide 1. Conversations the week before. Then the vote takes care of itself. When you're ready to see what board-ready, council-ready reporting actually looks like, request a ClearPoint demo.

About this guide. Written by Joseph Lucco, VP of Customer Success at ClearPoint Strategy, drawing on aggregated, anonymized platform data from our local-government customer base (124 organizations, 1,167 active plans, 41,687 measures; verified June 2026) and on the council proposals our customer success team has helped build. Where a figure is an illustrative example for a hypothetical city, we say so; the platform benchmarks are measured.

Sources

• Denver Auditor Timothy M. O'Brien — audit of the Mayor's Office of Social Equity & Innovation (plan "lacks measurable objectives, updated metrics, cost and responsibility designations"), Feb 2025; follow-up Jan 2026. Source: Denver Gazette.
• City of Bellingham, WA — investigation after records (Cascade PBS / KNKX) showed a staffer asking ChatGPT to shape contract requirements to favor or exclude vendors (reported Jan 2026); WA cities' AI-policy gap (Aug 2025). Source: Cascade PBS.
• ClearPoint Strategy platform data — aggregated, anonymized: 124 local-government organizations, 1,167 active plans, 41,687 tracked measures (demo/training excluded); verified June 2026.
• ClearPoint Strategic Planning Report — 20,582 strategic plans / 31.2M data rows / 562 organizations (2017–2024).