I founded NextGen Consulting, Inc. in 2006. For most of those years the work was modernization: tax, licensing, regulatory and public-service systems for federal, state and local agencies. They were large programs with many stakeholders and long timelines, the kind where the technology is rarely the hard part.
The hard part is always the same: fragmented ownership, approvals that nobody is accountable for, and a plan that everyone agrees with and no one is executing. Programs rarely collapse. More often they stall while everyone involved is working hard.
What we build now is a response to that. NGOS is the system the firm runs itself on. It covers capture, proposal, staffing, compliance, and delivery, with AI drafting throughout and a human approving anything that matters. NEMS is the governance layer around it: controlled documents, maker-checker approval, risk, audit, corrective action.
The design principle is narrow and I'd defend it anywhere: critical approval rules should be enforced in the data model as well as in the application, with controlled privileges and schema changes. Code can be changed by a well-meaning engineer on a deadline. A constraint cannot. No one approves their own work. Nothing is released that wasn't cleared. Every action leaves a record of who took it.
We built it for ourselves before we offered it to anyone else. Five hundred-odd controlled documents and the whole of our own operation run on it. Doing it in that order is the only honest way I know to sell an operating discipline.