Services/industries/Government

States & MunicipalitiesActive conversations

Government

State, county, and municipal websites — built carefully, accessibility-first, with the FOIA-aware content workflows most agencies refuse to take on. Plain-language transformation, Section 508 conformance, AI-augmented content with human review.

04industries/government.ts

our_take_on_government

Government digital work scares most agencies off. It’s heavily regulated, accessibility-mandated, FOIA-aware, and reviewed by committees rather than founders. We do it carefully — because the services on the other side of these sites matter. Section 508 and WCAG AA aren’t add-ons; they’re the design constraint. AI-augmented content generation with mandatory human review for tone, accuracy, and compliance. Plain-language transformation so a resident actually understands the form they need to fill out. The boring, careful work that constituents feel even when they can’t name what changed.

whats_broken_here

Common challenges.

01
Accessibility debt at scale — legacy sites with thousands of PDFs, broken form patterns, and contrast failures that fail the residents most reliant on the service.
02
Plain-language gap — eligibility rules, permit instructions, tax notices written in legalese. The resident can’t complete the task; staff absorbs the support burden.
03
FOIA-aware content production — anything published becomes a public record. Drafting workflows that ignore this create exposure; workflows that overcompensate stop publishing entirely.
04
Procurement-shaped engagements — RFPs that specify the wrong thing because the previous vendor wrote the requirements. We help shape scope inside the procurement constraints, not against them.
05
Multi-stakeholder review — comms, legal, the department subject-matter expert, the elected official’s office. Most workflows die in the review loop; we redesign it to actually function.

how_we_work_in_government

Our channels applied here.

Agentic Development

Accessible, performant municipal sites — built to Section 508 / WCAG AA from the first wireframe, deployed in modern frameworks staff can actually maintain.

Content Engineering

Plain-language transformation of policy and procedural content, FOIA-aware editorial workflows, agent-drafted first versions reviewed by departmental SMEs.

SEO / AEO

Resident-intent SEO — so when someone searches “how do I renew my [permit] in [city]” the official answer wins, not a third-party scraper site monetizing the gap.

Paid Performance

Public-information campaigns, civic-engagement drives, program-awareness funnels. Procurement-compliant, measured against actual program enrollment.

how_an_engagement_runs

A typical engagement.

PHASE 01

Accessibility + content audit

Automated + manual conformance audit, plain-language scoring on key resident-facing content, FOIA-implication review on existing publishing patterns.

weeks 1–3

PHASE 02

Foundation rebuild

Accessible component library, Section 508 / WCAG AA pass on existing site, schema for services and locations. Boring foundational work residents feel immediately.

weeks 4–10

PHASE 03

Content + workflow

Plain-language rewrite on priority services, AI-augmented drafting workflow with structured SME review, FOIA-aware publishing patterns built into the CMS.

weeks 11–20

PHASE 04

Ongoing care

Accessibility doesn’t stay fixed; content drifts; review workflows need tending. We stay accountable through the entire term of engagement.

ongoing

what_success_looks_like

WCAG AA

non_negotiable

The floor on every government build — accessibility as design constraint, not remediation pass.

Plain

language_pass

Resident-facing content rewritten so the task can actually be completed without phoning the office.

Review

redesigned

Multi-stakeholder approval workflows redesigned so SMEs review complete drafts, not in-progress work.

questions_we_get

Honest answers.

Can you work inside a procurement / RFP framework?

Yes — and we’ll help shape scope where the constraints allow. Sole-source isn’t our expectation; we work inside standard procurement timelines, deliverable structures, and the required compliance attestations. Section 508 and WCAG AA are baseline; specific state and municipal requirements layer on top.

How do you handle FOIA exposure?

Drafting workflows assume anything published is a public record. We don’t use systems that retain drafts where retention would create disclosure exposure beyond what your records office expects. Practitioners trained on the implications. Workflow designed by people who’ve done this in regulated environments.

Will AI content pass legal and comms review?

First draft, yes — with citations, in plain language, against a tone guide approved by your comms office. A practitioner edits; departmental SMEs verify; legal/comms approves. Throughput rises; the review bar holds.

What CMS / platform do you build on?

Depends on your environment. We’ve worked across institutional WordPress, Drupal, and headless stacks deployed to government-approved cloud infra. The constraint shapes the build; we don’t fight the constraint for sport.

Ready to put The Nine to work in Government?

next_step

~$nine init --audit

Start with an Insight Genesis audit. Six weeks. Fixed scope. A written diagnosis of where your marketing actually stands — plus a working agent prototype tailored to your business.

Start an audit→↵Book a discovery call⌘ B