
Building an AI Copilot for Internal Government Finance Workflows
How the City of North Miami automated policy drafting, audit prep, and budget analysis without sacrificing human judgment. A case study in practical municipal AI implementation.
The Problem: Finance Staff Drowning in Process
The City of North Miami Finance Department faced a common challenge in municipal government: smart, capable staff buried under institutional knowledge and repetitive workflows. Every policy needed to be researched, assessed, approved, and implemented. Every audit required evidence gathering and documentation. Every budget scenario required manual modeling. The work was sound, but the process was slow.
The Finance Director estimated that 40% of the department’s time was spent on tasks that followed predictable, templated patterns:
- Policy development: Benchmarking peers, legal review, stakeholder feedback gathering
- Audit preparation: Organizing evidence, creating checklists, cross-referencing requirements
- Budget analysis: Scenario modeling, variance calculation, forecasting
- Compliance checking: Verifying policies against Florida statutes and GFOA standards
- Staff onboarding: Training on procedures, policies, and compliance requirements
The question wasn’t whether these tasks needed doing. It was whether they needed to consume this much human time.
“We spend weeks on policy development that follows the same structure every time. Then we spend more weeks on implementation that fails because there’s no bandwidth left for rollout. An AI assistant that could handle the repetitive research and drafting phases would be a game changer.”Finance Director, City of North Miami
The Approach: Build Before Advising
Rather than propose a solution, we applied AI Made This methodology: build a working proof of concept first. This meant designing an AI assistant that would live inside the Finance Department’s secure network, with access to North Miami’s specific policies, procedures, and regulatory requirements.
The assistant was built around seven core workflows:
Policy copilot
Draft, review & refine finance policies in real-time
Interactive mockup. Try clicking different workflows or typing a question.
Key Capabilities in Action
1. Policy Copilot
The assistant drafts policies from templates, automatically referencing GFOA standards and Florida statute requirements. Instead of starting from a blank page, finance staff get a structured draft in minutes, with built-in compliance checkpoints.
Time saved per policy: 8 hours (benchmarking, legal review, stakeholder synthesis)
2. Audit Preparation
Automatically organizes evidence by audit requirement, generates checklists, cross-references findings against policies, and drafts compliance responses. Staff no longer dig through email chains and spreadsheets to find proof.
Time saved per audit cycle: 12 hours (evidence gathering, organization, response drafting)
3. Budget Analysis
Runs scenario forecasting, variance analysis, and risk modeling. The assistant can model recession impacts, revenue growth scenarios, and service cut options in minutes. Staff can focus on strategy, not calculation.
Time saved per analysis: 5 hours (data aggregation, scenario modeling, documentation)
4. Compliance Checking
Verifies proposed policies against Florida Statutes, federal requirements, and GFOA best practices. Flags gaps and recommends remediation before policies go to council.
Audit findings prevented: Estimated 2-3 per year (compliance gaps caught upstream)
5. Document Templates & FAQ
Pre-built policy structures, council presentation templates, and searchable knowledge base reduce the need to reinvent the wheel. New staff can onboard faster. Repetitive questions get self-service answers.
Support tickets reduced: ~60% (self-service answers eliminate “how do I…” questions)
Why This Works: The Data
A 2-week pilot with the North Miami Finance Department produced concrete evidence:
But the real win was psychological: staff said they felt more confident drafting policies and preparing compliance documentation. The assistant didn’t replace judgment, but it removed drudgework, leaving room for strategy.
The Implementation Path
The assistant runs on a secure, city-owned infrastructure (not public Claude.ai). This matters in government because data privacy is non-negotiable. The deployment includes:
Architecture
- Secure backend: Claude API (enterprise tier) or on-premise LLM, deployed inside city network
- Authentication: City SSO (Active Directory) so staff log in as they normally would
- Data: Policies, procedures, and documents stored in encrypted, city-owned storage (SharePoint or equivalent)
- Access logs: All interactions logged for compliance and audit purposes
Governance
- All outputs flagged: “Draft only, requires legal review and human approval before implementation”
- Human-in-the-loop: Finance Director or CFO retains final decision authority on all policies and compliance determinations
- Monthly audits: Sample 10% of interactions to verify quality and catch drift
- Escalation protocol: Unclear or risky outputs escalated to human reviewer immediately
Rollout Timeline
- Week 1-2: Infrastructure setup, staff training, quick-start guide
- Week 3-4: Pilot with 2-3 staff members (policy copilot only)
- Week 5-6: Expand to audit prep and compliance checking
- Week 7-8: Add budget analysis and FAQ modules
- Week 9+: Ongoing refinement, quarterly training, monthly compliance review
What This Isn’t (Misconceptions to Clear Up)
This is not a replacement for human judgment. The assistant can’t vote on policy, sign off on compliance, or make strategic decisions. It drafts, summarizes, and organizes. Humans decide.
This is not a cost-cutting move. The goal isn’t to lay off staff; it’s to free them from drudgework so they can focus on analysis, strategy, and stakeholder engagement. Same payroll, higher-value work.
This is not a chatbot. It’s not cute or conversational. It’s purpose-built for seven specific workflows, with strict templates and compliance guardrails. It’s boring by design.
This is not a security risk. It runs entirely inside the city’s network, with the same authentication and audit trails as any other city system. In many ways, it’s more secure than email-based policy drafting and scattered spreadsheet analysis.
The Bigger Picture
North Miami’s Finance AI Assistant is a proof of concept for a larger shift in municipal government. Across cities, finance departments are struggling with the same problem: too much compliance work, too little time for strategy.
AI doesn’t solve politics or budgeting philosophy. But it can solve the process tax: the 40-60 hours per month spent on templated research, documentation, and synthesis work that follows predictable patterns.
For North Miami, that translates to:
- Policy rollout compressed from 20 weeks to 8 weeks
- Audit prep streamlined from 40 hours to 20 hours per cycle
- New staff onboarded in days instead of weeks
- Compliance gaps caught upstream instead of in audit findings
That’s not AI magic. That’s process efficiency. And it opens up time for the work that actually requires human expertise: deciding what policies North Miami needs, and building the political and operational will to implement them.
Ready to Build Your Finance AI Assistant?
We don’t just advise on municipal AI. We build working proofs of concept first, so you can see exactly what your team will use before making any commitment. Whether you’re in finance, HR, 311, or permits, the same principle applies: build before you buy.
If you’d like to explore an AI assistant for your department’s workflows, let’s talk about what a proof of concept looks like for your team.
Schedule a Discovery Call