Jean-Hervé Jenn and the price of a better question

In 2012, Jean-Hervé Jenn had a fairly persuasive answer to the question of why a shipping company should care about better software: look at the fuel bill. A buying decision made when fuel cost $200 looked rather different when the price reached $700. The ship still needed feeding. The room for being casual about it had become considerably smaller.

Jenn was talking about information that could help buyers compare ports and follow price movements. Shipping companies had expensive physical assets to run; he was offering a way to make the decisions around them less cumbersome. His explanation had the appeal of a calculation scribbled on the back of an envelope. Software could justify itself through the cost of the problem it helped solve.

The former Inatech chief executive’s career stretches across civil engineering, consulting, banking, outsourced services and energy software. Across those settings, his public comments repeatedly touch the same difficulty: businesses accumulate information, then struggle to put it to work. A customer conversation, a development brief and a fuel purchase can all contain something valuable that an organisation fails to use.

The arithmetic of paying attention

By the time Jenn became Inatech CEO in April 2012, he had already spent years in businesses organised around complicated client relationships. Inatech would give that experience a particular setting: the fuel buyer, the oil trader and the people responsible for keeping their operations connected.

Cloud delivery was part of the proposition from the beginning of his public fuel-software pitch. A mid-sized shipping company might want better information without wanting to become the proprietor of a substantial IT operation. Subscription software offered a way to buy access while leaving administration with the supplier. The commercial question included who would maintain the machinery behind the screen.

“now that it’s $700 it does matter”Jean-Hervé Jenn, discussing fuel prices in 2012

There is something pleasingly unromantic about this entry into a technology story. The appeal rests on a buyer’s working day and an expense that demands attention. The cloud can sound airy. A bunker fuel invoice brings the conversation firmly back to earth.

Before the fuel desk, the customer

Jenn studied civil engineering at the École Spéciale des Travaux Publics in Paris, took a management master’s at UCLA and completed INSEAD’s Executive Management Programme. His professional background includes IBM, Gemini Consulting, KPMG and Goldman Sachs. The combination put technical work, professional services and commercial management on the same résumé before his energy-software chapter.

At Convergys, his responsibilities widened through a sequence of international jobs. He was president for EMEA from 2003 to 2007, then president of Information Management International in 2007 and 2008. In January 2009 he became executive vice president for global information-management market and client development. The titles are a mouthful; the progression places him repeatedly between a service organisation and its markets.

International work also involved a considerable amount of movement. In December 2006, he was travelling to India every two months while discussing Convergys’s operations and a prospective mobile-billing order. Behind the broad geographical responsibilities sat the familiar problems of delivering services, retaining people and meeting clients’ requirements.

In March 2010, Jenn became chairman of Teleperformance France. That year he spoke about valuable information collected through customer-service operations that companies were failing to exploit. He pointed to the experience of advisers and criticised a preoccupation with cost savings among some clients. The observation gives his later software work a useful antecedent: information could be present in abundance and still fail to influence a decision.

Former Teleperformance colleague Anne Rebulet later recalled a meeting with Jenn that took an unexpected turn. It had been arranged to sign a confidentiality agreement connected with a tender response. It became an internal job interview. The episode adds a less formal moment to the sequence of corporate appointments: a meeting intended for paperwork became a conversation about a person’s next role. A change in the agenda could carry rather more consequence than the document that brought them together.

Five developers and a lot of questions

One of the more revealing episodes arrived in 2018, when Inatech added five developers in Bucharest. They would work alongside its established development operation in Chennai. Jenn explained the expansion partly as a way to broaden the talent pool and allow ideas to travel between locations.

Then he offered a more memorable detail. The Bucharest specialists liked to think through an assignment before coding. There would be questions. Quite a few questions. Enough, in his telling, to try the patience of the person supplying the brief. He regarded the interrogation as useful because it helped produce the product the business actually needed.

