I Studied Every SaaS That Secretly Owns a Government Workflow. The Margins Are Obscene.

There's a SaaS company in Idaho that charges $4.95 every time someone files a business entity document with the state. The state processes roughly 120,000 of these filings per year. That's $594,000 in annual revenue from a single state contract, running on software that hasn't been meaningfully updated since 2019. The gross margin is estimated at over 93%.

Nobody on Twitter is talking about this company. Nobody on r/SaaS is trying to compete with it. And that's exactly the point.

While the entire SaaS world is fighting over the same AI wrapper ideas and the same saturated B2B verticals, a quiet class of software companies has figured out something powerful: if you become the default tool inside a government workflow, you essentially print money with almost no churn, no competition, and no marketing spend.

I went deep on this. What I found changes how I think about where the real SaaS opportunities are hiding.

The Government Software Gap Is Staggering

Let me frame this with a number that should stop you in your tracks.

U.S. state and local governments spend over $110 billion annually on IT. Federal spending adds another $100 billion-plus. And yet, the technology powering most government workflows is laughably outdated. We're talking about systems built on COBOL, manual PDF processes, fax-based approvals, and spreadsheets emailed between departments.

The reason is structural. Government procurement is slow, bureaucratic, and confusing. Most SaaS founders look at it and immediately move on. The sales cycles are long. The RFP process is painful. The compliance requirements are dense.

But the founders who push through that friction discover something remarkable on the other side: once you're in, you're in for years. Often decades. Government contracts renew almost automatically. Switching costs are enormous — not because the software is sticky in a product sense, but because the procurement process to replace you is so painful that nobody wants to go through it again.

This creates a dynamic that's almost unheard of in SaaS: near-zero churn combined with high margins and growing usage.

The Pattern I Keep Seeing

The SaaS companies that quietly dominate government workflows share a specific set of characteristics. And they look nothing like the typical YC-style startup.

They solve one narrow workflow, not a platform. The successful govtech SaaS tools don't try to be Salesforce for government. They pick one specific process — permit applications, public records requests, court filing management, business license renewals, inspection scheduling — and they own it completely. The narrower the workflow, the easier it is to become the default.

They charge per transaction, not per seat. This is where the margins get obscene. Instead of charging a flat monthly fee, many of these tools charge a small fee per filing, per request, or per transaction. The government agency itself often pays nothing — the fee gets passed to the citizen or business using the service. This is a brilliant pricing model because it eliminates the budget approval bottleneck entirely. The agency doesn't need to find money in their budget. The software effectively pays for itself through convenience fees.

I wrote about how SaaS tools that charge over $500/month exploit specific blind spots — government SaaS takes this to another level. The "blind spot" is that citizens will happily pay $5-15 in convenience fees to avoid driving to a government office and waiting in line for two hours.

They grow through word-of-mouth between agencies. Government employees talk to each other. County clerks attend the same conferences. City managers share vendor recommendations. Once you're in three or four counties in a state, the rest start calling you. This is organic distribution that costs almost nothing.

They have almost no direct competition. Because the market looks unattractive from the outside, most SaaS founders never enter it. The companies that are already there face so little competitive pressure that they can maintain pricing power indefinitely.

Five Government Workflows Where the Opportunity Is Wide Open

Let me get specific. These are areas where I see massive gaps between what exists and what's possible — especially now that AI tools make it feasible for small teams to build sophisticated software quickly.

1. Public Records Request Management (FOIA/FOIL Processing)

Every government agency in the United States is legally required to respond to public records requests. At the federal level, it's FOIA (Freedom of Information Act). States have their own versions — FOIL in New York, CPRA in California, and so on.

The volume is enormous. The federal government alone receives over 800,000 FOIA requests per year. State and local agencies collectively handle millions more.

And the process at most agencies is shockingly manual. A request comes in via email or a web form. Someone logs it in a spreadsheet. They email various departments asking for responsive documents. They manually review each document for redaction needs. They track deadlines on a calendar. They respond via email with attached PDFs.

