Industries
Financial services and insurance
The work is the system your operators already use, not a claim that this practice is a financial-services firm.
Siebel is still the book of record for sales and service in parts of insurance and financial operations. A small internal team is often responsible for an instance that was configured by people who have left. The pain is specific: a quote that will not become an order, a case view users will not trust, an extract that billing has to repair by hand. A past Open UI performance review at PNC looked at browsers, network traffic, and the SQL behind slow views. It was a short engagement, and it is not a current role.
.NET usually sits beside that CRM. A portal, a review tool, a billing extract, a job that was supposed to be temporary in 2014. AI, when it belongs at all, is a draft or a sort on fields the team already stores — correspondence, intake, a first pass at a note — with a person still accountable for what goes out.
Typical project shapes
One operational path
Quote to order, claim to case, or the screen a service rep has stopped using. Named before any repository work starts.
The integration that “usually works”
The batch or web service that fails on the records everyone already knows about, and that nobody has time to read.
An upgrade with a Monday
A test list built from the paths the business cannot pause, not from a generic Siebel checklist.
Boundary
Higgs Software is not a broker, a carrier, or a compliance department. How a rule should be interpreted for your regulators stays with you. The consulting work is the system that has to carry that rule.
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.