Industries
Government-adjacent and regulated teams
Defined project work for teams with a real system and a thin bench. No clearances, vehicles, or past-performance library are claimed here.
The practice is based in the Harrisonburg, VA area. Past work has included Siebel Public Sector case management for the New York State Office of the Attorney General, from 2016 to May 2023, and earlier Siebel and SOA work for the Department of Homeland Security, from 2010 to 2013. Neither is a current role. The fit, when there is one, is a defined project: a Siebel or .NET system that predates the current team, a scope that can be written down, and a person on the client side who can say what done looks like.
Regulated does not only mean government. Insurers, benefits operations, and anyone whose records have a retention story have the same shape of problem. The system is important, the staff is small, and a helpdesk contract does not answer the question in front of them. Where an environment has to be rebuilt the same way twice, the project can include Ansible, Terraform, and a GitHub Actions or GitLab CI pipeline. That is a defined build, not a standing operations desk.
Typical project shapes
A written scope
What will be touched, what will not, and who accepts the result. Useful in any environment where a verbal “we’ll figure it out” becomes a finding later.
The system the last vendor left
Configuration and code that works until someone has to change it. The project is to make a change the current staff can live with.
A narrow assistant, if the records are ready
Drafting or sorting from data you are allowed to use. If the data cannot leave the building, that constraint is the start of the conversation, not a surprise in week six.
A repeatable environment
Ansible, Terraform, and GitHub Actions or GitLab CI when a regulated build cannot live on one laptop. The same Siebel or .NET environment, stood up again, with the steps written down.
Boundary
This site does not claim a clearance, a contract vehicle, a set-aside, or a past-performance volume. If a project requires any of those, say so in the first note. It is a fast way to learn whether the work fits.
If the system matters and the team is small, start with a conversation.
A paragraph on the system, the constraint, and the timing is enough. Jon reads these. There is no intake desk.