There are a few existing tools in this space — NextRequest (acquired by a larger company), JustFOIA, and a handful of others. But coverage is thin. Most small and mid-sized agencies (cities under 100,000 people, county governments, school districts, special districts) have no dedicated software for this at all.

The AI angle is what makes this exciting right now. The most time-consuming part of FOIA processing is document review and redaction — identifying Social Security numbers, personal addresses, privileged communications, and other exempt information across thousands of pages. This is exactly the kind of task that modern LLMs handle well. A tool that could auto-suggest redactions and auto-classify documents by exemption category would save agencies hundreds of hours per year.

There are roughly 90,000 local government entities in the U.S. If even 10% adopted a tool at $300/month, that's $324 million in ARR. At a transaction-based model ($5-10 per request passed to the requester), the numbers get even bigger.

2. Code Enforcement and Violation Tracking

Every city and county has code enforcement officers — the people who deal with overgrown lawns, unpermitted construction, abandoned vehicles, noise complaints, and zoning violations. It's unglamorous work, and the software supporting it is atrocious.

Most code enforcement departments use a combination of paper forms, Excel spreadsheets, and maybe a legacy system from the 1990s that runs on a local server somewhere. Officers drive around taking photos on their personal phones, then come back to the office and manually enter data.

The workflow is ripe for a modern, mobile-first SaaS tool. Imagine an app where officers can photograph a violation, GPS-tag it, auto-generate a notice letter, track the compliance timeline, and escalate to legal — all from their phone. Add AI-powered image recognition to auto-classify violation types from photos, and you've got something genuinely powerful.

The existing competitors are mostly legacy on-premise solutions like CityView and Accela, which are expensive, complex, and designed for large municipalities. The small and mid-sized market (cities with 10,000-75,000 people) is drastically underserved. There are over 19,000 incorporated cities in the U.S., and the vast majority fall into this size range.

Pricing at $200-500/month per department makes this accessible. That's a potential market well north of $100 million.

3. Government Meeting and Agenda Management

City councils, county boards, school boards, planning commissions, water districts — there are hundreds of thousands of government bodies in the U.S. that hold regular public meetings. Each meeting requires an agenda, supporting documents, public notices, minutes, and often video recording.

The process of assembling a meeting agenda is surprisingly labor-intensive. Staff members from various departments submit agenda items. Someone (usually a city clerk) compiles them, formats them, attaches supporting documents, routes the packet for approval, publishes it to a website, and distributes it to board members.

There are a few tools in this space (BoardDocs, Granicus, Novus Agenda), but they're mostly designed for larger agencies and priced accordingly. The small-government market — the thousands of special districts, small towns, and minor boards — is wide open.

The AI opportunity here is automatic minute-taking. Most agencies are still paying someone to sit in a meeting and manually transcribe what happened. An AI tool that could record the meeting, generate draft minutes with speaker attribution, flag action items, and track follow-up tasks would be transformative for small agencies that don't have dedicated staff for this.

I track opportunities like this at SaasOpportunities, and government meeting management consistently shows up as a gap with minimal competition and strong willingness to pay.

4. Permit and Inspection Workflow Automation

Building permits, business permits, event permits, health permits — the permitting process is one of the most universally hated interactions citizens have with their local government. And the software behind it is a big reason why.

Many small municipalities still process permits on paper. An applicant fills out a physical form, drops it off at city hall, and waits days or weeks for someone to review it. Inspections are scheduled by phone. Results are recorded on clipboards. Approvals require physical signatures.

Larger cities use enterprise platforms like Tyler Technologies or Accela, which can cost hundreds of thousands of dollars per year and require lengthy implementation projects. But for a city of 15,000 people? Those solutions are wildly overbuilt and overpriced.

The gap is a lightweight, modern permitting tool designed specifically for small municipalities. Think of it as what Stripe did for payments — take something that was needlessly complex and make it simple. An applicant submits online, the system routes to the right reviewer, the reviewer approves or requests changes, inspections get scheduled automatically, and the permit gets issued digitally.

