Industries
Public sector software, cloud and AI

Who we help
Public bodies of every size, and the companies that serve them, from a small town putting its first services online to a state agency modernizing systems residents depend on.
- Small towns, counties and special districts such as water, fire and transit
- School districts and colleges
- Nonprofits and grant-funded programs that report on outcomes and spending
- City and state agencies modernizing legacy systems and resident services
- Public safety and justice programs that handle criminal justice information
- Govtech startups preparing to sell to state and local government
Outcomes
What changes when the work is done well. We agree the measures with you during discovery and report against them.
- Websites, apps and documents that meet WCAG 2.1 AA for the ADA Title II web accessibility rule
- Residents able to apply, pay and request services online, with staff working from one queue
- Grant and program reporting from governed data instead of year-end spreadsheet work
- Cloud environments that meet GovRAMP, FedRAMP or CJIS requirements where your policy calls for them
- AI use that is inventoried, approved and explainable to your council, board or auditors
What we do
Our five practices applied to the public sector: product, platforms, AI, cloud and data, each built to be accessible, secure and accountable.
What this covers
- Accessibility audits and remediation for websites, portals, apps and PDFs
- Resident services: online forms, permits, licensing, payments, case management and notifications
- Modernization of legacy finance, HR, grants and case systems, one service at a time
- AI agents for resident questions, intake and records requests, with staff approving anything before it is sent or decided
- Document AI for applications, permits and records processing
- Secure cloud foundations and data platforms on AWS, Azure or Google Cloud
Compliance and security
- AI use cases inventoried and risk-assessed under the NIST AI Risk Management Framework before deployment
- People make eligibility, enforcement and benefits decisions, and every AI-assisted action is logged
- Public records retention and disclosure considered in every design
Example use cases
Typical projects, from a small town's first online service to a statewide program.
- Accessibility program: a county website and its PDFs audited against WCAG 2.1 AA, the most-used pages fixed first and ongoing testing set up
- Online permits: a small town's permit and inspection requests moved from paper to an online portal with payments
- Grant reporting: a nonprofit's program, finance and outcome data combined into funder-ready reports
- Records requests: document AI and an AI agent locate, redact and assemble records for staff review before release
- Cloud migration: an agency workload moved to FedRAMP-authorized cloud regions such as AWS GovCloud or Azure Government, where agency policy requires them
- School district identity: single sign-on and phishing-resistant multi-factor authentication across learning and administrative systems
- Govtech readiness: controls, documentation and evidence for a startup pursuing GovRAMP authorization
Integrations
We work with the systems public bodies already run, through their supported APIs and data exports.
- Permitting and land management: Accela, Cityworks, OpenGov and Tyler Technologies
- Finance and ERP: Tyler Technologies, Workday, Oracle, Dynamics 365, NetSuite and Sage Intacct
- CRM and case management: Salesforce, Dynamics 365 and ServiceNow
- Education: PowerSchool, Infinite Campus, Canvas and Google Workspace for Education
- Identity: Microsoft Entra ID, Okta and Login.gov where eligible
- GIS and data: Esri ArcGIS, Snowflake, Databricks, Microsoft Fabric, BigQuery and Power BI
Compliance and security
We build to the rules public bodies are held to and document the controls, so you have evidence ready for auditors, oversight bodies and the public.
- ADA Title II: the Department of Justice web accessibility rule requires WCAG 2.1 AA, with deadlines of April 2027 or April 2028 depending on your size (as extended in 2026); we also build to Section 508 where it applies
- GovRAMP (formerly StateRAMP) and FedRAMP: we build on authorized services and prepare documentation and evidence; authorization decisions rest with each program
- Hosting: FedRAMP-authorized cloud regions such as AWS GovCloud or Azure Government, where your policy requires them
- Criminal Justice Information Services (CJIS) Security Policy for systems that handle criminal justice information
- Family Educational Rights and Privacy Act (FERPA) for student records, and state privacy and records retention laws
- AI governance aligned with the NIST AI Risk Management Framework and your state's AI policies
- Zero trust access: single sign-on, phishing-resistant multi-factor authentication and least-privilege permissions
How we work
Small, reviewable steps, with security, accessibility and evidence built in from the first sprint rather than added at the end.
- Discover: short workshops to map resident journeys, back-office steps and the policies that apply
- Blueprint: target design, integration list, controls, an accessibility plan and a release plan
- Build: phased releases, each tested with assistive technology, documented and reviewed with your staff
- Run: monitoring, maintenance and improvement after go-live, with evidence kept current for audits
Timeline
One model for every engagement. Dates are estimates we confirm after discovery, not promises.
- Discover: typically 1–2 weeks
- First working release: typically within 6–10 weeks
- Larger programs continue in phased releases; a full platform go-live is typically about 90 days
- After go-live: ongoing support and improvement, if you want it
Engagement options
Three ways to work with us, each with a clear scope and acceptance criteria that fit public procurement.
- Assess: a fixed-scope accessibility, security or architecture assessment, with a prioritized plan you can act on with or without us
- Build: a delivery program in phased releases, from a first online service to a multi-department rollout
- Run: ongoing support and improvement after go-live, including monitoring, maintenance and updates as systems and rules change
FAQs
Straight answers to the questions public bodies ask us most.
- When do the ADA Title II web accessibility deadlines apply?
- As of September 2026, the Department of Justice rule applies from April 26, 2027 for governments serving 50,000 people or more, and April 26, 2028 for smaller ones and special districts. Check ada.gov for the latest dates; we start with the pages and documents residents use most.
- Are you GovRAMP or FedRAMP authorized?
- Those authorizations apply to cloud products. We build your systems on authorized cloud services and help govtech companies prepare their own authorization packages.
- Do you work with small towns and nonprofits?
- Yes, with work sized to your budget and staff: a fixed-scope assessment, a focused first release, and systems your team can run afterward.
- How do you keep AI use accountable?
- We inventory each use case, assess its risk, keep staff approving decisions that affect residents and log what the AI did, so you can answer questions from your council, board or auditors.
- Can you work within our procurement process?
- Usually. A fixed-scope assessment often fits smaller purchasing thresholds, and later phases can go through your normal process with clear deliverables and acceptance criteria.
- How long does a first release take?
- Discovery typically takes 1–2 weeks, and a first working release typically follows within 6–10 weeks, depending on integrations and scope. We confirm the estimate after discovery.
See it at work
Insights
Related insights
Facing an accessibility deadline or a modernization project?
Tell us what you need to deliver and by when. We will give you a realistic plan that holds up to audits and public scrutiny.