Industry IT services: eight sectors, eight sets of constraints

Most technology providers segment by headcount. A fifty-person business gets the fifty-person package. In practice, two businesses of the same size can have almost nothing in common technically, because two things dominate every decision and neither tracks with size.

The first is the cost of an hour. For a medical practice, an hour of downtime during clinic hours means appointments that have to be rescheduled and patients who were already in the waiting room. For a manufacturer mid-run, it can mean scrapped material. For a retailer on a Saturday in December, it is revenue that does not come back. These are not the same problem wearing different clothes. They demand different redundancy, different maintenance windows, and different response commitments.

The second is who audits you.Some sectors answer to a federal framework, some to an insurer, some to their largest customer's security questionnaire, and some to nobody until something goes wrong. That determines how much of the work is documentation rather than configuration, and documentation is the part most providers underestimate.

Everything else, including the ten services we deliver, is constant. These two variables decide how they get delivered.

Our deepest specialism, and the sector our processes are built around. Protected health information sets the floor: who can reach it, how you would know if someone reached it who should not have, and whether you can show an auditor your work. HIPAA asks for evidence, not for products.

The operational constraint is clinic hours. Maintenance that a normal business schedules on a Wednesday afternoon has to happen around a patient schedule, and an EHR that cannot talk to the imaging system is a daily tax on staff time rather than an IT ticket. We also run practice buildouts, which means for new practices we are involved before the floorplan is final, the stage where most of the expensive mistakes get made.

Read more about our healthcare IT services →

The defining problem is that the plant floor and the office network were never designed as one thing. Machines run controllers with operating systems that went unsupported years ago and cannot simply be patched, because the vendor certified the machine against that exact configuration. Segmentation is not a best practice here; it is the only way both halves can coexist safely.

Downtime is measured against the run, not the day. That changes when work can happen, often a planned shutdown weeks out rather than an evening, and it means the maintenance plan has to be built around the production calendar.

Dealerships and service operations run on a dealer management system that everything else has to integrate with, and the integration surface is rarely as open as the vendor's sales deck suggests. Multi-site groups add the second problem: each rooftop has usually grown its own setup, and consolidating them without interrupting sales or service is the actual project.

Customer financial data raises the stakes. A dealership holds credit applications and identity documents, which makes it a target disproportionate to its size. Service bay uptime is the operational constraint; a bay that cannot pull a work order is a technician standing still.

Point of sale uptime at peak, and nothing else comes close. The traffic pattern is the constraint: a system sized for a Tuesday will fail on the day that matters, and the days that matter are known in advance, which makes capacity a planning problem rather than a monitoring one.

Card data narrows the options. Anything that touches payment brings scope with it, and the cheapest way to handle that scope is usually to shrink it: keeping card data out of systems that do not need to see it, rather than hardening every system that accidentally does.

Two networks that must never be the same network: the business systems, and the operational technology that controls physical infrastructure. Keeping those properly separated while still getting data out of the operational side for reporting is the central design problem.

The work is also field work. Crews need systems that function with intermittent connectivity and on equipment that lives in a truck. And outage response means the systems used to coordinate a response must be the most resilient things you own, because they are needed exactly when everything else is failing.

Sites are remote, conditions are hard on equipment, and the connectivity you would assume exists often does not. A design that works in an office park does not survive a facility where the nearest fiber is miles away and the control room cannot lose visibility.

Safety systems sit apart from everything else and stay that way. Alongside that, the record-keeping burden is heavy and continuous: environmental and operational records that have to be retained, retrievable and intact. That pushes a lot of the work toward data integrity and retention rather than toward endpoints.

Booking and dispatch are real-time, and the cost of downtime is immediate and visible to customers. A booking system that is down is not a backlog; it is lost bookings and a public complaint. Redundancy here is not optional infrastructure. It is the product.

The second constraint is that a meaningful part of the operation is moving. Vehicles, crews and depots need systems that degrade gracefully when the connection drops and reconcile cleanly when it returns, which is a design decision rather than a configuration one.

File sizes break the assumptions most networks are built on. Moving footage and finished assets between editors, storage and clients needs bandwidth and storage designed for the throughput, not for the headcount. The moment it is too slow, people route around it with consumer tools and the organization loses track of its own assets.

Deadlines do not move. A broadcast slot or a release date is fixed, so the maintenance window is whatever the schedule leaves, and the recovery plan is judged by whether you still make the date.

The ten services are identical in every sector. These two columns are what we scope differently.

These eight are where we have the most depth, not the limit of what we do. The two questions above, what an hour costs you and who audits you, are answerable for any business, and they are the first two questions we ask.

If your sector is not here, that mostly means we would spend the first conversation learning your constraints rather than arriving with them. Tell us what you run and we will be straight about whether we are the right fit.