About
One principal. The person who does the work.
Higgs Software Consulting, LLC is a boutique practice. It has been Jon Higgs’s firm since 2010. The page is short because the firm is.
At a glance
- Firm
- Higgs Software Consulting, LLC
- Principal
- Jon Higgs
- Founded
- 2010
- Based
- Harrisonburg, VA area
- Phone
- 540-246-4877
- Experience
- 20+ years across Siebel, .NET, and iOS
- Study
- B.S., computer science, University of Georgia
- Work
- Siebel CRM, .NET applications, iOS development, AI consulting, build automation
- Not
- A helpdesk MSP, a staffing firm, or a license reseller
Jon Higgs
Jon is the principal. Clients talk to him about the project, and he is the person who does the consulting. There is no team chart on this site, and no stock photograph, because neither would be telling the truth.
The practice is based in the Harrisonburg, VA area. The work is not limited to a commute: it goes where the system is. What does not travel is a claim of a local badge, a clearance, or a contract vehicle. None of those are offered here.
Jon has 20+ years in this work, across Siebel CRM, .NET, and iOS. The practice uses that depth, and adds practical AI when the records are already there.Build automationis part of the same work when a release is the bottleneck: Ansible, Terraform, GitHub Actions, GitLab CI, automated environment builds, and repeatable deploys. A lot of firms still run Siebel or a line-of-business .NET system, and the useful AI projects are the ones that sit on top of those records instead of replacing them. iOS is the same kind of work on a phone: a defined app, shipped. The public example isCurio, an iPhone game Jon helped develop in 2012. That is one title, not a studio.
This biography stays short on purpose. It names the University of Georgia degree and does not turn the rest of a résumé into the page. Past employers, when they appear, are on the work index and are not current roles. If a procurement form needs a credential inventory, ask on the contact page. If the form needs a logo wall, this is the wrong firm.
How an engagement feels
A written scope
What is in, what is out, and what done means. Agreed before the interesting work starts, and updated when the system turns out to be different from the first description.
One person accountable
You are not introduced to a seller and then handed to a rotation. The principal who scoped the work stays on it.
A handoff, not a dependency
The internal admin or developer should be more able to run the system when the project ends. A ticket portal would do the opposite.
If you want to know whether the fit is real, write to Jon.
Include the system and the constraint. He will say if it is a project this practice should take.