1
Discovery & user research
We talk to citizens and agency staff. Most government software fails because the people who use it weren’t consulted.
Government software that treats citizens like users.
We build public-sector platforms with the user research, accessibility, and operational discipline citizens deserve, and the procurement and compliance posture agencies need.
What we do for the public sector.
In the public sector, engineering carries a civic responsibility. We build for state agencies, large city governments, and federal program contractors, with a procurement-aware engagement model and the operational maturity government needs. We’re not a prime federal contractor; we partner with primes and work directly with state and local agencies.
Where it helps most
State agencies
Modernization of citizen-facing services, internal tooling, and data platforms.
Large city & county governments
Permitting, licensing, citizen engagement, and operational analytics.
Federal sub-prime engagements
We work as a sub-prime to federal primes on relevant program work.
Public-sector adjacent
Universities, hospitals, transit authorities, and other public-mission organizations.
What we deliver.
Each item below is a concrete deliverable that we scope, build, and stay accountable for.
Citizen-facing platforms
Permitting, licensing, benefit applications, and public records, designed in plain language and fully accessible.
Identity & access
Login.gov integration, ID.me, state SSO, multi-factor authentication, and access policies for sensitive data.
AI for government
Document intelligence, case triage, and citizen-facing assistants, with careful evaluation and FOIA-aware logging.
Operational analytics
Performance dashboards, program outcome tracking, and the data work that supports evidence-based policymaking.
Section 508 / WCAG
WCAG 2.1 AA and Section 508 conformance with manual testing and disability-community feedback.
FedRAMP-aware cloud
FedRAMP Moderate-aligned cloud foundations, StateRAMP-relevant work, and the documentation rigor procurement requires.
How an engagement runs.
Five phases, each with outcomes we can measure.
Why work with us.
Accessibility is a release blocker
Section 508 and WCAG 2.1 AA conformance are not negotiable. We don’t ship features that don’t pass.
Citizens are the users
Our discovery starts with citizens, not agency org charts. The result is software citizens actually use.
Procurement-aware engagements
We’ve operated under T&M, fixed-price, and IDIQ contracting. We adapt to the contracting vehicle, not the other way around.
Frequently asked questions.
Still unsure? A 30-minute call with a tech lead answers the rest.
Ask us directlyAre you a federal prime?
No. We sub-prime through federal partners and work directly with state and local agencies. For federal direct contracting we partner rather than compete.
Do you have FedRAMP authorization?
We’ve built and operated FedRAMP Moderate-aligned platforms, but we’re not a FedRAMP-authorized SaaS vendor. We’re a services partner that builds within authorized environments.
Do you support 18F-style discovery sprints?
Yes. We run user-centered discovery sprints aligned with USDS / 18F practices, and we’ve worked as a subcontractor to teams that do this work.
How do you handle FOIA?
Audit logging, retention policies, and access patterns are designed with FOIA in mind from sprint zero.
What about state-specific procurement?
We’ve worked through state-specific procurement vehicles in CA, TX, NC, NY, and several others. Procurement is a learned skill, and we’ve learned it.
Let’s talk about your project.
Tell us about your team, your stack and the problem you want solved. We’ll come back with how we would approach it.
Response time
Within one business day
Prefer a call?
Headquarters
Charlotte, North Carolina
Thank you. Your message has reached our team.
A member of our team will reply, usually within one business day. Your reference is .