Frederic Laluyaux and the Decision That Wouldn’t Go Away

At 27, Frederic Laluyaux had to close a company in Paris. Its electronic data interchange technology had been overtaken by the internet. His father, usually sparing with words, wrote him a letter reminding him what he had accomplished. Years later, Laluyaux still had it. The business had failed; the letter helped him try again.

Today, he runs Aera Technology, which builds software to recommend and execute business decisions. Between those two points lies a career spent close to the machinery of corporate judgment: costing, analytics, financial planning, and the increasingly elaborate apparatus companies buy to help them decide. He has sold that apparatus, managed its integration, and questioned whether it was doing enough.

The recurring question is disarmingly ordinary. A company knows something has changed. Who decides what happens next? For Laluyaux, the answer has become a company, a product, and a long argument about the way people work.

Before the spreadsheets, a pair of turntables

He grew up in Paris with an early determination to reach the United States. In college, his first business involved music: DJ sets, lighting, and setting up stages. A technology internship took him to Milwaukee at 20. He founded his first tech company in Paris at 23. The path to enterprise software included rather more cables and dance music than the average executive biography admits.

He now lives in San Francisco, but the route ran through Atlanta. He moved there in 2002 with his wife, Elizabeth, to lead global operations for Armstrong Laing, known as ALG Software. His responsibilities had expanded from building the French business to running international operations. The work dealt with costs and performance, subjects that rarely inspire a crowded dance floor but do attract the attention of chief financial officers.

Business Objects acquired ALG in 2006. SAP subsequently acquired Business Objects, bringing Laluyaux into a much larger organization. He worked on integration and strategy before leading finance, performance, and risk management applications. Each step put him closer to the people responsible for making expensive decisions with imperfect information. He was learning the problem from inside the companies selling its proposed solutions.

The phone call after meeting Michael Gould

In March 2012, a recruiter suggested he meet Michael Gould, an Anaplan founder. Gould had worked on planning software at Adaytum; Laluyaux had spent years in financial performance management. Both knew what happened when software companies were absorbed into larger portfolios. Both were interested in what a new technical foundation might permit.

Laluyaux later recalled immediately calling his wife in Atlanta after meeting Gould. He could already see them working together. The company was small, with roughly 20 employees. By July, he had become CEO. Moving from SAP to Anaplan exchanged the reach of an established software group for the chance to build a business around a different approach to planning.

Anaplan’s proposition connected financial and operational planning through cloud software. The appeal was practical: finance, sales, and operations could work with related models instead of treating each department’s plans as a separate universe. Laluyaux’s job was to turn that proposition into an organization able to serve large customers across countries.

He argued for going international early. In 2015, he described building culture, hiring people who fitted the pace, and introducing processes before disorder became permanent. He accepted some startup chaos, but wanted enough structure to support corporate buyers. That is a revealing combination: urgency about the market, almost unfashionable seriousness about the plumbing.

His Anaplan tenure ended in April 2016, before the company’s public listing. During his leadership, the business grew from about 20 to 650 employees and reached a valuation above $1 billion. The scale matters, but so does the ending. A successful chapter can close while the question that brought someone into it remains unfinished.

The argument he carried out of SAP

Laluyaux dates a written version of his decision-making thesis to 2010, while he was at SAP. He saw three pressures building together: more decisions, greater complexity, and less time to respond. Better planning tools could help people understand a business. He wanted to address what happened when the required volume of decisions exceeded their capacity to keep up.

The frustration became sharper. By 2018, he was publicly criticizing the cycle of giving customers more data and another set of tools, then leaving them to work out the answer. Improvements to familiar software could arrive regularly without changing that basic arrangement. He had spent enough time inside the industry to recognize its habits, including the habit of calling another incremental release a transformation.

With Shariq Mansoor, Aera’s co-founder and technology chief, he pursued a different arrangement. Aera launched in 2017, following the business previously known as FusionOps. The aim was to bring together operational data, decision logic, execution, and feedback. A recommendation would have somewhere to go after appearing on a screen.

