Getting Elected Officials to Fund AI Initiatives

You've identified a perfect AI use case. Your team is ready. The ROI is clear.

But when you present to the City Council or Board of Supervisors, you get:

"Isn't this just hype?"
"Can't we just hire another person?"
"What about all those AI failures I read about?"

The problem isn't your idea—it's your pitch.

Elected officials think differently than technologists. After working with dozens of local government CIOs navigating these conversations, I've identified three approaches that consistently work.

Approach 1: Lead with Pain, Not Technology

The Wrong Way

"We'd like to implement a machine learning solution leveraging natural language processing to enhance our document classification workflow through automated routing algorithms..."

What they hear: Expensive tech experiment with unclear value.

Result: "Let's table this for now."

The Right Way

"Citizens currently wait 3-4 weeks for permit responses because our planning staff spends 15 hours every week manually sorting and routing submitted documents. One AI tool can reduce that to under an hour per week, cutting citizen wait times to 1-2 weeks."

What they hear: Citizens are frustrated, staff is overwhelmed, and there's a specific solution.

Key differences:

Started with citizen impact, not technology
Quantified the problem (15 hours/week wasted)
Showed citizen benefit (faster response times)
Made solution sound simple (one tool, not a complex system)

The Formula

Pain point (What's broken and who it affects)
Cost of inaction (What happens if we don't fix it)
Solution (What we'll do)
Outcome (What changes for citizens/staff/budget)

Example:

"Our 911 dispatch center handles 2,400 non-emergency calls per month—calls that should go to 311 instead. This ties up emergency lines and delays real emergency response. We can implement an AI call routing system that automatically directs non-emergencies to the right department. Dispatch can focus on actual emergencies, and citizens get faster resolution to their issues."

Notice: Zero tech jargon, crystal clear impact.

Approach 2: Use Proof, Not Promises

Elected officials have heard countless "this will revolutionize everything" pitches. They're skeptical—rightfully so.

The Wrong Way

"AI will transform our operations and save millions of dollars across all departments."

What they think: "Sure it will. Just like that last 'revolutionary' system."

The Right Way

Show them it already worked somewhere similar.

Tactic 1: Peer City Examples

"Mountain View, a city our size, implemented this exact system in their planning department. They cut document processing time by 80%, saved $67K in overtime in the first year, and reduced permit wait times from 4 weeks to 9 days. Here's their published case study."

Why it works: Elected officials care deeply about peer comparisons. If a similar city did it successfully, it's not a risky experiment—it's catching up.

Pro tip: Find 2-3 examples. More is better. Bonus points if they're in your state or region.

Tactic 2: Run a Micro-Pilot First

"We ran a 30-day test in one division using free trial access. Here are the results: 12 hours saved per week, 99% accuracy, zero complaints from staff, enthusiastic feedback. We want to expand it citywide."

Why it works: You're not asking them to bet on an unproven idea. You're showing them proof from your own organization.

How to do this:

Find AI tools with free trials or low-cost pilots
Test in one team for 30-60 days
Track metrics religiously
Gather user testimonials
Present results, not predictions

Tactic 3: Show the Risk of Inaction

"Every month we delay, we're leaving $8,000 on the table in staff time costs. Over a year, that's $96K—enough to fund two additional infrastructure projects from the CIP list."

Why it works: Reframes the decision. The risk isn't "what if AI doesn't work?" It's "what are we losing by not acting?"

Approach 3: Make It Safe to Say Yes

Elected officials avoid risky decisions—especially technology decisions they don't fully understand.

Your job: Make it feel safe.

Tactic 1: Phase It

Instead of: "We need $150K to implement AI across the organization."

Say: "We propose a three-phase approach:

Phase 1 (60 days, $15K): Pilot in Planning Department, measure results
Phase 2 (90 days, $45K): If Phase 1 hits targets, expand to Building & Safety
Phase 3 (conditional): Only proceed if Phase 2 shows continued ROI"

Why it works:

Small initial commitment ($15K vs $150K)
Built-in checkpoints
They can stop if it's not working
Demonstrates your confidence (you're willing to be judged on results)

Tactic 2: Offer a Guarantee

"If we don't save at least 10 hours per week within 90 days, we'll cancel the contract and return to the previous process. No questions asked."

Why it works: You're taking on the risk, not them.

How to do this: Negotiate trial periods and off-ramps with vendors. Many SaaS tools allow quarterly cancellations.

Tactic 3: Third-Party Validation

Options:

Bring in a peer CIO who implemented successfully
Get a letter of support from your county or state CIO organization
Hire a consultant for an independent assessment (if budget allows)
Reference analyst reports (Gartner, Forrester) on the specific tool category

Why it works: Distributes decision-making risk. They're not just trusting you—there's external validation.

The Three-Minute Pitch Template

When you have limited time (typical council presentation), use this structure:

Slide 1: The Problem (30 seconds)

"Citizens wait 4 weeks for permits because staff manually processes 300+ documents per week. This delays construction projects and frustrates residents."

Visual: Show citizen complaint data or processing backlog chart.

Slide 2: The Solution (30 seconds)

"One AI tool can automatically sort and route these documents, cutting processing time from 15 hours to under 1 hour per week."

Visual: Simple before/after comparison.

Slide 3: The Proof (45 seconds)

*"Three peer cities our size implemented this:

Boulder: 80% time savings, $67K first-year savings
Fort Collins: Permit times dropped from 28 days to 12 days
Eugene: 94% accuracy, enthusiastic staff adoption

We ran a 30-day test—here are our results."*

Visual: Peer city logos + your pilot metrics.

Slide 4: The Ask (30 seconds)

"We request $15K for a 90-day pilot. If we don't cut processing time by at least 50%, we'll cancel. If successful, we'll expand with a separate request."

Visual: Timeline showing 90-day decision point.

Slide 5: The Impact (45 seconds)

*"Success means:

Permits processed in 2 weeks instead of 4
Staff freed up to handle complex cases
$96K annual savings we can redirect
Happier citizens and contractors"*

Visual: Benefit summary with photos of happy citizens/staff.

Common Objections (And How to Handle Them)

"This sounds expensive"

Response: "The pilot is $15K. We currently spend $96K per year in staff time on manual processing. If we save even 50%, we recoup the investment in 2 months."

Key: Always compare to current costs, not zero.

"What if it doesn't work?"

Response: "That's exactly why we're proposing a 90-day pilot with clear metrics. We've set a minimum bar: must save at least 10 hours per week. If we don't hit that, we cancel. No long-term commitment until we prove it works."

Key: Show you're just as skeptical as they are—but willing to test with clear exit criteria.

"Can't we just hire another person?"

Response: "We could—but that's $75K per year ongoing, plus benefits. This solution is $24K per year after the pilot, with no turnover risk. Plus, hiring takes 3-6 months; this can be running in 30 days."

Key: Make the comparison apples-to-apples, including hiring timeline and turnover risk.

"I read AI makes mistakes"

Response: "You're right to be concerned—that's why we're not using this for high-stakes decisions. This automates document sorting and routing, which staff will still review. Think of it like spell-check: it flags issues, humans make final calls. Our 30-day test showed 99% accuracy."

Key: Acknowledge the concern, explain the safeguards, show proof.

"What about our staff? Will this eliminate jobs?"

Response: "No positions eliminated. Right now, Sarah and her team spend 60% of their time on routine document sorting and only 40% on complex permit review—the work they were hired to do. This frees them up to focus on their actual expertise, reduces overtime, and improves job satisfaction."

Key: Position as augmentation, not replacement. Use specific staff examples.

Your Action Plan

Before your next council presentation:

1. Reframe Your Pitch

[ ] Lead with citizen/community impact
[ ] Quantify current pain (hours wasted, costs, delays)
[ ] Remove technical jargon entirely
[ ] Show outcome, not process

2. Build Your Proof

[ ] Find 3 peer city examples (similar size, region, or demographics)
[ ] Run a 30-60 day micro-pilot if possible
[ ] Gather testimonials from pilot users
[ ] Calculate ROI with conservative estimates

3. De-Risk the Decision

[ ] Propose phased approach with checkpoints
[ ] Offer clear exit criteria and guarantees
[ ] Get third-party validation if available
[ ] Show what happens if we do nothing

4. Prepare for Objections

[ ] Write out 5 likely objections
[ ] Draft specific, evidence-based responses
[ ] Practice with a colleague who'll play skeptic
[ ] Bring backup slides for deep-dive questions

5. Keep It Simple

[ ] Can you explain it in 3 minutes? If not, simplify.
[ ] Would your non-technical friend understand? If not, remove jargon.
[ ] Is the ask crystal clear? If not, rewrite.

The Bottom Line

Elected officials don't fund AI because it's innovative or cutting-edge. They fund it because:

It solves a real problem citizens or staff are experiencing
It's proven to work in similar contexts
It's safe to try with limited risk and clear metrics

Master those three elements, and you'll win funding for the right projects—and avoid wasting political capital on the wrong ones.

Need help crafting your pitch? I offer presentation coaching for local government CIOs preparing budget requests or council presentations. Let's talk →

Want more leadership strategies? Subscribe to the newsletter for weekly insights on navigating organizational change in local government.