Work
Verified mission outcomes.
As of January 2026. Challenge, intervention, and result, not a gallery of logos.
01 Civilian health
Replatform a public CMS before the ATO window closed
- Challenge
- A civilian health agency had to retire a legacy content system without interrupting public information services.
- Intervention
- We replatformed the CMS, mapped editorial workflows, and put accessibility checks in the publishing path.
- Measurable outcome
- Services stayed online through cutover. Authorization proceeded on schedule.
2.5M+ Lines of code migrated
02 Citizen services
Clear Section 508 so the service could ship
- Challenge
- Citizen-facing views failed accessibility review and could not enter production.
- Intervention
- We rebuilt the interface against WCAG AA, with keyboard paths, contrast, and assistive-tech testing in CI.
- Measurable outcome
- Audited views met Section 508 and WCAG AA before authorization.
100% Audited views compliant
03 Data interoperability
Unify siloed agency datasets for operators
- Challenge
- Teams queried incompatible sources by hand, delaying operational decisions.
- Intervention
- We stood up governed ingest, role-based retrieval, and a human review step before any generated output.
- Measurable outcome
- Operators query a single, permissioned index instead of five disconnected systems.
Real-time Governed retrieval
Extended record
Further outcomes across our teams, described without agency, system, or program detail. Full references are provided in proposal packages for eligible acquisitions.
- WF-OUT-2025-11 Defense and national security Delivered a service inside a controlled-environment boundary, with continuous authorization evidence produced by the pipeline. cATO
- WF-OUT-2026-02 Public health Consolidated eligibility and case data behind role-based retrieval for a population-scale service. 5 to 1 systems
- WF-OUT-2026-04 Education and research Rebuilt an institutional service against WCAG AA and cleared accessibility review before launch. WCAG AA
- WF-OUT-2026-05 Civilian government Migrated a legacy publishing system through the cutover window with no public downtime. 0 downtime
- WF-OUT-2026-07 Regulated commercial Applied the same DevSecOps control gates outside government, with a bill of materials on every build. SBOM
- WF-OUT-2026-08 Civilian government Instrumented a delivery pipeline so each change carries its own authorization evidence. Per-change
How we report outcomes
We report the result the program was accountable for: a service that stayed up, an authorization that held its date, an accessibility standard that cleared before launch. We do not report satisfaction scores, logo counts, or effort.
- Operational, not vanity. The metric is the thing the mission needed, stated in the program’s own terms.
- Attributable. Every figure traces to evidence the delivery system produced: pipeline records, audit results, cutover logs.
- Bounded. We describe what was measured and what was not. A pass on audited views is not a claim about every view.
- Non-identifying. Outcomes are described without exposing agencies, systems, or details that are not ours to publish.
Related reading: report the result the program was accountable for and cutover is a control. See our capabilities.
If the constraint is current, submit an RFI.