The transaction-based pricing model works beautifully here. Charge the applicant a $10-25 "technology fee" on top of the permit fee. The city pays nothing out of pocket. The applicant happily pays to avoid an in-person visit. Everyone wins.

With roughly 35,000 general-purpose local governments in the U.S. and most small ones lacking modern permitting software, even modest penetration represents a massive business. This is the kind of SaaS that can quietly cross $50K MRR without anyone in the tech world noticing.

5. Utility Billing for Small Municipal Utilities

This one is less obvious but potentially the most lucrative.

There are over 2,000 municipal electric utilities, 50,000+ community water systems, and thousands of municipal gas and sewer systems in the United States. The large ones use enterprise billing platforms. The small ones — and there are thousands of them — use a patchwork of ancient software, sometimes literally DOS-based programs, to manage customer billing.

A small town water utility might serve 3,000 customers. Their billing "system" might be a 25-year-old desktop application that only runs on one specific computer in the office. When that computer dies, they have a crisis.

Modern, cloud-based utility billing for small municipal utilities is a massive gap. The tool would handle meter reading imports, rate calculations (which can be surprisingly complex with tiered pricing and seasonal adjustments), bill generation, payment processing, delinquency management, and customer self-service portals.

The willingness to pay is high because utility billing is mission-critical — it's literally how the municipality generates revenue. Pricing in the $500-2,000/month range is easily justifiable, and adding a small per-transaction payment processing fee creates additional recurring revenue.

