The World Runs on Companies You Have Never Heard Of

I keep finding myself drawn to industries that sound almost aggressively uninteresting at first.

Commercial laundry. Elevator inspection. Medical sterilization. Undersea cable repair. Industrial gases. Funeral logistics. Wastewater monitoring. Building façade inspection. Ship classification. Cold-chain compliance. The systems that track where cooking oil goes after it leaves a restaurant.

None of these are the kinds of things people usually bring up when they talk about innovation. They do not appear in keynote montages. They rarely have charismatic founders explaining how they are changing the world. Their websites often look old, their software looks worse, and the people working inside them are usually too busy keeping something operational to perform technological excitement for outsiders.

And yet these are often the industries where the world is actually being held together.

We spend a lot of time looking at the visible layer of modern life. The app used to order the food. The brand printed on the package. The electric vehicle. The AI assistant. The smooth consumer interface through which everything appears to happen instantly.

Underneath that is a much stranger system.

Someone inspects the ventilation system in the restaurant. Someone certifies the lift carrying ingredients between floors. Someone checks the refrigeration records. Someone maintains the grease trap. Someone collects the used oil. Someone audits the fire suppression system. Someone calibrates the thermometer. Someone transports the waste. Someone verifies that the company transporting it is licensed to do so.

The polished interface is often only the final centimetre of a process extending through warehouses, regulations, vehicles, forms, sensors, phone calls, spreadsheets, institutional memory and people who know what a strange noise means before any system has registered an error.

This may be why I find another beautifully designed productivity app increasingly difficult to care about.

It is not that the app cannot be useful. It is that many of these products seem to exist in a world where nothing is wet, heavy, contaminated, late, mislabelled, legally ambiguous or physically stuck somewhere it should not be. They are designed for clean objects moving through clean states. A lead becomes qualified. A task becomes completed. A document becomes approved.

Real operational systems do not behave like that.

A shipment arrives, but one pallet is damaged. The temperature log has a gap. The person authorized to accept it is absent. The replacement part has the same product code but a different certification. The customer entered the address incorrectly. The building has been renovated since the drawings were made. The sensor is working, but positioned badly. The software says the inspection is complete, while the inspector knows the reading makes no sense.

The interesting part is rarely the normal flow. It is the accumulation of exceptions around it.

This is also why old industrial software can be so difficult to replace. From the outside, it looks obviously bad. Tiny text. Dense tables. Strange abbreviations. Too many fields. Buttons placed in ways no contemporary product designer would defend.

But sometimes the ugliness is carrying information.

An experienced dispatcher can scan a screen that appears incomprehensible to everyone else and notice that three numbers do not belong together. A technician may rely on an awkward sequence because it forces a second check before something dangerous happens. A field that seems redundant may exist because ten years ago two organizations merged and still use different classifications.

The interface is not simply a visual layer. It is a fossil record of the institution.

This does not mean it should never be redesigned. It means the redesign requires more humility than most design work allows.

You cannot enter a system like this, interview five people, simplify the navigation and announce that you have reduced complexity. Sometimes you have only removed the visible evidence of complexity while leaving the underlying situation untouched. The user now sees fewer fields, but must make more phone calls. The workflow has fewer steps, but errors become harder to detect. The screen looks calmer, while the person using it has become less certain.

There is a particular kind of damage caused by making a complicated system look simpler than it is.

I have started thinking that many neglected industries do not suffer from a lack of technology. They suffer from badly distributed understanding.

The field worker understands the equipment but not why a form is required. The administrator understands the form but not what happens on site. The regulator understands the rule but not how the software interprets it. The customer sees a status label without knowing what it means. Management sees a dashboard built from data that has already lost its connection to reality.

Each part may work reasonably well on its own. The failure happens between them.

This is where interaction design becomes much more interesting to me than interface design. The real material is not the screen. It is the relationship between people, machines, rules, timing, responsibility and evidence.

Who is allowed to make a decision? What happens when they are unavailable? Which mistake is reversible? Which one is dangerous? What needs to be recorded? What only needs to be understood? Where does trust come from? When does a person override the system? How can the next person tell whether that override was justified?

These questions exist everywhere, but obscure industries make them impossible to avoid.

A music app can survive a confusing recommendation. An elevator inspection system cannot casually lose the distinction between “checked,” “passed” and “temporarily accepted under a specific condition.” A social app can redesign its interface every few months. A hospital sterilization workflow cannot move things around simply because the new version feels more modern.

The constraints are not inconveniences around the design. They are the design.

This may also be why these sectors are often described as business opportunities. People notice fragmented markets, old software, regulatory pressure, aging workforces and low digital maturity, then call them blue oceans.

Sometimes they probably are.

But the phrase makes me slightly uncomfortable because it encourages the fantasy that obscurity means emptiness. Usually the space is not empty at all. It is crowded with small companies, local knowledge, procurement relationships, informal workarounds, certification bodies, regional standards and people who have spent decades learning why the obvious solution does not work.

The absence of a famous software platform does not mean nobody has solved the problem. It may mean the problem has been solved in hundreds of partial, local and incompatible ways.

That is much harder, but also more interesting.

The opportunity is not necessarily to arrive with a universal platform and replace everything. It may be to understand one narrow system well enough to connect the parts that currently misunderstand each other.

A better inspection record that works in gloves and poor connectivity. A customer portal that explains uncertainty instead of hiding it. A scheduling tool that accounts for travel time, equipment, certification and site access rather than treating workers as movable calendar blocks. A handover process that preserves the reasoning behind an exception. A public-facing status that tells the truth without exposing internal chaos.

These are not dramatic inventions. They are improvements in how reality is represented.

I suspect this is close to what I want HAAM to become.

Not a studio that arrives after everything important has been decided and makes the interface nicer. Not another agency promising digital transformation before understanding what is being transformed. More like a practice for entering systems that have become difficult to see as wholes.

The kind of work where design, technology and operations cannot be separated cleanly because the problem lives in the gaps between them.

There is probably less glamour in this than building the next consumer AI product. The sales cycles are slower. The terminology is harder. The software may need to work on old hardware in a warehouse rather than look impressive in a portfolio. Success may mean fewer mistakes, shorter phone calls, clearer responsibility or one less moment where a worker has to guess.

It is also possible that some of these industries do not want to be redesigned.

They may have survived precisely because they were ignored by hype. Their systems may be clumsy but stable. Their customers may value continuity more than novelty. The people inside them may have watched several consultants arrive, misunderstand everything and leave behind another layer of software.

That resistance deserves to be taken seriously.

Still, I cannot stop looking at these systems.

The world presented through technology is increasingly smooth, immediate and abstract. The world underneath remains physical, conditional and maintained by people whose work only becomes visible when it fails.

Maybe that is the attraction.

Not that obscure industries are strange, but that they reveal how much ordinary life depends on things we have trained ourselves not to notice.

Connected reading

• The Interface as an Archaeological Site
• I Want to Work Somewhere the Work Is Already Necessary
• The System Around the Medical Model
• Digital Product Assurance

AI authorship note

This essay grew from Kris Haamer noticing a recurring fascination with obscure industries and the hidden systems behind ordinary life. AI supported structuring, drafting, editing, and implementation. Kris selected the examples, connected the argument to interaction design and HAAM, and approved the final essay for publication.