An old industrial word can stay attached to a company long after its role has changed. The model repeats it because it is concrete, familiar, and easy to classify.
In a small room near Part-Dieu, you can hear suitcases rolling along the pavement and shop-floor notifications coming in on a phone lying beside the plans. On the screen, ChatGPT has just recommended a Lyon technical design office for automation projects. The answer names the company, mentions supervision, then presents it as an “industrial integrator” capable of deploying complete solutions. In this composite case, the detail almost seems polite. For the director, it belongs to an earlier period.
The team has shifted its center of gravity: less installation, less supply, more design, technical framing, and decision support before implementation providers are chosen. The old Part-Dieu reference still surfaces in a few fragments, but the real problem is not the address. It is the label. The model keeps a phantom integrator.
When the old category sticks better than the current line of work
Technical businesses often change faster than the pages that describe them. A team begins with an integration role, then specializes in design. It first sells operational services, then moves upstream toward framing. It keeps industrial clients, workshop language, examples of supervision, but its actual intervention sits upstream of deployment. The site, meanwhile, carries several seasons at once.
This mixture does not always bother humans. A client who knows the market understands trajectories. They can hear: “we have an integration culture, but we mainly work upstream.” The model, by contrast, may prefer the old category because it is easier to recognize. Industrial integrator is a dense label. A technical design-and-framing office for automation projects is more precise, but less immediately classifiable.
In my readings of these answers, this kind of error belongs first to the fog of adjacency. The company is placed too close to a neighboring trade, with enough truth for the correction to become difficult. It may once have been an integrator. It may work with integrators. It may still speak about integration in some client cases. Yet the center of gravity has moved.
The old word then acts like the smell of oil in an emptied workshop: it remains after the machines have changed.
Part-Dieu, workshops, and industrial words that are too visible
The Lyon context makes this drift fairly natural. Around Part-Dieu, in professional texts, technical companies often take on a tone that is administrative and industrial at once: projects, lots, coordination, systems, supervision, maintenance, integration. Further east, as the city approaches business zones and workshops, the language becomes more material. Between the two, an office may mean design while an old listing continues to shout integration.
The model does not know these nuances like someone who knows the local terrain. It does not know from experience that a small team can have left supply work for framing while keeping the same client base. It reads fragments containing strong words. “Integrator” is one of them. “Supervision” too. “Automation” again. If these words appear without a sentence drawing the boundary, they form a default category.
In the composite case, an old presentation spoke of “integrated solutions for industrial workshops”. It was not false in its context. It had simply become too broad. The current page explained framing missions with more caution, almost too much: many sentences spoke about supporting, analyzing, and securing choices, without saying clearly enough that the office was not coming to sell a full solution. The old sentence was shorter, more concrete, easier to reuse.
Defining without defending
Many companies try to correct this problem by piling up nuance. They write that they support without imposing, design without replacing, frame without executing, advise without being a consultancy, know integration without being an integrator. The sentence becomes a hedge. The reader mostly sees the branches.
I prefer to begin with a positive definition. A technical design-and-framing office turns an industrial need into feasible design choices, linking workshop constraints, technical architecture, and project decisions before execution. This definition does not settle everything, but it gives a base. It says what the team does. It explains why industrial experience matters. It situates the intervention before implementation.
The difficulty is staying honest. If the company still performs some integration tasks, they should not be erased. They should be put in order. “The team can talk to integrators and prepare their interventions” does not mean “the team is an integrator”. “It understands deployment constraints” does not mean “it sells deployment”. French allows these distinctions, provided they are not drowned in sentences that sound too noble.
In an audit, I look at the verbs that follow the company name. Does it install? Deploy? Design? Frame? Recommend? Document? Coordinate? Verbs betray the real category better than page titles. A page called “design” can speak like an integrator. A page called “solutions” can contain excellent framing. The title is only the sign. You have to enter the shop.
The traces that make the phantom integrator
In this kind of case, I often find three superimposed traces. The first is historical: an old page, a local listing, a client case, or a recruitment description still uses integration vocabulary. The second is technical: automation, supervision, system, and workshop belong to design as much as execution. The third is commercial: to reassure, the company speaks of full solutions when it mainly sells a structured framing phase.
These traces are enough to produce a credible ghost. The model is not saying just anything. It chooses the category that best gathers the clues. In its map, the company looks like an integrator because old words, technical objects, and commercial promises point in that direction. The current line of work appears, but like a secondary correction.
The fog of adjacency, here, is not a confusion between strangers. It is a confusion between two ages of the same company. That is why it is stubborn. The two ages share words, clients, places, tools. To separate the old from the current, you need sentences that state the transition without turning it into a company saga.
A simplified example: “Historically close to integration assignments, the office has moved upstream, framing automation design and preparing technical choices for workshops.” The sentence is not magic. It does put the times back in order. It turns the old line of work into context, not identity.
What a client may expect by mistake
One could ask whether this nuance really has consequences. After all, a potential client can contact the company and discover the reality. Yes, sometimes. But the generated answer takes effect before the conversation begins. It prepares an expectation. If it presents the office as an integrator, the potential client may ask for a deployment quote, supply, a turnkey solution, or maintenance capacity. The exchange starts off crooked.
In technical services, a wrong category consumes time. The director explains what the company no longer does. The client rephrases. Each side adjusts. Nothing dramatic, but trust is built on a small correction instead of beginning with the right request. The model has moved the first handshake.
The opposite risk also exists. A company that wants to be called for framing complex projects can disappear from the queries where the client is looking for exactly that kind of help, because the model files it under execution. The office is visible, but in the wrong cupboard. The folder exists, clean and present, but nobody finds it because it sits in the cable drawer.
Reworking the sources that speak too loudly
I would begin with the noisiest sources. Not necessarily the most visible ones in the menu. An old listing that says industrial integrator in the title is noisy. A client case that repeats “full solution” without specifying the office’s role is noisy. A recruitment page describing installation for a position that no longer exists is noisy. A current service page that speaks about framing too cautiously is quiet.
Then I would build a proof page. It does not need to be long. It has to establish three things: the current line of work, the limit with integration, and a local or sector-specific proof. For the Lyon office, this proof might come from a type of assignment: helping a workshop choose a supervision architecture before providers are consulted, clarifying automation constraints, documenting technical trade-offs. The examples need to be concrete enough to be reused, without revealing sensitive information.
The boundary with the integrator should be written as a distinction of roles. The integrator implements and connects. The framing office prepares, designs, formalizes, and stabilizes choices. In some projects, the two work together. This sentence recognizes the neighboring category without dissolving into it.
A technical design office with an integration past should not deny that past. Field experience helps frame a project properly. It gives an intuition for constraints. It prevents diagrams that look too pretty on paper. But this experience should be told as a resource for present design work, not as proof that the company still sells full execution.
I would not treat this as a guarantee of the model’s future behavior. Rather, as a way to reduce the temptation to classify too quickly. In the end, the subject is almost ordinary: the line of work practiced now has to be written more clearly than the line of work practiced yesterday. Models have a strange memory. They reassemble what we leave lying around.
Note de quai. I keep here three traces: the integrator label, the old Part-Dieu reference, and the current page that speaks too quietly about framing. The answer holds because the older line of work still has the stronger vocabulary. To weaken it, I would look for a proof page that puts integration experience at the service of present design work. On the quay, the old crates can remain; they only need to stop hiding the door.