He had a concrete example of the frustration: large businesses could struggle to answer when an order would be delivered despite decades of investment in enterprise systems. Separate systems held different pieces of the answer. Joining them was a prerequisite for useful action. A conversational interface might make the question easier to ask; it would still need a dependable account of the business underneath.

A decision needs a memory

Consider an inventory transfer, one of the recurring decisions Aera addresses. There is stock in one location and demand in another. Moving it affects transport costs, service, available capacity, and the needs of other customers. A useful system has to weigh those constraints, obtain the necessary permission, and make the change in the relevant operational system.

The next step is essential to Laluyaux’s argument: preserve what happened. Which information informed the choice? What was recommended? What action followed? What result came back? A record of transactions tells a company what moved. A record of decisions can help it understand why, and whether its reasoning deserves to be repeated.

He has made this organizational memory a recurring theme in recent conversations. Employees carry practical knowledge that can disappear into meetings, individual recollections, or disconnected workflows. Capturing the context of decisions is Aera’s proposed way of keeping that experience available as the business changes. The ambition extends beyond answering today’s question to improving the next answer.

Trust develops less automatically. In an early Unilever deployment, only about 20 to 30 percent of recommendations initially received human approval, according to Laluyaux’s account in 2024. Acceptance improved as the system learned what people approved. He compares the process to a manager learning to trust another person’s judgment: the underlying data and logic must survive examination.

That puts a distinctly human obstacle in the middle of his automation project. People responsible for an outcome need reasons to delegate. A recommendation must be understandable, and the permission to execute it must have limits. The self-driving enterprise, as he describes it, still has people setting objectives and governing the decisions made in their name.

Direct, open, and without a door

Asked to describe his leadership, Laluyaux chose “Direct and open.” He said he sat among colleagues and had no office door to open. He also valued humor. It is a compact management philosophy: be accessible, deal with problems plainly, and leave room for a joke.

His public work has gradually become part explanation, part demonstration. He interviews operators about decisions inside their businesses, including supply-chain leader Reyes Garcia Mota at Coca-Cola Southwest Beverages. The subjects are stockouts, spreadsheets, and how teams coordinate. These discussions keep the larger argument attached to recognizable work. There is an actual shelf somewhere at the end of the software.

He is also arguing for different jobs. In his account, decision analysts monitor outcomes and refine logic; decision architects define objectives and constraints. People would spend less time carrying out individual routine choices and more time shaping the system that makes them. That remains a proposed direction for work, with the details depending on what organizations automate and how they manage it.

“I like to believe that my proudest moment is ahead of me.”

Frederic Laluyaux, 2018

The question now has a market

In 2026, Aera was named a Leader in Gartner’s first Magic Quadrant for Decision Intelligence Platforms. Laluyaux described the category’s recognition as a personally meaningful milestone. After years of explaining why decisions deserved their own software layer, the industry had given that layer an established place in its buying conversation.

Accenture Ventures invested in Aera in May 2026, with financial terms undisclosed. The companies announced a partnership to bring decision intelligence into complex supply chains. Hershey was already using support from both businesses for AI-enabled supply-chain decisions. For Laluyaux, the commercial test is increasingly about expanding the approach through operating organizations, beyond a persuasive presentation.

His September 2026 Interlinks conversation returned to the organizational consequences: knowledge held by employees, coordination between departments, changing skills, and the role of a decision architect. AeraHUB 26 is scheduled for October 27 and 28 in New York. The event provides another venue for customers and practitioners to compare experience with the promises.

The early letter from his father survives in the story for a reason. Laluyaux has experienced technology changing the rules faster than a company could adapt. Now he is trying to build systems that help other businesses notice, decide, and respond sooner. Whether that ambition works is tested in repeated operational choices, where a late answer can be as troublesome as a wrong one.

He keeps returning to the interval between knowing and doing. It has taken him through planning models, acquisitions, a startup’s expansion, and another company’s launch. The question has acquired new language over the years. The human predicament is familiar: we have the information, the meeting is underway, and someone still has to make the call.