It is an unusually human description of software development. The impatient commissioner and the persistent engineer are recognisable figures. In Jenn’s account, the delay at the beginning had a purpose. Understanding the request was part of delivering it. A brisk start could be less valuable than an awkward conversation that exposed an assumption.

His public recommendation of product leader Rowena Bataille offers a related clue about what he valued in colleagues. He credited her with bringing commodity traders’ and operators’ user experience into the centre of Inatech’s development process, and with building a product-design team that worked closely with product management.

Read beside the Bucharest anecdote, that endorsement makes the working relationship around the software visible. Developers needed to understand the problem. Designers needed to understand the people using the system. A chief executive could praise both without pretending to have written every line himself.

A terminal is a demanding customer

In September 2018, Petro-Diamond, Mitsubishi’s oil-trading business, appointed Inatech to digitise its gasoline supply chain. The customer operated a 600,000-barrel terminal at the Port of Long Beach in California. This was a brief with storage tanks attached.

Inatech adapted Techoil to the requirements of wholesale distribution and rack marketing. Planning, contracts, scheduling, pricing and settlement needed to connect. Prices moved during the day, and the software had to support decisions involving sourcing, inventory and risk. The details explain why understanding the customer’s business mattered as much as presenting a list of features.

Jenn welcomed the scrutiny Petro-Diamond had applied to the work. He also described the project as opening a new market segment. There is a practical commercial logic here: a demanding customer can help shape a product for other businesses with similar problems. The scrutiny is part of the opportunity, even when it makes the assignment harder.

A later deployment at Emad Energy supplied a different test. Inatech installed Techoil remotely in under four weeks, bringing the trading company’s activities onto one platform. Jenn described the system as sitting at the centre of operations and planning. Delivery had become another part of the product’s value: how a system reaches its users affects how useful the promise becomes.

Growth, risk and a change of owner

By early 2022, Inatech’s work extended across shipping procurement, fuel trading and US wholesale markets. The company had grown by around 25 percent in 2021. Jenn nevertheless described that year as disappointing compared with 2020, while reporting a stronger start to 2022. The comparison says something about the benchmark behind a growth figure: a respectable number can look different beside the previous year.

He was also discussing investment in renewables, including work with clients in California. The energy market around the software was changing, and Inatech was looking beyond its established hydrocarbon and bunker-fuel base.

In March 2022, a partnership with cQuant.io added another strand. The integration brought advanced risk analytics into Techoil, including scenario analysis, stress testing and value-at-risk models. Jenn linked the need for better decision support to new fuels, more data and greater trading complexity. Recording a transaction was one task. Helping managers understand the exposure around it was another.

That June, Valsoft announced its acquisition of Inatech from Glencore, buying all the outstanding shares. Inatech had more than 30 clients in hydrocarbon and marine fuel markets. The buyer saw the business as an entry into energy trading and risk-management software, with scope for a broader portfolio.

Jenn’s stated ambition at the time was to widen the energy offering as customers adapted to alternative fuels. He also stressed continuity. In his discussion of the sale, Glencore’s concern for the business’s stability and longevity featured prominently; many customers were counterparties of the seller. Both Jenn and Fred Bendle had signed three-year contracts as part of the transaction. An ownership change still had to accommodate people relying on the existing systems.

The question travels

In May 2024, Jenn became a director of Future Analytica Ltd. The appointment adds a new company to a career already spanning several kinds of technology and services business. Inatech, meanwhile, has moved through its own leadership changes: Floris Bos became CEO in August 2025, succeeding Fred Bendle.

There is a lighter note in Jenn’s public life, too. On LinkedIn, he announced becoming a grandfather and added an affectionate joke about the baby’s capacity to scream. Even a career spent improving the use of information leaves room for a small person who communicates very effectively without a dashboard.

The useful thread through Jenn’s working life is the attention he gives to the moment before a decision: the adviser’s knowledge, the developer’s questions, the trader’s requirements, the buyer’s calculation. Seen together, those episodes suggest a consistent professional concern. Before asking a system for an answer, spend some time deciding whether it understands the question.