Manifesto

We spent decades teaching machines to answer. Nobody taught companies to understand.

Databases, data warehouses, BI, cloud, artificial intelligence: every wave promised to democratise corporate data. Decades later, the people who decide still ask someone else. Technology got faster at answering and nothing changed for the person asking.

01

An answer is not the same as understanding.

An answer settles one specific doubt and expires along with it. Understanding is something else: recognising patterns, suspecting causes and applying what you learned to a situation that has not happened yet.

02

Every answer should improve the next question.

When the interaction ends in an isolated answer, almost nothing stays. When it shows the same subject from several angles, the person who asked walks away with repertoire — and the next question is born better.

03

Companies also need to learn continuously.

Organisations do not learn by storing information. They learn when more people can interpret their own numbers, share what they found and decide better next time.

04

Knowledge should not depend on a handful of specialists.

Analysts and data teams remain essential. But their biggest impact is not answering requests: it is building the structure that lets the rest of the company ask on its own.

Our mission

Build the layer that was missing between the data and the decision.

So that any professional — whatever their title or technical background — can explore the company’s data, see the relationships in it and use that in their own work, without asking anyone.

Our vision

Understanding as a capability spread across the whole organisation.

Companies where data is not locked inside a report, a tool or a department. Where people from different areas, countries and languages keep learning about the same business.

The principles that guide Luminy.

We are not trying to build a faster tool. We are trying to build one that leaves autonomy behind when the session ends.

Principle 01

Clarity before complexity

Technology should shorten the distance between the person and the decision, not add one more layer of difficulty to cross.

Principle 02

Exploration before conclusion

A good analysis does not hand over an answer and close. It opens angles and lets the hypothesis be tested by whoever had the hypothesis.

Principle 03

Learning before dependency

Our job is to hold your hand at the start and become less and less necessary after that. Software that creates dependency solved the wrong problem.

Principle 04

Meaning before technology

Databases, models, charts and AI are means. None of them is the product. The product is a person understanding their own business better.

The journey

It started as a way of asking. It became a category.

Luminy was born from a problem that repeated at every company we visited: the data kept growing, and understanding stayed concentrated in the same few people.

The origin

Ask in plain language, get a chart

The platform started by solving access: anyone could ask in their own words and get a visual answer.

The discovery

The questions changed on their own

With use, people stopped asking what happened and started asking why, where and what to do next.

The category

It was not BI. It was not AI.

We realised what we were building competed with neither: it was a layer above, dedicated to developing the person who asks.

What comes next

Companies, countries and partners

Now the work is building the ecosystem that takes this capability to organisations in other markets.

AI only answers questions. Luminy generates understanding. Understanding generates better questions. Better questions build better companies.
Answers expire. Understanding compounds.