Skip to content
Higgs Software

Higgs Software Consulting · Harrisonburg, VA area

Siebel CRM, .NET, iOS, and practical AI for a defined project.

Higgs Software works with small IT teams on the systems they already run, and on iOS apps that have to ship. Jon Higgs has 20+ years in the work and takes the project: Siebel CRM, a .NET application, an iPhone or iPad app, or an AI workflow that has to fit the stack in front of you.

One principal. No helpdesk contract.hello@higgssoftware.com540-246-4877

Firm
Consulting LLC since about 2010
Place
Harrisonburg, VA area
Shape
One principal on the work
Scope
Projects, not a helpdesk

Named work is limited to what can be said accurately. Past client names are previous engagements, not current employers. This site does not borrow client logos, and it does not invent certifications, download counts, or result percentages.

Process

Assess, build, then stay through the handoff.

The sequence is short on purpose. A boutique project does not need a methodology diagram. It needs a scope, a change in the system, and someone who is still around when the first real user hits it.

  1. 01

    Assess

    Read the system and the constraint before writing a change. The output is a scope: what is in, what is out, and what done means for this project.

  2. 02

    Build

    Do the work — configuration, code, integration, or a narrow AI workflow against data you already keep. You see the change in the system, not only in a slide.

  3. 03

    Support

    Stay for the handoff and the questions that show up after go-live. This is project continuity with the same person. It is not a ticket queue, a monitoring contract, or overnight coverage.

Principal

Jon Higgs

Higgs Software Consulting, LLC

Jon has run this practice since about 2010. The work is project consulting for smaller IT teams: Siebel, .NET, iOS, and practical AI. You talk to the person doing the work. There is no associate bench on this site because there is not one to introduce.

About the practice

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.