Module 1
The Budget Calendar
CA cities operate on a July 1 – June 30 fiscal year. Everything revolves around this cycle. Know where you are in it and you know what questions to ask.
Jul–Aug
New fiscal year begins. Prior-year books still open for final adjustments. Ask: "How did you close out last year? Any carryovers?"
Sep–Oct
ACFR preparation begins. Auditors arrive. Q1 actuals available. Ask: "Are you tracking to budget through Q1? Any surprises?"
Nov–Dec
Mid-year budget review. Revenue projections updated. CIP status reviewed. Ask: "What does your mid-year look like? Revenue above or below forecast?"
Jan–Feb
Budget kickoff. City Manager issues instructions. Departments submit requests. Ask: "What are your departments asking for this cycle? Any big new asks?"
Mar–Apr
Budget compilation. Analyst reconciles requests vs. revenue. Cuts and priorities. Ask: "Where are you cutting? What didn't make the cut?"
May–Jun
Council hearings. Public comment. Budget adoption (must adopt by June 30). Ask: "When's your budget hearing? Any controversial items?"
Timing your outreach: January is ideal. Budget season is starting, the analyst is overwhelmed, and they're looking at last year's spending data to make this year's projections. That's exactly what our system provides — pre-analyzed.
Module 2
Vocabulary You Need Cold
Say these correctly and you're an insider. Fumble them and you're a vendor. Master the first 12 and you can hold a conversation with any finance director.
General Fund
The city's main operating account. Police, fire, parks, admin. Where most discretionary money lives. "How's your General Fund looking?" = "How healthy is the city?"
ACFR
Annual Comprehensive Financial Report (formerly CAFR). The audited financial statement every city must produce. GFOA gives awards for excellence. Ask if they've won one.
Warrant Register
The list of payments approved by the city council. This is our primary data source. "I pulled your warrant register" = you did your homework.
CIP
Capital Improvement Program. Roads, buildings, infrastructure. Separate budget from operating. Usually multi-year. Big dollar amounts.
Fund Accounting
Government accounting uses separate "funds" — General, Enterprise (water/sewer), Special Revenue, etc. Money can't move between them freely. Ask: "Which fund is that in?"
Encumbrance
Money that's committed (purchase order issued) but not yet spent. Key for budget tracking — an encumbered dollar isn't available even though it hasn't left the account.
Appropriation
The legal authority to spend. Council votes to appropriate funds. Spending beyond appropriation = illegal. "Over-appropriation" is the worst word a finance director can hear.
Variance
Difference between budgeted and actual. Positive variance = underspent. Negative = overspent. "Your Public Works dept has a 15% negative variance" = they're over budget.
GASB
Governmental Accounting Standards Board. Sets the rules. GASB 68 (pensions) and GASB 75 (OPEB) are the ones that keep finance directors up at night.
OPEB
Other Post-Employment Benefits. Retiree health care obligations. A massive unfunded liability for many CA cities. "What's your OPEB liability?" = sophisticated question.
Prop 218
CA constitutional amendment. Cities must get voter approval for most new taxes and assessments. Limits revenue options. "How's Prop 218 affecting your rate structure?"
CalPERS
CA Public Employees' Retirement System. The pension fund. Rates keep going up. "What's your CalPERS contribution rate?" = you understand their biggest cost pressure.
Fiscal Impact Statement
Required for council agenda items. Shows the cost/revenue impact of a proposed action. Analysts write these constantly.
SB 1
Gas tax revenue for roads. Cities must report spending annually. "Are you getting your SB 1 allocation?" = another hook into their data.
Enterprise Fund
Self-sustaining operations like water, sewer, garbage. Must break even through user fees. Separate from General Fund. Often the biggest budgets.
Reserve Policy
How much cash the city keeps in savings. GFOA recommends 2 months (16.7%). "What's your reserve level?" = "Are you financially healthy?"
Module 3
Budget Questions That Show You Know
Each of these is a question a real analyst asks regularly. For each one, we show what it reveals, why it matters, and what our system can answer automatically.
"What's your biggest year-over-year spending change by department?"
This is the single most useful question you can ask. It surfaces hidden problems — a department that's quietly growing 20% while revenue is flat. It also shows you did the work before walking in.
Our system answers this: Signal Stack tracks SPENDING_SPIKE across all ingested cities. Pull up the city, filter by department, compare YoY. You can walk in with the answer already printed.
Follow-up: "Is that increase structural or one-time?" One-time = a capital project or grant drawdown. Structural = permanent staffing or contract increase. Structural is the one that worries finance directors.
"How do your per-capita costs compare to similar cities?"
This is the question that opens doors. No city has an easy way to answer it. They know their own numbers but not their neighbors'. This is our entire competitive advantage.
Our system answers this: Multi-city data across 4 counties. We can show: "Hanford spends $X per capita on public safety vs. Selma's $Y." Nobody else does this for small cities.
They'll push back: "We're different because..." Let them explain. The comparison isn't the point — the conversation is. You're now talking about their budget with data they've never seen.
"What percentage of your General Fund goes to personnel costs?"
CA cities typically spend 70-85% of General Fund on salary + benefits. If it's over 80%, they're stressed. If it's climbing, they're heading for a structural deficit. CalPERS rate increases are the usual driver.
Our system answers this: Partial. We see vendor payments but don't separately categorize payroll. This is a build-next item — payroll vs. services vs. supplies categorization.
Follow-up: "What's your CalPERS rate, and what are you projecting for next year?" CalPERS publishes rate schedules. You can look this up before the meeting.
"Do you have any single vendors over 10% of a department budget?"
Concentration risk. If one vendor handles 30% of your Public Works spend and they walk away, you have an emergency. Cities rarely track this proactively.
Our system answers this: Yes — CONCENTRATION_RISK signal fires at >30% of dept spend. We can run this for any city in our pipeline and show them vendor concentration they didn't know they had.
This one gets attention. Finance directors know it's a risk but don't have time to monitor it. You just did their job for them — for free.
"When was the last time you benchmarked your contract rates?"
Cities renew contracts out of habit. A landscaping contract from 2018 might be 40% above market because nobody checked. Cross-city comparison reveals this instantly.
Our system answers this: MULTI_CITY_PATTERN signal + vendor search. "You pay Vendor X $200K/yr for service Y. Two other cities pay them $140K for the same thing."
This is the money pitch. If you can find one contract that's overpriced, you've paid for your service ten times over.
"How are you tracking your unfunded liabilities?"
OPEB + CalPERS unfunded liability = the existential threat for CA cities. Some have hundreds of millions in unfunded pension obligations. This question shows you understand the real pressure.
Our system doesn't cover this yet. But: CalPERS publishes actuarial reports by employer. You can look up any city's unfunded liability before the meeting. It's free public data.
Don't lead with this — it's a downer. Use it as a "I understand your constraints" signal after you've established rapport.
Module 4
Vendor Intelligence — Your Strongest Card
Nobody else does cross-city vendor analysis for small municipalities. This is the demo that sells.
"Do you know which of your vendors also work for neighboring cities?"
The answer is always no. They don't have time, they don't have the data, and it's never occurred to them to check. When you show them, it changes the conversation.
Demo script: "I ran your warrant register against three neighboring cities. Here are 14 vendors you share with Selma, 8 with Lemoore. Would it be useful to know what those cities are paying them?"
The implication is clear: you might be overpaying. Or they might be. Either way, you have information they don't.
"Have any new vendors appeared in the last 6 months that weren't in prior years?"
New vendors can signal new contracts (planned) or new problems (emergency repairs, consultant creep). Either way, finance directors want to know.
Our system answers this: VENDOR_APPEARED signal. Automatic detection for every city in our pipeline. "Three new vendors appeared in your Public Works spend this quarter — here they are."
"Which vendors disappeared from your payment rolls this year?"
A disappeared vendor means a contract ended, a service was cut, or someone went out of business. Sometimes it reveals a lapsed renewal nobody noticed.
Our system answers this: VENDOR_DISAPPEARED signal. "You were paying Vendor X $50K/yr through last March. No payments since. Was that intentional?"
"What's your largest vendor by total annual spend?"
They'll know #1 (usually CalPERS or a construction firm). They probably don't know #4 through #10. That's where the surprises are.
Our system answers this: Vendor ranking by total payments, per-city. Show them their top-20 vendor list sorted by spend. Half the time they're surprised by something in positions 5-15.
Module 5
The Federal Funding Angle
Most small cities don't know what federal money is flowing into their county. You do — $15 billion across 4 counties. This is the "how did you know that?" moment.
"Are you aware of the federal grants your county received last year?"
Small cities often miss federal funding opportunities because they don't know to look. Counties receive pass-through grants from HUD, HHS, USDA, and DOT — and cities can apply for sub-awards.
Demo: "Fresno County received $3.6 billion in federal awards last year. $931 million of that went to vendors who also appear in local city payments. Here's the flow."
Show the pipeline view: Federal agency → County → local vendors → your city's payments. The visual is powerful.
"Did you know [similar city] received a USDA grant for [project type]?"
This is the grant opportunity matcher play. Small cities don't have grant writers. Showing them what peers received is the closest thing to writing the application for them.
Our system answers this: USASpending data by county + award type. Filter by USDA/HUD/etc., show grants to cities of similar size. "Lemoore got $2M from USDA Rural Development for infrastructure. You could apply for the same program."
"How are you tracking your ARPA spending deadlines?"
American Rescue Plan Act funds had strict spending deadlines. Cities that haven't spent them risk losing them. This question shows awareness of federal compliance pressure.
Even if ARPA is done, the pattern repeats — there's always a federal program with a deadline. The question demonstrates that you track these things.
Module 6
Stakeholder Translation
The same data means different things to different people. Analysts spend most of their time translating. Here's the cheat sheet.
City Council Members
They want: Simple summaries. "Is it going up or down?" Bottom line first, details only if asked. Political implications matter — what will constituents think?
Say: "Public safety spending increased 12% while revenue grew 3%. Here are three options." Never say: "The regression model shows a coefficient of..."
City Manager / CAO
They want: Decision-quality analysis. Options with tradeoffs. Risk assessment. They're the ones who have to defend the budget.
Say: "Your vendor concentration in Public Works is high — one vendor handles 35%. Here's a comparison to peer cities and a risk mitigation option."
Finance Director
They want: Accuracy. Detail. Compliance assurance. They're personally liable for financial statements. They'll test you on specifics.
Say: "I pulled your warrant register and cross-referenced it with USASpending data. Here's the methodology." They want to know HOW, not just WHAT.
Department Heads
They want: Their budget isn't cut. Data that supports their requests. Proof they're efficient.
Say: "Your per-unit cost for [service] is 15% below the regional average. That's a strong argument for your budget request."
The Public / Media
They want: Transparency. Where does the money go? Is anyone wasting it? Simple visuals.
Say: "Here's where every dollar of your tax money goes." The Spend Dashboard is built for this audience.
Module 7
Red Flags to Spot in the Data
When you're looking at a city's spending data, these are the patterns that a seasoned analyst would flag. Find one and you've earned credibility.
Payments just below approval thresholds ($24,999 when the limit is $25,000)Suggests someone is splitting purchases to avoid council approval. Fraud red flag.
Same vendor, multiple department codes, large totalVendor is spread across departments to stay under each department's radar. Concentration risk hiding in plain sight.
Year-end spending spike (May-June)"Use it or lose it" budget burning. Departments spending down remaining budget before fiscal year close. Common but worth flagging.
Vendor payment amounts that are always round numbers ($5,000, $10,000)Real invoices have cents. Round numbers suggest retainer arrangements or, worse, payments not tied to actual services delivered.
Consultant spend growing while headcount stays flat or growsStaff augmentation creep. The city is outsourcing work it should be doing internally (or vice versa). Either way, it's expensive.
Revenue from one source exceeding 40% of totalRevenue concentration. If that source declines (sales tax, property tax, a single business), the city is in trouble. Similar to vendor concentration but on the income side.
Reserve fund declining for 3+ consecutive yearsA slow bleed. Each year the city takes a little from savings to cover operations. Within 5 years, reserves hit zero and the credit rating drops.
Pension costs growing faster than revenueThe structural deficit time bomb. CalPERS rates are scheduled to increase through 2030. If revenue can't keep up, services get cut.
How to bring these up: Never accuse. Frame it as "I noticed a pattern that might be worth looking into." The finance director may already know and have a good explanation. Your job is to surface it, not to judge it.
Module 8
The Pitch Script
Three proven openers depending on who you're talking to and how you got the meeting. Each one leads with value, not with the product.
Cold outreach — email to Finance Director
You
"I've been analyzing public spending data across Central Valley cities and noticed something interesting about [City Name]. Your top vendor in Public Works — [Vendor Name] — also serves three neighboring cities, but at different price points. Would a 15-minute comparison be useful?"
Lead with a specific finding from their data. Attach nothing — make them ask for it.
Warm intro — city clerk or council member connection
You
"I built a system that cross-references your warrant register data with federal spending in the county. I found that [specific dollar amount] in federal grants went to vendors you already work with. I'd love to show your finance team — it might surface grant opportunities you're missing."
The federal angle is novel. Nobody else does this for small cities. It positions you as a resource, not a vendor.
In the room — the demo script
You
"Let me show you three things from your own data that I think you haven't seen before."
1. Show their vendor concentration — the CONCENTRATION_RISK finding.
2. Show the cross-city vendor comparison — what neighboring cities pay the same vendors.
3. Show the federal funding pipeline — money flowing through their county they didn't know about.
You
"This is what I can produce for you automatically, every month, from public data. Your analyst doesn't have time to do this manually. I'm not replacing them — I'm giving them 4 hours back every week."
Them
"What does this cost?"
You
"Let's start with a free report for this quarter. If it saves you time, we talk about a monthly service. Less than what you'd pay an intern."
Free first. Always. The data sells itself — your job is to get it in front of them.
The close: Don't sell the system. Sell the insight. "Would it be useful to know X?" is always stronger than "Our platform does X." You're not a software vendor — you're a data analyst who happens to have better tools than they do.
Your progress meter — the things above this line are what you need to walk into a meeting. Everything below is depth.
8/12 modules complete. Remaining: GASB deep dive, CalPERS analysis, grant writing basics, ACFR reading guide. These are depth modules — build them when you need them.