Public-sector infrastructure that holds up under FOIA.
Municipal departments, public authorities, civic nonprofits, and the agencies that serve them. We build the boring, durable plumbing — records-compliant, audit-traceable, vendor-neutral — that makes the rest of the work possible.
Service requests, applications, complaints, and FOIA requests come in by web form, email, phone, and walk-in. They get logged in a system, sometimes. They get routed to a department, eventually. The person on the front desk is the integration. When that person is out, the queue stops.
A division director writes the council memo because the template is old. A deputy summarizes the public-comment file because nobody else has time. The grant writer reformats line items at 9pm because the procurement system rejects three-decimal numbers.
Permits processed, response times, case backlogs, cost per service — the numbers exist somewhere, in two systems that disagree, and the reports get assembled by hand the week before the council meeting. Annual reporting is a project, not a query.
The PMS the department runs on hasn’t had a real product update since 2014. The vendor wants to sell a "modernization" the budget cycle won’t support. Meanwhile the work goes on. The civic infrastructure is the staff working around the software, not the software itself.
You probably need two or three of these on day one. We tell you which on the audit call.
Claude and Gemini wired into your records: drafting council memos against the policy archive, summarizing public-comment files and meeting transcripts, classifying constituent intake, drafting FOIA-responsive packets with redaction logs. Private inference when the data demands it. Drafts go to the human — sends do not.
One database where constituents, cases, permits, properties, and grants live once. Supabase by default; NocoDB self-hosted when residency rules require it. The legacy PMS keeps running. The new database becomes the system of record the rest of the agency reads from.
Make.com or n8n routing the work between the legacy PMS, the constituent CRM, the GIS layer, and the email platform. Inbound forms classified, routed, and logged. SLA timers running on every case. The audit trail is a query, not a binder.
Grant disbursement runners that reconcile expenditures to line items. Vendor bill capture coded to fund and account. Period reporting drafted automatically against the live data. Procurement-compliant approval flows with named approvers and timestamps.
We’ve shipped against all of these in production. If yours isn’t listed, we’ll be honest about ramp time on the audit call.
Accela, Tyler, OpenGov, GovQA, NextRequest
Esri ArcGIS, Cityworks, Cartegraph
Outlook, Gmail, Granicus, GovDelivery
Tyler Munis, Workday, QuickBooks Online, Plaid
Anthropic Claude, OpenAI, Google Gemini, self-hosted Llama
Make.com, n8n, Supabase, NocoDB
The compliance binder, the hand-typed quarterly report, the grant reconciliation spreadsheet that takes a person two days a month. We’ll tell you what we’d automate first and what it would cost.