The competitive landscape is thin. There are some legacy vendors (Harris Computer, Tyler Technologies' Incode), but they're expensive and slow to innovate. A modern, cloud-native solution designed for utilities serving under 10,000 customers would have a clear lane.

Why This Opportunity Is Bigger Now Than Ever Before

Government software has always been a good business for the companies already in it. So why is this moment different? Why should a solo developer or small team consider entering this market now?

Three things have changed simultaneously.

First, AI makes small teams capable of building enterprise-grade software. The reason government software has historically been dominated by large companies is that the requirements are complex. Compliance, accessibility, security, reporting — building all of this used to require large engineering teams. With AI coding tools like Claude and Cursor, a small team can now build and maintain software that would have required 20 engineers five years ago. I've written about how founders are building sophisticated SaaS products in a weekend — government software is the next frontier for this approach.

Second, the American Rescue Plan flooded local governments with technology funding. The $350 billion in state and local fiscal recovery funds allocated in 2021 included explicit provisions for technology modernization. Many agencies are actively looking to spend this money on modern software before the spending deadlines hit. This is a once-in-a-generation procurement window.

Third, citizen expectations have permanently shifted. After COVID forced government services online, citizens now expect digital-first interactions with their local government. Agencies that were previously resistant to change are now under pressure from their own constituents to modernize. The political will for technology adoption in government is higher than it's ever been.

The Playbook for Getting In

The biggest objection I hear about government SaaS is the sales cycle. "I can't wait 18 months for a contract." And for large federal or state contracts, that's a valid concern. But local government is different.

Small municipalities — cities under 50,000 people, counties, special districts — often have much simpler procurement processes. Many can approve purchases under $25,000 or even $50,000 without a formal RFP. A city manager or department head can often sign off on a monthly SaaS subscription with a simple purchase order.

The playbook that works consistently:

Start with one agency and make them wildly successful. Pick a small city or county near you. Offer them a free pilot or a heavily discounted first year. Your goal isn't revenue — it's a case study and a reference. Government buyers are risk-averse. They want to know that someone like them is already using your tool successfully.

Attend one state-level conference. Every state has associations for city managers, county clerks, finance officers, and other municipal roles. These conferences are where purchasing decisions get influenced. A booth at a state municipal clerks conference might cost $500-2,000, and you'll be in front of every potential buyer in that state.

Build for compliance from day one. Government software needs to meet accessibility standards (WCAG 2.1), data residency requirements, and often specific state regulations. If you build these in from the start, they become your moat. Most SaaS founders bolt compliance on as an afterthought, which is exactly why most SaaS businesses that die make predictable mistakes — in government, cutting corners on compliance is fatal.

Use the transaction-based pricing model whenever possible. This is the single most important tactical decision. If you can structure your pricing so the agency pays nothing and the end user pays a small convenience fee, you eliminate the biggest friction point in government sales: budget approval. The agency gets better software for free. You get recurring revenue that scales with usage.

The Margins Nobody Talks About

Let me come back to margins, because this is where government SaaS gets genuinely unusual.

Typical B2B SaaS companies operate at 70-80% gross margins, which is already excellent. Government SaaS companies operating on transaction-based models routinely hit 90-95% gross margins. The reason is that once the software is built and deployed, the incremental cost of processing each transaction is nearly zero. There's no sales team to commission. There's minimal support overhead because the workflows are standardized. And there's no marketing spend because growth happens through inter-agency referrals.

Churn rates in government SaaS are typically under 3% annually. Compare that to the 5-7% monthly churn that many B2C SaaS products experience. A government contract that renews annually with near-certainty is worth dramatically more than a consumer subscription that might cancel next month.

This is why government SaaS companies, despite being relatively unknown, often generate more profit per employee than their flashier B2B counterparts. It's the same dynamic I've seen in SaaS companies doing $1M+ ARR with under 3 employees — small teams, focused products, high margins, low churn.

The Risks Are Real (But Manageable)

I don't want to paint this as a risk-free opportunity. There are genuine challenges.

Payment processing compliance. If you're handling government payments (permit fees, utility bills, etc.), you need PCI compliance and potentially specific state-level payment processing certifications. This is solvable but requires upfront investment.

Accessibility requirements. Government websites and applications must meet ADA and WCAG accessibility standards. This isn't optional — it's legally required. Building accessible software from the start is the right approach; retrofitting it later is expensive and painful.

Slow initial traction. Even with simplified procurement at the local level, your first 5-10 customers will take longer to close than a typical B2B SaaS sale. You need to be capitalized (or have other income) to survive the initial ramp.

Political risk. Occasionally, a new city manager or elected official will want to shake things up and replace existing vendors. This is rare but it happens. The mitigation is to make your software so embedded in daily workflows that replacing it would be genuinely disruptive.

Where I'd Start If I Were Building This Today

If I were a solo developer or small team looking at this space right now, I'd start with public records request management. The reasons:

The pain is universal — every government agency deals with records requests. The existing solutions are either too expensive for small agencies or too basic to be useful. The AI angle (automated document review and redaction) is a genuine differentiator that didn't exist two years ago. The compliance requirements, while real, are manageable for a small team. And the transaction-based pricing model ($5-10 per request, paid by the requester) works perfectly.

Build a clean, modern web application. Integrate an LLM for document classification and redaction suggestions. Make it dead simple for a city clerk with no technical background to set up and use. Price it so the agency pays nothing. Launch in one state, get three to five agencies on board, then expand state by state.

Within 18 months, you'd have a product generating meaningful recurring revenue with margins that would make most SaaS founders jealous. Within three years, you'd have something that could credibly be called a platform — and you'd be operating in a market where the leverage of being inside an ecosystem works overwhelmingly in your favor.

The Bigger Picture

The SaaS world has a visibility bias. We pay attention to the companies that launch on Product Hunt, get covered on TechCrunch, and post their MRR screenshots on Twitter. We assume that's where the money is.

But some of the most profitable software businesses in the world are ones you've never heard of. They sell to government agencies, utilities, courts, and regulatory bodies. They don't need to go viral. They don't need a content marketing strategy. They just need to solve one specific workflow problem for a customer who will never leave.

The founders building these businesses aren't famous. They're not posting growth metrics on social media. They're quietly collecting transaction fees from thousands of government workflows, watching their bank accounts grow month after month, and wondering why more people aren't doing this.

Now you know the playbook. The question is whether you'll actually use it.

The government workflows I've described aren't going to digitize themselves. The agencies are ready. The funding is available. The competition is thin. And for the first time in history, a solo developer with AI tools can build software sophisticated enough to win these contracts.

Pick one workflow. Find one agency. Build something that makes their life easier. The margins will take care of the rest.